scp-dbus-service.py crashed with KeyError in _set_job_document_text(): 38
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
system-config-printer (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: system-
Deleting an already canceled item from the job list yields to this exception. I haven't been able to reproduce it methodically but it happens consistently when trying to completely delete a canceled print job.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: system-
ProcVersionSign
Uname: Linux 2.6.38-7-generic x86_64
NonfreeKernelMo
Architecture: amd64
Date: Fri Apr 1 16:10:02 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/share/
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1)
InterpreterPath: /usr/bin/python2.7
Lpstat: device for HP-Deskjet-f2400: smb://WORKGROUP
MachineType: Packard Bell imedia S3800
Papersize: letter
PpdFiles: HP-Deskjet-f2400: HP Deskjet f2400 Series, hpcups 3.11.1
ProcCmdline: /usr/bin/python /usr/share/
ProcEnviron:
LANGUAGE=en_US:en
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
PythonArgs: ['/usr/
SourcePackage: system-
Title: scp-dbus-service.py crashed with KeyError in _set_job_
Traceback:
Traceback (most recent call last):
File "/usr/share/
job = self.jobs[jobid]
KeyError: 38
UpgradeStatus: Upgraded to natty on 2011-03-31 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare www-data
dmi.bios.date: 12/23/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P01-A4
dmi.board.
dmi.board.name: FIH57
dmi.board.vendor: Packard Bell
dmi.chassis.type: 3
dmi.chassis.vendor: Packard Bell
dmi.modalias: dmi:bvnAmerican
dmi.product.name: imedia S3800
dmi.sys.vendor: Packard Bell
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 #748366, 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.