Bug 359121 - Volume when rebooting or logging in is set at max even though end user had turned it down before longing out.
Summary: Volume when rebooting or logging in is set at max even though end user had tu...
Status: REPORTED
Alias: None
Product: kmix
Classification: Applications
Component: KMix Panel Docking (other bugs)
Version First Reported In: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Christian Esken
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-08 05:20 UTC by djraptor29
Modified: 2021-03-10 00:16 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description djraptor29 2016-02-08 05:20:21 UTC 
Volume seems to have a mind of it's own. When I log off or shut down the computer the volume turns to max on next reboot. As long as I am logged in the volume stays the same where I have set it. But as soon as I log out or reboot without touching the volume wheel or volume notification it shoots right back up to max volume.

Reproducible: Always

Steps to Reproduce:
1. Logged Out Happened
2. Rebooted Happened
3.

Actual Results:  
Same thing Volume was at max

Expected Results:  
Should have remembered what the volume was last set at.

none
Comment 1 djraptor29 2016-02-09 01:39:03 UTC 
Also want to report that I am using a Toshiba Laptop and it seems that the problem is when there are any notification it pops the volume up to max. I also experienced the same issue when I unplugged the power cord and ran on battery. Of course I was able to turn the volume down with both the task bar method and the volume control on the laptop. In addition I did not have this problem with Kubuntu 15.10. So it maybe an issue with Opensuse 42.1 Leap 64Bit version.
Comment 2 Justin Zobel 2021-03-10 00:16:23 UTC 
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.