Bug 445336 – crash in Window Selector: browsing the following p...

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 445336 - crash in Window Selector: browsing the following p...


Summary:	crash in Window Selector: browsing the following p...


Status:	RESOLVED DUPLICATE of bug 431990

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-08 00:46 UTC by furutaka.kazuyoshi
Modified:	2007-06-10 19:50 UTC

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

Description furutaka.kazuyoshi 2007-06-08 00:46:29 UTC

Version: 2.18.0

What were you doing when the application crashed?
browsing the following page:
http://www-geant4.kek.jp/forum/index.php?t=msg&th=21&start=0&S=bdcab69f1267605afa838e9423a05fd3


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: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 52572160 vsize: 52572160 resident: 15962112 share: 11112448 rss: 15962112 rss_rlim: 4294967295
CPU usage: start_time: 1180915205 rtime: 4166 utime: 3814 stime: 352 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 -1208457504 (LWP 5120)]
(no debugging symbols found)
0x00a34402 in __kernel_vsyscall ()

+ Trace 139237

Thread 1 (Thread -1208457504 (LWP 5120))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 pthread_mutex_lock
from /lib/libpthread.so.0
#5 ??
from /usr/lib/libcairo.so.2
#6 ??
from /usr/lib/libcairo.so.2
#7 ??
from /usr/lib/libcairo.so.2
#8 cairo_scaled_font_text_extents
from /usr/lib/libcairo.so.2
#9 ??
from /usr/lib/libpangocairo-1.0.so.0
#10 ??
from /usr/lib/libpangocairo-1.0.so.0
#11 ??
from /usr/lib/libpangocairo-1.0.so.0
#12 pango_font_get_glyph_extents
from /usr/lib/libpango-1.0.so.0
#13 pango_ot_buffer_output
from /usr/lib/libpangoft2-1.0.so.0
#14 ??
from /usr/lib/libpangoft2-1.0.so.0
#15 ??
from /usr/lib/libpango-1.0.so.0
#16 pango_shape
from /usr/lib/libpango-1.0.so.0
#17 ??
from /usr/lib/libpango-1.0.so.0
#18 ??
from /usr/lib/libpango-1.0.so.0
#19 ??
from /usr/lib/libpango-1.0.so.0
#20 ??
from /usr/lib/libpango-1.0.so.0
#21 ??
from /usr/lib/libgtk-x11-2.0.so.0
#22 g_cclosure_marshal_VOID__BOXED
from /lib/libgobject-2.0.so.0
#23 ??
from /lib/libgobject-2.0.so.0
#24 g_closure_invoke
from /lib/libgobject-2.0.so.0
#25 ??
from /lib/libgobject-2.0.so.0
#26 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#27 g_signal_emit_by_name
from /lib/libgobject-2.0.so.0
#28 ??
from /usr/lib/libgtk-x11-2.0.so.0
#29 ??
from /usr/lib/libgtk-x11-2.0.so.0
#30 gtk_widget_size_request
from /usr/lib/libgtk-x11-2.0.so.0
#31 ??
from /usr/lib/libgtk-x11-2.0.so.0
#32 g_cclosure_marshal_VOID__BOXED
from /lib/libgobject-2.0.so.0
#33 ??
from /lib/libgobject-2.0.so.0
#34 g_closure_invoke
from /lib/libgobject-2.0.so.0
#35 ??
from /lib/libgobject-2.0.so.0
#36 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#37 g_signal_emit_by_name
from /lib/libgobject-2.0.so.0
#38 ??
from /usr/lib/libgtk-x11-2.0.so.0
#39 ??
from /usr/lib/libgtk-x11-2.0.so.0
#40 gtk_widget_size_request
from /usr/lib/libgtk-x11-2.0.so.0
#41 ??
from /usr/lib/libgtk-x11-2.0.so.0
#42 g_cclosure_marshal_VOID__BOXED
from /lib/libgobject-2.0.so.0
#43 ??
from /lib/libgobject-2.0.so.0
#44 g_closure_invoke
from /lib/libgobject-2.0.so.0
#45 ??
from /lib/libgobject-2.0.so.0
#46 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#47 g_signal_emit_by_name
from /lib/libgobject-2.0.so.0
#48 ??
from /usr/lib/libgtk-x11-2.0.so.0
#49 ??
from /usr/lib/libgtk-x11-2.0.so.0
#50 gtk_widget_size_request
from /usr/lib/libgtk-x11-2.0.so.0
#51 ??
#52 ??
#53 ??
#54 ??
#0 __kernel_vsyscall



----------- .xsession-errors (244760 sec old) ---------------------
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0005a (OpenOffice)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e02848 (OpenOffice)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e070df (OpenOffice)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e070df (OpenOffice)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x420005b (OpenOffice)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
uim-helper_server write(2) failed: Broken pipe
closing
gnome-mount 0.6
uim-helper_server write(2) failed: Broken pipe
fd = 8
--------------------------------------------------

Comment 1 Vincent Untz 2007-06-10 19:50:44 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 431990 ***