gnome-panel crashed with SIGSEGV

Bug #207693 reported by machak
700
This bug affects 8 people
Affects Status Importance Assigned to Milestone
GTK+
Expired
Critical
libwnck (Ubuntu)
Fix Released
High
Ted Gould

Bug Description

Binary package hint: gnome-panel

often crashes after hardy beta upgrade

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Thu Mar 27 13:11:53 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/gnome-panel
Package: gnome-panel 1:2.22.0-0ubuntu2
PackageArchitecture: i386
ProcCmdline: gnome-panel --sm-config-prefix /gnome-panel-g0hqiW/ --sm-client-id 117f000101000119676302600000065510000 --screen 0
ProcEnviron:
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/home/username/jdk1.5.0_14/bin:/home/username/java/tools/maven/bin
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gnome-panel
StacktraceTop:
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? ()
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? ()
Title: gnome-panel crashed with SIGSEGV
Uname: Linux 2.6.24-12-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin netdev plugdev powerdev sambashare scanner vboxusers video

Tags: apport-crash

Related branches

Revision history for this message
machak (machak) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:_gtk_tooltip_handle_event (event=0x85c0d90)
IA__gtk_main_do_event (event=0x85c0d90) at /build/buildd/gtk+2.0-2.12.9/gtk/gtkmain.c:1608
gdk_event_dispatch (source=0x80eb270, callback=0, user_data=0x0)
IA__g_main_context_dispatch (context=0x80ec620)
g_main_context_iterate (context=0x80ec620, block=1, dispatch=1, self=0x80c25b8)

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in gnome-panel:
importance: Undecided → Medium
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: http://bugzilla.gnome.org/show_bug.cgi?id=524651

Changed in gtk+2.0:
assignee: nobody → desktop-bugs
status: New → Triaged
Revision history for this message
Bruno Munoz (bruno-bmunoz) wrote :

Just mousing over 4 times make it crash

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

could you give extra details? mouse what over what and where?

Revision history for this message
Saivann Carignan (oxmosys) wrote :

I can reproduce this like breefru described. Steps to reproduce :

1. Have compiz enabled
2. Have 5 virtual desktop
3. Put your mouse over the virtual desktop switcher applet and wait for the instructions about how to use virtual Desktop with keyboard to appears.
4. Put your mouse over something else to make this bubble disappears.
5. Repeat 3 and 4, at least 4 time.

Result: Gnome panel crash. You might have to repeat the mentioned steps if it does not crash the first time.

Revision history for this message
Aicardi (aicardi) wrote :

Crash can be triggered when you put your mouse over the virtual switch applet and change the workspace with Ctrl-Alt-Left or Right

Revision history for this message
AJ's Corner (aj-boer) wrote :

Just a side-note, it alse crashes with 4 virtual desktops. Just wait for the balloon to pop-up and switch to another desktop by clicking on it and there she goes...... And indeed its reproducible for just a couple times (i tried it for several times and it looks like it is stable when it crashes three times, after a reboot you can try it again).

Revision history for this message
Jai Harrison (jai) wrote :

I can confirm this problem in Gutsy Beta, clean install.

Aicardi is correct. That does indeed cause the problem.

Changed in gtk+2.0:
importance: Medium → High
milestone: none → ubuntu-8.04
Revision history for this message
Sebastien Bacher (seb128) wrote :

seems to be due to the libwnck tooltip changes

Changed in gtk+2.0:
assignee: desktop-bugs → tedg
Changed in libwnck:
assignee: tedg → ted-gould
Revision history for this message
Colin Brace (cbrace) wrote :

I am seeing the same behaviour here. I too wondered if it was something to do with the tooltip...

Revision history for this message
iGadget (igadget) wrote :

