scp-dbus-service.py crashed with KeyError in get_notifications(): 'job-originating-user-name'
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
system-config-printer (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
1. Ubuntu 11.10
2. system-
Installed: 1.3.5+20110801-
Candidate: 1.3.5+20110801-
Version table:
*** 1.3.5+20110801-
500 http://
100 /var/lib/
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: system-
ProcVersionSign
Uname: Linux 3.0.0-8-generic x86_64
Architecture: amd64
Date: Mon Aug 22 13:40:54 2011
ExecutablePath: /usr/share/
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
InterpreterPath: /usr/bin/python2.7
Lpstat:
device for HP-LaserJet-4000: socket:
device for HP_LaserJet_
device for HP_LaserJet_
MachineType: LENOVO 3323A37
PackageArchitec
Papersize: a4
PpdFiles:
HP-LaserJet-4000: HP LaserJet 4000 Series Postscript (recommended)
HP_LaserJet_
HP_LaserJet_
ProcCmdline: /usr/bin/python /usr/share/
ProcKernelCmdLine: BOOT_IMAGE=
PythonArgs: ['/usr/
SourcePackage: system-
Title: scp-dbus-service.py crashed with KeyError in get_notificatio
Traceback:
Traceback (most recent call last):
File "/usr/share/
attrs[
KeyError: 'job-originatin
UpgradeStatus: Upgraded to oneiric on 2011-08-20 (1 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 04/26/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 6QET45WW (1.15 )
dmi.board.name: 3323A37
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.name: 3323A37
dmi.product.
dmi.sys.vendor: LENOVO
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 #827573, 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.