Description of problem: When selecting the alert sound ('Sound' settings) the new sound is played, but the old alert sound remains active till the user logs out and in again, then suddenly the new alert sound is active. Version-Release number of selected component (if applicable): gnome-control-center-3.3.90-1.mga2 How reproducible: always Steps to Reproduce: 1. open the sound settings (either click on the speaker icon or start gnome-control-center and select sound) 2. switch to the 'Sound Effects' tab and select a new 'alert sound' 3. open a terminal and press Backspace
Assignee: bugsquad => olavSource RPM: (none) => gnome-control-center
CC: (none) => djmarian4uSummary: Alert Sound change isn't applied until logout/login => alert Sound change isn't applied until logout/login
Could you attach your ~/.xsession-errors? Please review the file before attaching!
Created attachment 1734 [details] requested .xsession-errors (clean login) nothing was removed from the log and the sound was modified during the session.
Whiteboard: (none) => NEEDHELP
just verified, issue still present with latest cauldron. gnome-shell-3.3.92-2.mga2
CC: (none) => herbert
(In reply to comment #3) > just verified, issue still present with latest cauldron. > gnome-shell-3.3.92-2.mga2 cc'ing some committers of this package because of the "NEEDHELP" on the whiteboard.
CC: (none) => cjw, dmorganec, fundawang, jani.valimaa, marja11
update, with the most recent Cauldron, the system sound cannot be enabled at all, i.e. you can test/hear it in the 'Sound' settings, but it isn't applied to the currently running session and it doesn't get applied/active after a logout either.
Summary: alert Sound change isn't applied until logout/login => Alert Sound change in Gnome control center isn't applied, but testing it works
CC: jani.valimaa => (none)
Hi, This bug was filed against cauldron, but we do not have cauldron at the moment. Please report whether this bug is still valid for Mageia 2. Thanks :) Cheers, marja
Keywords: (none) => NEEDINFO
Please look at the bottom of this mail to see whether you're the assignee of this bug, if you don't already know whether you are. If you're the assignee: We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead. If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard. Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why. Thanks :) **************************** @ the reporter and persons in the cc of this bug: If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us. @ the reporter of this bug If you didn't reply yet to a request for more information, please do so within two weeks from now. Thanks all :-D
Closing as old, there has been no feedback in over 1½ year. Feel free to reopen if needed
Status: NEW => RESOLVEDResolution: (none) => OLD