software-center crashed with DBusException in call_blocking()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
software-center (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: software-center
I purchased a new ubuntu 10.10 & mint 10 cd last week in the hope I could clear the shadowed bios/video that seems to have corrupted 13 laptop bios in the past 2 years. I have isolated the problem to either the ramfs has a executable suid ro cache and or a remote installed system bios neither of which clear after shutting down a live session.
the bug automaticly sets all the modes and connects through pppd using ieee (experimental) and begins tx/rx data packets via streaming with or without being connected to the internet. (cdc_adm?? ring any bells)
if you need more info I have screen shots on my blackberry I can forward from there if supplied with an address. send to d_nelson AT vzw DOT blackberry net
ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: software-center 3.0.4
ProcVersionSign
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
Date: Mon Jan 31 05:56:45 2011
ExecutablePath: /usr/share/
InterpreterPath: /usr/bin/python2.6
LiveMediaBuild: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007.1)
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
PythonArgs: ['/usr/
SourcePackage: software-center
Title: software-center crashed with DBusException in call_blocking()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
tags: | removed: need-duplicate-check |
description: | updated |
security vulnerability: | yes → no |
visibility: | private → public |
Hi dowat. Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 705215, so it 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.