I also have this bug when spawning/killing hundreds of Xpra instances.

You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.

  Hundreds of dbus-daemon processes

Status in dbus package in Ubuntu:

Bug description:
  I find a growing number of root owned dbus-daemon processes.
  Eventually, this results in a 'too many processes' error preventing something 
to fork, e.g. a login.

  They get created by batches of 4, every 30 minutes on my box.
  My box is a puppet client, so that these 30 minutes are not in a local cron 
  The pids are 11 units apart (when the box is otherwise idle).
  The command line is:
  //bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session

  ~# ps -fu root | grep dbus-daemon | grep -v grep | tail -8
  root     17509     1  0 11:25 ?        00:00:00 //bin/dbus-daemon --fork 
--print-pid 4 --print-address 6 --session
  root     17520     1  0 11:25 ?        00:00:00 //bin/dbus-daemon --fork 
--print-pid 4 --print-address 6 --session
  root     17531     1  0 11:25 ?        00:00:00 //bin/dbus-daemon --fork 
--print-pid 4 --print-address 6 --session
  root     17542     1  0 11:25 ?        00:00:00 //bin/dbus-daemon --fork 
--print-pid 4 --print-address 6 --session
  root     17972     1  0 11:55 ?        00:00:00 //bin/dbus-daemon --fork 
--print-pid 4 --print-address 6 --session
  root     17983     1  0 11:55 ?        00:00:00 //bin/dbus-daemon --fork 
--print-pid 4 --print-address 6 --session
  root     17994     1  0 11:55 ?        00:00:00 //bin/dbus-daemon --fork 
--print-pid 4 --print-address 6 --session
  root     18005     1  0 11:55 ?        00:00:00 //bin/dbus-daemon --fork 
--print-pid 4 --print-address 6 --session

  I reported this first to https://bugs.freedesktop.org/show_bug.cgi?id=74114
  and was told to report it to ubuntu instead.
  Here were some additional comments:

  The symptoms you described probably mean that something running as
  root is either running /usr/bin/dbus-launch, or attempting to access a
  D-Bus session via the autolaunch: transport while under a transient
  X11 session, 4 times every 30 minutes.

  If this machine does not intentionally run an X11 GUI or a D-Bus
  session, uninstalling the dbus-x11 package or making /usr/bin/dbus-
  launch non-executable might work around this. Don't do that if you use
  an X11 GUI environment, though.

  Since 1.4.8, dbus autolaunch has only been effective when DISPLAY is
  set and non-empty, so if this is autolaunch, an X11 session must be
  involved somehow.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: dbus 1.4.18-1ubuntu1.4
  ProcVersionSignature: Ubuntu 3.2.0-58.88-generic 3.2.53
  Uname: Linux 3.2.0-58-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Mon Jan 27 14:51:19 2014
  MarkForUpload: True
   PATH=(custom, no user)
  SourcePackage: dbus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to