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
while printing to a samba printer.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: system-
ProcVersionSign
Uname: Linux 3.0.0-8-generic i686
NonfreeKernelMo
Architecture: i386
CupsErrorLog: Error: [Errno 13] Keine Berechtigung: '/var/log/
CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied
Date: Mon Aug 22 11:59:50 2011
ExecutablePath: /usr/share/
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
InterpreterPath: /usr/bin/python2.7
Lpstat: device for HP-LaserJet-
MachineType: ASUSTeK Computer INC. 1201T
PackageArchitec
Papersize: a4
PpdFiles: HP-LaserJet-
ProcCmdline: /usr/bin/python /usr/share/
ProcEnviron:
LANGUAGE=de:en
PATH=(custom, no user)
LANG=de_DE.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
UdevDb: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden
UpgradeStatus: Upgraded to oneiric on 2011-08-16 (5 days ago)
UserGroups: admin
dmi.bios.date: 03/11/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0319
dmi.board.
dmi.board.name: 1201T
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer INC.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: 1201T
dmi.product.
dmi.sys.vendor: ASUSTeK Computer 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.