Paladine: I've only quickly skimmed this report but using -new for appropriate cards is effectively Bug #93209 but Bug #106649 is more targeted. The hidden file problem is bug #106217 . restricted-manager is supposed to leave already installed binary NVIDIA drivers alone so it will help if you carefully outline when this doesn't happen, how often you can reproduce the issue and the steps that can be followed that always reproduce the issue (this is definitely worth investigating). It's best to stick to one issue per bug even if the issues initially look related otherwise things can be come unfocussed and it becomes impossible to duplicate one bug on another bug.
If someone goes down the manual binary driver installation route they are on their own (you can do what you like to your own system but you have to live with the consequences). The reasoning is that they have stepped outside the packaging system thus it is impossible to safely clean up because you don't know what has been done and you don't know how to undo it. Anything you do will be a guess and it could be a guess that just leads to more problems (if someone has done two manual installs on top of another you may never be able to find your original mesa libraries which the original install moved out of the way). A fine point though and hopefully https://help.ubuntu.com/community/NvidiaManual will be updated to reflect this. Driver mismatches happen for a lot of reasons (e.g. missing drivers, manual install conflicting with repository drivers etc) and it is dangerous to create an issue called "driver mismatch" because all these different problems will be lumped together confusing people. I hope this is useful. -- Restricted Drivers Manager and NVidia https://bugs.launchpad.net/bugs/131852 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
