I run gentoo stable with gnome and metacity and have recently noticed that windows are not focusing properly when I click on them in the gnome-panel. Basically what happens is that clicking on them will defocus the current window, but not focus the new window. I then have to click a second time to focus the window properly. I have noticed that this happens in the following situations: firefox -> gnome-terminal gnome-terminal -> firefox xchat -> gnome-terminal gnome-terminal -> xchat etc. I've noticed this DOESN'T happen when changing window to/from nautilus. I reported the problem on the gentoo forums, and it seems a few people have encountered the problem. http://forums.gentoo.org/viewtopic.php?p=2365689 Please help! Its fairly unprofessional for a distribution such as gentoo to have this sort of problem in its stable tree. Thanks very much, Matt
What versions of metacity and libwnck do you have in your system? Also, please remember to always include the output from 'emerge info' when reporting bugs. Thanks.
Apologies: metacity is at version: 2.8.13 libwnck is at version: 2.8.1-r1 root@eustathios matt # emerge info Portage 2.0.51.19 (default-linux/x86/2005.0, gcc-3.3.5-20050130, glibc-2.3.4.20041102-r1, 2.6.10 i686) ================================================================= System uname: 2.6.10 i686 Pentium III (Katmai) Gentoo Base System version 1.4.16 Python: dev-lang/python-2.3.5 [2.3.5 (#1, Apr 29 2005, 08:23:28)] distcc 2.16 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] dev-lang/python: 2.3.5 sys-apps/sandbox: [Not Present] sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.5, 1.8.5-r3, 1.9.5, 1.6.3, 1.7.9-r1, 1.4_p6 sys-devel/binutils: 2.15.92.0.2-r7 sys-devel/libtool: 1.5.16 virtual/os-headers: 2.6.8.1-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O2 -march=pentium3 -pipe -ftracer -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=pentium3 -pipe -ftracer -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo" LANG="en_GB.UTF-8" LDFLAGS="-Wl,-O1" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X a52 aac alsa apache2 avi bash-completion berkdb bitmap-fonts cdr divx dvd dvdread ffmpeg gif gnome gpm gtk gtk2 imlib javascript jpeg mp3 mpeg nls nptl nptlonly opengl pam perl png quicktime real ssl truetype truetype-fonts type1-fonts userlocales x86 xv xvid userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CBUILD, CTARGET, LC_ALL, LINGUAS, PORTDIR_OVERLAY
Same problem here. If I remember correctly it started upgrading from 2.8.2 to 2.8.3. Gentoo Base System version 1.4.16 Portage 2.0.51.19 (default-linux/amd64/2004.3, gcc-3.4.3, glibc-2.3.4.20041102-r1, 2.6.11-cko5 x86_64) ================================================================= System uname: 2.6.11-cko5 x86_64 AMD Athlon(tm) 64 Processor 3200+ Python: dev-lang/python-2.3.5 [2.3.5 (#1, May 12 2005, 10:18:07)] ccache version 2.3 [enabled] dev-lang/python: 2.3.5 sys-apps/sandbox: [Not Present] sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.7.9-r1, 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.9.5 sys-devel/binutils: 2.15.92.0.2-r8 sys-devel/libtool: 1.5.16 virtual/os-headers: 2.6.8.1-r4 ACCEPT_KEYWORDS="amd64" AUTOCLEAN="yes" CFLAGS="-march=athlon64 -O2 -pipe -fomit-frame-pointer" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=athlon64 -O2 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox strict" GENTOO_MIRRORS="http://gentoo.inode.at" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="amd64 16bit X a52 aac acpi4linux alsa audiofile avi bash-completion bitmap-fonts blender-game bzip2 ccache cdda cdparanoia cdr codecs cscope css cups dpms dv dvd dvdr dvdread emacs emul-linux encode fame ffmpeg freetype ftp gimp gimpprint glut gnome gpm gstreamer gtk gtk2 hal java jpeg lm_sensors mikmod mmap mp3 mpeg mpeg4 mplayer multilib ncurses nls nptl nptlonly oggvorbis opengl pam pdflib png readline rtc sdl ssl tcpd tiff truetype truetype-fonts type1-fonts unicode userlocales utf8 v4l xv xvid zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY
does using metacity-2.10.x improve the situation ?
No, metacity upgrade doesn't help, I've already tested it. BUT I've just tried updating gnome-base/gnome-panel to 2.10 and it WORKS! No problems anymore. So my suggestion for everyone that have this problem is: ACCEPT_KEYWORDS="~amd64" emerge "=gnome-panel-2.10.0" These are the updated packages on my system: Calculating dependencies ...done! [ebuild U ] gnome-base/gnome-vfs-2.10.0-r1 [2.8.4-r1] -debug -doc -gnutls +hal -howl -ipv6 -samba +ssl 1,856 kB [ebuild U ] gnome-base/gnome-desktop-2.10.0 [2.8.3] -debug 1,076 kB [ebuild N ] gnome-base/gnome-menus-2.10.0 -debug 329 kB [ebuild U ] x11-libs/libwnck-2.10.0 [2.8.1-r1] -debug -doc 409 kB [ebuild U ] dev-libs/atk-1.9.1 [1.8.0] -debug -doc -static 472 kB [ebuild U ] gnome-base/libglade-2.5.1 [2.4.2] -debug -doc 310 kB [ebuild U ] gnome-base/gnome-panel-2.10.0 [2.8.3] -debug -doc -eds 3,012 kB Total size of downloads: 7,467 kB
never emerge a package with "ACCEPT_KEYWORDS="~arch" emerge <package". That will revert everything back to the old versions upon an emerge update. use the /etc/portage/package.keywords for that.
(In reply to comment #6) > never emerge a package with "ACCEPT_KEYWORDS="~arch" emerge <package". That will > revert everything back to the old versions upon an emerge update. > use the /etc/portage/package.keywords for that. No, if I wait for 2.10 to become "stable" before running "emerge gnome ..." :D Ok, ok. One may want to run "emerge --update world"... but I usually don't and I've posted the first thing that worked for me, not the _perfect_ one. :)
how come you don't update world? how do you update your system? that's another bad advice. :P ok, everyone knows how to run their system, but i just told that because many people may come here to find the solution and emerging things that way might do some harm.
(In reply to comment #8) > how come you don't update world? how do you update your system? that's another > bad advice. :P > ok, everyone knows how to run their system, but i just told that because many > people may come here to find the solution and emerging things that way might do > some harm. I periodically run "emerge --update system" and manually update other packages I'm interested in (and the dependences cause the update of other packages, usually libs). The end result is an almost fully updated system. And note that I've said: "I usually don't run: emerge --update world", and not "I never run...". Apart these considerations it's obvious that the right thing to do is what you have said.
Matthew, Can you confirm if upgrading to gnome-panel-2.10 resolves this problem for you? Pedro, Please refrain yourself from posting comments with no relevant information regarding the bug. Bugzilla is not the place for discussing things like the way to use portage, as the reporters know what they're doing.
No further back from original reporter. Apparently it's fixed in gnome-panel-2.10.0, as stated in comment #5.
