[Error 09:28:19.713] [PidginAccountItemSource] Could not get Pidgin accounts: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)

Bug #603080 reported by Fernando Miguel
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
dbus (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: dbus

for the last week or week, my system has teh overall feeling of being slow... very slow.
Some apps like gwibber and pidgin tend to show this much more the others.
it becomes so slow that the app stops accepting input and just freezes.

it would seem to be caused by DBUS timeouts or some gconf settings

possibly related to https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/582169

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: dbus 1.2.16-2ubuntu4
ProcVersionSignature: Ubuntu 2.6.35-6.9-generic 2.6.35-rc3
Uname: Linux 2.6.35-6-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Thu Jul 8 11:09:35 2010
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20091130)
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: dbus

Revision history for this message
Fernando Miguel (fernandomiguel) wrote :
Revision history for this message
Fernando Miguel (fernandomiguel) wrote :
Revision history for this message
Cesare Mastroianni (cece) wrote :

BUGabundo ::

I don't know if there is some relation between bugs #603080 and #582169. The latter (at least for me) happens when trying to connect to a server (via SMB or FTP): the service is refused because of a DBUS timeout. Nothing else happens, no application is slowed down, the system won't freeze. Some now and then, the DBUS timeout is followed by a crash of GVFS (not always).

In both cases, I'm not able to generate a backtrace. The DBUS timout pops up from a process which is unpredictably forked from the DBUS daemon: so I have no chance to attach it from GDB. GVSF starts in an unpredictable moment and then crash just less then a second later, so it is not possible to get the process' PID and pass it to GDB.

Is there any trick to trace fast-generating or fast-forking processes from GDB?

I would like to spend sometime in finding more data and details about this bug: please, tell me how could I help You in finding the real problem and maybe its solution...

Before May (before I upgraded to Lucid) I never experienced such problem, nor with Karmic nor with Hardy ...

Ciao
CM

Revision history for this message
Mörgæs (moergaes) wrote :

Closing due to age.
If a similar problem appears in the latest Ubuntu release please open a new report.

Changed in dbus (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.