Ubuntu
kde-workspace package

systemsettings crashed with AttributeError in fillPrinterOptions(): 'bool' object has no attribute 'markDefaults'

Bug #864554 reported by Julien Aubin on 2011-10-02

This bug report is a duplicate of: Bug #763369: Printer configuration was working, installed Samba4 for browsing samba shares, crashes now. Edit Remove

This bug affects 1 person

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

Bug Description

The error occurs every time I open the printer applet. This looks like a regression from Maverick Meerkat.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: systemsettings 4:4.7.1-0ubuntu5
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu2
Architecture: i386
CheckboxSubmission: 0e878e1c8f5208740c5ad5f0eee92eb5
CheckboxSystem: edda5d4f616ca792bf437989cb597002
Date: Sun Oct 2 12:51:32 2011
ExecutablePath: /usr/bin/systemsettings
ProcCmdline: /usr/bin/systemsettings -caption Configuration\ du\ système --icon preferences-system
ProcEnviron:
LANG=fr_FR.UTF-8
SHELL=/bin/bash
SourcePackage: kde-workspace
Title: systemsettings crashed with AttributeError in fillPrinterOptions(): 'bool' object has no attribute 'markDefaults'
UpgradeStatus: Upgraded to oneiric on 2011-09-22 (9 days ago)
UserGroups: adm audio cdrom dialout dip disk fax floppy kvm lpadmin plugdev scanner tape video

Tags:

Revision history for this message

Julien Aubin (gojulgarbmail) wrote on 2011-10-02:

Traceback.txt Edit (558 bytes, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2011-10-02: 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 #763369, 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.