printer-applet.py crashed with KeyError in get_notifications()

Bug #629753 reported by Torsten Burschka
798
This bug affects 85 people
Affects Status Importance Assigned to Milestone
kdeutils (Ubuntu)
Fix Released
High
Unassigned

Bug Description

Binary package hint: kdeutils

Just right after start Kubuntu 10.10 with latest updates

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: printer-applet 4:4.5.1-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-19.28-generic 2.6.35.3
Uname: Linux 2.6.35-19-generic i686
Architecture: i386
Date: Fri Sep 3 21:02:34 2010
ExecutablePath: /usr/share/kde4/apps/printer-applet/printer-applet.py
InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Beta i386 (20100902.1)
InterpreterPath: /usr/bin/python2.6
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()
Traceback:
 Traceback (most recent call last):
   File "/usr/share/kde4/apps/printer-applet/monitor.py", line 376, in get_notifications
     jobid = event['notify-job-id']
 KeyError: 'notify-job-id'
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Torsten Burschka (torsten-burschka) wrote :
tags: removed: need-duplicate-check
Jonathan Riddell (jr)
visibility: private → public
tags: added: bugpattern-needed
fuggum (fuggum)
tags: added: amd64
Changed in kdeutils (Ubuntu):
status: New → Confirmed
Revision history for this message
Stefan K. (78luphr0rnk2nuqimstywepozxn9kl-launchpad) wrote :

What I experienced: Document is printed but the "monitor.py" crashes, which trying to fetch the uid of the originating user. Guess it shall monitor the status of the printing job and notify the user that the printing finished.

Revision history for this message
FreeMinded (pascal-planetmages) wrote :

I can confirm this bug for Kubuntu 11.10 beta 1

Revision history for this message
Scott Gillett (dty6) wrote :

this bug also happened for me. Printer Model is HP OfficeJet 7500A Wide Format.

Revision history for this message
Sebastian (guttenb) wrote :

For me this happens in Kubuntu 11.10 (last upgraded today, September 27, 2011) every time I try to print something.

Changed in kdeutils (Ubuntu):
importance: Undecided → High
Revision history for this message
Scott Kitterman (kitterman) wrote :

I think this exact bug was fixed by https://projects.kde.org/projects/kde/kdeutils/printer-applet/repository/revisions/213c943e847bc225ed6ed7c014c5d244ff58e30c but there is a follow-on bug that apport marks as a dupe of this one. See Bug 861560 for an example. Note that it's KeyError: 'job-originating-user-name', not KeyError: 'notify-job-id'.

Is anyone using Oneiric still getting the KeyError: 'notify-job-id' error?

Revision history for this message
Bruce Miller (brm0423) wrote : Re: [Bug 629753] Re: printer-applet.py crashed with KeyError in get_notifications()

I am one of those who, as Scott Kitterman reported, has had a recent bug report marked as duplicate because it closely resembles an older and fixed bug.

I confirm that the current crash message is: 'job-originating-user-name.'

Revision history for this message
Scott Kitterman (kitterman) wrote :

I've fixed the 'job-originating-user-name' crash and it should be in oneiric shortly. For bug management purposes, I'm going to close this as one bug since apport doesn't seem to be able to distinguish.

Changed in kdeutils (Ubuntu):
status: Confirmed → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package kdeutils - 4:4.7.1-0ubuntu3

---------------
kdeutils (4:4.7.1-0ubuntu3) oneiric; urgency=low

  * Catch KeyError in printer-applet monitor.py to avoid crash (LP: #629753)
    - debian/patches/printer-applet-monitor.diff
 -- Scott Kitterman <email address hidden> Wed, 28 Sep 2011 12:56:45 -0400

Changed in kdeutils (Ubuntu):
status: Fix Committed → Fix Released
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.