Same here, although I must admit my installation does not contain the latest updates (kind of weird that I'm no longer prompted about this). Will check again when the latest (30 march 2008) updates are applied, if this still happens.

Revision history for this message
iGadget (igadget) wrote :

With latest updates installed, this still happens (although I wasn't promted to report the crash this time). Just hover over the Workspace Switcher a few times and boom.

Revision history for this message
Sam Juvonen (sam-juvonen) wrote :

I think my crash came after hovering over the workspace switcher as well. See trace.

Revision history for this message
Florent Mertens (givre) wrote :

https://bugs.edge.launchpad.net/ubuntu/+source/libwnck/+bug/199380 is the same bug and contains a valgrind showing the issue :

==27419== Invalid read of size 4
==27419== at 0x44B87D1: gtk_tooltip_start_delay (gtktooltip.c:1015)
==27419== by 0x44B93DF: _gtk_tooltip_handle_event (gtktooltip.c:1298)
==27419== by 0x43DBCF9: gtk_main_do_event (gtkmain.c:1608)
==27419== by 0x464FA99: gdk_event_dispatch (gdkevents-x11.c:2351)
==27419== by 0x4858D15: g_main_context_dispatch (gmain.c:2003)
==27419== by 0x485C0D2: g_main_context_iterate (gmain.c:2636)
==27419== by 0x485C68D: g_main_context_iteration (gmain.c:2699)
==27419== by 0x751BDF3: processEvents (gconf.c:1886)
==27419== by 0x757B13D: ccsProcessEvents (main.c:1729)
==27419== by 0x7544549: wnck_pager_query_tooltip (in /usr/lib/libwnck-1.so.22.3.6)
==27419== by 0x43E09A3: _gtk_marshal_BOOLEAN__INT_INT_BOOLEAN_OBJECT (gtkmarshalers.c:835)
==27419== by 0x47EE078: g_type_class_meta_marshal (gclosure.c:567)
==27419== by 0x47EF82E: g_closure_invoke (gclosure.c:490)
==27419== by 0x4804119: signal_emit_unlocked_R (gsignal.c:2478)
==27419== by 0x4805946: g_signal_emit_valist (gsignal.c:2209)
==27419== by 0x4805EDF: g_signal_emit_by_name (gsignal.c:2267)
==27419== by 0x44B9275: gtk_tooltip_run_requery (gtktooltip.c:747)
==27419== by 0x44B9485: _gtk_tooltip_handle_event (gtktooltip.c:1256)
==27419== by 0x43DBCF9: gtk_main_do_event (gtkmain.c:1608)
==27419== by 0x464FA99: gdk_event_dispatch (gdkevents-x11.c:2351)
==27419== by 0x4858D15: g_main_context_dispatch (gmain.c:2003)
==27419== by 0x485C0D2: g_main_context_iterate (gmain.c:2636)
==27419== by 0x485C68D: g_main_context_iteration (gmain.c:2699)
==27419== by 0x751BDF3: processEvents (gconf.c:1886)
==27419== by 0x757B13D: ccsProcessEvents (main.c:1729)
==27419== by 0x7544549: wnck_pager_query_tooltip (in /usr/lib/libwnck-1.so.22.3.6)
==27419== by 0x43E09A3: _gtk_marshal_BOOLEAN__INT_INT_BOOLEAN_OBJECT (gtkmarshalers.c:835)
==27419== by 0x47EE078: g_type_class_meta_marshal (gclosure.c:567)
==27419== by 0x47EF82E: g_closure_invoke (gclosure.c:490)
==27419== by 0x4804119: signal_emit_unlocked_R (gsignal.c:2478)
==27419== by 0x4805946: g_signal_emit_valist (gsignal.c:2209)
==27419== by 0x4805EDF: g_signal_emit_by_name (gsignal.c:2267)
==27419== by 0x44B9275: gtk_tooltip_run_requery (gtktooltip.c:747)
==27419== by 0x44B9485: _gtk_tooltip_handle_event (gtktooltip.c:1256)
==27419== by 0x43DBCF9: gtk_main_do_event (gtkmain.c:1608)
==27419== by 0x464FA99: gdk_event_dispatch (gdkevents-x11.c:2351)
==27419== by 0x4858D15: g_main_context_dispatch (gmain.c:2003)
==27419== by 0x485C0D2: g_main_context_iterate (gmain.c:2636)
==27419== by 0x485C68D: g_main_context_iteration (gmain.c:2699)
==27419== by 0x751BDF3: processEvents (gconf.c:1886)
==27419== Address 0x48 is not stack'd, malloc'd or (recently) free'd

Revision history for this message
Lomax (lomaxfalconer) wrote :

i am having the same problem, just switching desk tops fast can cause it to crash.

Revision history for this message
JohnnyZee (john-zanettos) wrote : Re: [Bug 207693] Re: gnome-panel crashed with SIGSEGV
Revision history for this message
Sebastien Bacher (seb128) wrote :

the bug is already milestoned, no need to add extra tags there

Revision history for this message
soumyajit (iamwhatiam-soumyajit) wrote :

i am having the same problem after upgrading to hardy heron beta.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libwnck - 2.22.0-0ubuntu3

---------------
libwnck (2.22.0-0ubuntu3) hardy; urgency=low

  * debian/control.in:
    - don't build using libcompizconfig
  * debian/patches/02_expose_wm_keybindings.patch:
    - drop the ubuntu changes adding the keyboard shortcuts to the
      workspace switcher tooltip for hardy, the implementation has some issues
      which will be worked next cycle (lp: #204994, #207693)
  * debian/patches/90_autoreconf_update.patch:
    - don't update the autotools not required now
  * debian/pixmaps:
    - the compiz icons are not required now
  * debian/rules:
    - don't install the icons which are not required now
  * debian/patches/80_from_bugzilla_add_action_above.patch:
    - drop change which should not be required

 -- Sebastien Bacher <email address hidden> Tue, 01 Apr 2008 21:13:26 +0200

Changed in libwnck:
status: Triaged → Fix Released
Revision history for this message
Rich Ringer (richringer1) wrote :

It still happenes here...
2.22.0-0ubuntu3 <-- I checked my system and I'm running this update.

Thanks

Revision history for this message
Raul (raulr) wrote :

same happens to me.
updates till now (5th april 2008 - 01:30)

system info > see profile

Changed in gtk:
status: Unknown → New
Changed in gtk:
importance: Unknown → Critical
Changed in gtk:
status: New → Expired
To post a comment you must log in.