Ubuntu
kdebase-workspace package

systemsettings crashed with ImportError in /usr/share/kde4/apps/system-config-printer-kde/options.py: No module named ppdippstr

Bug #804591 reported by John Hibdon on 2011-07-02

This bug report is a duplicate of: Bug #793679: systemsettings crashed with ImportError in /usr/share/kde4/apps/system-config-printer-kde/options.py: No module named ppdippstr. Edit Remove

This bug affects 1 person

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

Bug Description

Attempting to setup printer

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: systemsettings 4:4.6.3-1ubuntu3
ProcVersionSignature: Ubuntu 3.0-2.3-generic 3.0.0-rc4
Uname: Linux 3.0-2-generic i686
Architecture: i386
Date: Fri Jul 1 19:17:54 2011
ExecutablePath: /usr/bin/systemsettings
InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110601)
ProcCmdline: /usr/bin/systemsettings -caption System\ Settings --icon preferences-system
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: kdebase-workspace
Title: systemsettings crashed with ImportError in /usr/share/kde4/apps/system-config-printer-kde/options.py: No module named ppdippstr
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors: (process:1811): libindicate-WARNING **: Unable to get property data: GDBus.Error:com.canonical.indicate.NO_SUCH_PROPERTY: Indicator 1 has no property named 'time'

Tags:

Revision history for this message

John Hibdon (jwhibdon) wrote on 2011-07-02:

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

Revision history for this message

Apport retracing service (apport) wrote on 2011-07-04: 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 #793679, 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.