cupsd crashed with SIGSEGV in dbus_message_iter_append_basic()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cups (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: cups
reported by system
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: cups 1.4.6-4
ProcVersionSign
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
CrashCounter: 1
Date: Wed Apr 13 14:02:54 2011
ExecutablePath: /usr/sbin/cupsd
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110321)
Lpstat:
device for Deskjet-
device for Hewlett-
device for HP_LaserJet_P1005: ipp://192.
device for Stylus-CX6600: ///dev/null
MachineType: Dell Inc. Latitude D531
Papersize: a4
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcAttrCurrent: /usr/sbin/cupsd (enforce)
ProcCmdline: /usr/sbin/cupsd -F
ProcEnviron: PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x2a4706: movdqu (%edi),%xmm1
PC (0x002a4706) ok
source "(%edi)" (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/i386-
?? () from /lib/i386-
?? () from /lib/i386-
dbus_message_
?? ()
Title: cupsd crashed with SIGSEGV in dbus_message_
UpgradeStatus: Upgraded to natty on 2011-03-31 (13 days ago)
UserGroups:
dmi.bios.date: 12/16/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: 0XM006
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Latitude D531
dmi.sys.vendor: Dell Inc.
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 #754567, 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.