GNOME Bugzilla – Bug 604281
gtk+ 2.18 breaks Google Chrome status bubble and find bar
Last modified: 2010-03-24 03:25:48 UTC
I have the dev-channel version of Google Chrome installed from http://www.google.com/chrome/intl/en/eula_dev.html?dl=unstable_i386_deb The Chrome UI is built on top of GTK+ I had GTK+ 2.16 installed previously, from Debian packages (libgtk2.0-0_2.16.6-1_i386.deb, etc.). With that 2.16 install, everything works as expected in Chrome; specifically, when I type Ctrl-f, I get a find bar (for searching for strings within the current page) at the top right part of the browser frame, and when I mouse over a hyperlink, I get a status bubble at the bottom left of the browser frame (showing the URL for the link). But after I installed GTK+ 2.18, I no longer get a find bar when I type Ctrl-f, and I no longer get a status bubble when I mouse over a hyperlink.
I can't reproduce this here (Ubuntu 9.10 with GTK+ 2.18.3) Did you try the beta version of chrome?
(In reply to comment #1) > I can't reproduce this here (Ubuntu 9.10 with GTK+ 2.18.3) > Did you try the beta version of chrome? Yep, I just installed the chrome beta and I'm still seeing exactly the same behavior as I do with the current chrome dev-channel release. :(
You're going to have to be more specific with which version of gtk+ you're using now. I've been using Chromium daily builds for a few months now (I think always with 2.18) and I've never seen any issues with using Ctrl-F.
(In reply to comment #3) > You're going to have to be more specific with which version of gtk+ you're > using now. I've been using Chromium daily builds for a few months now (I think > always with 2.18) and I've never seen any issues with using Ctrl-F. (Apologies for the delay in replying, was on a long holiday break) The version of GTK+ 2.18 I'm using is the current Debian testing version, "2.18.3-1" Package: libgtk2.0-0 Maintainer: Sebastien Bacher <seb128@debian.org> Architecture: i386 Source: gtk+2.0 Version: 2.18.3-1 Depends: libgtk2.0-common, libatk1.0-0 (>= 1.20.0), libc6 (>= 2.3.6-6~), libcairo2 (>= 1.6.4-6.1), libcups2 (>= 1.4.0), libfontconfig1 (>= 2.4.0), libfreetype6 (>= 2.2.1), libglib2.0-0 (>= 2.22.0), libgnutls26 (>= 2.7.14-0), libgssapi-krb5-2 (>= 1.6.dfsg.2), libjasper1 (>= 1.900.1), libjpeg62, libpango1.0-0 (>= 1.20.0), libpng12-0 (>= 1.2.13-4), libtiff4, libx11-6, libxcomposite1 (>= 1:0.3-1), libxcursor1 (>> 1.1.2), libxdamage1 (>= 1:1.1), libxext6, libxfixes3 (>= 1:4.0.1), libxi6, libxinerama1, libxrandr2 (>= 2:1.2.99.2), libxrender1, zlib1g (>= 1:1.1.4), shared-mime-info Filename: pool/main/g/gtk+2.0/libgtk2.0-0_2.18.3-1_i386.deb
(In reply to comment #4) > (In reply to comment #3) > > You're going to have to be more specific with which version of gtk+ you're > > using now. I've been using Chromium daily builds for a few months now (I think > > always with 2.18) and I've never seen any issues with using Ctrl-F. > > The version of GTK+ 2.18 I'm using is the current Debian testing version, > "2.18.3-1" In order to try to figure out if it was just a Debian packaging problem, I went ahead and downloaded the GTK+ 2.15 sources and built and installed from those. ...but I nevertheless still see the same exact problem. The only other data possibly-useful data point about my environment that I can think to offer is that I'm running relatively old X server: X.org 7.3 (~2 years old) rather than the currently available X.org 7.4). I'm running X.org 7.3 because when I initially tried to upgrade my environment to 7.4 (about a year ago I guess), I couldn't get my X server to restart, so I backed out to the stable versions I had on my machine and then marked them all as "hold" to prevent them from being auto upgraded. I suppose I should probably try again to install the latest versions of those and see if it fixes that problem I had before.
2.15 is ancient history and even an unstable version. Also, it's vague as it misses the last number.
(In reply to comment #6) > 2.15 is ancient history and even an unstable version. > Also, it's vague as it misses the last number. That was a typo. Sorry for the confusion -- I meant to type "2.18". The exact version I installed was this: http://ftp.gnome.org/pub/gnome/sources/gtk+/2.18/gtk+-2.18.5.tar.gz
(In reply to comment #5) > I'm running X.org 7.3 I upgraded my Debian environment to X.org 7.3 packages and now the problem is gone. So I'm wondering if perhaps the problem I was seeing with Chrome running under GTK+ 2.18 in an X.org 7.3 environment was exposing an incompatibility problem between GTK+ 2.18 and X.org 7.3
Great, closing then