Bug 335610 – wnck-applet dies for no apparent reason

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 335610 - wnck-applet dies for no apparent reason


Summary:	wnck-applet dies for no apparent reason


Status:	RESOLVED DUPLICATE of bug 317333

Product:	gnome-panel
Classification:	Other
Component:	clock
Version:	unspecified
Hardware:	Other other

Importance:	High critical
Target Milestone:	---
Assigned To:	Panel Maintainers
QA Contact:	Panel Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-03-23 05:11 UTC by bugs
Modified:	2006-03-23 09:33 UTC

See Also:
GNOME target:	---
GNOME version:	2.11/2.12

Description bugs 2006-03-23 05:11:56 UTC

Distribution: Unknown
Package: gnome-panel
Severity: critical
Version: GNOME2.12.0 unspecified
Gnome-Distributor: SUSE
Synopsis: wnck-applet dies for no apparent reason
Bugzilla-Product: gnome-panel
Bugzilla-Component: clock
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.12.0)
Description:
Description of the crash:
wnck-applet dies, then all panel applets crash

Steps to reproduce the crash:
1. Remain logged in 4+ hours; allow system to idle.
2. Resume working.
3. 

Expected Results:
Applications continue to run

How often does this happen?
Every hour or so after being logged in for 4+ hours.

Additional Information:
No screen saver or power saving is active.


Debugging Information:

Backtrace was generated from '/opt/gnome/libexec/wnck-applet'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 1090293472 (LWP 8112)]
(no debugging symbols found)
0xffffe410 in ?? ()

+ Trace 67154

Thread 1 (Thread 1090293472 (LWP 8112))

#0 ??
#1 ??
#2 ??
#3 ??
#4 __waitpid_nocancel
from /lib/tls/libpthread.so.0
#5 libgnomeui_module_info_get
from /opt/gnome/lib/libgnomeui-2.so.0
#6 <signal handler called>
#7 g_type_check_instance_is_a
from /opt/gnome/lib/libgobject-2.0.so.0
#8 wnck_window_get_transient
from /opt/gnome/lib/libwnck-1.so.18
#9 wnck_tasklist_get_size_hint_list
from /opt/gnome/lib/libwnck-1.so.18
#10 wnck_tasklist_get_size_hint_list
from /opt/gnome/lib/libwnck-1.so.18
#11 wnck_tasklist_new
from /opt/gnome/lib/libwnck-1.so.18
#12 g_cclosure_marshal_VOID__OBJECT
from /opt/gnome/lib/libgobject-2.0.so.0
#13 g_closure_invoke
from /opt/gnome/lib/libgobject-2.0.so.0
#14 g_signal_stop_emission
from /opt/gnome/lib/libgobject-2.0.so.0
#15 g_signal_emit_valist
from /opt/gnome/lib/libgobject-2.0.so.0
#16 g_signal_emit
from /opt/gnome/lib/libgobject-2.0.so.0
#17 wnck_screen_move_viewport
from /opt/gnome/lib/libwnck-1.so.18
#18 wnck_screen_move_viewport
from /opt/gnome/lib/libwnck-1.so.18
#19 g_child_watch_add
from /opt/gnome/lib/libglib-2.0.so.0
#20 g_main_context_dispatch
from /opt/gnome/lib/libglib-2.0.so.0
#21 g_main_context_check
from /opt/gnome/lib/libglib-2.0.so.0
#22 g_main_loop_run
from /opt/gnome/lib/libglib-2.0.so.0
#23 bonobo_main
from /opt/gnome/lib/libbonobo-2.so.0
#24 bonobo_generic_factory_main_timeout
from /opt/gnome/lib/libbonobo-2.so.0
#25 bonobo_generic_factory_main
from /opt/gnome/lib/libbonobo-2.so.0
#26 panel_applet_factory_main_closure
from /opt/gnome/lib/libpanel-applet-2.so.0
#27 panel_applet_factory_main
from /opt/gnome/lib/libpanel-applet-2.so.0
#28 main
#0 ??





------- Bug created by bug-buddy at 2006-03-23 05:11 -------

Comment 1 Sergej Kotliar 2006-03-23 09:33:31 UTC

Are you running in multihead (multiple monitors) mode?
Cause this bug is extremely similar to bug 317333, which is triggered in multihead mode. 
I'll close the bug as a duplicate, but please reopen this bug if you feel they are different somehow, or add comments to the other bug.

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