colord crashed with SIGSEGV in cd_device_register_object()

Bug #1039620 reported by vijayakrishna Rowthu
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
colord (Ubuntu)
New
Undecided
Unassigned

Bug Description

colord crashed with SIGSEGV in cd_device_register_object()

Description: Ubuntu quantal (development branch)
Release: 12.10

gnome-panel:
  Installed: 1:3.5.4-0ubuntu2
  Candidate: 1:3.5.4-0ubuntu2
  Version table:
 *** 1:3.5.4-0ubuntu2 0
        500 http://in.archive.ubuntu.com/ubuntu/ quantal/universe amd64 Packages
        100 /var/lib/dpkg/status

I got this crash msg right after logging in. And to this , my previous attempt was to log-in in my guest account ,which didn't happen and the screen was blank when i select Guest account.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: colord 0.1.21-1
ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2
Uname: Linux 3.5.0-11-generic x86_64
ApportVersion: 2.4-0ubuntu8
Architecture: amd64
Date: Tue Aug 21 00:22:52 2012
ExecutablePath: /usr/lib/x86_64-linux-gnu/colord/colord
ProcCmdline: /usr/lib/x86_64-linux-gnu/colord/colord
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0x40b1dd <cd_device_register_object+157>: mov 0x8(%rax),%rbx
 PC (0x0040b1dd) ok
 source "0x8(%rax)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rbx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: colord
StacktraceTop:
 cd_device_register_object ()
 ?? ()
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: colord crashed with SIGSEGV in cd_device_register_object()
UpgradeStatus: Upgraded to quantal on 2012-08-11 (10 days ago)
UserGroups: scanner

Revision history for this message
vijayakrishna Rowthu (2rowthu) 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 #1021374, 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
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.