update-manager crashed with DBusException in _convert_dbus_exception(): 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.

Bug #707990 reported by Vladimir Scherbaev
208
This bug affects 39 people
Affects Status Importance Assigned to Milestone
Aptdaemon
Invalid
Undecided
Unassigned
aptdaemon (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: update-manager

Description: Ubuntu natty (development branch)
Release: 11.04
update-manager:
  Установлен: 1:0.145.10
  Кандидат: 1:0.145.10
  Таблица версий:
 *** 1:0.145.10 0
        500 http://archive.ubuntu.com/ubuntu/ natty/main i386 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: update-manager 1:0.145.10
ProcVersionSignature: Ubuntu 2.6.37-12.26-generic 2.6.37
Uname: Linux 2.6.37-12-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Wed Jan 26 13:30:35 2011
ExecutablePath: /usr/bin/update-manager
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python2.7 /usr/bin/update-manager
ProcEnviron:
 LANGUAGE=ru_RU:ru:en_GB:en
 LANG=ru_RU.UTF-8
 LC_MESSAGES=ru_RU.utf8
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/update-manager']
SourcePackage: update-manager
Title: update-manager crashed with DBusException in _convert_dbus_exception(): 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.
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Vladimir Scherbaev (zemik) wrote :
tags: removed: need-duplicate-check
visibility: private → public
Revision history for this message
Michael Vogt (mvo) wrote :

From the traceback it looks like cancel() got clicked, but for some reason the reply from dbus took too long and that raised the error.

affects: update-manager (Ubuntu) → aptdaemon (Ubuntu)
Changed in aptdaemon (Ubuntu):
status: New → Confirmed
importance: Undecided → Medium
Revision history for this message
ahmetcgl (ahmetcgl) wrote :

I was trying to update my newest version of ubuntu which is also alpha, this crash report was created...

Revision history for this message
Ian Nicholson (imnichol) wrote :

Occurred for me after an update

Revision history for this message
SlugiusRex (slugiusrex) wrote :

Occurred for me during a Distribution Update on Percise A1. Rebooted performed partial update. No further issues encountered. Fortunately no corrultion to the installation occurred.

Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, this bug report is about a DBus client failing to connect with the DBus backend and to really understand the issue we need the crash from the DBus backend not from the client. Client crashes are prevented from being report by apport in Precise and in the event that the backend crashes apport should report those ass separate. Because of the previously stated reasons I am setting this bug report to Invalid.

Changed in aptdaemon (Ubuntu):
status: Confirmed → Invalid
importance: Medium → Low
Revision history for this message
Marius B. Kotsbak (mariusko) wrote :

Which package would be the right one to report the bug against the next time this happens?

Revision history for this message
Federico (fkremer-terra) wrote :

siguen los problemas con evince-gtk

Revision history for this message
Federico (fkremer-terra) wrote :

El problema continúa con las actualizaciones de hoy.

Revision history for this message
Pablo Almeida (pabloalmeidaff9) wrote :

Got this after closing the update manager from the Unity launcher.

Revision history for this message
nick (jonesnick17771) wrote :

This bug continues in precise (completely updated as of today)

Revision history for this message
blinkblink (thomasthoma) wrote :

I too confirm the bug in precise.

Changed in aptdaemon (Ubuntu):
status: Invalid → New
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in aptdaemon (Ubuntu):
status: New → Confirmed
Revision history for this message
Muhammad Aamir Ullah Khan (mauk006) wrote :

So many bugs,From 11.10 i upgraded to 12.04,11.10 worked seamlessly and never troubled me but i don't why 12.04 always shows error codes ubuntu found some errors or 12.04 ubuntu system files have error,or sudden freezes softwares crashing,every day i have to send some 4-5 times of crash reports. I know its still beta version but hey its almost 12 days for the complete release and this package of ubuntu is LTS package and honestly its not delivering the goods.I thought it would be different and faster then the older version,their's nothing new though except some or very few changes.I update daily but still problem persists.I hope ubuntu figures it out quickly coz they normally do they are 1 of the best in that.And i would also request to the ubuntu developers to release some more themes for desktop.

Revision history for this message
Marius B. Kotsbak (mariusko) wrote :

I guess it is just a new system that automatically wants you to report bugs at each crash, whereas before the crash would just happen silently. This is good if more bugs get caught, but the number of bugs causing this should be low before the official release.

Also there is an option for this function to be silent for new bugs in the same package version of an application, but it seems not to apply to system crashes.

Revision history for this message
Sebastian Heinlein (glatzor) wrote :

Most likely this error is the result of a failing client after an aptdaemon crash. We don't track the client error anymore, since the valuable information is the server side.

Changed in aptdaemon (Ubuntu):
status: Confirmed → Invalid
Changed in aptdaemon:
status: New → Invalid
Revision history for this message
Mike L (mikerl) wrote :

Invalid? Then how come I just got this error?

Revision history for this message
Sebastian Heinlein (glatzor) wrote :

If the aptdaemon service crashes there will be two errors: one of the client and the another one of the service. The client one only tells that the service has crashed but cannot provide any more details. So we don't track those. (the client is ok).

Please update your system. The report should not be reported any more by the crash handler (apport).

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.