Bug 391929 – Right click in taskbar causes crash

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 391929 - Right click in taskbar causes crash


Summary:	Right click in taskbar causes crash


Status:	RESOLVED DUPLICATE of bug 346523

Product:	gnome-panel
Classification:	Other
Component:	general
Version:	2.16.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Panel Maintainers
QA Contact:	Panel Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-01-02 16:16 UTC by V Sridhar
Modified:	2007-01-14 23:46 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Attachments
Stack trace generated by bug-buddy (16.92 KB, text/plain) 2007-01-05 15:51 UTC, Charles-henri DE BLESSON	Details

Description V Sridhar 2007-01-02 16:16:52 UTC

Steps to reproduce:
1. Enable "Always on Visible Workspace"
2. Then - in the GNOME Panel - right click on the Nautilus File Manager Icon
3. Crash is generated


Stack trace:
Memory status: size: 40374272 vsize: 0 resident: 40374272 share: 0 rss: 19566592 rss_rlim: 0
CPU usage: start_time: 1167712090 rtime: 0 utime: 2102 stime: 0 cutime:1991 cstime: 0 timeout: 111 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/gnome-panel'

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1225128272 (LWP 4828)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 98744

Thread 1 (Thread -1225128272 (LWP 4828))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 wnck_workspace_get_viewport_x
from /usr/lib/libwnck-1.so.18
#5 wnck_tasklist_get_type
from /usr/lib/libwnck-1.so.18
#6 _gtk_marshal_BOOLEAN__BOXED
at gtkmarshalers.c line 84
#7 IA__g_closure_invoke
at gclosure.c line 490
#8 signal_emit_unlocked_R
at gsignal.c line 2440
#9 IA__g_signal_emit_valist
at gsignal.c line 2209
#10 IA__g_signal_emit
at gsignal.c line 2243
#11 gtk_widget_event_internal
at gtkwidget.c line 3911
#12 IA__gtk_propagate_event
at gtkmain.c line 2211
#13 IA__gtk_main_do_event
at gtkmain.c line 1445
#14 gdk_event_dispatch
at gdkevents-x11.c line 2320
#15 IA__g_main_context_dispatch
at gmain.c line 2045
#16 g_main_context_iterate
at gmain.c line 2677
#17 IA__g_main_loop_run
at gmain.c line 2881
#18 IA__gtk_main
at gtkmain.c line 1024
#19 main
at main.c line 95
#0 __kernel_vsysc


Other information:

Comment 1 Baptiste Mille-Mathias 2007-01-02 16:25:07 UTC

Change Title,
Increase Priority due to the useful back trace

Comment 2 Charles-henri DE BLESSON 2007-01-05 15:51:12 UTC

Created attachment 79454 [details]
Stack trace generated by bug-buddy

Do you know why bug-buddy tells me the crashed application is unknown ?

Comment 3 Charles-henri DE BLESSON 2007-01-05 15:53:33 UTC

I had my stack trace because it seems to be different from the reporter's one.

I Hope it will help.

Thank you for your work.

Best regards,
Charles-henri.

Comment 4 Vincent Untz 2007-01-14 23:46:21 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 346523 ***