Hello There,

Trying to start Amarok i all of a sudden get this:

Code: Select all

amarok: symbol lookup error: /usr/lib/libGL.so.1: undefined symbol: _nv000189gl

it used to work just fine till now - where is this coming from and how can i resolve it?
Thank you!
Ron

A bit more information about your Amarok version, KDE version and what you did change since the last time it did work might be helpful.

Mamarok wrote:A bit more information about your Amarok version, KDE version and what you did change since the last time it did work might be helpful.

My amarok is whatever came with Kubuntu 10.04 - that'd be 2.3 I believe. KDE is 4.4.2 and what i did directly before this happened was, i fixed things with akonadi namely, i changed user and permissions on my akonadi directory, nothing else really i can think of...

Could you please make sure your system is up-to-date, e.g. that you have loaded all the updates since the release of Kubuntu 10.04?

Mamarok wrote:Could you please make sure your system is up-to-date, e.g. that you have loaded all the updates since the release of Kubuntu 10.04?

Okay, I did an apt-get update and an apt-get upgrade anbd a few packets got updated, those namely are:
gnome-screensaver google-chrome-beta gtk2-engines-pixbuf libgail18 libgtk2.0-0 libgtk2.0-bin
libgtk2.0-common libgtk2.0-dev libgtk2.0-doc libpq5 librsvg2-2 librsvg2-common libvirtodbc0 openssh-client
openssh-server python-apt ssh virtuoso-nepomuk virtuoso-opensource-6.0 virtuoso-opensource-6.0-bin
but even after the update i still get:

Code: Select all

reg@reg-desktop:~$ amarok
amarok: symbol lookup error: /usr/lib/libGL.so.1: undefined symbol: _nv000189gl

libGL - sounds kinda similar to that issue i had after the update to Lucid when i wasn't able to logon to KDE anymore. Following this posting actually solved the issue for me: http://kubuntuforums.net/forums/index.p ... #msg227515 don't know if that may go together in one way or another...? Even tho after doing this, I was still able to start Amarok just fine up till now...

cerr wrote:

Mamarok wrote:Could you please make sure your system is up-to-date, e.g. that you have loaded all the updates since the release of Kubuntu 10.04?

Okay, I did an apt-get update and an apt-get upgrade anbd a few packets got updated, those namely are:
gnome-screensaver google-chrome-beta gtk2-engines-pixbuf libgail18 libgtk2.0-0 libgtk2.0-bin
libgtk2.0-common libgtk2.0-dev libgtk2.0-doc libpq5 librsvg2-2 librsvg2-common libvirtodbc0 openssh-client
openssh-server python-apt ssh virtuoso-nepomuk virtuoso-opensource-6.0 virtuoso-opensource-6.0-bin
but even after the update i still get:

Code: Select all

reg@reg-desktop:~$ amarok
amarok: symbol lookup error: /usr/lib/libGL.so.1: undefined symbol: _nv000189gl

libGL - sounds kinda similar to that issue i had after the update to Lucid when i wasn't able to logon to KDE anymore. Following this posting actually solved the issue for me: http://kubuntuforums.net/forums/index.p ... #msg227515 don't know if that may go together in one way or another...? Even tho after doing this, I was still able to start Amarok just fine up till now...

Okay, got it fixed!!!
I rebooted my pc and i wasn't able to logon to KDE anymore and thus i just deleted /usr/lib/libGL.so.1 again and recreated xorg-conf with nvidia-xconfig and tattaaaaaaaa. I can logon again and use amarok as well.... now i just would love if someone was able to explain what is going on here...

roN

Sounds like a KDM problem to me...

Mamarok wrote:Sounds like a KDM problem to me...

Mh, dunno, kdm seemed to start-up nicely, upon user/pwd entry and [enter], it would start trying to load KDE, then the screen would turn black for a few ms and it would bring me back to the user/pwd prompt... don't know how much kdm is doing until it hands control over to KDE...and anyways, if it was a kdm issue, what does Amarok care...?

Well, I think it is not an Amarok error in the first place, a symbol lookup error could well be a packaging error. But KDE not starting can have various reasons, mostly due to either KDM or to some configuration files.

