[Bug 656134] Re: dbus periodically becomes unresponsive and a reboot is required to regain system functionality

[Matthieu Patou]

I'm facing this problem or something very simmilar in Ubuntu 11.04.

The first symptom is nm-applet not able to associate with a Wifi
network. Logs shows that network manager manage to associate with the
access point, eventually the interface will get an IP address but as nm-
applet or network manager fails to understand it, it will disconnect and
restart a full association cycle.

At this moment the only solution is to logout, shutdown gdm, stop dbus,
remove /var/run/dbus/pid restart dbus restart gdm and login.

I tried to restart gdm and not stopping dbus and I got a dialog box
saying that gdm/X11 is in failsafe mode.

I faced already this problem a couple of time after some days of
activity, for instance right now my laptop is up since ~6.5 days. I'm
doing compilations on it (mostly wireshark and samba) a couple of time a
day. Problem don't seems to occurs while compiling and even not just
after compilation.


** Attachment added: "Strace of dbus after it has gone "crazy" and while starting GDM"
   https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/656134/+attachment/2161943/+files/strace_dbus

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/656134

Title:
  dbus periodically becomes unresponsive and a reboot is required to
  regain system functionality

Status in “dbus” package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: dbus

  After periods of heavy load, dbus goes off into the weeds and just
  refuses to come back and work.  This requires a reboot to fix and
  since so many things rely on dbus, many things just stop working until
  the system is rebooted.

  I've noticed this can happen after a few days of uptime with moderate
  system use, or after a lot of heavy use.  For example, today, I've
  been using usb-creator-gtk to make a lot of usb keys from Maverick
  ISOs for test purposes.  After a while I started getting dbus timeout
  error messages whenever I'd try to make a new bootable usb key.  After
  a while, it happened every single time I tried doing anything via usb-
  creator-gtk. If I was in the process of actually putting the ISO onto
  the usb key, I'd just get a generic message saying that the action
  failed.  If I tried erasing the usb key prior to starting the ISO
  transfer, I'd get a popup explaining that there was a dbus message
  timeout error.

  I also got that by running u1sdtool -s, which also relies on dbus for
  communications.  So, the point is, once dbus goes off into the weeds,
  everything that relies on dbus stops working right.  And trying to
  just restart dbus is ... well, and adventure in itself.

  So the only remedy I can find so far is a system reboot which is
  disappointing to say the least.

  I've noticed this happens a LOT now that I've upgraded to Maverick.  I
  don't recall them happening that frequently in Lucid, though I DID
  experience the dbus issues there as well.  It just seems more
  prevalent in Maverick, and happens especially after periods of heavy
  usage or several days of uptime.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: dbus 1.4.0-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Thu Oct  7 01:16:53 2010
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: dbus

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/656134/+subscriptions