I had the same problem I solved it with the command
sudo ln -s /usr/lib/nvidia-331/libGL.so.1 /usr/lib/libGL.so.1
my nvidia drives were install using nvidia-331
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
That version is no more supported; please open a new bug report if the
actual archive found version also has the same issue.
** Changed in: mesa (Ubuntu)
Status: New => Invalid
** Changed in: fglrx-driver (Ubuntu)
Status: New => Invalid
** Changed in: nvidia-drivers-ubuntu
** Also affects: mesa (Ubuntu)
Importance: Undecided
Status: New
** Also affects: fglrx-driver (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
have a similar program with the mesa drivers, using different program: Ansolft
HFSS.
i tried to use the sym link work-around without success
the error from hfss on the command line is
Unable to resolve function glXQueryExtension
my links are
> ls -al /usr/lib/libGL*
lrwxrwxrwx 1 root root
Right. The current alternatives system via ld.so.conf.d is easier to
maintain and a bit less fragile than our previous system.
It does have the problem that software with a fixed search path, or that
doesn't use the linker, will not work. For those, I suggest the symlink
workaround. We can't ea
** Changed in: nvidia-graphics-drivers (Ubuntu)
Status: New => Won't Fix
--
Unable to resolve function glX...
https://bugs.launchpad.net/bugs/589250
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubun
libGL.so is provided by multiple packages: mesa, nvidia, ati. In the
past, it used to use the alternatives system to select the GL library.
The current approach since (and including) lucid is to install a
configuration file in /etc/ld.so.conf.d that instructs the linker to
look in /usr/lib/$PROVIDE
libGL.so is provided by multiple packages: mesa, nvidia, ati. In the
past, it used to use the alternatives system to select the GL library.
The current approach since (and including) lucid is to install a
configuration file in /etc/ld.so.conf.d that instructs the linker to
look in /usr/lib/$PROVIDE
his bug also affects Altair's HyperView software. The above work around
fix the the problem. I would be interested to know why the libGL.so.1
was moved when compared to Ubuntu 9.10.
--
Unable to resolve function glX...
https://bugs.launchpad.net/bugs/589250
You received this bug notification be
I agree with Graham.
Conceptually you have to find where is your libGL.so.1 and then create a
dynamic link in /usr/lib/.
In my case i have Ansys WB 12.1 on a Sony-Vaio laptop with ATI Radeon Video
card and O.S. Ubuntu 10.04 Desktop for X86-64 and i solved the problem this
way:
sudo ln -s /usr
I've discovered that ANSYS DesignModeller expects to find libGL.so.1 in
/usr/lib/.
The following solved my problem:
sudo ln -s /usr/lib/nvidia-current/libGL.so.1
/usr/lib/libGL.so.1
--
Unable to resolve function glX...
https://bugs.launchpad.net/bugs/589250
You received this bug notific
** Also affects: nvidia-drivers-ubuntu
Importance: Undecided
Status: New
--
Unable to resolve function glX...
https://bugs.launchpad.net/bugs/589250
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
u
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/49609018/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/49609020/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/49609021/Dependencies.txt
** A
13 matches
Mail list logo
