Version: (using KDE 4.3.2) OS: Linux Installed from: Debian testing/unstable Packages When switching computers in a /home on NFS setup I get a very annoying popup from KDE4 telling me that some audio devices disappeared. As this is a heterogeneous environment hardware-wise this is to be expected, as sound cards differ. Of course I could say "Do not ask again for these devices" each and every time until I hit all the available sound cards. However what I really need is a way to just set a default as administrator (i.e. keeping all the mixer settings until the user comes back to the specific machine). Not only there are multiple computers, but there are also many users, all faced with this popup on login and confused what they should do. How to Reproduce: Log into a machine at the console which shares the home directory with other machines which are not identical, then log off and re-login at one of the other machines. Expected Behaviour: Provide a way to set a global system default for disappearing sound devices.
I'm a admin of a school network with /home on nfs. We have many different machines with much more users switching between them. And we want to switch to KDE SC 4. We currently have only 5 machines updated for testing but are hit by this annoying popup and users asking what to do nearly every day. Please provide a global way to turn this popup off.
I can confirm this. my setup at home is a linux desktop/server which is always on and a laptop in the living room, for more casual use. Some software I always run on the machine that is always on, like thunderbird and kopete (which is where this message comes up). So I log onto the machine using ssh -X and start kopete there, the display is usually the laptop downstairs. Whenever a new message comes in, kopete (though probably not kopete itself, but a KDE lib it is using) gives a hard to ignore/turn-off message: "KDE detected that one or more internal sound devices were removed" It doesn't inform the user what is going on, so he/she can't fix it, which makes it annoying. Some questions that come up when I see this: - KDE on which machine? (probably the X-client side, so the machine upstairs) - removed since when? - why is this a problem? - how can I fix it permanently? - should I somehow have automatically working sound over the network (that would be nice ;-) Solutions would include: - not showing the message when the display isn't on localhost - not blocking on the message - providing more information to solve the problem - automatically choosing a permanent solution and telling me where I can change this via some non-blocking desktop message. Cheers Simon
First of all, there is a patch now in Novell's Bugzilla: https://bugzilla.novell.com/show_bug.cgi?id=609396 Otherwise my workaround is to set up a shutdown script by placing a file in .kde/shutdown/ with something like: if [ -f $HOME/.kde/share/config/phonondevicesrc ]; then /usr/bin/perl -p -i -e "s/^deleted=false/deleted=true/g" $HOME/.kde/share/config/phonondevicesrc /usr/bin/perl -p -i -e "s/^hotpluggable=false/hotpluggable=true/g" $HOME/.kde/share/config/phonondevicesrc fi This resets the device list on every logout, so that devices are not checked again. I'm not sure about resetting "hotpluggable", it may not be actually required (not tested). I did not try the patch, but it might be that the above workaround is better. This is because the problem is not only in the fact that dialog box appears and must be clicked through to forget devices (this is what patch solves, as I can judge from its name). The problem is that devices, which were formerly active, seem to be actually checked (looked for), making a noticeable (a minute or so) pause on login to a different machine in roaming environment.
I love KDE, primarily KDE applications. But Linux users do not want the annoyance of windows where the desktop takes over the dialog. I like to statically configure things and leave it because I cannot have popups which have usually proven to be worthless interruptions. Allow users to turn off dynamic configurations. I do not use a mouse and keyboard with my mythtv system and when myth is not running I don't want a beautiful slide show screen saver disrupted with dialog boxes that cannot be handled without connecting remotely to the display. Same goes with system notifications. I have managed to disable all but these sound devices notifications. For instance 'display manager change monitor' service can be turned off, I want the same with audio devices. I like many of the updates with the kde applications but the desktop itself has gone backwards from kde3.
Created attachment 87660 [details] Use a global phonondevicesrc (4.4.5) I work around this very annoying issue the following way: 1. Apply a patch to phonon/kded-module/phononserver.cpp so that a global (i.e. /etc/kde4) phonondevicesrc gets loaded and its entries get registered. 2. On each desktop machine (we only support a handful of hardware series), deploy a global phonondevicesrc that lists all that hardware's devices and assign suitable preference values. So, the user's individual phonondevicesrc remains essentially empty and the annoying messages don't appear. This original version of the patch dates back to 2011 and applies against 4.4.5 (the version in Debian squeeze).
Created attachment 87661 [details] Use a global phonondevicesrc (4.8.4) This recent version of the patch applies against 4.8.4, the Version included in Debian wheezy.
Thanks for the patch. Let's reassign this to Phonon developers to see if it is still needed. As far as I know, the dynamic handling of devices was no longer needed and got removed.
It is inactive when Pulseaudio is used and one really should use pulseaudio in this kind of setup. That being said the code is still there, so I'll have a look during the Randa sprint. Would be great if you could throw the patch up on reviewboard though. Reviewing things in bug reports is very tedious.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
I don't have a setup anymore that could reproduce this. With the recent changes to the audio subsystems in Linux (from pulseaudio to pipewire) the whole thing may also be completely changed w.r.t. phonon? Currently my audio works fine and I never run into this error anymore.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!