gnome-panel workspace switcher segfaults when switching workspaces

Bug #203125 reported by hype
This bug report is a duplicate of:  Bug #207693: gnome-panel crashed with SIGSEGV. Edit Remove
2
Affects Status Importance Assigned to Milestone
gnome-panel (Ubuntu)
Incomplete
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gnome-panel

Using Hardy Heron, up to date (03/17/08)

I noticed gnome-panel crashed often when using the workspace switcher applet, especially if i have amule running.
I generated a gdb log (but couldnt find any info specific to the fact that amule is running)

I noticed a similar bug, https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/89471, but this one seems to be reported to Edgy Eft.

ii gnome-panel 1:2.22.0-0ubuntu2

Revision history for this message
hype (hypeuser-lp) wrote :
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instuctions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

Changed in gnome-panel:
status: New → Invalid
Revision history for this message
hype (hypeuser-lp) wrote :

ok, found nothing revelant in /var/crash: no bug concerning gnome-panel.
I did run gdb, attach gnome-panel's pid, and created this gdb output. So there's nothing more i can do.
Thanks for "help".

Revision history for this message
Pedro Villavicencio (pedro) wrote :

the trace you submitted doesn't show any symbol just a kernel_syscall that isn't useful at all, please look at http://live.gnome.org/GettingTraces/Details to see how a good backtrace looks like, thanks in advance.

Revision history for this message
hype (hypeuser-lp) wrote :

Ok, thanks for help.
I installed gdb package related to libgtk, here is the new gdb output, which seems more understandable. (see attached file)

To sum-up:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb6d19720 (LWP 28604)]
gtk_tooltip_start_delay (display=0x80e6010) at /build/buildd/gtk+2.0-2.12.9/gtk/gtktooltip.c:1015
1015 /build/buildd/gtk+2.0-2.12.9/gtk/gtktooltip.c: No such file or directory.
 in /build/buildd/gtk+2.0-2.12.9/gtk/gtktooltip.c

Revision history for this message
Pedro Villavicencio (pedro) wrote :

rock on, thanks for doing it, it indeed contains some symbols but not all of them, please follow this instructions in order to get a more detailed stacktrace: https://wiki.ubuntu.com/Backtrace , thanks in advance.

Changed in gnome-panel:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: Invalid → Incomplete
Revision history for this message
hype (hypeuser-lp) wrote :

Thats precisely the link i followed to provide this backtrace.
I actually used the second part:
"Already running programs"
on this exact same wiki page.
(as gnome-panel is set to restart, it's more handy to attach gnome-panel's pid than running it from gdb)

Also, i didnt only install libgtk-gdb, but gnome-panel-gdb.
Thought it would be fine to track a bug in gnome-panel.

Revision history for this message
hype (hypeuser-lp) wrote :

Wow, seems i forgot 30% of the back-trace info. (after the "continue" :p)

I added libglib2.0-0-gdb; here is the hopefully complete crashlog (attached file)

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.