On Wed, Apr 17, 2013 at 06:38:28PM +0200, David Sommerseth wrote: > >> > >> Hi, there. I am extremely super curious - "what warning?" > > > > https://plus.google.com/u/0/112648813199640203443/posts/7LrVTf43yz8 > > <http://www.h-online.com/open/news/item/Chrome-stops-declaring-Linux-systems-obsolete-1803451.html> >
And *that* link refers to: https://code.google.com/p/chromium/issues/detail?id=175842 and https://plus.google.com/u/0/100132233764003563318/posts/Y1s6T44Soby And this is all from last February (it is April now). The issue seems to be related to the required GTK version (rpm -q gtk2). Here is today's version of the relevant code: http://git.chromium.org/gitweb/?p=chromium/chromium.git;a=blob;f=chrome/browser/ui/startup/obsolete_os_prompt_gtk.cc;h=a27746e4fd1d32d93867efc32784bff057c370bc;hb=3a9448cfd3ae19cc02ed441beaff4359d9925516 SL6 gtk2 is gtk2-2.18.9-12.el6.x86_64 required by google-chrome is: gtk_check_version(2, 18, 0) So looks like we are okey, right? 2.18 present, 2.18 required. But wait, there is more! the g+ code snapshot has the function name "ObsoleteOSinfobar::Create", the code I found looks completely different. So what is going on? google search to the rescue, here it is: https://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/ui/startup/obsolete_os_infobar_delegate.cc and it has: gtk_check_version(2, 24, 0) I do not know why codes at git.chromium.org and at src.chromium.org are so different. Now, will the real source code for google-chrome stand up please. P.S. One thing is clear now. It looks as if people who see the warning are running chromium from chromium, not google-chrome from google. -- Konstantin Olchanski Data Acquisition Systems: The Bytes Must Flow! Email: olchansk-at-triumf-dot-ca Snail mail: 4004 Wesbrook Mall, TRIUMF, Vancouver, B.C., V6T 2A3, Canada
