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

Bug #842592 reported by Stefan K.
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kdeutils (Ubuntu)
New
Undecided
Unassigned

Bug Description

The program crashed directly after sending print job from okular (encrypted pdf with form fields). Print dialog opened as normal... then printer was selected and confirmed with "OK". No special options.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: printer-applet 4:4.7.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
Uname: Linux 3.0.0-10-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Tue Sep 6 14:07:49 2011
ExecutablePath: /usr/share/kde4/apps/printer-applet/printer-applet.py
InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110830.1)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: python /usr/bin/printer-applet
ProcEnviron:
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
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

summary: printer-applet.py crashed with KeyError in get_notifications(): 'job-
- originating-user-name', crashed directly after sending print job from
- okular (encrypted pdf with form fields).
+ originating-user-name'
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.