udev-configure-printer crashed with SIGSEGV in __libc_start_main()

Bug #547002 reported by buzz
36
This bug affects 4 people
Affects Status Importance Assigned to Milestone
system-config-printer (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: system-config-printer

Scanner/Printer HP F2480

ProblemType: Crash
Architecture: i386
CupsErrorLog:
 E [25/Mar/2010:09:37:49 +0100] Unable to remove temporary file "/var/spool/cups/tmp/.hplip" - Is a directory
 E [25/Mar/2010:15:41:29 +0100] [cups-driverd] Bad driver information file "/usr/share/cups/drv/sample.drv"!
 E [25/Mar/2010:16:53:45 +0100] [cups-driverd] Bad driver information file "/usr/share/cups/drv/sample.drv"!
Date: Thu Mar 25 16:53:42 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /lib/udev/udev-configure-printer
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100224.1)
Lpstat: device for Deskjet-F2400-series: hp:/usb/Deskjet_F2400_series?serial=CN9CHB846305BS
MachineType: SAMSUNG ELECTRONICS CO., LTD. P560
NonfreeKernelModules: nvidia
Package: system-config-printer-udev 1.1.17+20100217-0ubuntu4
Papersize: a4
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
PpdFiles: Deskjet-F2400-series: HP Deskjet f2400 Series, hpcups 3.10.2
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-16-generic root=UUID=8574a54e-1812-4a01-973c-66eecf80ef1d ro quiet splash
ProcCmdline: /lib/udev/udev-configure-printer add /devices/pci0000:00/0000:00:1a.7/usb1/1-1/1-1:1.1
ProcEnviron:

ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
SegvAnalysis:
 Segfault happened at: 0x804acb5: movzbl (%edx),%ecx
 PC (0x0804acb5) ok
 source "(%edx)" (0x00000007) not located in a known VMA region (needed readable region)!
 destination "%ecx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: system-config-printer
StacktraceTop:
 ?? ()
 ?? ()
 __libc_start_main (main=0x804c050, argc=3,
 ?? ()
Title: udev-configure-printer crashed with SIGSEGV in __libc_start_main()
Uname: Linux 2.6.32-16-generic i686
UserGroups:

dmi.bios.date: 01/12/2010
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 11LU.MP00.20100112.hkk
dmi.board.name: P560
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr11LU.MP00.20100112.hkk:bd01/12/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnP560:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnP560:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
dmi.product.name: P560
dmi.product.version: Not Applicable
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

Revision history for this message
buzz (buzz2) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 do_add (cmd=<value optimized out>,
 ?? ()
 __libc_start_main (main=0x804c050 <main+16>, argc=3,
 _start ()

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 system-config-printer (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Robert Roth (evfool) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

visibility: private → public
Changed in system-config-printer (Ubuntu):
status: New → Confirmed
Revision history for this message
dino99 (9d9) wrote :

This version has expired long ago; no more supported

Changed in system-config-printer (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.