cupsd crashed with SIGSEGV in dbus_connection_send_with_reply()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cups (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
This seems the same as 1063555 but that one was marked as invalid for not enough infomation.
I have just updated and rebooted, so everything should be current
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: cups-daemon 1.6.1-1ubuntu1
ProcVersionSign
Uname: Linux 3.8.0-1-generic x86_64
ApportVersion: 2.8-0ubuntu2
Architecture: amd64
Date: Sat Jan 19 07:35:04 2013
ExecutablePath: /usr/sbin/cupsd
InstallationDate: Installed on 2011-11-29 (417 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111126)
Lpstat: device for Deskjet-
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
MarkForUpload: True
Papersize: a4
PpdFiles:
HP_HP_
Deskjet-
ProcAttrCurrent: /usr/sbin/cupsd (enforce)
ProcCmdline: BOOT_IMAGE=
ProcEnviron:
PATH=(custom, no user)
TERM=linux
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x7f47438bbcec: mov %rdx,0x8(%rax)
PC (0x7f47438bbcec) ok
source "%rdx" ok
destination "0x8(%rax)" (0x00000008) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: cups
StacktraceTop:
?? () from /lib/x86_
?? () from /lib/x86_
?? () from /lib/x86_
dbus_connectio
dbus_connectio
Title: cupsd crashed with SIGSEGV in dbus_connection
UpgradeStatus: Upgraded to raring on 2012-12-04 (46 days ago)
UserGroups:
dmi.bios.date: 07/13/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.30
dmi.board.name: Z77 Pro4-M
dmi.board.vendor: ASRock
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: To Be Filled By O.E.M.
dmi.product.
dmi.sys.vendor: To Be Filled By O.E.M.
mtime.conffile.
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1102084, 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.