GNOME Bugzilla – Bug 312659
window selector runs, but doesn't function.
Last modified: 2005-09-03 05:05:30 UTC
Please describe the problem: Windows do not switch. Minimized, rolled, hidden, doesn't matter. Windows do not focus at all. Have to use alt-tab instead. Steps to reproduce: 1. Click on the window-selector icon. 2. Click on a listed app. 3. App doesn't come into focus. Window doesn't become active window. Actual results: App windows do not come into focus like they are supposed to. Window doesn't become active. Expected results: App window should come into focus. App window should become active. Does this happen every time? Since last package upgrade consisting of the following packages: glib2 2.6.5-1 --> 2.6.6-1; gtk2 2.6.8-1 --> 2.6.9-1; hal 0.5.2-4 --> 0.5.3-1 Other information:
Please close this bug. I don't know why, but it works ok now (after a restart).
It doesn't work again :( I don't know why yet, but let me find out. Thanks.
I think I am experiencing this very same bug too, have a look at the following Debian bug: (are you using debian too?): http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=321949 Also see http://lists.debian.org/debian-gtk-gnome/2005/08/msg00010.html Hans, I think you should bump Severity of this bug, I cannot do so.
Adding to Hans experience... I have a single window-selector applet on the panel that exibits this behavior. If I add another window-selector to the panel, it will work for a short time, then fail as before.
@ Ralph Sorry but I'm not running debian but archlinux. Upping the severity to major. Like what Matthew reports, I confirm that a new instance of window selector does work for a short time then fails. Btw, when did you guys notice this bug? (after package upgrades, etc.)
I noticed after a GTK+ Upgrade from 2.6.4 to 2.6.9
I track Debian unstable, i.e. I update every day. Therefore I cannot say exactly *if* this problem is update related, but I suppose it is very likely. Look at my Debian bug for the program versions shortly after my problem appeared. I don't know the version before, but it might have been a case of updating to GTK+ 2.6.9, as with Dave. /ralph -- thanks hans for upping severity. This makes the applet useles for me.
Ah, and forgot to add: Right after logging in, the applet works a few times, like others have reported.
Appears to be a unique bug reports, setting version ->2.10, marking priority->high & severity->critical (the applet doesn't crash, but doesn't work either). I can trigger it always, the first time i use the applet to give focus to an app window it works as expected, the second time i try i've got the following error messages on the terminal (running the applet thru gdb) and the app window stay without focus. (I've tried to get a backtrace but i think isn't so useful). (wnck-applet:20604): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed (wnck-applet:20604): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (wnck-applet:20604): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed (wnck-applet:20604): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (wnck-applet:20604): Gtk-CRITICAL **: gtk_window_group_add_window: assertion `GTK_IS_WINDOW_GROUP (window_group)' failed (wnck-applet:20604): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed (wnck-applet:20604): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (wnck-applet:20604): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed (wnck-applet:20604): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (wnck-applet:20604): Gtk-CRITICAL **: gtk_window_group_add_window: assertion `GTK_IS_WINDOW_GROUP (window_group)' failed (wnck-applet:20604): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed (wnck-applet:20604): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (wnck-applet:20604): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed (wnck-applet:20604): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (wnck-applet:20604): Gtk-CRITICAL **: gtk_window_group_add_window: assertion `GTK_IS_WINDOW_GROUP (window_group)' failed (wnck-applet:20604): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed (wnck-applet:20604): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed Program received signal SIGINT, Interrupt. [Switching to Thread -1223227008 (LWP 20604)] 0xffffe410 in __kernel_vsyscall () (gdb) thread apply all bt
+ Trace 62532
Thread 1 (Thread -1223227008 (LWP 20604))
Can one of you downgrade to GTK+ 2.6.8 and see if it works?
Ok, i think i've replaced all the relevant gtk libs: $ dpkg -l | grep libgtk2.0 ~ ii libgtk2.0-0 2.6.8-1 The GTK+ graphical user interface library ii libgtk2.0-bin 2.6.8-1 The programs for the GTK+ graphical user int ii libgtk2.0-common 2.6.8-1 Common files for the GTK+ graphical user int ii libgtk2.0-dev 2.6.9-1 Development files for the GTK+ library and seems to fix it. Vincent, should i check something else?
So, it means a change in GTK+ triggers this bug. We need to look at what has changed between those two releases (it shouldn't be a big list).
Created attachment 51282 [details] diff -u gtk+-2.6.8/gtk/gtkwindow.c gtk+-2.6.9/gtk/gtkwindow.c
I've done a fast search in the sources and found some diff in gtk/gtkwindow.c about focus behaviour, do you spot something?
I experienced this bug, too, but after an update to gtk 2.8.0, the applet works again. (gnome-panel version is 2.10.2, distribution is debian)
Andrea: do you have the possibility to update GTK+ to 2.8.x? :-)
Sorry if i wasn't clear in comment #11, i've tried with libgtk 2.6.8 and the applet works ok, the bug disappear. I was trying to recompile the 2.6.9 without the diff above, but seems i cant build a working lib, even without touching the sources (every gtk program segfault, i've asked in the debian gtk-gnome mailing list for help)...
Problem seems fixed with libgtk 2.6.10. Vincent, only now i've realized what you asked in #16. Doh!
I can confirm that this problem is fixed with gtk 2.6.10.
*** Bug 314313 has been marked as a duplicate of this bug. ***
I confirm as well. Fixed in GTK+ 2.6.10.
Thanks all. Closing.