Bug 496022 – crash in Show Desktop: Setting up Sprint Pantec...

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 496022 - crash in Show Desktop: Setting up Sprint Pantec...


Summary:	crash in Show Desktop: Setting up Sprint Pantec...


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-12 01:46 UTC by astravates
Modified:	2007-11-13 07:26 UTC

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

Description astravates 2007-11-12 01:46:43 UTC

Version: 2.18.3

What were you doing when the application crashed?
Setting up Sprint Pantech PX-500 


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

System: Linux 2.6.23.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 39235584 vsize: 39235584 resident: 21786624 share: 17252352 rss: 21786624 rss_rlim: 4294967295
CPU usage: start_time: 1194808792 rtime: 8519 utime: 7874 stime: 645 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 -1208269088 (LWP 3268)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 177122

Thread 1 (Thread -1208269088 (LWP 3268))

#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 (1575 sec old) ---------------------
Sending reload event...
beryl: core: Received winTypeAtom but unable to find the window for the event
Sending reload event...
beryl: core: Received winTypeAtom but unable to find the window for the event
Sending reload event...
error getting update info:  Cannot retrieve repository metadata (repomd.xml) for repository: fedora. Please verify its path and try again
GTK Accessibility Module initialized
68.30.45.150
6977
Sending reload event...
Sending reload event...
GTK Accessibility Module initialized
ppp0: error fetching interface information: Device not found
68.29.3.123
caldomain8221
--------------------------------------------------

Comment 1 Vincent Untz 2007-11-13 07:26:11 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 ***