Bug 360742 – Panel lacking functionality when coupled with KNOME hack

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 360742 - Panel lacking functionality when coupled with KNOME hack


Summary:	Panel lacking functionality when coupled with KNOME hack


Status:	RESOLVED DUPLICATE of bug 403377

Product:	libwnck
Classification:	Core
Component:	general
Version:	2.17.x
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-10-08 21:03 UTC by Paul Valencourt
Modified:	2007-04-30 09:21 UTC

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

Description Paul Valencourt 2006-10-08 21:03:25 UTC

Please describe the problem:
When one uses the KNOME hack with Ubuntu Edgy Beta, which allows the usage of GNOME with kwin, the gnome panel ceases to function properly. It crashes and restarts upon every xserver restart, and applications don't maximize with respect to it.

KNOME hack - http://www.ubuntuforums.org/showthread.php?t=115974&page=1

Steps to reproduce:
1. Follow the kwin hack instructions linked above. Ubuntu Edgy might be necessary.
2. Restart the xserver. The panel crashes and restarts.
3. Maximize a window. Observe the badthingitude.

Actual results:
Crashage, pwnage, fryage, burnage. Generally not working with kwin.

Expected results:
Might depend on the version of kwin in ubuntu, but what I specified above. Apt reports the version as 4:3.5.4-ubuntu29.

Does this happen every time?
Yes.

Other information:
Report generated by bug buddy, with gnome-panel debugging symbols: 
Memory status: size: 37015552 vsize: 0 resident: 37015552 share: 0 rss: 13451264 rss_rlim: 0
CPU usage: start_time: 1160339273 rtime: 0 utime: 124 stime: 0 cutime:119 cstime: 0 timeout: 5 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/gnome-panel'

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

+ Trace 75307

Thread 1 (Thread -1225017680 (LWP 5143))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 wnck_workspace_get_width
from /usr/lib/libwnck-1.so.18
#5 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#6 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#7 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#8 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#9 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#10 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#11 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#12 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#13 gdk_window_is_viewable
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 gtk_container_check_resize
from /usr/lib/libgtk-x11-2.0.so.0
#16 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#17 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#18 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#19 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#20 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#21 main
at main.c line 95
#0 __kernel_vsyscall

Comment 1 Vincent Untz 2007-02-18 01:31:11 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!

(we need libwnck symbols here)

Comment 2 Sebastien Bacher 2007-02-24 22:43:54 UTC

Ubuntu bug about that: https://launchpad.net/bugs/87466

Debug backtrace for the crash:

+ Trace 113637

#0 wnck_workspace_get_width
at workspace.c line 293
#1 _gtk_marshal_BOOLEAN__BOXED
at gtkmarshalers.c line 84
#2 g_type_class_meta_marshal
at gclosure.c line 567
#3 IA__g_closure_invoke
at gclosure.c line 490
#4 signal_emit_unlocked_R
at gsignal.c line 2478
#5 IA__g_signal_emit_valist
at gsignal.c line 2209
#6 IA__g_signal_emit
#7 gtk_widget_event_internal
at gtkwidget.c line 3915
#8 IA__gtk_main_do_event
at gtkmain.c line 1550
#9 gdk_window_process_updates_internal
at gdkwindow.c line 2333
#10 IA__gdk_window_process_all_updates
at gdkwindow.c line 2396
#11 gtk_container_idle_sizer
at gtkcontainer.c line 1113
#12 g_idle_dispatch
at gmain.c line 3928
#13 IA__g_main_context_dispatch
at gmain.c line 2045
#14 g_main_context_iterate
at gmain.c line 2677
#15 IA__g_main_loop_run
at gmain.c line 2881
#16 IA__gtk_main
at gtkmain.c line 1171
#17 main


(gdb) p *space
$1 = {parent_instance = {g_type_instance = {g_class = 0x82e1e20}, ref_count = 4, qdata = 0x824ae50}, priv = 0x210fc0}

(gdb) p *space->priv
Cannot access memory at address 0x210fc0

Comment 3 Vincent Untz 2007-04-29 23:21:09 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 ***

Comment 4 Vincent Untz 2007-04-30 09:21:30 UTC

Note that I'm not 100% sure it's a duplicate, but the current stack trace is unfortunately not useful. Either it's a duplicate and we're fine, or we'll need a new stack trace (which is likely to be reported in a new bug) to get more information.