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

Bug #856932 reported by C de-Avillez
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kdeutils (Ubuntu)
New
Undecided
Unassigned

Bug Description

Opened Chromium, went to maps.google.com, selected print, selected the printer; while the job went to the printer, I got the crash warning.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: printer-applet 4:4.7.1-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
CheckboxSubmission: 24776dc1392ac4f88b6beaa2d7cdfe16
CheckboxSystem: d00f84de8a555815fa1c4660280da308
Date: Thu Sep 22 19:57:59 2011
ExecutablePath: /usr/share/kde4/apps/printer-applet/printer-applet.py
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: Upgraded to oneiric on 2011-08-22 (31 days ago)
UserGroups: adm admin cdrom dialout kismet kvm libvirtd lpadmin plugdev sambashare vboxusers

Revision history for this message
C de-Avillez (hggdh2) 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 #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.

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.