Ubuntu
kdebase-workspace package

systemsettings crashed with AttributeError in maintenance_command()

Bug #455834 reported by Tobin Davis on 2009-10-19

This bug report is a duplicate of: Bug #436392: systemsettings crashed with AttributeError in maintenance_command() after "clean printer heads" button is pressed. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	kdebase-workspace (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: kdebase-workspace

After upgrading my Jaunty desktop to Karmic, had to reinstall the printer as cups had duplicate printers configured, neither of which would print. After deleting all existing printers and re-adding my HP 8250 as a new one, tried to print a test page.

ProblemType: Crash
Architecture: i386
Date: Mon Oct 19 14:36:43 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/systemsettings
NonfreeKernelModules: nvidia
Package: systemsettings 4:4.3.2-0ubuntu5
ProcCmdline: /usr/bin/systemsettings -caption System\ Settings -icon preferences-system
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: kdebase-workspace
Title: systemsettings crashed with AttributeError in maintenance_command()
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev pulse-access sambashare vboxusers

Tags:

Revision history for this message

Tobin Davis (gruemaster) wrote on 2009-10-19:

Traceback.txt Edit (436 bytes, text/plain; charset="utf-8")
XsessionErrors.txt Edit (1.0 MiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2009-10-20: 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 #436392, 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.