cairo-dock crashed with SIGSEGV

Bug #941053 reported by Marcos K
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
cairo-dock (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

this happens immediately at startup

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: cairo-dock-core 2.4.0~2-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-16.29-generic 3.0.20
Uname: Linux 3.0.0-16-generic i686
ApportVersion: 1.23-0ubuntu4
Architecture: i386
Date: Sat Feb 25 19:40:52 2012
ExecutablePath: /usr/bin/cairo-dock
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
ProcCmdline: cairo-dock
SegvAnalysis:
 Segfault happened at: 0x2d4ea8b: mov 0x18(%edi),%eax
 PC (0x02d4ea8b) ok
 source "0x18(%edi)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: cairo-dock
Stacktrace:
 #0 0x02d4ea8b in ?? () from /usr/lib/fglrx/libGL.so.1
 No symbol table info available.
 #1 0x09645ed0 in ?? ()
 No symbol table info available.
 Backtrace stopped: Not enough registers or memory available to unwind further
StacktraceTop:
 ?? () from /usr/lib/fglrx/libGL.so.1
 ?? ()
Title: cairo-dock crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

Revision history for this message
Marcos K (g-ubuntu-com-y) wrote :
visibility: private → public
Revision history for this message
Marcos K (g-ubuntu-com-y) wrote :

duplicate of another recent Apport crash? this happened immediately at startup

Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 0x02d4ea8b in ?? () from /tmp/tmpQJtj9d/usr/lib/fglrx/libGL.so.1
 No symbol table info available.
 #1 0x09645ed0 in ?? ()
 No symbol table info available.
 Backtrace stopped: Not enough registers or memory available to unwind further
StacktraceTop:
 ?? () from /tmp/tmpQJtj9d/usr/lib/fglrx/libGL.so.1
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in cairo-dock (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:

outdated debug symbol package for libavahi-common3: package version 0.6.30-4ubuntu1 dbgsym version 0.6.30-0ubuntu2
outdated debug symbol package for libtiff4: package version 3.9.5-1ubuntu1 dbgsym version 3.9.4-5ubuntu6
libxfixes3 version 1:5.0-4ubuntu1newyork1 required, but 1:5.0-4 is available
outdated debug symbol package for libgpg-error0: package version 1.10-0.3ubuntu1 dbgsym version 1.10-0.2ubuntu1
outdated debug symbol package for libavahi-client3: package version 0.6.30-4ubuntu1 dbgsym version 0.6.30-0ubuntu2
outdated debug symbol package for passwd: package version 1:4.1.4.2+svn3283-3ubuntu2 dbgsym version 1:4.1.4.2+svn3283-3ubuntu1
outdated debug symbol package for libdatrie1: package version 0.2.4-3 dbgsym version 0.2.4-1
outdated debug symbol package for libthai0: package version 0.1.15-2 dbgsym version 0.1.14-2ubuntu1
outdated debug symbol package for libltdl7: package version 2.4-2ubuntu1 dbgsym version 2.2.6b-2ubuntu3
outdated debug symbol package for gtk2-engines-pixbuf: package version 2.24.6-0ubuntu5 dbgsym version 2.24.4-0ubuntu2

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-i386-retrace
Revision history for this message
Matthieu Baerts (matttbe) wrote :

Hello and thank you for this bug report.

I'm not sure that this bug is due to Cairo-Dock because it crashes in /usr/lib/fglrx/libGL.so.1 (ATI drivers)
But is it possible to install the current beta version (Cairo-Dock 3.0.0.0beta1)? If it still crashes, can you give us a backtrace produced by gdb? It's not difficult, simply have a look to this wiki page ;) : http://wiki.glx-dock.org/?p=ddd

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.