cairo-dock crashed with SIGSEGV in _on_device_changed()

Bug #1304994 reported by Aaron Fried
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cairo-dock-plug-ins (Ubuntu)
Incomplete
Medium
Matthieu Baerts

Bug Description

Fallback cairo-dock crashed in xubuntu 14.04

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: cairo-dock-core 3.3.99.beta1.2.really.3.3.2-0ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
Uname: Linux 3.13.0-23-generic i686
ApportVersion: 2.14.1-0ubuntu1
Architecture: i386
CurrentDesktop: XFCE
Date: Wed Apr 9 06:49:02 2014
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/cairo-dock
InstallationDate: Installed on 2014-04-08 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily i386 (20140408)
ProcCmdline: cairo-dock -A
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x805496a <_start+1106>: mov (%eax),%eax
 PC (0x0805496a) ok
 source "(%eax)" (0x00000049) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: cairo-dock
Stacktrace:
 #0 0x0805496a in _start ()
 No symbol table info available.
StacktraceTop: _start ()
Title: cairo-dock crashed with SIGSEGV in _start()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

StacktraceTop:
 _on_device_changed (pDevice=0x89fe700, data=0x0) at /build/buildd/cairo-dock-plug-ins-3.3.99.beta1.2.really.3.3.2/powermanager/src/powermanager-upower.c:191
 g_cclosure_marshal_VOID__VOIDv (closure=0x8b37470, return_value=0x0, instance=0x89fe700, args=0xbfe6a57c "", marshal_data=0x0, n_params=0, param_types=0x0) at /build/buildd/glib2.0-2.40.0/./gobject/gmarshal.c:115
 _g_closure_invoke_va (closure=closure@entry=0x8b37470, return_value=return_value@entry=0x0, instance=instance@entry=0x89fe700, args=args@entry=0xbfe6a57c "", n_params=0, param_types=0x0) at /build/buildd/glib2.0-2.40.0/./gobject/gclosure.c:831
 g_signal_emit_valist (instance=instance@entry=0x89fe700, signal_id=signal_id@entry=230, detail=detail@entry=0, var_args=var_args@entry=0xbfe6a57c "") at /build/buildd/glib2.0-2.40.0/./gobject/gsignal.c:3215
 g_signal_emit (instance=instance@entry=0x89fe700, signal_id=230, detail=detail@entry=0) at /build/buildd/glib2.0-2.40.0/./gobject/gsignal.c:3363

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 cairo-dock (Ubuntu):
importance: Undecided → Medium
summary: - cairo-dock crashed with SIGSEGV in _start()
+ cairo-dock crashed with SIGSEGV in _on_device_changed()
tags: removed: need-i386-retrace
Revision history for this message
Matthieu Baerts (matttbe) wrote :

Thank you for this bug report! I'll have a look ASAP ;-)

information type: Private → Public
affects: cairo-dock (Ubuntu) → cairo-dock-plug-ins (Ubuntu)
Changed in cairo-dock-plug-ins (Ubuntu):
assignee: nobody → Matthieu Baerts (matttbe)
Revision history for this message
Matthieu Baerts (matttbe) wrote :

@Aaron: what did you do just before the crash?
The crash is due to the PowerManager applet, when receiving a message from UPower notifying that a "device" (a battery) status has "changed". Did you modify the PowerManager applet? Or did you just (un)plug your battery?

Changed in cairo-dock-plug-ins (Ubuntu):
status: New → Incomplete
Revision history for this message
Aaron Fried (woodwork78) wrote :

Thanks Matthieu. To be honest I can't remember. I believe I was in a Cairo-dock(gnome) session and was using compiz config. I'm pretty sure I made no changes to power source. I don't understand much about debugging but I figure crash reports can be useful to people that understand them better than I do. I haven't had a similar problem since, and because I don't remember exactly what I was doing I imagine it would be hard to diagnose.

Revision history for this message
Matthieu Baerts (matttbe) wrote :

> I figure crash reports can be useful to people that understand them better than I do.

Yes, they are important :-)
But here the problem seems a bit complex... If you are able to reproduce it, please add a new comment here ;-)

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.