cupsd crashed with SIGABRT in raise()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cups (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
The crash happened right after using ctrl-alt-f1 to switch to a text terminal and then back to the x display on vt7. I had a few hours earlier restarted gnome-shell in :0 from vt1 after it had crashed.
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: cups 1.6.1-0ubuntu8
ProcVersionSign
Uname: Linux 3.5.0-15-generic x86_64
ApportVersion: 2.5.3-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Sat Sep 29 08:01:45 2012
ExecutablePath: /usr/sbin/cupsd
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120902)
Lpstat:
device for FreeDriverAppSo
device for FreeDriverCLP-325: dnssd:/
device for PropDriverAppSo
device for PropSamsungCLP325: dnssd:/
MachineType: Dell Inc. Inspiron 1545
Papersize: letter
PpdFiles:
PropDriverAppS
FreeDriverAppS
PropSamsungCLP325: Samsung CLP-320 Series (SPL-C)
FreeDriverCLP-325: Samsung CLP-325 Foomatic/foo2qpdl (recommended)
ProcAttrCurrent: /usr/sbin/cupsd (enforce)
ProcCmdline: BOOT_IMAGE=
ProcEnviron:
PATH=(custom, no user)
TERM=linux
ProcKernelCmdLine: BOOT_IMAGE=
Signal: 6
SourcePackage: cups
StacktraceTop:
raise () from /lib/x86_
abort () from /lib/x86_
?? () from /lib/x86_
?? () from /lib/x86_
?? () from /lib/x86_
Title: cupsd crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 12/07/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A14
dmi.board.name: 0G848F
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Inspiron 1545
dmi.sys.vendor: Dell Inc.
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 #1034045, 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.