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

[Julien Aubin]

Binary package hint: kdebase-workspace

The printer applet under systemsettings does not work at all in KDE, error being : "The printer settings service does not provide interface KCModule with keyword system-config-printer-kde/system-config-printer-kde.py. The factory does not provide creation of components of the specified type"

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: systemsettings 4:4.6.2a-0ubuntu4
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
CheckboxSubmission: 0e878e1c8f5208740c5ad5f0eee92eb5
CheckboxSystem: edda5d4f616ca792bf437989cb597002
Date: Sun Apr 17 12:50:52 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: kdebase-workspace
Title: systemsettings crashed with AttributeError in fillPrinterOptions(): 'bool' object has no attribute 'markDefaults'
UpgradeStatus: Upgraded to natty on 2011-04-13 (3 days ago)
UserGroups: adm audio cdrom dialout dip disk fax floppy kvm lpadmin plugdev scanner tape video
XsessionErrors:
 (firefox-bin:3216): GLib-CRITICAL **: g_hash_table_insert_internal: assertion `hash_table != NULL' failed
 (firefox-bin:25830): GLib-CRITICAL **: g_hash_table_insert_internal: assertion `hash_table != NULL' failed
 (exe:3728): Gdk-WARNING **: XID collision, trouble ahead
 (exe:3728): Gdk-WARNING **: XID collision, trouble ahead

[Apport retracing service (apport)]

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.