my system had logon/logoff audio notivication set to on update changed that to off w/o notice or offering choice Reproducible: Always Steps to Reproduce: 1.update installed system 2. 3. Actual Results: logon/logoff sounds were not active Expected Results: no change to existent choices see discussion in opensuse-kde mail list, thread: can system sounds work by default (or be customized) without pulseaudio installed?
You are no longer able to activate the logout sound? Note that changing defaults is no bug, we do this all the time at several places.
Mailing list thread referred to in comment 0: http://lists.opensuse.org/opensuse-kde/2013-10/msg00023.html This particular change in defaults is inane. Default to sound at login on means one is on notice: 1-sound system is properly configured 2-login has completed 3-speakers are turned on 4-volume is or is not set appropriately Sound on at login by default is one of the relatively few sane things Windows does (or at least did through XP - did newer versions change this?), and users migrating from Windows to Linux expect. For those who never needed to fiddle with system sound settings, figuring out how in KDE settings is no small feat either. One needs to figure out the required setting is accessible only after a select list's default is changed, then somehow has to figure out which of the alternatives holds the magic, then once that has been figured out, find among an unsorted list of titles which it is that needs to be changed.
For a discussion why they have been disabled by default, please read http://lists.kde.org/?t=136821407300002&r=1&w=2 especially Aaron's first and last reply. If you want to add to the discussion, please use the mailing list, not this bug tracker. The information that is needed is whether the reporter is able to re-enable the sounds via System Settings.
Yes, I can "re-enable" logon/logoff sound. The point is I had logon/logoff sound enabled and an upgrade deactivated that configuration. I have sense re-enabled the audio notice. An "upgrade/update" should not change the status. Only on a new installation or installation of something not previously installed (not an update/upgrade) should a *default* setting be imposed on a system. I nowhere implied that I could not make the setting or that I had a problem with the decided *default*. My default is what I have configured or accepted as installed. From then on reguardless of *any* decision to make a setting "default". my settings should not be changed, especially w/o any notice.
I justed tested this in a VM using default KDE 4.10 from openSUSE 12.3. There, sounds are enabled by default. Updating to KDE 4.11 disabled those. But when I had first disabled, then re-enabled sounds in KDE 4.10, then the setting was kept after updating. > My default is what I have configured or accepted as installed. But here you did not configure it, but only accepted the default. The default changed, and since you accept the default (because you never changed it), sounds are now disabled. What maybe could be done here is that .notifyrc files are completely written on first application launch, so that the full defaults are copied to the user's configuration, not only changed entries. But I am not sure if applications inform KDE libraries of the full set of notifications even without ever visiting the Notifications configuration dialog.
The configuration loading is inside each knotify module, so there is no simple way to copy defaults. It would amount to scanning all applications for their .notifyrc files on each start of KDE.