unity-panel-service crashed with SIGSEGV in g_cclosure_marshal_VOID__OBJECT()

Bug #738561 reported by Mark Cariaga
60
This bug affects 9 people
Affects Status Importance Assigned to Milestone
Application Menu Indicator
Fix Released
Medium
Ted Gould
indicator-appmenu (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: indicator-appmenu

unity crashed after opening shotwell.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: indicator-appmenu 0.1.97-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-7.36-generic 2.6.38
Uname: Linux 2.6.38-7-generic i686
Architecture: i386
Date: Sat Mar 19 23:22:25 2011
ExecutablePath: /usr/lib/unity/unity-panel-service
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110202)
ProcCmdline: /usr/lib/unity/unity-panel-service
ProcEnviron:
 SHELL=/bin/bash
 LANGUAGE=en_CA:en
 LANG=en_CA.UTF-8
SegvAnalysis:
 Segfault happened at: 0x9082089: cmp %eax,(%edx)
 PC (0x09082089) ok
 source "%eax" ok
 destination "(%edx)" (0x00000008) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: indicator-appmenu
StacktraceTop:
 ?? () from /usr/lib/indicators/5/libappmenu.so
 g_cclosure_marshal_VOID__OBJECT () from /usr/lib/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
Title: unity-panel-service crashed with SIGSEGV in g_cclosure_marshal_VOID__OBJECT()
UpgradeStatus: Upgraded to natty on 2011-03-09 (11 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Related branches

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

StacktraceTop:
 root_changed (client=0x93bc420, new_root=0x93be8f8, user_data=0x93dc090) at window-menus.c:527
 g_cclosure_marshal_VOID__OBJECT (closure=0xb3113c10, return_value=0x0, n_param_values=2, param_values=0x91918a0, invocation_hint=0xbf8cde20, marshal_data=0x0) at /build/buildd/glib2.0-2.28.3/./gobject/gmarshal.c:638
 g_closure_invoke (closure=0xb3113c10, return_value=0x0, n_param_values=2, param_values=0x91918a0, invocation_hint=0xbf8cde20) at /build/buildd/glib2.0-2.28.3/./gobject/gclosure.c:767
 signal_emit_unlocked_R (node=0x9195b00, detail=0, instance=0x93bc420, emission_return=0x0, instance_and_params=0x91918a0) at /build/buildd/glib2.0-2.28.3/./gobject/gsignal.c:3252
 g_signal_emit_valist (instance=0x93bc420, signal_id=177, detail=0, var_args=0xbf8cdfe0 "\001") at /build/buildd/glib2.0-2.28.3/./gobject/gsignal.c:2983

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in indicator-appmenu (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
visibility: private → public
Revision history for this message
sdaau (sd-imi) wrote :

There is a persistent bug I have on fresh Natty (alpha3) with Unity; hope this is the one. Note that I have 'scite' installed and tried to make it default text editor... So basically, I open several tabs in Nautilus in one Unity workspace, open Scite in another workspace, and open Firefox (Minefield) in third. Everything works fine for a while - and then, usually when I try to open a file either in Scite or pdf in Evince, no window appears and something in Unity freezes - usually it's the title bars (so they cannot be moved) - but then, Alt+drag sometimes works in this case, sometimes not... Another symptom is that file items in Nautilus cannot be selected with the mouse anymore.

Anyways, after this happens, cannot open files with right-click anymore, so then usually logout (clicking there is still possible, usually), and during logoff, after most windows have shut down, I can usually see that actually there is a crash report window in the background that barely becomes visible and then it too shuts down before complete logoff. So I'm not sure if this is the same bug - I hope it is, because it occured in the same situation - right-click to open a pdf; but it's the first time everything stayed put long enough for the crash window to appear...

Cheers!

Changed in indicator-appmenu:
assignee: nobody → Ted Gould (ted)
Ted Gould (ted)
Changed in indicator-appmenu:
status: New → In Progress
Changed in indicator-appmenu (Ubuntu):
status: New → In Progress
status: In Progress → Triaged
Changed in indicator-appmenu (Ubuntu):
status: Triaged → Fix Committed
Changed in indicator-appmenu:
importance: Undecided → Medium
status: In Progress → Fix Committed
Ted Gould (ted)
Changed in indicator-appmenu:
milestone: none → 0.2.0
Ted Gould (ted)
Changed in indicator-appmenu:
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package indicator-appmenu - 0.2.0-0ubuntu1

---------------
indicator-appmenu (0.2.0-0ubuntu1) natty; urgency=low

  * New upstream release.
    ∘ Adding a check of the indicator environment to hide the menu stubs
      under Unity (LP: #703555)
    ∘ Send about-to-show on menus that don't have any children currently
      (LP: #619811)
    ∘ Work around bugs in signaling by delaying the destruction of menu
      caches for five seconds (LP: #718926)
    ∘ Disconnecting client signal handlers on displose (LP: #738561)
    ∘ Remove menuitem signals on root changes (LP: #743404)
 -- Ted Gould <email address hidden> Thu, 07 Apr 2011 11:01:06 -0500

Changed in indicator-appmenu (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.