colord crashed with SIGSEGV

Bug #981154 reported by Fouad
This bug report is a duplicate of:  Bug #840392: colord crashed with SIGSEGV. Edit Remove
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
colord (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Description: Ubuntu precise (development branch)
Release: 12.04

apt-cache policy colord
colord:
  Installed: 0.1.16-2
  Candidate: 0.1.16-2
  Version table:
 *** 0.1.16-2 0
        500 http://nl.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
        100 /var/lib/dpkg/status

After login I always get this message dat colord crashed.. this was also the issue before my update minutes ago, so not fixed yet.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: colord 0.1.16-2
Uname: Linux 3.3.0-030300-generic x86_64
ApportVersion: 2.0.1-0ubuntu2
Architecture: amd64
Date: Sat Apr 7 02:20:04 2012
ExecutablePath: /usr/lib/x86_64-linux-gnu/colord/colord
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
ProcCmdline: /usr/lib/x86_64-linux-gnu/colord/colord
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0x7ff2b507366c: mov (%rax),%rdx
 PC (0x7ff2b507366c) ok
 source "(%rax)" (0x7ff200000001) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: colord
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
Title: colord crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Fouad (fouad-ramsis) 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 #840392, 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
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in colord (Ubuntu):
status: New → Confirmed
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.