Bug 447800 – crash in Window Selector: switch window

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 447800 - crash in Window Selector: switch window


Summary:	crash in Window Selector: switch window


Status:	RESOLVED DUPLICATE of bug 444012

Product:	gnome-panel
Classification:	Other
Component:	window selector
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-06-15 07:52 UTC by voliron
Modified:	2007-06-15 13:51 UTC

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

Description voliron 2007-06-15 07:52:45 UTC

Version: 2.18.2

What were you doing when the application crashed?
switch window		


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 67289088 vsize: 67289088 resident: 22106112 share: 18071552 rss: 22106112 rss_rlim: 4294967295
CPU usage: start_time: 1181893718 rtime: 76 utime: 70 stime: 6 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 -1209080096 (LWP 2797)]
(no debugging symbols found)
0x00dc8402 in __kernel_vsyscall ()

+ Trace 141139

Thread 1 (Thread -1209080096 (LWP 2797))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 cairo_rectangle
from /usr/lib/libcairo.so.2
#5 ??
from /usr/lib/libwnck-1.so.18
#6 ??
from /usr/lib/libwnck-1.so.18
#7 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-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/libwnck-1.so.18
#13 ??
from /usr/lib/libwnck-1.so.18
#14 ??
from /usr/lib/libgdk-x11-2.0.so.0
#15 ??
from /usr/lib/libgdk-x11-2.0.so.0
#16 ??
from /usr/lib/libgdk-x11-2.0.so.0
#17 ??
from /usr/lib/libgdk-x11-2.0.so.0
#18 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#19 ??
from /lib/libglib-2.0.so.0
#20 g_main_loop_run
from /lib/libglib-2.0.so.0
#21 bonobo_main
from /usr/lib/libbonobo-2.so.0
#22 bonobo_generic_factory_main_timeout
from /usr/lib/libbonobo-2.so.0
#23 bonobo_generic_factory_main
from /usr/lib/libbonobo-2.so.0
#24 panel_applet_factory_main_closure
from /usr/lib/libpanel-applet-2.so.0
#25 panel_applet_factory_main
from /usr/lib/libpanel-applet-2.so.0
#26 main
#0 __kernel_vsyscall



----------- .xsession-errors (222 sec old) ---------------------
Checking for XComposite extension               : passed (v0.3)
Checking for XDamage extension                  : passed
Checking for RandR extension                    : passed
Checking for XSync extension                    : passed
Checking Screen 0 ...
Checking for GLX_SGIX_fbconfig                  : passed
Checking for GLX_EXT_texture_from_pixmap        : passed
Checking for non power of two texture support   : passed
Checking maximum texture size                   : passed (2048x2048)
beryl: water: GL_ARB_fragment_program is missing
error getting update info:  Cannot open/read repomd.xml file for repository: fedora
--------------------------------------------------

Comment 1 Vincent Untz 2007-06-15 13:51:46 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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