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
Ubuntu 11.10 amd64
Steps to reproduce it:
1) Open a doucment .pdf with evince
2) Go to File>Print..
3) Select "print all pages" and click on "print"
the imput is send to the printer, but the document is not print and a crash appears to me
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: system-
ProcVersionSign
Uname: Linux 3.0.0-8-generic x86_64
Architecture: amd64
Date: Sat Aug 13 19:51:01 2011
ExecutablePath: /usr/share/
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110812)
InterpreterPath: /usr/bin/python2.7
Lpstat: device for 4300: usb://Samsung/
MachineType: System manufacturer System Product Name
PackageArchitec
Papersize: a4
PpdFiles: 4300: Samsung SCX-4300, 2.0.0
ProcCmdline: /usr/bin/python /usr/share/
ProcEnviron:
PATH=(custom, no user)
LANG=it_IT.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/01/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0302
dmi.board.
dmi.board.name: P5QL-VM EPU
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: System Product Name
dmi.product.
dmi.sys.vendor: System manufacturer
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.