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
none
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: system-
ProcVersionSign
Uname: Linux 3.0.0-8-generic-pae i686
Architecture: i386
CupsErrorLog:
W [19/Aug/
W [19/Aug/
W [19/Aug/
W [19/Aug/
W [19/Aug/
Date: Fri Aug 19 16:43:28 2011
ExecutablePath: /usr/share/
InterpreterPath: /usr/bin/python2.7
Lpstat: device for Samsung-ML-1660: smb://SEGURA/
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 003: ID 0471:207c Philips (or NXP)
MachineType: MICRO-STAR INTERNATIONAL CO., LTD MS-1454
PackageArchitec
Papersize: a4
PpdFiles: Samsung-ML-1660: Samsung ML-1660, 2.0.0
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: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 03/30/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E1454IMS.110
dmi.board.
dmi.board.name: MS-1454
dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
dmi.board.version: REV:1.0
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: MS-1454
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: MS-1454
dmi.product.
dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD
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.