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
Printed a document. Crashed, but still printed out.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: system-
ProcVersionSign
Uname: Linux 3.0.0-8-generic x86_64
NonfreeKernelMo
Architecture: amd64
CheckboxSubmission: 1a0f9747e1d27c1
CheckboxSystem: 7e42599bda39ea7
Date: Sun Aug 14 03:03:06 2011
ExecutablePath: /usr/share/
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64+mac (20110724)
InterpreterPath: /usr/bin/python2.7
Lpstat: device for Brother-MFC-8480DN: dnssd:/
MachineType: Apple Inc. MacBookPro5,4
PackageArchitec
Papersize: letter
PpdFiles: Brother-MFC-8480DN: Brother MFC-8480DN BR-Script3
ProcCmdline: /usr/bin/python /usr/share/
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
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: 06/15/09
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP53.88Z.
dmi.board.
dmi.board.name: Mac-F22587A1
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro5,4
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.
dmi.modalias: dmi:bvnAppleInc
dmi.product.name: MacBookPro5,4
dmi.product.
dmi.sys.vendor: Apple Inc.
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.