On Fri, 10 Dec 2010 14:35:35 -0800
Daniel Hedlund dijo:
>On Fri, Dec 10, 2010 at 11:17, John Jason Jordan
>wrote:
>> So I reinstalled mesa-libGL and it recreated the link that I had
>> renamed. WTH? Of course, recreating the link means Fontmatrix is back
>> telling me that it can't find libnvidi
On Fri, 10 Dec 2010 14:35:35 -0800
Daniel Hedlund dijo:
>On Fri, Dec 10, 2010 at 11:17, John Jason Jordan
>wrote:
>> So I reinstalled mesa-libGL and it recreated the link that I had
>> renamed. WTH? Of course, recreating the link means Fontmatrix is back
>> telling me that it can't find libnvidi
> "Denis" == Denis Heidtmann writes:
>> ... Sorry I am so late in replying here. I had a medical crisis
>> where I was barely conscious upon arrival that the emergency
>> room. I just got home a couple hours ago after spending the past
>> two days in the ICU.
Denis> Never mind the computer
On Sun, Dec 12, 2010 at 9:30 PM, John Jason Jordan wrote:
> ...
> Sorry I am so late in replying here. I had a medical crisis where I
> was barely conscious upon arrival that the emergency room. I just
> got home a couple hours ago after spending the past two days in the
> ICU.
> _
On Fri, 10 Dec 2010 14:35:35 -0800
Daniel Hedlund dijo:
>On Fri, Dec 10, 2010 at 11:17, John Jason Jordan
>wrote:
>> So I reinstalled mesa-libGL and it recreated the link that I had
>> renamed. WTH? Of course, recreating the link means Fontmatrix is back
>> telling me that it can't find libnvidi
On Fri, Dec 10, 2010 at 11:17, John Jason Jordan wrote:
> So I reinstalled mesa-libGL and it recreated the link that I had
> renamed. WTH? Of course, recreating the link means Fontmatrix is back
> telling me that it can't find libnvidia-tls.so.260.19.21.
Hmm...maybe the nvidia driver registered i
On Thu, 9 Dec 2010 22:19:09 -0800
Daniel Hedlund dijo:
>I'm guessing that when the Nvidia drivers were installed, their own
>versions of shared libraries (i.e. libGL.so.260.19.21) were installed
>into the /usr/lib64 directory and some symlinks were updated to point
>to their version (i.e. libGL.s
On Thu, 9 Dec 2010 22:19:09 -0800
Daniel Hedlund dijo:
>On Thu, Dec 9, 2010 at 21:39, John Jason Jordan
>wrote:
>> The sbin command returned nothing, other than a dozen "no such
>> address or device" messages. But the lib64 command (in addition to a
>> couple dozen similar error messages), gave
On Thu, Dec 9, 2010 at 21:39, John Jason Jordan wrote:
> The sbin command returned nothing, other than a dozen "no such address
> or device" messages. But the lib64 command (in addition to a couple
> dozen similar error messages), gave the following:
>
> /usr/lib64/libcucul.so.0.99.17
> /usr/lib64
On Thu, 9 Dec 2010 20:39:32 -0800
Daniel Hedlund dijo:
>On Thu, Dec 9, 2010 at 19:51, John Jason Jordan
>wrote:
>> I ran "ldd -v $(which fontmatrix) > ~/ldd_fontmatrix.txt. Then I
>> opened up the text file and searched on nvidia. All I found were the
>> same two lines as before:
>>
>> lib
On Thu, Dec 9, 2010 at 19:51, John Jason Jordan wrote:
> I ran "ldd -v $(which fontmatrix) > ~/ldd_fontmatrix.txt. Then I opened
> up the text file and searched on nvidia. All I found were the same two
> lines as before:
>
> libnvidia-tls.so.260.19.21 => not found
> libnvidia-glcore.so
On Thu, 9 Dec 2010 19:15:06 -0800
Daniel Hedlund dijo:
>On Thu, Dec 9, 2010 at 17:02, John Jason Jordan
>wrote:
>> $ ldd $(which ksysguard)
>>
>> libnvidia-tls.so.260.19.21 => not found
>> libnvidia-glcore.so.260.19.21 => not found
>>
>> $ ldd $(which fontmatrix)
>>
On Thu, Dec 9, 2010 at 17:02, John Jason Jordan wrote:
> $ ldd $(which ksysguard)
>
> libnvidia-tls.so.260.19.21 => not found
> libnvidia-glcore.so.260.19.21 => not found
>
> $ ldd $(which fontmatrix)
>
> libnvidia-tls.so.260.19.21 => not found
> libnvid
On Thu, 9 Dec 2010 16:31:34 -0800
Dan Young dijo:
>On Wed, Dec 8, 2010 at 5:59 PM, John Jason Jordan
>wrote:
>> I am at a loss to figure out why installing the nVidia driver should
>> affect these two applications or how it managed to do so. They were
>> both running fine with the nouveau driver
On Thu, 9 Dec 2010 15:28:43 -0800
Daniel Hedlund dijo:
>On Wed, Dec 8, 2010 at 17:59, John Jason Jordan
>wrote:
>
>> $ ksysguard
>> ksysguard: error while loading shared libraries:
>> libnvidia-tls.so.260.19.21: cannot open shared object file: No
>> such file or directory
>
>Is the
On Wed, Dec 8, 2010 at 5:59 PM, John Jason Jordan wrote:
> I am at a loss to figure out why installing the nVidia driver should
> affect these two applications or how it managed to do so. They were
> both running fine with the nouveau driver before I installed the nVidia
> driver.
>
> Does anyone
On Wed, Dec 8, 2010 at 17:59, John Jason Jordan wrote:
> $ ksysguard
> ksysguard: error while loading shared libraries:
> libnvidia-tls.so.260.19.21: cannot open shared object file: No
> such file or directory
Is the libnvidia-tls.so file still on the filesystem?
$ locate libnvidia
On Thu, 9 Dec 2010 10:48:14 -0800
Dale Snell dijo:
># setsebool -P allow_execstack 0
>
> ... The second is for systems running SELinux, which includes
> Fedora. It closes a security hole that nVidia opens.
# setsebool pP allow_execstack 0
setsebool: SELinux is disabled.
I have never messed w
On Thu, 9 Dec 2010 10:48:14 -0800
Dale Snell dijo:
>On Wed, 8 Dec 2010 17:59:19 -0800
>John Jason Jordan wrote:
>
> %< snip! >%
>
>> $ ksysguard
>> ksysguard: error while loading shared libraries:
>> libnvidia-tls.so.260.19.21: cannot open shared object
>> file: No such file or dire
On Wed, 8 Dec 2010 17:59:19 -0800
John Jason Jordan wrote:
%< snip! >%
> $ ksysguard
> ksysguard: error while loading shared libraries:
> libnvidia-tls.so.260.19.21: cannot open shared object
> file: No such file or directory
>
> So today I launched Fontmatrix and discovered the
Without going into the details of an incredibly long trek, about a
month ago I installed the proprietary nVidia driver on my laptop. The
laptop runs Fedora 14 x86_64 and has the nVidia NVS 140M graphics chip.
Later I uninstalled the nVidia driver and went back to the nouveau
driver. I am happy with
21 matches
Mail list logo
