computer-janitor-gtk crashed with DBusException in call_blocking(): org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
computer-janitor (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: computer-janitor
I was trying to remove some old kernels from my system. computer-janitor was actually still open on my system when I reported the bug. Additionally, I found the following in /var/log/syslog:
Apr 12 09:18:08 localhost computerjanitord: INFO: post-cleanup: <unsupported_
Apr 12 09:18:08 localhost computerjanitord: INFO: post-cleanup: <autoremoval_
Apr 12 09:18:08 localhost computerjanitord: INFO: post-cleanup: <dpkg_dotfile_
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: computer-
ProcVersionSign
Uname: Linux 2.6.38-8-server x86_64
Architecture: amd64
CheckboxSubmission: fee5e196cb921cb
CheckboxSystem: 2a6f54df59af338
Date: Tue Apr 12 09:18:33 2011
ExecutablePath: /usr/share/
InterpreterPath: /usr/bin/python2.7
PackageArchitec
ProcCmdline: /usr/bin/python /usr/share/
ProcEnviron:
LANGUAGE=en_US:en
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/zsh
PythonArgs: ['/usr/
SourcePackage: computer-janitor
Title: computer-
UpgradeStatus: Upgraded to natty on 2011-04-10 (1 days ago)
UserGroups: adm admin audio cdrom dialout dip family floppy fuse libvirtd lpadmin plugdev pulse pulse-access sambashare sbuild scanner video
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #749004, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.