cupsd crashed with SIGABRT in raise()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cups (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Just completed 13.10 update/upgrade. Only applications started were Firefox, my GTK app, and VLC running radio streaming.
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: cups-daemon 1.6.3-1
ProcVersionSign
Uname: Linux 3.9.0-7-generic x86_64
ApportVersion: 2.11-0ubuntu1
Architecture: amd64
CupsErrorLog:
Date: Fri Jul 26 09:36:42 2013
ExecutablePath: /usr/sbin/cupsd
InstallationDate: Installed on 2013-06-28 (27 days ago)
InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 (20130626)
Lpstat: device for HP_Photosmart_1210: usb://HP/
MachineType: Si G41M-P33
MarkForUpload: True
Papersize: letter
PpdFiles: HP_Photosmart_1210: HP Photosmart c4100 Series, hpcups 3.13.4
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_
__assert_fail () from /lib/x86_
?? () from /usr/lib/
Title: cupsd crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 01/05/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V7.7
dmi.board.
dmi.board.name: G41M-P33 (MS-7592)
dmi.board.vendor: MSI
dmi.board.version: 3.0
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: G41M-P33
dmi.product.
dmi.sys.vendor: Si
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 #1131854, 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.