Version: 4.6 (using KDE 4.6.0) OS: Linux The "Removed Sound Devices" dialog pops up every time I start KDE even if I check "Do not ask again for these devices" Regression from 4.5 Reproducible: Always Steps to Reproduce: - Have some sound devices that KDE considers removed. - Start KDE - In the "Removed Sound Devices" dialog check "Do not ask again for these devices" - Click "No" so that KDE won't remove the devices - Start KDE again Actual Results: The dialog is shown again. Expected Results: The dialog is not shown again. In cases where this is hard to debug I can add debug output in KDE as I finally managed to build my own version.
Sounds like a weird transition issue WRT to solid's uuid actually. Please paste your phonondevicesrc.
Created attachment 57617 [details] phonondevicesrc
file is attached. Note: the problem is not that I have unused audio devices. The problem is that the dialog shows up every time even though I selected "don't show".
*** Bug 280104 has been marked as a duplicate of this bug. ***
*** Bug 317329 has been marked as a duplicate of this bug. ***
Removing subscriber from bug report per abuse report.
tldr: shouldn't happen with PA anymore, probably an alsa upstream problem. I can reproduce this with alsa userspace 1.0.25 and KDE/4.10. This is in fact a very precise issue (other than some of the others regarding phononserver). For some reason Phonon doesn't get the correct name from libsolid and since Phonon caches devices by name it thinks stuff changed. In particular for me suddenly the UDI was used rather than a readable name essentially making phononserver think that all devices were removed. Equally the next time it would get non-UDI names it would again think all devices were removed. So in the end there is a endless loop between name identificiation. Having briefly looked at libsolid's code I do believe this issue may be caused by libasound itself and since we know there are some reentrancy issues with .25 that does not seem like an unlikely cause. It's really hard to debug this reliably though, so I guess the best way would be to wait for alsa userspace .27 and check again. At any rate I added some additional debug output to master that should help with finding it out what goes on when phononserver decides that a device was "removed".
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.