ubiquity crashed with DBusException in call_blocking(): org.freedesktop.DBus.Error.ServiceUnknown: The name :1.63 was not provided by any .service files

Bug #833695 reported by PsionicBOOM
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
New
Undecided
Unassigned

Bug Description

Perhaps these extra details are not relevant, but I don't know.

I am not sure if they are included in the automatic report.

I am running the daily-live, dated about 8AM, August 25th,
which I put on a USB drive, using the USB creator in Natty.
I was able to boot into the grub menu of the daily-live,
but had issues booting from there,
so I tried adding i915.modeset=0, to my boot options,
which worked.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: ubiquity 2.7.17
ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3
Uname: Linux 3.0.0-9-generic i686
Architecture: i386
CasperVersion: 1.279
Date: Thu Aug 25 11:32:04 2011
ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
InterpreterPath: /usr/bin/python2.7
LiveMediaBuild: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110825)
ProcCmdline: /usr/bin/python /usr/lib/ubiquity/bin/ubiquity gtk_ui
ProcEnviron: Error: [Errno 13] Permission denied: '/proc/3451/environ'
PythonArgs: ['/usr/lib/ubiquity/bin/ubiquity', 'gtk_ui']
SourcePackage: ubiquity
Title: ubiquity crashed with DBusException in call_blocking(): org.freedesktop.DBus.Error.ServiceUnknown: The name :1.63 was not provided by any .service files
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
PsionicBOOM (psionicboom) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #653571, 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.

tags: removed: need-duplicate-check
visibility: private → public
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.