On Sat, Oct 5, 2013 at 7:52 PM, John Andersen wrote:
On 10/4/2013 10:42 PM, David Haller wrote:
Your solution fits that suspicion. With your "reinstall" you did it the right way around: first Mesa (via the default or Xorg repo) and then overwrite the Mesa libglx.so (and the symlinks to the Mesa libGL*.so*) with the files/links to the nvidia libglx.so/libGL* via the install from the nvidia repo.
This is a fundamentally broken way of doing things if you ask me.
If Nvidia needs a to overwrite a system package with their own, you are in a situation where your system is at risk with any update, or security patch.
At a very least Nvidia needs to be a couple release numbers ahead of the system package they are replacing, or change things such that the system package name is not used.
Its a ticking time bomb.
Agreed... and like I said in an earlier reply.. out of a dozen or so separate installs on systems with NVidia... this is the ONLY one that's behaving this way. I've never had to futz about with Mesa and doing any "forced" reinstalls of NVidia drivers because of odd library mismatches or library file overwrites. I even wiped my own machine and did a parallel install with my friend's machine.. mine worked perfect, his failed with X segfaults. It has all the usual bugs we know and love in 12.3... like the initial broken state of the Network Manager... plus this new and exciting segfaulting X. This isn't on a single install either.. we've reinstalled from scratch several times and got the same behaviour. I'm open to doing odd fixes with this particular case... but I don't yet see why this one machine is behaving so differently than any other 12.3 install I've done. I'll poke the log files when we have a chance again this weekend.. maybe the Xorg log file has a new clue? C. -- openSUSE 12.3 x86_64, KDE 4.11 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org