It seems to be OK in 8.10
--
6.06.1 upgrade of nvidia restricted modules fails
https://bugs.launchpad.net/bugs/70235
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Thanks for following up. I'm closing this report due to your last
comment. Don't hesitate to submit any new bug.
** Changed in: update-manager (Ubuntu)
Status: Incomplete = Fix Released
** Changed in: nvidia-kernel-common (Ubuntu)
Status: Confirmed = Fix Released
--
6.06.1
Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently. We were wondering is this still an issue
for you? Can you try with latest Ubuntu release? Thanks in advance.
** Changed in:
That's correct: 6.0.6.1. I'm unwilling to move to edgy because when I
tried it on my laptop it screwed up my working wireless connection
[#69059]. I'll try edgy on my main machine when that gets fixed.
--
6.06.1 upgrade of nvidia restricted modules fails
https://launchpad.net/bugs/70235
--
Ugh. I meant 6.06.1
--
6.06.1 upgrade of nvidia restricted modules fails
https://launchpad.net/bugs/70235
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
The you aren't using edgy, correct?
--
6.06.1 upgrade of nvidia restricted modules fails
https://launchpad.net/bugs/70235
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I already had
linux-amd64-generic
linux-image-amd64-generic
linux-restricted-modules-amd64-generic
--
6.06.1 upgrade of nvidia restricted modules fails
https://launchpad.net/bugs/70235
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Changed in: update-manager (Ubuntu)
Status: Unconfirmed = Confirmed
--
6.06.1 upgrade of nvidia restricted modules fails
https://launchpad.net/bugs/70235
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
This sounds more like a problem with users not having proper meta
packages installed, so getting version skew.
sudo apt-get install linux-generic linux-restricted-modules-generic
That should pull in everything required, please test and make sure.
If you had the proper metapackages before
** Also affects: update-manager (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
6.06.1 upgrade of nvidia restricted modules fails
https://launchpad.net/bugs/70235
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I had this problem when I upgraded nvidia-glx and linux-restricted-
modules a few days ago. The contents of /var/log/gdm/:0.log are in the
file attached. The error reported is that there is a version mismatch
between the kernel module (8762) and the X module (8776)
This happens with kernel
I just realized that I have XGL installed, I'm betting that's the cause
of my problem
--
6.06.1 upgrade of nvidia restricted modules fails
https://launchpad.net/bugs/70235
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I had the same problem. After a complete re-install I installed the
nvidia binary driver and a new kernel (2.6.15-27-686 with SMP enabled).
I changed the driver from nv to nvidia but then xorg gave me the api
error. After a reboot everything worked fine.
--
6.06.1 upgrade of nvidia restricted
I had the same problem after updating my system on Nov 5. I resolved it
by downgrading nvidia-glx using the following command:
sudo apt-get install nvidia-glx=1.0.8762+2.6.15.11-1
** Changed in: nvidia-kernel-common (Ubuntu)
Status: Unconfirmed = Confirmed
--
6.06.1 upgrade of nvidia
** Changed in: Ubuntu
Sourcepackagename: None = nvidia-kernel-common
--
6.06.1 upgrade of nvidia restricted modules fails
https://launchpad.net/bugs/70235
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I'd like to convert this into a bug about the update-manager but don't
know how to do this.
Clearly, the solution was to reboot, but the update-manager normally
prompts the user when a reboot is necessary. It didn't do so on this
occasion. I clearly should. It doesn't make sense to have it
16 matches
Mail list logo
