session-installer crashed with org.freedesktop.DBus.Error.NoReply in _show_error(): 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 #958575 reported by Nicolas Riesco on 2012-03-18
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apport (Ubuntu)
High
Martin Pitt
Precise
Undecided
Unassigned
sessioninstaller (Ubuntu)
Undecided
Unassigned
Precise
Undecided
Unassigned

Bug Description

Using Ubuntu 12.04 beta version.

After double clickig on a mobi file, a pop-up window informed me that no applications were available to open "Mobipocket e-book" (before upgrade, I could do so using Okular).

I was offered to install Okular and the crash happened after accepting to install Okular.

Afterwads, I checked and Oular was already installed, however it fails to open mobi files.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: sessioninstaller 0.20+bzr123-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
Date: Sun Mar 18 13:58:51 2012
ExecutablePath: /usr/bin/session-installer
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/session-installer
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANGUAGE=en_GB:en
 LANG=en_GB.UTF-8
PythonArgs: ['/usr/bin/session-installer']
SourcePackage: sessioninstaller
Title: session-installer crashed with org.freedesktop.DBus.Error.NoReply in _show_error(): 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 precise on 2012-03-14 (3 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse libvirtd lpadmin mail netdev plugdev powerdev scanner tape users uucp video

Nicolas Riesco (nicolas-riesco) wrote :
tags: removed: need-duplicate-check
visibility: private → public
Changed in apport (Ubuntu):
assignee: nobody → Martin Pitt (pitti)
Brian Murray (brian-murray) wrote :

I would have expected this not to be reported because of the fix for bug 914220. Perhaps it should be:

if 'org.freedesktop.DBus.Error.NoReply' in str(exc_obj):

Changed in apport (Ubuntu):
status: New → Triaged
importance: Undecided → High
Martin Pitt (pitti) wrote :

Fixed in trunk r2257.

Changed in apport (Ubuntu):
status: Triaged → Fix Committed
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package apport - 2.0-0ubuntu1

---------------
apport (2.0-0ubuntu1) precise; urgency=low

  * New upstream release: This is the final 2.0 release, featuring the
    overhauled and simplified GUI, support for whoopsie-daemon, and
    client-side duplicate checking.
    - report.py, anonymize(): Only replace whole words, not substrings.
      (LP: #966562)
    - apport_python_hook.py: Fix filtering of
      org.freedesktop.DBus.Error.NoReply exceptions. (LP: #958575)
    - crashdb.py: When publishing the crash database, cut hash file names
      after quoting, to avoid that the quoting causes them to become too long.
      (LP: #968070) This also uncovered that known() did not actually find any
      signature which contained an URL-quoted character, therefore breaking
      client-side duplicate checking in a lot of cases. Double-quote the file
      name now, as urlopen() unquotes it.
    - Add a new crash database option "problem_types" and a CrashDatabase
      method "accepts(report)". This can be used to stop uploading particular
      problem report types to that database. E. g. a distribution might decide
      to not get "Crash" reports any more after release. Document the new
      option in doc/crashdb-conf.txt.
    - ui.py: Do not upload a report if the crash database does not accept the
      report's type. This behaviour is not really correct, but necessary as
      long as we only support a single crashdb and have whoopsie hardcoded.
      Once we have multiple crash dbs, we need to not even present the data if
      none of the DBs wants the report. See LP #957177 for details.
      (LP: #968121)
    - ui.py: Do not short-circuit information collection if report already has
      a "DistroRelease" field, as the GUIs add that in some cases. Check for
      "Dependencies" instead. This fixes information collection for kernel
      problems (which now has a full GTK GUI test case). (LP: #968488)
  * Merge from trunk:
    - test_ui_gtk.py: Disable package hooks for the tests, as they might ask
      for sudo passwords and other interactive bits, and thus make the tests
      hang.
 -- Martin Pitt <email address hidden> Fri, 30 Mar 2012 12:38:02 +0200

Changed in apport (Ubuntu):
status: Fix Committed → Fix Released
Changed in sessioninstaller (Ubuntu):
status: New → Invalid
Martin Pitt (pitti) wrote :

Reopening, Steve says bug 734376 is still being reported to errors.u.c.

Changed in apport (Ubuntu):
status: Fix Released → Triaged
Martin Pitt (pitti) wrote :

The apport fix for bug 1042970 was just accepted into precise-proposed.

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

Other bug subscribers