colord crashed with SIGABRT in raise(). This was after resizing partitions using gparted live.

Bug #941232 reported by Randall Guest
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
colord (Ubuntu)
New
Undecided
Unassigned

Bug Description

I added a hard drive, and partitioned it. I also shrunk the Linux partition on the boot drive and added a data partition. When booting off the HD, I use the F as prompted to fix the disc problems (/tmp is unavailable). Things work for a few minutes, then the mounting drives is not possible, applications crash or refuse to open, etc. The errors show that the / directory is read-only.

I booted using Ubuntu 11.10 live to try accessing the partitions through gparted from an Ubuntu environment. This probably won't work.

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: Sun Feb 26 02:59:19 2012
ExecutablePath: /usr/lib/x86_64-linux-gnu/colord/colord
LiveMediaBuild: Ubuntu 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

Revision history for this message
Randall Guest (rvguest) wrote :
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 this software 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.

visibility: private → public
visibility: private → public
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.