Bug 484392 – 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 484392 - 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-10-07 13:05 UTC by ilan
Modified:	2007-10-11 18:17 UTC

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

Description ilan 2007-10-07 13:05:59 UTC

Version: 2.18.0

What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (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: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Clearlooks

Memory status: size: 56598528 vsize: 56598528 resident: 13410304 share: 9588736 rss: 13410304 rss_rlim: 4294967295
CPU usage: start_time: 1191739155 rtime: 1528 utime: 1377 stime: 151 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 -1208867104 (LWP 3278)]
(no debugging symbols found)
0x009c1402 in __kernel_vsyscall ()

+ Trace 168529

Thread 1 (Thread -1208867104 (LWP 3278))

#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 ??
from /lib/libglib-2.0.so.0
#6 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#7 ??
from /lib/libglib-2.0.so.0
#8 g_main_loop_run
from /lib/libglib-2.0.so.0
#9 bonobo_main
from /usr/lib/libbonobo-2.so.0
#10 bonobo_generic_factory_main_timeout
from /usr/lib/libbonobo-2.so.0
#11 bonobo_generic_factory_main
from /usr/lib/libbonobo-2.so.0
#12 panel_applet_factory_main_closure
from /usr/lib/libpanel-applet-2.so.0
#13 panel_applet_factory_main
from /usr/lib/libpanel-applet-2.so.0
#14 main
#0 __kernel_vsyscall



----------- .xsession-errors (4307 sec old) ---------------------
13878753 [AWT-EventQueue-0] INFO  org.tn5250j.framework.common.Sessions  -  sent heartbeat to 720
6541830 [AWT-EventQueue-0] INFO  org.tn5250j.framework.common.Sessions  -  sent heartbeat to 720
13893757 [AWT-EventQueue-0] INFO  org.tn5250j.framework.common.Sessions  -  sent heartbeat to 720
6556834 [AWT-EventQueue-0] INFO  org.tn5250j.framework.common.Sessions  -  sent heartbeat to 720
13908761 [AWT-EventQueue-0] INFO  org.tn5250j.framework.common.Sessions  -  sent heartbeat to 720
6571838 [AWT-EventQueue-0] INFO  org.tn5250j.framework.common.Sessions  -  sent heartbeat to 720
13923765 [AWT-EventQueue-0] INFO  org.tn5250j.framework.common.Sessions  -  sent heartbeat to 720
6586842 [AWT-EventQueue-0] INFO  org.tn5250j.framework.common.Sessions  -  sent heartbeat to 720
13938769 [AWT-EventQueue-0] INFO  org.tn5250j.framework.common.Sessions  -  sent heartbeat to 720
6601846 [AWT-EventQueue-0] INFO  org.tn5250j.framework.common.Sessions  -  sent heartbeat to 720
13953773 [AWT-EventQueue-0] INFO  org.tn5250j.framework.common.Sessions  -  sent heartbeat to 720
6616850 [AWT-EventQueue-0] INFO  org.tn5250j.framework.common.Sessions  -  sent heartbeat to 720
13968777 [AWT-EventQueue-0] INFO  org.tn5250j.framework.common.Sessions  -  sent heartbeat to 720
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Vincent Untz 2007-10-11 18:17:33 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 ***