Please see:
https://bugzilla.gnome.org/show_bug.cgi?id=590404
Notes Client 8.5 (and 8.5.1) will not run on Linux due to how is writes the GTK UI …
Please help fix… we planned on rolling out Ubuntu 9.10 when released, but will obviously hold out until this issue is resolved… Thanks… hopefully it’ll make its way into 8.5.1 … anyone have insight if this issue is being worked on?
Subject: Under investigation…
This is being investigated in SPR: YYSN7VRA4F. As a work-around, use GTK v2.17.2.
Subject: thanks, but that’s not completely accurate
I appreciate the SPR, but your suggestion won’t work. Notes breaks in Gtk 2.17.2 or higher, so you can either use the default Gtk in Ubuntu 9.10, which is 2.16, or only upgrade as high as 2.17.1.
There is some urgency to this issue since Gtk 2.18 is targeted for release in October. Once that package is updated and added to the standard repositories for Ubuntu, Red Hat, and Suse, you are going to start seeing a lot more reports of this.
Subject: Workaround != Fix
Yes, you can do a work around by copying the 2.17.2 libraries into /opt/ibm/lotus/notes, but the problem is about to become severe as many distributions are slated to release new versions very shortly:
openSUSE 11.2
Ubuntu 9.10
Fedora 12
(just to name some of the major distributions).
As stated in the other response 2.18 is already slated for release, and we’re at 2.17.11 in the 2.17 versioning.
My question is will this issue be fixed with 8.5.1 which I’m sure is slated to be released AROUND the same time these new distributions come out.
If not, then what and when can we expect a fix?
Subject: GTK+ v2.17.x is currently unstable…
Per the following URL:
http://www.gtk.org/download-linux.html
Notice how announcements on the GTK+ Project’s website related to v2.17.x releases all note this & that they are ‘Development releases’:
Unfortunately, there are some distros of Linux which distribute updates with unstable packages. That said, we cannot expect IBM to support unstable releases of GTK+. It is interesting to note that some can work-around the problem using v2.17.2, while others must use v2.17.1.
Subject: Yes… BUT
Yes but the code from the development / unstable packages will be rolled into 2.18 which will be released around the time of these distributions (and I’m guessing they will roll out with 2.18, or have an update path to it).
with that said I’d expect the issue to still be in 2.18.