applet.py crashed with ImportError: could not import pango direct after booting (unity on screen) ubuntu 11.10 as Live CD from USB as loop (ISO) using Grub2

Bug #975605 reported by Hans
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
system-config-printer (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Release Ubuntu 11.10

Crashed direct after booting (unity on screen) ubuntu 11.10 as Live CD from USB from loop (ISO) using Grub2.
Same sytem installed on hdd is starting without crash.

Grub 1.9X start sequence

menuentry "Ubuntu 11.10 (ubuntu-11.10-desktop-i386.iso" {
        loopback loop /ubuntu-11.10-desktop-i386.iso
        linux (loop)/casper/vmlinuz boot=casper iso-scan/filename=/ubuntu-11.10-desktop-i386.iso file=(loop)/preseed/mint.seed quiet splash lang=de noeject noprompt --
       initrd (loop)/casper/initrd.lz
}

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: system-config-printer-gnome 1.3.6+20110831-0ubuntu9
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
ApportVersion: 1.23-0ubuntu3
Architecture: i386
CasperVersion: 1.287
CupsErrorLog:

Date: Sat Apr 7 00:23:10 2012
ExecutablePath: /usr/share/system-config-printer/applet.py
InterpreterPath: /usr/bin/python2.7
LiveMediaBuild: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added.
MachineType: SAMSUNG ELECTRONICS CO., LTD. N150P
PackageArchitecture: all
Papersize: a4
ProcCmdline: /usr/bin/python /usr/share/system-config-printer/applet.py
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=(loop)/casper/vmlinuz boot=casper iso-scan/filename=/hostname-11.10-desktop-i386.iso file=(loop)/preseed/mint.seed quiet splash lang=de noeject noprompt --
PythonArgs: ['/usr/share/system-config-printer/applet.py']
SourcePackage: system-config-printer
Title: applet.py crashed with ImportError: could not import pango
Traceback: ImportError: could not import pango
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 12/20/2010
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 01GT.M026.20101220.RHU
dmi.board.asset.tag: SAMSUNG
dmi.board.name: N150P
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr01GT.M026.20101220.RHU:bd12/20/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnN150P:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnN150P:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
dmi.product.name: N150P
dmi.product.version: Not Applicable
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

Revision history for this message
Hans (hj-mue) wrote :
tags: removed: need-duplicate-check
information type: Private → Public
Revision history for this message
gf (gf-interlinks-deactivatedaccount) wrote :

Hello Hans,
Thank you for submitting this bug and reporting a problem with system-config-printer. You made this bug report in 2012 and Ubuntu has been updated since then.

Could you confirm that this is no longer a problem and that we can close the bug report?
If it is still a problem, are you still interested in finding a solution to this bug?
If you are, could you let us know, and in the current version, run the following (only once):
apport-collect BUGNUMBER
and upload the updated logs and and any other logs that are relevant for this particular issue.

Thank you again for helping make Ubuntu better.
G
[Ubuntu Bug Squad volunteer triager]

Changed in system-config-printer (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for system-config-printer (Ubuntu) because there has been no activity for 60 days.]

Changed in system-config-printer (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.