Ubuntu
kdeutils package

printer-applet.py crashed with KeyError in get_notifications(): 'job-originating-user-name'

Bug #831906 reported by Hatem MASMOUDI on 2011-08-23

This bug report is a duplicate of: Bug #629753: printer-applet.py crashed with KeyError in get_notifications(). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	kdeutils (Ubuntu)	New	Undecided	Unassigned

Bug Description

printer-applet.py crashed with KeyError in get_notifications(): 'job-originating-user-name'

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: printer-applet 4:4.7.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-9.13-generic 3.0.3
Uname: Linux 3.0.0-9-generic i686
Architecture: i386
Date: Tue Aug 23 12:09:58 2011
ExecutablePath: /usr/share/kde4/apps/printer-applet/printer-applet.py
InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110816)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: python /usr/bin/printer-applet
PythonArgs: ['/usr/bin/printer-applet']
SourcePackage: kdeutils
Title: printer-applet.py crashed with KeyError in get_notifications(): 'job-originating-user-name'
Traceback:
Traceback (most recent call last):
File "/usr/share/kde4/apps/printer-applet/monitor.py", line 394, 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 vboxusers

Tags:

Revision history for this message

Hatem MASMOUDI (hatem-masmoudi) wrote on 2011-08-23:

ProcEnviron.txt Edit (115 bytes, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2011-08-24: 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 #629753, 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.