gnome-panel crashed with SIGSEGV in _panel_applet_frame_update_flags()

Bug #710678 reported by pepness
92
This bug affects 16 people
Affects Status Importance Assigned to Milestone
gnome-panel (Ubuntu)
Invalid
Low
Unassigned
meta-gnome3 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: gnome-panel

encendi la maquina y cuando cargo el escritorio mando el error

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: gnome-panel 1:2.32.1-0ubuntu6
ProcVersionSignature: Ubuntu 2.6.38-1.28-generic 2.6.38-rc2
Uname: Linux 2.6.38-1-generic i686
Architecture: i386
Date: Mon Jan 31 08:09:34 2011
ExecutablePath: /usr/bin/gnome-panel
GConfNonDefault:
 /apps/panel/general/applet_id_list=[applet_0,applet_6,applet_3,applet_1]
 /apps/panel/general/object_id_list=[object_6,object_5,object_0]
 /apps/panel/general/toplevel_id_list=[panel_0]
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcCmdline: gnome-panel
ProcEnviron:
 LANGUAGE=es_MX:es:en_GB:en
 PATH=(custom, no user)
 LANG=es_MX.UTF-8
 LC_MESSAGES=es_MX.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x8088090 <_panel_applet_frame_update_flags+128>: mov 0x64(%eax),%eax
 PC (0x08088090) ok
 source "0x64(%eax)" (0x00000064) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-panel
StacktraceTop:
 _panel_applet_frame_update_flags ()
 ?? () from /usr/lib/gnome-panel/modules/libpanel-applets-bonobo.so
 bonobo_marshal_VOID__STRING_BOXED_BOXED () from /usr/lib/libbonobo-2.so.0
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 bonobo_closure_invoke_va_list () from /usr/lib/libbonobo-2.so.0
Title: gnome-panel crashed with SIGSEGV in _panel_applet_frame_update_flags()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors: (nautilus:1524): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed

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

Stacktrace:
 #0 0x08088090 in _panel_applet_frame_update_flags (frame=0x8e29820, major=0,
     minor=1, has_handle=1) at panel-applet-frame.c:861
  background = Unhandled dwarf expression opcode 0x9f
StacktraceTop: _panel_applet_frame_update_flags (frame=0x8e29820, major=0,

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-panel (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
tags: added: iso-testing
visibility: private → public
Revision history for this message
rniamo (rniamo) wrote :

same here:

http://pastebin.com/uYMvgBRg for the stacktrace on natty (2.6.38-5-generic)

Revision history for this message
Pavel Mlčoch (pavkamlc) wrote :

I've this crash after I install quick-lounge-applet

Revision history for this message
Sebastien Bacher (seb128) wrote :

is that a one time crash on new applets install?

Changed in gnome-panel (Ubuntu):
importance: Medium → Low
Changed in gnome-panel (Ubuntu):
status: New → Confirmed
Revision history for this message
Steve Brown (sbrown) wrote :

Same here. Happens for me upon upgrade to natty. My user-defined session apparently has applets that natty upgrade broke -- the problem resolves if I use the fresh "ubuntu classic" session (how can I isolate which?). We should look into this regression (users will log in and be presented with blank screen -> panic!)

(gdb) p frame->priv.panel
$1 = (PanelWidget *) 0x0
(gdb) p frame->priv.applet_info
$2 = (AppletInfo *) 0x0
(gdb) p frame->priv.iid
$3 = (gchar *) 0x958c298 "OAFIID:GNOME_WindowPicker"

Revision history for this message
dino99 (9d9) wrote :

This version is outdated and no more supported

Changed in gnome-panel (Ubuntu):
status: Confirmed → Invalid
affects: gnome-panel (Fedora) → meta-gnome3 (Ubuntu)
Changed in meta-gnome3 (Ubuntu):
importance: Unknown → Undecided
status: Unknown → New
status: New → Invalid
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.