cairo-dock crashed with SIGABRT in cd_log_location()

Bug #764871 reported by Luciano Édipo on 2011-04-18
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cairo-dock (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: cairo-dock

problem by applying new theme

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: cairo-dock-core 2.2.0~4-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
Date: Mon Apr 18 12:53:48 2011
ExecutablePath: /usr/bin/cairo-dock
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: cairo-dock -c
ProcEnviron:
 LANGUAGE=pt_BR:en
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: cairo-dock
StacktraceTop:
 cd_log_location () from /usr/lib/libgldi.so.2
 ?? ()
 <signal handler called>
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
Title: cairo-dock crashed with SIGABRT in cd_log_location()
UpgradeStatus: Upgraded to natty on 2011-04-07 (11 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors: (nautilus:1933): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #762752, 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
Matthieu Baerts (matttbe) wrote :

Thank you for this bug report!
I think this bug has been fixed in the current 2.3 version.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers