scp-dbus-service.py crashed with KeyError in get_notifications(): 'job-originating-user-name'

Bug #829740 reported by J
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
system-config-printer (Ubuntu)
New
Undecided
Unassigned

Bug Description

none

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: system-config-printer-common 1.3.5+20110801-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-8.11-generic-pae 3.0.1
Uname: Linux 3.0.0-8-generic-pae i686
Architecture: i386
CupsErrorLog:
 W [19/Aug/2011:09:06:06 -0300] failed to AddProfile: org.freedesktop.ColorManager.Failed:profile object path '/org/freedesktop/ColorManager/profiles/Samsung_ML_1660_Gray__' has already been added
 W [19/Aug/2011:10:39:53 -0300] failed to CreateProfile: org.freedesktop.DBus.Error.NoReply:Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
 W [19/Aug/2011:10:39:58 -0300] failed to CreateDevice: org.freedesktop.DBus.Error.NoReply:Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
 W [19/Aug/2011:15:31:19 -0300] failed to CreateProfile: org.freedesktop.DBus.Error.NoReply:Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
 W [19/Aug/2011:15:31:24 -0300] failed to CreateDevice: org.freedesktop.DBus.Error.NoReply:Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Date: Fri Aug 19 16:43:28 2011
ExecutablePath: /usr/share/system-config-printer/scp-dbus-service.py
InterpreterPath: /usr/bin/python2.7
Lpstat: device for Samsung-ML-1660: smb://SEGURA/SEG-B1-COM02/Comercial-Samsung-1660
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
PackageArchitecture: all
Papersize: a4
PpdFiles: Samsung-ML-1660: Samsung ML-1660, 2.0.0
ProcCmdline: /usr/bin/python /usr/share/system-config-printer/scp-dbus-service.py
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-8-generic-pae root=UUID=93d6f3de-6246-4db0-9847-98af40412ef1 ro quiet splash pcie_aspm=force vt.handoff=7
PythonArgs: ['/usr/share/system-config-printer/scp-dbus-service.py']
SourcePackage: system-config-printer
Title: scp-dbus-service.py crashed with KeyError in get_notifications(): 'job-originating-user-name'
Traceback:
 Traceback (most recent call last):
   File "/usr/share/system-config-printer/monitor.py", line 441, in get_notifications
     attrs['job-originating-user-name'] != cups.getUser ()):
 KeyError: 'job-originating-user-name'
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.asset.tag: To be filled by O.E.M.
dmi.board.name: MS-1454
dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
dmi.board.version: REV:1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: MS-1454
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1454IMS.110:bd03/30/2010:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-1454:pvrREV1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-1454:rvrREV1.0:cvnMS-1454:ct10:cvrN/A:
dmi.product.name: MS-1454
dmi.product.version: REV:1.0
dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD

Revision history for this message
J (jsartti) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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.

tags: removed: need-duplicate-check
visibility: private → public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.