Bug 470130 – crash in Window List: ワークスペースの設定をしていた。

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 470130 - crash in Window List: ワークスペースの設定をしていた。


Summary:	crash in Window List: ワークスペースの設定をしていた。


Status:	RESOLVED DUPLICATE of bug 403377

Product:	gnome-panel
Classification:	Other
Component:	window list
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-08-25 08:14 UTC by kiukutikazuki917
Modified:	2007-08-27 20:10 UTC

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

Description kiukutikazuki917 2007-08-25 08:14:51 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.22.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 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: 52436992 vsize: 52436992 resident: 16969728 share: 11456512 rss: 16969728 rss_rlim: 4294967295
CPU usage: start_time: 1188065542 rtime: 1316 utime: 1171 stime: 145 cutime:2 cstime: 1 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 -1208564000 (LWP 3010)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 157773

Thread 1 (Thread -1208564000 (LWP 3010))

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



----------- .xsession-errors (55 sec old) ---------------------
kbuildsycoca running...
Reusing existing ksycoca
kbuildsycoca running...
Reusing existing ksycoca
kbuildsycoca running...
Reusing existing ksycoca
ウィンドウ・マネージャの警告: ディスプレイ ':0.0' への接続が切れました。
おそらくＸサーバがシャットダウンしたか、
ウィンドウ・マネージャが強制終了/破棄されたようです。
Sending reload event...
Sending reload event...
Sending reload event...
Sending reload event...
Sending reload event...
Sending reload event...
--------------------------------------------------

Comment 1 Susana 2007-08-27 20:10:50 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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