From: Alex Schuster <wonko@wonkology.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] /dev/dsp: Device or resource busy
Date: Sat, 18 Feb 2012 18:17:18 +0100 [thread overview]
Message-ID: <20120218181718.07fd56ce@weird.wonkology.org> (raw)
In-Reply-To: <20120218170327.GH3062@solfire>
meino.cramer@gmx.de writes:
> Alex Schuster <wonko@wonkology.org> [12-02-18 17:36]:
> > meino.cramer@gmx.de 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.
Wonko
next prev parent reply other threads:[~2012-02-18 17:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-18 15:46 [gentoo-user] /dev/dsp: Device or resource busy Alex Schuster
2012-02-18 15:55 ` meino.cramer
2012-02-18 16:08 ` Michael Mol
2012-02-18 16:27 ` Alex Schuster
2012-02-18 17:03 ` meino.cramer
2012-02-18 17:17 ` Alex Schuster [this message]
2012-02-18 17:27 ` meino.cramer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120218181718.07fd56ce@weird.wonkology.org \
--to=wonko@wonkology.org \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox