kblueplugd crashed with DBusException in call_blocking()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kdebluetooth (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: kdebluetooth
This bug was filed automatically by the crash agent. I know that this bug is a dupe, but I am filing it anyway as I receive the message "extra debug information will be added to the bug automatically" and I do not know if that is the case if I mark it as a dupe of another bug. Next time this happens, should I mark as dupe? Will the extra info be added?
Thanks!
ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/kblueplugd
InterpreterPath: /usr/bin/python2.5
Package: kdebluetooth 1:0.2-0ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/python /usr/bin/kblueplugd
ProcEnviron:
PATH=/
LANG=en_US.UTF-8
SHELL=/bin/bash
PythonArgs: ['/usr/
SourcePackage: kdebluetooth
Title: kblueplugd crashed with DBusException in call_blocking()
Uname: Linux 2.6.27-6-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
As this is a test system with no personal information stored, would I be better off marking these crash reports as not private in the future?