Ubuntu
colord package

colord crashed with SIGSEGV

Bug #947333 reported by SarahSlean on 2012-03-05

This bug report is a duplicate of: Bug #840392: colord crashed with SIGSEGV. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	colord (Ubuntu)	New	Undecided	Unassigned

Bug Description

in ubuntu precise beta1

I have the top bar of windows orange colored transparent

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: colord 0.1.16-2
ProcVersionSignature: Ubuntu 3.2.0-18.28-generic-pae 3.2.9
Uname: Linux 3.2.0-17-generic-pae i686
ApportVersion: 1.94-0ubuntu1
Architecture: i386
Date: Sun Mar 4 13:10:04 2012
ExecutablePath: /usr/lib/i386-linux-gnu/colord/colord
ExecutableTimestamp: 1329176867
ProcCmdline: /usr/lib/i386-linux-gnu/colord/colord
ProcCwd: /
ProcEnviron:

SegvAnalysis:
Segfault happened at: 0xb5fdfa12: mov (%edx),%esi
PC (0xb5fdfa12) ok
source "(%edx)" (0x625f6d65) not located in a known VMA region (needed readable region)!
destination "%esi" ok
Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: colord
StacktraceTop:
?? () from /lib/i386-linux-gnu/libdbus-1.so.3
?? () from /lib/i386-linux-gnu/libdbus-1.so.3
?? () from /lib/i386-linux-gnu/libdbus-1.so.3
?? () from /lib/i386-linux-gnu/libdbus-1.so.3
?? () from /lib/i386-linux-gnu/libdbus-1.so.3
Title: colord crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Tags:

Revision history for this message

SarahSlean (yoda4) wrote on 2012-03-05:

Dependencies.txt Edit (2.9 KiB, text/plain; charset="utf-8")

Revision history for this message

SarahSlean (yoda4) wrote on 2012-03-05:

Every I log

Revision history for this message

Apport retracing service (apport) wrote on 2012-03-05: 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 #851607, 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.