--- Erik Frisk [EMAIL PROTECTED] 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
Okay Qin Gao, marwooj, seems like you ran into another problem there
apparmor related
[ 576.852972] [c01fc517] apparmor_inode_permission+0x47/0x70
[ 576.853002] [c021098f] kobject_get+0xf/0x20
[ 576.853013] [c018fbd6] cdev_get+0x16/0x60
this doesn't happen with the 64bit version, neither with a
Public bug reported:
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
** Attachment added: close all filedescriptors when forking out dbus-launch
http://launchpadlibrarian.net/14547037/dbus-fix-inherited-fds.diff
--
dbus inherits parent filedescriptors
https://bugs.launchpad.net/bugs/230877
You received this bug notification because you are a member of Ubuntu
** Attachment added: close all filedescriptors when forking out dbus-launch
(removed if check)
http://launchpadlibrarian.net/14547671/dbus-fix-inherited-fds-2.diff
--
dbus inherits parent filedescriptors
https://bugs.launchpad.net/bugs/230877
You received this bug notification because you
