Comment 16 for bug 230877

--- Erik Frisk <email address hidden> schrieb:

> I'd like to bump this, problem still exists here.
>

I think the problem still exists if an application
opens a memory mapping to a v4l device and dbus forks
off afterwards.
This is moreover a design bug in that case and
applications should be pinned somewhere in order to
rebase the dbus or alsa (->only has the memory mapping
problem) implementation in the corresponding
applications, forking off before setting up mappings
will work fine.

Markus

> --
> dbus inherits parent filedescriptors
> https://bugs.launchpad.net/bugs/230877
> You received this bug notification because you are a
> direct subscriber
> of the bug.
>
> Status in D-Bus: Fix Released
> Status in “dbus” source package in Ubuntu: Fix
> Committed
>
> Bug description:
> Binary package hint: dbus
>
> When running mplayer the dbus library forks out the
> dbus-launcher which inherits the filedescriptors of
> mplayer.
> If one of those filedescriptors accesses a
> video4linux or DVB device the filehandle will be
> kept open. In case of multistandard devices which
> support analog TV or digital TV (or other modes)
> this will lock the device in the corresponding mode
> until someone kills the dbus daemon.
>
> Attached you can find a patch against the ubuntu
> dbus package
>
> English:
> http://ubuntuforums.org/showthread.php?t=652941
> German:
>
http://www.ubuntu-forum.de/artikel/29814/dbus-blockiert-datei-nach-mplayer-aufruf.html
>