Hmm. It looks like that .nvidia_new_installed was modified on the 28th. medigeek: OK here's what I think part of the issue is: 1. nvidia-glx-new was installed by hand creating a hidden dotfile. 2. Thanks to certain modaliases restricted-manager defaulted to installing nvidia-glx on your hardware. 3. The left over dotfile caused the loading of the nvidia-glx-new kernel module even though restricted manager had put nvidia-glx on. 4. X fails to start.
This would boil down to Bug #106217 (the dotfile should have been removed when restricted-manager pulled up nvidia-glx-new or when nvidia- glx was installed). This is testable by remove nvidia-glx-new, checking to see if that dotfile remains and if so removing that and then using restricted-manager etc. The other part of the issue is why did X fail to start after a kernel update (which caused you to use restricted-manager in the first place)? I suspect the clues and logs as to why that happened are long gone but in many respects that's the more interesting issue. Could it have been another module mismatch? Did depmod just need to be run at the right time (but had previously failed due to races)? Unless you find steps that can reliably reproduce that problem we may never know... At the end of the day I guess this boils down to which issue do you want this bug to be about? -- restricted drivers manager installs wrong driver for nx7300gt https://bugs.launchpad.net/bugs/136746 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
