cupsd crashed with SIGSEGV

Bug #628531 reported by Tobin Davis
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
cups (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: cups

Crashed on boot of http://cdimage.ubuntu.com/kubuntu/ports/daily-preinstalled/20100901/maverick-preinstalled-desktop-armel+omap.img.gz after logging in for the first time.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: cups 1.4.4-3
ProcVersionSignature: Ubuntu 2.6.35-19.28-omap 2.6.35.3
Uname: Linux 2.6.35-19-omap armv7l
Architecture: armel
Date: Wed Sep 1 22:22:28 2010
ExecutablePath: /usr/sbin/cupsd
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added.
Lspci:
 Error: command ['lspci', '-vvnn'] failed with exit code 1: pcilib: Cannot open /proc/bus/pci
 lspci: Cannot find any working access method.
Lsusb:
 Bus 001 Device 005: ID 05d5:6781 Super Gate Technology Co., Ltd
 Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
 Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
ProcCmdLine: quiet splash ro elevator=noop vram=12M omapfb.mode=dvi:1280x720MR-16@60 root=UUID=27beae0f-7ef5-4c17-ae15-f77bd88d425f fixrtc
ProcCmdline: /usr/sbin/cupsd -C /etc/cups/cupsd.conf
ProcEnviron: PATH=(custom, no user)
Signal: 11
SourcePackage: cups
Stacktrace:
 #0 0x400cd5ec in ?? () from /lib/ld-linux.so.3
 No symbol table info available.
 #1 0x400c7b54 in ?? () from /lib/ld-linux.so.3
 No symbol table info available.
 Backtrace stopped: previous frame identical to this frame (corrupt stack?)
StacktraceTop:
 ?? () from /lib/ld-linux.so.3
 ?? () from /lib/ld-linux.so.3
Title: cupsd crashed with SIGSEGV
UserGroups:

Revision history for this message
Tobin Davis (gruemaster) wrote :
Tobin Davis (gruemaster)
visibility: private → public
tags: added: iso-testing
Steve Langasek (vorlon)
tags: added: arm-porting-queue
Revision history for this message
Jani Monoses (jani) wrote :

did this still happen on natty and on 10.10 final images ?

Revision history for this message
Jani Monoses (jani) wrote :

Probably fixed as it does not happen in newer images.

Changed in cups (Ubuntu):
status: New → Fix Released
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.