[apport] gnome-panel crashed with SIGSEGV in wnck_window_get_transient()

[Bill Hand]

Binary package hint: gnome-panel

Have been having a lotttttttt of trouble when trying to right click on the window 'frames' to send to a different desktop and clicking on 'view', in the 'file Browser' to make changes... When right clicking on the window 'frame' it's like nautilus cycles through all the windows on each desktop, until it stops on the one that I started with, trying to move it to a different desktop.... It's been doing this off and on for a month or so now.... I pretty much do the 'updates' for fiesty as they come out... I can't seem to nail this down as to when exactly it began though....

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Sat Mar 3 20:44:07 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/gnome-panel
Package: gnome-panel 2.17.92-0ubuntu3
ProcCmdline: gnome-panel --sm-config-prefix /gnome-panel-j3uxSw/ --sm-client-id 117f000101000116622449200000048420001 --screen 0
ProcCwd: /home/crazyeccentric
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gnome-panel
StacktraceTop:
 wnck_window_get_transient () from /usr/lib/libwnck-1.so.18
 ?? () from /usr/lib/libwnck-1.so.18
 ?? ()
 ?? ()
 ?? ()
Uname: Linux CrazyEccentric 2.6.20-9-generic #2 SMP Mon Feb 26 03:01:44 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio avahi-autoipd cdrom clamav dhcp dialout dip fax floppy fuse lpadmin netdev plugdev powerdev scanner video

[Sebastien Bacher (seb128)]

Thank you for your bug. That's known upstream: http://bugzilla.gnome.org/show_bug.cgi?id=317333

[Sebastien Bacher (seb128)]

upstream comment:

"This crash is still happening, but we need a recent stack trace, or a valgrind
log as Elijah already pointed out.

Marking as NEEDINFO until we get some new data."

[Sebastien Bacher (seb128)]

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.