hpijs crashed with SIGSEGV

[Peter van der Laan]

Binary package hint: hplip

Error occurs randomly.

ProblemType: Crash
Architecture: i386
Date: Mon Nov 2 10:33:38 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/hpijs
Lpstat:
 device for Deskjet_F4100_series: hp:/usb/Deskjet_F4100_series?serial=CN78Q3W0G504TJ
 device for HP-Deskjet-f4100: smb://WERKGROEP/HOMEXP/HPF4100
 device for HP-Deskjet-f4100-2: smb://WERKGROEP/HOMEXP/HPF4100
MachineType: Acer Aspire L3600
NonfreeKernelModules: wl
Package: hpijs 3.9.8-1ubuntu2
Papersize: letter
PpdFiles:
 Deskjet_F4100_series: HP Deskjet f4100 Series hpijs, 3.9.8
 HP-Deskjet-f4100: HP Deskjet f4100 Series hpijs, 3.9.8
 HP-Deskjet-f4100-2: HP Deskjet f4100 Series hpijs, 3.9.8
ProcCmdLine: root=UUID=16d7b5c8-d230-4b06-946a-5c5825c3553c ro quiet splash
ProcCmdline: hpijs
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x806911b: cmpb $0x0,(%eax,%ecx,1)
 PC (0x0806911b) ok
 source "$0x0" ok
 destination "(%eax,%ecx,1)" (0x00000257) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: hplip
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: hpijs crashed with SIGSEGV
Uname: Linux 2.6.31-14-generic i686
UserGroups:

dmi.bios.date: 09/24/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: R01-A1
dmi.board.name: G31
dmi.board.vendor: Acer
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A1:bd09/24/2007:svnAcer:pnAspireL3600:pvrR01-A1:rvnAcer:rnG31:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: Aspire L3600
dmi.product.version: R01-A1
dmi.sys.vendor: Acer

[Apport retracing service (apport)]

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 #278521, 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.