Do.exe crashed with SIGSEGV

Bug #1036274 reported by Iain Lane
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-do (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

On startup.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: gnome-do 0.9-1build1
ProcVersionSignature: Ubuntu 3.5.0-9.9-generic 3.5.0
Uname: Linux 3.5.0-9-generic x86_64
ApportVersion: 2.4-0ubuntu6
Architecture: amd64
CrashCounter: 1
Date: Mon Aug 13 17:14:24 2012
ExecutablePath: /usr/lib/gnome-do/Do.exe
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
InterpreterPath: /usr/bin/mono
ProcCmdline: /usr/bin/cli /usr/lib/gnome-do/Do.exe
SegvAnalysis:
 Segfault happened at: 0x7fa985ac9762 <malloc_consolidate+210>: mov 0x8(%rbx),%rdx
 PC (0x7fa985ac9762) ok
 source "0x8(%rbx)" (0x100000007) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-do
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: Do.exe crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip libvirtd lpadmin plugdev sambashare sbuild sudo

Revision history for this message
Iain Lane (laney) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? () from /tmp/tmp85HMhK/lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /tmp/tmp85HMhK/lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /tmp/tmp85HMhK/lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /tmp/tmp85HMhK/lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /tmp/tmp85HMhK/lib/x86_64-linux-gnu/libdbus-1.so.3

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 gnome-do (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

libdrm-intel1 version 2.4.37-0ubuntu2 required, but 2.4.38-0ubuntu1 is available
outdated debug symbol package for initscripts: package version 2.88dsf-13.10ubuntu13 dbgsym version 2.88dsf-13.10ubuntu11.1
libdrm-radeon1 version 2.4.37-0ubuntu2 required, but 2.4.38-0ubuntu1 is available
libdrm-nouveau1a version 2.4.37-0ubuntu2 required, but 2.4.38-0ubuntu1 is available
libkms1 version 2.4.37-0ubuntu2 required, but 2.4.38-0ubuntu1 is available
libdrm2 version 2.4.37-0ubuntu2 required, but 2.4.38-0ubuntu1 is available
outdated debug symbol package for module-init-tools: package version 3.16-1ubuntu3 dbgsym version 3.16-1ubuntu2

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

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.