Bug 498202 – crash in Show Desktop:

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 498202 - crash in Show Desktop:


Summary:	crash in Show Desktop:


Status:	RESOLVED DUPLICATE of bug 446227

Product:	gnome-panel
Classification:	Other
Component:	show-desktop-button
Version:	2.18.x
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-11-19 14:52 UTC by lakhterman
Modified:	2007-11-19 20:29 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description lakhterman 2007-11-19 14:52:59 UTC

Version: 2.18.3

What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Crux
Icon Theme: Clearlooks

Memory status: size: 26091520 vsize: 26091520 resident: 9777152 share: 7380992 rss: 9777152 rss_rlim: 4294967295
CPU usage: start_time: 1195483819 rtime: 15 utime: 13 stime: 2 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/libexec/wnck-applet'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208764704 (LWP 4070)]
(no debugging symbols found)
0x00ea6402 in __kernel_vsyscall ()

+ Trace 178719

Thread 1 (Thread -1208764704 (LWP 4070))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 wnck_workspace_is_virtual
from /usr/lib/libwnck-1.so.18
#5 wnck_create_window_action_menu
from /usr/lib/libwnck-1.so.18
#6 ??
from /usr/lib/libwnck-1.so.18
#7 ??
from /usr/lib/libgtk-x11-2.0.so.0
#8 g_closure_invoke
from /lib/libgobject-2.0.so.0
#9 ??
from /lib/libgobject-2.0.so.0
#10 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#11 g_signal_emit
from /lib/libgobject-2.0.so.0
#12 ??
from /usr/lib/libgtk-x11-2.0.so.0
#13 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#14 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#15 ??
from /usr/lib/libgdk-x11-2.0.so.0
#16 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#17 ??
from /lib/libglib-2.0.so.0
#18 g_main_loop_run
from /lib/libglib-2.0.so.0
#19 bonobo_main
from /usr/lib/libbonobo-2.so.0
#20 bonobo_generic_factory_main_timeout
from /usr/lib/libbonobo-2.so.0
#21 bonobo_generic_factory_main
from /usr/lib/libbonobo-2.so.0
#22 panel_applet_factory_main_closure
from /usr/lib/libpanel-applet-2.so.0
#23 panel_applet_factory_main
from /usr/lib/libpanel-applet-2.so.0
#24 main
#0 __kernel_vsyscall



----------- .xsession-errors (68 sec old) ---------------------
(evolution:2896): calendar-gui-CRITICAL **: e_week_view_add_event: assertion `end > add_event_data->week_view->day_starts[0]' failed
** (gnome-compiz-preferences:3884): WARNING **: plugin crashhandler isn't installed
** (gnome-compiz-preferences:3884): WARNING **: plugin showdesktop isn't installed
** (gnome-compiz-preferences:3884): WARNING **: plugin inputzoom isn't installed
** (gnome-compiz-preferences:3884): WARNING **: plugin animation isn't installed
(gnome-compiz-preferences:3884): Wnck-WARNING **: Received a timestamp of 0; window activation may not function properly.
(emerald-theme-manager:3956): Gtk-WARNING **: You must override the default 'drag_data_received' handler on GtkTreeView when using models that don't support the GtkTreeDragDest interface and enabling 
--------------------------------------------------

Comment 1 Cosimo Cecchi 2007-11-19 20:29:32 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 446227 ***