Red Hat Bugzilla – Bug 151774
gam_server "locks" alsa dmix device
Last modified: 2008-08-02 19:40:32 EDT
When using totem+gstreamer for playing mp3s, after a while of inactivity, totem
refuses to play music anymore. When i close and restart totem, it says that the
dmix device is locked. Using lsof to determine which application has the dmix
device locked turned out to be gam_server. Killing gam_server (autorestarts
here) fixed the problem: i can play music again with totem.
Can't reproduce it atm somehow, but it has happened to me twice now (different
days). This is what lsof when totem is working ok:
[root@orcrist ~]# lsof /dev/snd/pcmC0D0p
COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME
totem 31672 jeroen mem CHR 116,16 5887 /dev/snd/pcmC0D0p
totem 31672 jeroen 30u CHR 116,16 5887 /dev/snd/pcmC0D0p
totem 31675 jeroen mem CHR 116,16 5887 /dev/snd/pcmC0D0p
totem 31675 jeroen 29u CHR 116,16 5887 /dev/snd/pcmC0D0p
When the bug occurs, it lists gam_server instead of totem.
Which version of gamin is installed? (rpm -q gamin)
Sorry, forgot that part: gamin-0.0.25-1.FC3
The simplest is to build rules to forbid kernel (dnotify) monitoring of
resources under /dev/ . I will add a default internal rule about this,
the simplest in the meantime is to use the config file
to ~/.gaminrc and run "killall gam_server"
Hopefully it should solve the issue until the next release,
I double checked and
is part of the default list of excluded resources in gamin sources.
So the only way this could have happened are case where kernel monitoring
could be called on excluded resources. I found a couple of locations in
the code source where this might be possible, and fixed them in the source
code. I have commited the extra checks upstream, I will try to update
a new version. The first thing to do in the meantime is to update to 0.0.26
which has been around for 10 days now.
Though not yet in yum (as of this morning) for FC3. Thanks for the rest.
not in Yum, and not pushed to yum !
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.