(Radeon) colord-sane crashed with SIGSEGV

Bug #1028860 reported by Nice Testhouse
This bug report is a duplicate of:  Bug #1029264: colord-sane crashed with SIGSEGV. Edit Remove
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
colord (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Ubuntu 12.10 Quantal (Radeon)- with ppa: SIL2100

System error pop-up window was shown to user during normal activity on machine. No specific action was done by user which produced this bug. See attached Screenshot.

Have pasted here, the message from the window indicating to user that the problem could not be reported as a bug.

The problem happened with the program /usr/lib/ubuntu-release-upgrader/do-partial-upgrade which changed since the crash occurred.

The problem cannot be reported:

You have some obsolete package versions installed. Please upgrade the following packages and check if the problem still occurs:

libtelepathy-glib0

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: colord 0.1.21-1
ProcVersionSignature: Ubuntu 3.5.0-6.6-generic 3.5.0
Uname: Linux 3.5.0-6-generic i686
ApportVersion: 2.4-0ubuntu5
Architecture: i386
Date: Tue Jul 24 17:41:09 2012
ExecutablePath: /usr/lib/i386-linux-gnu/colord/colord-sane
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120713.1)
ProcCmdline: /usr/lib/i386-linux-gnu/colord/colord-sane
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0xb544aa83: mov 0x8(%eax),%edx
 PC (0xb544aa83) ok
 source "0x8(%eax)" (0x00000009) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL 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-sane crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Nice Testhouse (testhouse) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 _dbus_counter_adjust_unix_fd (counter=0x1, delta=0) at ../../dbus/dbus-resources.c:181
 _dbus_message_add_counter_link (message=0x880fe00, link=0x880f99c) at ../../dbus/dbus-message.c:254
 _dbus_message_add_counter (message=0x880fe00, counter=0x880cc28) at ../../dbus/dbus-message.c:278
 _dbus_transport_queue_messages (transport=0x880c938) at ../../dbus/dbus-transport.c:1138
 do_reading (transport=0x880c938) at ../../dbus/dbus-transport-socket.c:851

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in colord (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-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.