Did an upgrade (NOT an install from scratch) to 9.3. Then started having problems trying to run Gnome-related stuff. Found the explanation. Last year, one way or another, I ended up with a Gtk library in /usr/local/lib. 9.3 put that same library into /opt/gnome/lib. But the upgrade hadn't cleaned up the previous /usr/local/lib. Result: This year's Gnome was still fetching from /usr/local/lib, and the module there didn't cut the mustard. My conclusion: The 'Update an existing system' installation process did not check whether the files it put into place had duplicates elsewhere in my system. [And when SuSEConfig runs, it re-links in the obsolete /usr/local/lib module !!] I *still* haven't figured out why on my 9.3 system the Gnome-related stuff was looking for that Gtk library first in /usr/local/lib and not first in /opt/gnome/lib. mikus
Mikus Grinbergs wrote:
Did an upgrade (NOT an install from scratch) to 9.3. Then started having problems trying to run Gnome-related stuff.
Found the explanation. Last year, one way or another, I ended up with a Gtk library in /usr/local/lib. 9.3 put that same library into /opt/gnome/lib. But the upgrade hadn't cleaned up the previous /usr/local/lib.
That's what happens if you don't use rpm to install packages. The system has no way of knowing that an old version of the lib is floating around. I *still*
haven't figured out why on my 9.3 system the Gnome-related stuff was looking for that Gtk library first in /usr/local/lib and not first in /opt/gnome/lib.
Because /usr/local/lib comes before /opt/gnome/lib in /etc/ld.so.conf? Regards, -- Jos van Kan www.josvankan.tk
On Thu, 01 Sep 2005 12:11:10 +0200 Jos van Kan <vankan@kabelfoon.nl> wrote:
Mikus Grinbergs wrote:
Did an upgrade (NOT an install from scratch) to 9.3. Then started having problems trying to run Gnome-related stuff.
Found the explanation. Last year, one way or another, I ended up with a Gtk library in /usr/local/lib. 9.3 put that same library into /opt/gnome/lib. But the upgrade hadn't cleaned up the previous /usr/local/lib.
That's what happens if you don't use rpm to install packages. The system has no way of knowing that an old version of the lib is floating around.
To the best of my recollection, I have *never* not used rpm. In particular, SuSE's 'Update an existing system' installation that I ran from the 9.3 DVD appeared to run 'rpm' under the covers in order to put in place the newer packages it provided.
I *still*
haven't figured out why on my 9.3 system the Gnome-related stuff was looking for that Gtk library first in /usr/local/lib and not first in /opt/gnome/lib.
Because /usr/local/lib comes before /opt/gnome/lib in /etc/ld.so.conf?
Good to learn. I *had* changed the order of the lines there. But I guess I hadn't rebooted since making that change. mikus
Mikus Grinbergs wrote:
On Thu, 01 Sep 2005 12:11:10 +0200 Jos van Kan <vankan@kabelfoon.nl> wrote:
Mikus Grinbergs wrote:
Found the explanation. Last year, one way or another, I ended
up with a Gtk library in /usr/local/lib. 9.3 put that same library into /opt/gnome/lib. But the upgrade hadn't cleaned up the previous /usr/local/lib.
That's what happens if you don't use rpm to install packages. The system has no way of knowing that an old version of the lib is floating around.
To the best of my recollection, I have *never* not used rpm. In particular, SuSE's 'Update an existing system' installation that I ran from the 9.3 DVD appeared to run 'rpm' under the covers in order to put in place the newer packages it provided.
Another possibility is that it is a third party package (suggested by the fact that it is in /usr/local) in which case SuSE declares it taboo and does not touch it. You can see that in Yast: it has a lock icon. But in that case I cannot imagine that Yast didn't balk about version conflicts.
I *still*
haven't figured out why on my 9.3 system the Gnome-related stuff was looking for that Gtk library first in /usr/local/lib and not first in /opt/gnome/lib.
Because /usr/local/lib comes before /opt/gnome/lib in /etc/ld.so.conf?
Good to learn. I *had* changed the order of the lines there. But I guess I hadn't rebooted since making that change.
You don't have to reboot, but you *must* run ldconfig after tinkering with ld.so.config Regards, -- Jos van Kan www.josvankan.tk
participants (2)
-
Jos van Kan -
mikus＠bga.com