[Bug 197430] New: kded4 does not release /dev/dsp and blocks sound

anton benderamp at gmail.com
Sun Jun 21 21:30:16 BST 2009


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

           Summary: kded4 does not release /dev/dsp and blocks sound
           Product: kde
           Version: unspecified
          Platform: SuSE RPMs
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: unassigned-bugs at kde.org
        ReportedBy: benderamp at gmail.com


Version:            (using KDE 4.2.90)
OS:                Linux
Installed from:    SuSE RPMs

Hi,

After some time working in kde my skype stops making calls telling me the error
"problem with audio playback".

After restarting computer if works ok for some time, but after a while starts
showing me this error again.

/dev/dsp is set to be used for all audio devices in skype options.

If I run it from console, it shows the following error:
> skype 
RtApiOss: OSS playback device (/dev/dsp) is busy 


fuser for /dev/dsp shows the following output:

> fuser -m -v /dev/dsp 
 USER PID ACCESS COMMAND 
/dev/dsp: 
 benderamp 1336 f.... konqueror 
 benderamp 1338 f.... kio_file 
 benderamp 1344 f.... kio_http 
 benderamp 1434 f.... kio_http 
 benderamp 3418 F...m kded4 
 benderamp 3444 f.... kwrapper4 
 benderamp 3445 f.... ksmserver 
 benderamp 3449 f.... kglobalaccel 
 benderamp 3459 f.... plasma-desktop 
 benderamp 3460 F.... knotify4 
 benderamp 3510 f.... kaccess


so, kded4 is the process who uses /dev/dsp. I also had amarok shown in this
list with "m" flag, but I killed it and only kded4 has left.

I have found out that kded4 is the core kde daemon. After killing it the whole
desktop has fallen apart (plasma crashed), but skype started making calls.

I am wondering if there is another way to make kded4 release /dev/dsp without
such radical effect.

-- 
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