systray.py crashed with SIGSEGV

Bug #856798 reported by Steve B
This bug report is a duplicate of:  Bug #860680: systray.py crashed with SIGSEGV. Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
hplip (Ubuntu)
New
Medium
Unassigned

Bug Description

Crash on startup

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: hplip-data 3.11.7-1ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu1
Architecture: i386
Date: Thu Sep 22 21:52:13 2011
ExecutablePath: /usr/share/hplip/systray.py
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110803.1)
InterpreterPath: /usr/bin/python2.7
Lpstat:
 device for OfficeJet-6100-Series: hp:/usb/OfficeJet_6100_Series?serial=MY33AF21PF2R
 device for OfficeJet-6100-Series-Fax: hpfax:/usb/OfficeJet_6100_Series?serial=MY33AF21PF2R
MachineType: SAMSUNG ELECTRONICS CO., LTD. R580/R590
PackageArchitecture: all
Papersize: a4
PpdFiles:
 OfficeJet-6100-Series: HP Officejet 6100 Series hpijs, 3.11.7
 OfficeJet-6100-Series-Fax: HP Fax hpcups
ProcCmdline: python /usr/bin/hp-systray
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-11-generic root=UUID=9e91860e-f71f-4e0a-ae32-cbc83fe564f8 ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x80dce34: mov 0x8(%eax),%eax
 PC (0x080dce34) ok
 source "0x8(%eax)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: hplip
StacktraceTop:
 ?? () from /usr/lib/i386-linux-gnu/libgdk-x11-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgdk-x11-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgdk-x11-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgdk-x11-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgdk-x11-2.0.so.0
Title: systray.py crashed with SIGSEGV
UpgradeStatus: Upgraded to oneiric on 2011-08-27 (26 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers
dmi.bios.date: 03/31/2010
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 08JB.M032.20100331.hkk
dmi.board.asset.tag: Tag 12345
dmi.board.name: R580/R590
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr08JB.M032.20100331.hkk:bd03/31/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR580/R590:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR580/R590:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
dmi.product.name: R580/R590
dmi.product.version: Not Applicable
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

Revision history for this message
Steve B (stevebsame) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 setup_context (registry=<synthetic pointer>, module=<synthetic pointer>, lineno=<synthetic pointer>, filename=<synthetic pointer>, stack_level=1) at ../Python/_warnings.c:449
 do_warn (message="gdk_xsettings_watch_cb(): Couldn't find window to unwatch", category=<type at remote 0x9fc8ae4>, stack_level=1) at ../Python/_warnings.c:594
 PyErr_WarnEx (category=<type at remote 0x9fc8ae4>, text=0xa397980 "gdk_xsettings_watch_cb(): Couldn't find window to unwatch", stack_level=1) at ../Python/_warnings.c:720
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in hplip (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
visibility: private → public
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.