Try moving your $HOME/.kde/ folder and see if that solves the login issue, then try starting Amarok again.

Mamarok wrote:Well, I think it is not an Amarok error in the first place, a symbol lookup error could well be a packaging error. But KDE not starting can have various reasons, mostly due to either KDM or to some configuration files.

Try moving your $HOME/.kde/ folder and see if that solves the login issue, then try starting Amarok again.

I had tried moving my .kde already before but it didn't help and anyways, this issue has been resolved if you read my posting above...so it's not current anymore, just wondering how it may have happened...?

This happened because the NVidia driver installation was screwed up. This could never have been the fault of KDE, since libGL.so is provided by the system ( ie. your distribution )

Uh, okay, today i got this very same same symbol lookup error again and i did a sudo mv /usr/lib/libGL.so.1 /usr/lib/libGL.so.1~;sudo nvidia-xconfig to get rid of it. I hope I won't need to keep doing this... sounds dangerously like the other symbol lookup error outlined here: viewtopic.php?f=115&t=83340 that came up over and over again with Karmic....

It is possible that the NVidia software did not overwrite higher level libGL.so files. In this case, automatic scripts on boot will replace this symlink with a link to the non-NVidia version.

Code: Select all

ben@grace:~> ls /usr/lib | grep libGL.so
libGL.so
libGL.so.1
libGL.so.1.2

Can you please post the output of the following command both prior to running nvidia-xconfig and after?

Code: Select all

ls -la /usr/lib | grep libGL.so

I moved the topic, since it is not Amarok related at all.

cerr wrote:Uh, okay, today i got this very same same symbol lookup error again and i did a sudo mv /usr/lib/libGL.so.1 /usr/lib/libGL.so.1~;sudo nvidia-xconfig to get rid of it. I hope I won't need to keep doing this... sounds dangerously like the other symbol lookup error outlined here: viewtopic.php?f=115&t=83340 that came up over and over again with Karmic....

The whole deal is right here:

Code: Select all

reg@reg-desktop:~$ ls -la /usr/lib | grep libGL.so
lrwxrwxrwx   1 root root       13 2010-05-01 01:23 libGL.so -> mesa/libGL.so
lrwxrwxrwx   1 root root       15 2010-05-28 18:59 libGL.so.1 -> libGL.so.180.29
lrwxrwxrwx   1 root root       15 2010-05-24 18:53 libGL.so.1~ -> libGL.so.180.29
-rwxr-xr-x   1 root root   701784 2009-02-18 18:45 libGL.so.180.29
lrwxrwxrwx   1 root root       15 2010-05-01 01:49 libGL.so.1.backup_10-05-02 -> libGL.so.180.29
lrwxrwxrwx   1 root root       15 2010-05-16 15:27 libGL.so.1.backup_10-05-21 -> libGL.so.180.29
reg@reg-desktop:~$ sudo mv /usr/lib/libGL.so.1 /usr/lib/libGL.so.1~;sudo nvidia-xconfig
[sudo] password for reg:

Using X configuration file: "/etc/X11/xorg.conf".
Backed up file '/etc/X11/xorg.conf' as '/etc/X11/xorg.conf.backup'
New X configuration file written to '/etc/X11/xorg.conf'

reg@reg-desktop:~$ ls -la /usr/lib | grep libGL.so
lrwxrwxrwx   1 root root       13 2010-05-01 01:23 libGL.so -> mesa/libGL.so
lrwxrwxrwx   1 root root       15 2010-05-28 18:59 libGL.so.1~ -> libGL.so.180.29
-rwxr-xr-x   1 root root   701784 2009-02-18 18:45 libGL.so.180.29
lrwxrwxrwx   1 root root       15 2010-05-01 01:49 libGL.so.1.backup_10-05-02 -> libGL.so.180.29
lrwxrwxrwx   1 root root       15 2010-05-16 15:27 libGL.so.1.backup_10-05-21 -> libGL.so.180.29
reg@reg-desktop:~$

Any further ideas...?