This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Amarok - won't start - libGL.so.1 [SOLVED]

Tags: None
(comma "," separated)
nilsvdburg
Registered Member
Posts
4
Karma
0
Hi,

I can't start amarok anymore, seems it looks for ligGL.so.1 but cant find it.

This is the output:
nils@nils:/usr/lib/amarok$ amarok
X Error: BadDevice, invalid or uninitialized input device 168
  Major opcode:  148
  Minor opcode:  3
  Resource id:  0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 168
  Major opcode:  148
  Minor opcode:  3
  Resource id:  0x0
Failed to open device
Amarok: [Loader] Starting amarokapp..
Amarok: [Loader] Don't run gdb, valgrind, etc. against this binary! Use amarokapp.
/usr/lib/amarok/amarokapp: error while loading shared libraries: libGL.so.1: cannot open shared object file: No such file or directory


I located the file libGL.so.1:

nils@nils:/usr/lib/amarok$ locate libGL.so.1
/home/nils/download/drivers/fglrx_6_8_0-8.28.8/usr/X11R6/lib/libGL.so.1.2
/home/nils/download/drivers/fglrx_6_8_0-8.28.8/debian/fglrx-6-8-0/usr/X11R6/lib/libGL.so.1.2
/usr/X11R6/lib/FGL.renamed.libGL.so.1.2
/usr/lib/fglrx/libGL.so.1.2.xlibmesa
/usr/lib/fglrx/libGL.so.1.xlibmesa
/usr/lib/FGL.renamed.libGL.so.1.2


But for now on i don't know what to do to make it work...

Any idea?

Last edited by Anonymous on Thu Aug 24, 2006 8:07 am, edited 1 time in total.
User avatar
dangle_wtf
Moderator
Posts
1252
Karma
0
depending on a huge variety of factors, none of which you outline in your email, pretty much anything could have happened.

Have you tried reinstalling or upgrading amarok?


"There are two theories to arguing with women. Neither one works."
.
If men could get pregnant, we'd learn the true meaning of "screaming nancyboy wuss"
User avatar
Jarsto
Registered Member
Posts
42
Karma
0
OS
Looking at my own system there should probably be a symbolic link somewhere from a libGL.so.1.2 to libGL.so.1, which doesn't appear in your "locate libGL.so.1" results. Which it should link to I'm afraid I can't say, that's probably at least partly distro specific and may depend on which drivers you use for x.org.


Jarsto

"There are three rules for writing a novel. Unfortunately, no one knows what they are."
W. Somerset Maugham
nilsvdburg
Registered Member
Posts
4
Karma
0
It was on Ubuntu, but already solved it by reinstalling the Ati drivers, i got the same error executing fglrxinfo, but now it is gone.
Thanks


Bookmarks



Who is online

Registered users: Bing [Bot], Google [Bot], Sogou [Bot], Yahoo [Bot]