system-config-printer.py crashed with SIGSEGV in fileno_unlocked()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
system-config-printer (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I have been unable to define my Hp LazerJet P1102w. I am not very experienced in Ubuntu and the System is not detecting the Printer automatically. Any hints?
This is the latest Ubuntu 12.04 Pangolin.
My best regards. Paulo.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: system-
ProcVersionSign
Uname: Linux 3.2.0-19-
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
CurrentDmesg: [ 1175.312081] system-
Date: Sat Mar 17 21:33:16 2012
ExecutablePath: /usr/share/
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301)
InterpreterPath: /usr/bin/python2.7
Lpstat:
device for HP-LaserJet-
device for HP-LaserJet-
MachineType: TOSHIBA Satellite A505
PackageArchitec
Papersize: letter
PpdFiles:
HP-LaserJet-
HP-LaserJet-
ProcCmdline: /usr/bin/python /usr/share/
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0xb7395caf <fileno_
PC (0xb7395caf) ok
source "(%eax)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: system-
StacktraceTop:
fileno_unlocked () from /lib/i386-
?? () from /usr/lib/
?? ()
PyObject_Call ()
PyEval_EvalFrameEx ()
Title: system-
UpgradeStatus: Upgraded to precise on 2012-03-15 (2 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 05/25/2010
dmi.bios.vendor: INSYDE
dmi.bios.version: 1.80
dmi.board.
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: Base Board Version
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.
dmi.modalias: dmi:bvnINSYDE:
dmi.product.name: Satellite A505
dmi.product.
dmi.sys.vendor: TOSHIBA
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #951001, 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.