colord crashed with SIGABRT in raise()

Bug #878921 reported by Eliah Kagan
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
colord (Ubuntu)
New
Undecided
Unassigned

Bug Description

I booted a Dell Studio XPS 8100 from the Lubuntu 10.10 Oneiric Ocelot amd64 desktop CD and selected the menu option to try without installing. The desktop came up and was fully functional, but I was immediately informed that colord (0.1.12-1ubuntu2) had crashed with SIGABRT in raise(). I have no other information about this crash, except that it appears similar to bug 827934 and bug 840146. Perhaps it is one of those bugs (once automatic symbolic retracing is done, it may be easier to judge that).

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: colord 0.1.12-1ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
ApportVersion: 1.23-0ubuntu3
Architecture: amd64
CasperVersion: 1.287
Date: Thu Oct 20 11:33:40 2011
ExecutablePath: /usr/lib/x86_64-linux-gnu/colord/colord
LiveMediaBuild: Lubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: /usr/lib/x86_64-linux-gnu/colord/colord
ProcEnviron:

Signal: 6
SourcePackage: colord
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
Title: colord crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: scanner

visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #827934, 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.

tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.