hpijs crashed with SIGSEGV

[James_in_CA]

Binary package hint: hplip

Occurred shortly after upgrade to KK.

ProblemType: Crash
Architecture: i386
Date: Sat Oct 31 15:36:56 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/hpijs
Lpstat: device for Deskjet-F300-series: hp:/usb/Deskjet_F300_series?serial=CN64LF51D204KH
Lsusb:
 Bus 002 Device 004: ID 0aec:3260 Neodio Technologies Corp. 7-in-1 Card Reader
 Bus 002 Device 002: ID 046d:c019 Logitech, Inc. Optical Tilt Wheel Mouse
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: BIOSTAR Group N61PA-M2S
NonfreeKernelModules: nvidia
Package: hpijs 3.9.8-1ubuntu2
Papersize: letter
PpdFiles: Deskjet-F300-series: HP Deskjet f300 Series hpijs, 3.9.8
ProcCmdLine: root=/dev/mapper/nvidia_cfffbfga1 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: 12/05/2007
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: N61PA-M2S
dmi.board.vendor: BIOSTAR Group
dmi.board.version: 1.0
dmi.chassis.type: 3
dmi.chassis.vendor: BIOSTAR Group
dmi.chassis.version: N61PA-M2S
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd12/05/2007:svnBIOSTARGroup:pnN61PA-M2S:pvr1.0:rvnBIOSTARGroup:rnN61PA-M2S:rvr1.0:cvnBIOSTARGroup:ct3:cvrN61PA-M2S:
dmi.product.name: N61PA-M2S
dmi.product.version: 1.0
dmi.sys.vendor: BIOSTAR Group

[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.