Alex Schuster <firstname.lastname@example.org> [12-02-18 18:20]:
> email@example.com writes:
> > Alex Schuster <firstname.lastname@example.org> [12-02-18 17:36]:
> > > email@example.com writes:
> > > > try (as root)
> > > >
> > > > fuser /dev/dsp
> > > >
> > > > to figure out, which task helds that device...
> > >
> > > I get no output at all.
> > ?Hu?
> > The access rights to that device are ok...?
> Yes, read-write access for all in the audio group:
> wonko@weird ~ $ ls -l /dev/dsp
> crw-rw----+ 1 root audio 14, 3 Feb 18 07:23 /dev/dsp
> And otherwise I would expect a permission denied error.
> Maybe it works when I log out of KDE and have a minimal environment, but
> I cannot do this now, too much important stuff is running at the moment.
I didnt know the origin of the error message "resource busy"...so if
it had come out of the application...even an error message can e wrong
May be it would help to unload the sound related modules from the
kernel and modprobe -a them again?
Should have the same effect as the reboot without a global hickup of
the whole system...
just a shot in the dark...