cupsd SIGSEGVs after resuming suspend
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cups (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
I had a queued task for a disconnected remote printer when I suspended my laptop, but when I resumed, cups had crashed.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: cups 1.4.6-5ubuntu1.4
ProcVersionSign
Uname: Linux 2.6.38-11-generic x86_64
NonfreeKernelMo
Architecture: amd64
Date: Wed Oct 12 10:12:15 2011
ExecutablePath: /usr/sbin/cupsd
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
Lpstat: device for Cyrillus: ipp://192.
MachineType: TOSHIBA Satellite L550
Papersize: a4
ProcAttrCurrent: /usr/sbin/cupsd (enforce)
ProcCmdline: /usr/sbin/cupsd -F
ProcEnviron: PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x7f21df8a95d1: movdqu (%rdi),%xmm1
PC (0x7f21df8a95d1) ok
source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%xmm1" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: cups
StacktraceTop:
?? () from /lib/x86_
?? () from /lib/x86_
?? () from /lib/x86_
dbus_message_
?? ()
Title: cupsd crashed with SIGSEGV in dbus_message_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 10/28/2009
dmi.bios.vendor: TOSHIBA
dmi.bios.version: V1.80
dmi.board.name: KTWAA
dmi.board.vendor: TOSHIBA
dmi.board.version: 1.00
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.
dmi.modalias: dmi:bvnTOSHIBA:
dmi.product.name: Satellite L550
dmi.product.
dmi.sys.vendor: TOSHIBA
Changed in cups (Ubuntu): | |
status: | New → Invalid |
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 #768274, 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.