software-properties-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.

Bug #893669 reported by Shock
92
This bug affects 20 people
Affects Status Importance Assigned to Milestone
software-properties (Ubuntu)
Won't Fix
Low
Unassigned

Bug Description

I clicked the Remove button with the firefox-aurora (Source code) ppa repository selected.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: software-properties-gtk 0.81.13.1
ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
Uname: Linux 3.0.0-13-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Tue Nov 22 18:14:09 2011
ExecutablePath: /usr/bin/software-properties-gtk
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/software-properties-gtk
PythonArgs: ['/usr/bin/software-properties-gtk']
SourcePackage: software-properties
Title: software-properties-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.
UpgradeStatus: Upgraded to oneiric on 2011-11-22 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Shock (mmiron) wrote :
tags: removed: need-duplicate-check
Daniel Hahler (blueyed)
visibility: private → public
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in software-properties (Ubuntu):
status: New → Confirmed
Revision history for this message
Nest (nestor15) wrote :

Also treid to remove a repository -> crash.

Precise x64 (all updates installed)

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 software-properties (Ubuntu):
status: Confirmed → Invalid
importance: Undecided → Low
Revision history for this message
Shock (mmiron) wrote :

I don't care if it crashed because dbus went away (which I don't think it's the case). I don't care if a meteor hit a canonical data center and some service went out. The client should not crash. For this reason I'm setting this bug as valid.

Changed in software-properties (Ubuntu):
status: Invalid → Confirmed
Revision history for this message
Scott Palmer (skewty) wrote :

I agree with Shock. This should not happen. The code should be adjusted so this doesn't occur.

Changed in software-properties (Ubuntu):
status: Confirmed → Incomplete
status: Incomplete → Fix Committed
status: Fix Committed → Fix Released
Revision history for this message
Shock (mmiron) wrote :

Kamran, what package version was this fixed in?

Changed in software-properties (Ubuntu):
status: Fix Released → Confirmed
Revision history for this message
Brian Murray (brian-murray) wrote :

While I agree with Shock that this should be fixed, it still stands that this crash report from the client has insufficient information and we really need the crash report from the backend to be able to fix the root cause of the crash.

Changed in software-properties (Ubuntu):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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