gutenprint.5.2 crashed with SIGSEGV

Bug #335661 reported by Peter T Hayward
80
This bug affects 3 people
Affects Status Importance Assigned to Milestone
gutenprint (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Just after logging after a reboot.

ProblemType: Crash
Architecture: i386
DistroRelease: /usr/bin/lsb_release:81: DeprecationWarning: the sets module is deprecated import sets Ubuntu 9.04
ExecutablePath: /usr/lib/cups/driver/gutenprint.5.2
Package: cups-driver-gutenprint 5.2.3-0ubuntu1
ProcCmdline: gutenprint.5.2 list
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_GB.UTF8
Signal: 11
SourcePackage: gutenprint
Stacktrace:
 #0 0xb7f2dd18 in ?? () from /lib/ld-linux.so.2
 #1 0xb7f2dd41 in ?? () from /lib/ld-linux.so.2
 #2 0xb7f2c932 in ?? () from /lib/ld-linux.so.2
 #3 0xb7f18c1d in ?? () from /lib/ld-linux.so.2
 #4 0xb7f18817 in ?? () from /lib/ld-linux.so.2
StacktraceTop:
 ?? () from /lib/ld-linux.so.2
 ?? () from /lib/ld-linux.so.2
 ?? () from /lib/ld-linux.so.2
 ?? () from /lib/ld-linux.so.2
 ?? () from /lib/ld-linux.so.2
Title: gutenprint.5.2 crashed with SIGSEGV
Uname: Linux 2.6.28-8-generic i686
UserGroups:

Revision history for this message
Peter T Hayward (energonic) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:check_one_fd () from /lib/ld-linux.so.2
__libc_check_standard_fds () from /lib/ld-linux.so.2
_dl_sysdep_start () from /lib/ld-linux.so.2
_dl_start () from /lib/ld-linux.so.2
_start () from /lib/ld-linux.so.2

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in gutenprint:
importance: Undecided → Medium
Revision history for this message
phil (pjentwisle) wrote :

attempted to update my jaunty devel install

encountered this after reboot

Changed in gutenprint (Ubuntu):
status: New → Confirmed
Revision history for this message
dino99 (9d9) wrote :

This version is outdated and no more supported

Changed in gutenprint (Ubuntu):
status: Confirmed → Invalid
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.