Bug 340100 – WindowNavigationApplets crashes unexpectely

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 340100 - WindowNavigationApplets crashes unexpectely


Summary:	WindowNavigationApplets crashes unexpectely


Status:	RESOLVED INCOMPLETE

Product:	libwnck
Classification:	Core
Component:	general
Version:	2.14.x
Hardware:	Other other

Importance:	High critical
Target Milestone:	---
Assigned To:	libwnck maintainers
QA Contact:	libwnck maintainers

URL:
Whiteboard:

Duplicates:	340266 (view as bug list)
Depends on:
Blocks:

Reported:	2006-04-29 09:07 UTC by vincent
Modified:	2007-02-28 23:27 UTC

See Also:
GNOME target:	---
GNOME version:	2.13/2.14

Attachments
stupid workaround (960 bytes, patch) 2006-05-21 20:15 UTC, Vincent Untz	none	Details \| Review

Description vincent 2006-04-29 09:07:50 UTC

Distribution: Ubuntu 6.06 (dapper)
Package: gnome-panel
Severity: Normal
Version: GNOME2.14.1 unspecified
Gnome-Distributor: Ubuntu
Synopsis: WindowNavigationApplets crashes unexpectely
Bugzilla-Product: ???
Bugzilla-Component: ???
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:
As my desktop is loaded, I allways get this error. I use Xgl

Steps to reproduce the crash:
1.
2.
3.

Expected Results:


How often does this happen?


Additional Information:
If you want me to test me something, I'll be really happy to help.
And please make bugbuddy more user-friendly! "please selecte the product 
that crashed", when the name was displayed is very irritating!

Debugging Information:

Backtrace was generated from '/usr/libexec/WindowNavigationApplets'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1224489280 (LWP 5655)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 67907

Thread 1 (Thread -1224489280 (LWP 5655))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 wnck_application_get_startup_id
from /usr/lib/libwnck-1.so.18
#5 wnck_screen_get_default
from /usr/lib/libwnck-1.so.18
#6 wnck_screen_get_default
from /usr/lib/libwnck-1.so.18
#7 g_child_watch_add
from /usr/lib/libglib-2.0.so.0
#8 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#9 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#10 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#11 bonobo_main
from /usr/lib/libbonobo-2.so.0
#12 bonobo_generic_factory_main_timeout
from /usr/lib/libbonobo-2.so.0
#13 bonobo_generic_factory_main
from /usr/lib/libbonobo-2.so.0
#14 panel_applet_factory_main_closure
from /usr/lib/libpanel-applet-2.so.0
#15 panel_applet_factory_main
from /usr/lib/libpanel-applet-2.so.0
#16 ??
#17 _IO_stdin_used
#18 ??
#19 ??
#20 ??
#0 __kernel_vsyscall





------- Bug created by bug-buddy at 2006-04-29 09:07 -------

Comment 1 Sergej Kotliar 2006-05-01 11:14:15 UTC

*** Bug 340266 has been marked as a duplicate of this bug. ***

Comment 2 Sebastien Bacher 2006-05-01 12:31:48 UTC

Ubuntu bug about that: https://launchpad.net/distros/ubuntu/+source/gnome-panel/+bug/42332

Comment 3 Sebastien Bacher 2006-05-01 12:38:24 UTC

From the Ubuntu bug:

"...
I found it when it crashed. I'm running Ubuntu Dapper Drake, XGL, Compiz on
a XP3200+, nvidia fx5200. (this what you mean by architecture?
..."

the issue seems to happen only with xgl, I've asked for a backtrace with a libwnck debug package

Comment 4 Sebastien Bacher 2006-05-01 19:10:23 UTC

debug backtrace from the Ubuntu bug: 

"...
Backtrace was generated from '/usr/libexec/WindowNavigationApplets'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1209263584 (LWP 5606)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 67955

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 _wnck_application_destroy
at application.c line 456
#5 update_client_list
at screen.c line 1418
#6 do_update_now
at screen.c line 1912
#7 update_idle
at screen.c line 1934
#8 g_child_watch_add
from /usr/lib/libglib-2.0.so.0
#9 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0

Comment 5 Vincent Untz 2006-05-21 20:15:08 UTC

Created attachment 65963 [details] [review]
stupid workaround

Here's the stupid workaround. But I'd prefer to understand how the app can be NULL. I can't see any case where this would be possible.

Comment 6 Daniel Holbach 2006-09-28 14:57:11 UTC

Is this still a problem? Should the patch be used?

Comment 7 Vincent Untz 2006-10-01 10:09:21 UTC

Daniel: did you get more duplicates in launchpad about this? Or did it only happen a few months ago?

Comment 8 Daniel Holbach 2006-10-01 10:21:21 UTC

The last comment was on 2006-05-01 21:11:20 CEST - no duplicates I know of.

Comment 9 Sebastien Bacher 2007-01-13 11:58:38 UTC

new comment on the distribution bug:

"No, I run edgy without compiz now. Have been running xubuntu and kubuntu for
a while, so I not planning to go testing soon, now I have Ubuntu installed
and configured to my needs again."

Comment 10 Daniel Holbach 2007-02-28 15:29:45 UTC

I closed the Ubuntu bug, I got no reply back.

Comment 11 Vincent Untz 2007-02-28 23:27:30 UTC

Closing without applying the patch, then. The user was using compiz, and maybe he was also using a patched libwnck at that time...