[Bug 285646] New: knotify4 blocks sound when a program was executed as root before

Johann Bergles hans.bergles at gmx.at
Thu Nov 3 12:52:11 GMT 2011


https://bugs.kde.org/show_bug.cgi?id=285646

           Summary: knotify4 blocks sound when a program was executed as
                    root before
           Product: kde
           Version: 4.7
          Platform: Ubuntu Packages
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: unassigned-bugs at kde.org
        ReportedBy: hans.bergles at gmx.at


Version:           4.7 (using KDE 4.7.2) 
OS:                Linux

Just tested the following :

Executed dolphin "kdesudo dolphin" click on any item for delete - it takes
soumd time for playback "ding" click cancel and end dolphin.

Now not any program started with "user" rights can play sound anymore.

PusleAudio says always "[alsa-sink] alsa-sink.c: Error opening PCM device
front:0: Das Gerät oder die Ressource ist belegt"

When looking in a console window the following program still runs even that
dolphin (or any other root program) was closed.

/dev/snd/pcmC0D0p:   root      13196 F...m knotify4
/dev/snd/timer:      root      13196 f.... knotify4

If the "root" instance of "knotify4" is killed , sound playback as per user
works correctly again.

Also this bug prevents system shutdown from the KApplication Luncer (Desktop
became darker but system fails to shutdown).






Reproducible: Always

Steps to Reproduce:
start any KDE program that play sound with root rights (e.g. Dolphin).
let the program play a sound (E.g. Dolphin click on "delete "a file)
Close the program.

Sound does now not work anymore for all users except root (busy).





Actual Results:  
No sound since knotif4 is started for user "root".


Expected Results:  
knotify4 for user "root" should be closed when no "root" program is running
anymore.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


More information about the Unassigned-bugs mailing list