ubuntu-sso-login crashed with DBusException in __new__(): org.freedesktop.DBus.Error.NoServer: Failed to connect to socket /tmp/dbus-WDXStIhKPf: Connection refused
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| ubuntu-sso-client (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
one of three or so bugs just on booting,
gnome-settings-
and now a couple more too
this one just on boot, don't see why it would crash,
even if I don't create/ use ubuntu cloud space...
may have some residual stuff from many ubuntu release versions ago
but shouldn't be on this machine with only two, natty and oneiric
installed, relatively new machine to me, though bought used
with windows, but no ubuntu, so I installed it...
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: ubuntu-sso-client 1.3.2-0ubuntu2
ProcVersionSign
Uname: Linux 3.0.0-9-generic i686
Architecture: i386
Date: Wed Aug 24 21:58:12 2011
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
InterpreterPath: /usr/bin/python2.7
PackageArchitec
ProcCmdline: /usr/bin/python /usr/lib/
ProcCwd: /
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, user)
LANG=en_US.UTF-8
PythonArgs: ['/usr/
SourcePackage: ubuntu-sso-client
Title: ubuntu-sso-login crashed with DBusException in __new__(): org.freedesktop
UpgradeStatus: Upgraded to oneiric on 2011-07-21 (34 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
| Jerry (jerrywone) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| tags: | removed: need-duplicate-check |
| visibility: | private → public |
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 #711413, 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.