systray.py crashed with SIGSEGV in gtk_widget_get_direction()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
hplip (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
systray.py crashed with SIGSEGV in gtk_widget_
ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: hplip-data 3.14.6-1ubuntu1
ProcVersionSign
Uname: Linux 3.16.0-5-generic x86_64
ApportVersion: 2.14.6-0ubuntu2
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue Aug 19 15:14:32 2014
ExecutablePath: /usr/share/
InstallationDate: Installed on 2014-05-16 (95 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
InterpreterPath: /usr/bin/python2.7
Lpstat:
device for CUPS-PDF-Printer: cups-pdf:/
device for HP-LaserJet-
device for HP_LaserJet_
device for HP_LaserJet_
PackageArchitec
Papersize: a4
PpdFiles:
HP_LaserJet_
CUPS-PDF-Printer: Generic CUPS-PDF Printer
HP-LaserJet-
HP_LaserJet_
ProcCmdline: /usr/bin/python /usr/bin/hp-systray -x
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x54a50c: mov 0x10(%rax),%rdi
PC (0x0054a50c) ok
source "0x10(%rax)" (0x00000010) not located in a known VMA region (needed readable region)!
destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: hplip
StacktraceTop:
gtk_widget_
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
QGtkStyle:
SystemImageInfo: Error: [Errno 2] Arquivo ou diretório não encontrado: 'system-image-cli'
Title: systray.py crashed with SIGSEGV in gtk_widget_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 11/19/2009
dmi.bios.vendor: Intel Corp.
dmi.bios.version: TCIBX10H.
dmi.board.
dmi.board.name: DH55HC
dmi.board.vendor: Intel Corporation
dmi.board.version: AAE70933-502
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCor
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 #1278729, 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.