After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 333444 - volume level is not restored for individual users
volume level is not restored for individual users
Status: RESOLVED OBSOLETE
Product: gnome-applets
Classification: Other
Component: mixer
2.13.x
Other All
: Normal normal
: ---
Assigned To: gnome-applets Maintainers
gnome-applets Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-03-05 06:03 UTC by ed_ong
Modified: 2015-09-26 04:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description ed_ong 2006-03-05 06:03:27 UTC
Please describe the problem:
when multiple user login to a system, the initial volume level for a user is set
to that of the previous user that logged in.

Steps to reproduce:
1. login as A, set the volume level to 50%, logout
2. login as B, set the volume level to 90%, logout
3. login as A, check the volume level


Actual results:
volume level for A is 90%

Expected results:
should be 50%

Does this happen every time?
yes

Other information:
Comment 1 Ronald Bultje 2006-06-15 21:28:44 UTC
Isnit volume a system thing? I'd hate to see stuff like this going into gconf, it's broken by concept...
Comment 2 Danielle Madeley 2006-06-16 11:45:19 UTC
Yeah. It feels like a system thing to me. How do you deal with the simultaneous multiuser case if you wanted to do something like this.

If you wanted to have a feature where your volumes were preserved per user, you could do this with alsactl and adding some parts to your X session.
Comment 3 ed_ong 2006-06-19 12:40:03 UTC
(In reply to comment #2)
> Yeah. It feels like a system thing to me. How do you deal with the simultaneous
> multiuser case if you wanted to do something like this.
> 
> If you wanted to have a feature where your volumes were preserved per user, you
> could do this with alsactl and adding some parts to your X session.
> 


Yes, i guess using the X session is a useful course to take. 

Even in that case, the multiuser case would still be an issue. I guess any volume control would need to be triggered when a user switches VT. Looks like it is more involved than what i had originally thought.

BTW, I only filed the report bcos my ears were nearly blown off :)