cupsd crashed with SIGSEGV

Bug #1286543 reported by Joel Peláez Jorge
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cups (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Sometimes cupsd crashes with a SIGSEGV, it isn't printed or anything.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: cups 1.6.1-0ubuntu11.5
ProcVersionSignature: Ubuntu 3.5.0-46.70-generic 3.5.7.27
Uname: Linux 3.5.0-46-generic x86_64
ApportVersion: 2.6.1-0ubuntu13
Architecture: amd64
CrashCounter: 1
Date: Sat Mar 1 07:55:04 2014
ExecutablePath: /usr/sbin/cupsd
InstallationDate: Installed on 2013-07-18 (225 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
Lpstat: device for Epson-Stylus-TX220: usb://EPSON/Stylus%20TX220?serial=4D46444B3037393466&interface=1
MachineType: Hewlett-Packard s5602la
MarkForUpload: True
Papersize: letter
PpdFiles: Epson-Stylus-TX220: Epson Stylus TX220 Series - epson-inkjet-printer 1.0.0-1lsb3.2 (Seiko Epson Corporation LSB 3.2)
ProcAttrCurrent: /usr/sbin/cupsd (enforce)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.5.0-46-generic root=UUID=ce1a8905-76ab-46d7-b5ce-a925138b6c49 ro crashkernel=384M-2G:64M,2G-:128M
ProcEnviron:
 PATH=(custom, no user)
 TERM=linux
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-46-generic root=UUID=ce1a8905-76ab-46d7-b5ce-a925138b6c49 ro crashkernel=384M-2G:64M,2G-:128M
SegvAnalysis:
 Segfault happened at: 0x7fce68fc0d00: movl $0xffffffff,0x4(%rdi)
 PC (0x7fce68fc0d00) ok
 source "$0xffffffff" ok
 destination "0x4(%rdi)" (0x00000004) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: cups
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
Title: cupsd crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 06/15/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 6.18
dmi.board.name: 2A99
dmi.board.vendor: PEGATRON CORPORATION
dmi.board.version: 6.01
dmi.chassis.asset.tag: MXX0440SRG
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr6.18:bd06/15/2011:svnHewlett-Packard:pns5602la:pvr:rvnPEGATRONCORPORATION:rn2A99:rvr6.01:cvnHewlett-Packard:ct3:cvrChassisVersion:
dmi.product.name: s5602la
dmi.sys.vendor: Hewlett-Packard
mtime.conffile..etc.cups.cupsd.conf: 2014-02-23T13:22:38.640590

Revision history for this message
Joel Peláez Jorge (joelpelaez) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 _dbus_watch_invalidate (watch=0x0) at ../../dbus/dbus-watch.c:171
 free_watches (transport=transport@entry=0x7fce6a96bf40) at ../../dbus/dbus-transport-socket.c:83
 socket_disconnect (transport=0x7fce6a96bf40) at ../../dbus/dbus-transport-socket.c:987
 _dbus_transport_disconnect (transport=0x7fce6a96bf40) at ../../dbus/dbus-transport.c:509
 _dbus_transport_disconnect (transport=0x7fce6a96bf40) at ../../dbus/dbus-transport.c:500

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in cups (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

Can you try a live system of Ubuntu Trusty (14.04 under development)? There the problem should be fixed.

Changed in cups (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for cups (Ubuntu) because there has been no activity for 60 days.]

Changed in cups (Ubuntu):
status: Incomplete → Expired
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.