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

Bug #851154 reported by Swâmi Petaramesh
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kdeutils (Ubuntu)
New
Undecided
Unassigned

Bug Description

Printer applet crashed immediately after sending a job to printing. (Job printout completed normally).

Tried twice, happened twice.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: printer-applet 4:4.7.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic i686
ApportVersion: 1.23-0ubuntu1
Architecture: i386
CheckboxSubmission: 1ea6109db29b53f721a523a77b7f3abf
CheckboxSystem: d00f84de8a555815fa1c4660280da308
Date: Thu Sep 15 20:17:02 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/share/kde4/apps/printer-applet/printer-applet.py
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: python /usr/bin/printer-applet
ProcEnviron:
 LANGUAGE=fr_FR:fr:en_US:en
 PATH=(custom, user)
 LANG=fr_FR.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: Upgraded to oneiric on 2011-09-04 (11 days ago)
UserGroups: adm admin cdrom dialout disk lpadmin plugdev sambashare vboxusers

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.