Restricted Update Manager only gets Nvidia drivers after update / reboot

Bug #366842 reported by traist120 on 2009-04-25
Affects Status Importance Assigned to Milestone
linux (Ubuntu)

Bug Description

After installing Jaunty Jackalope's final release, I have had problems with both of my machines.

The Jaunty I installed was 64bit on a Dell Laptop and a Dell Desktop, both using Nvidia graphics cards. After each installation, I would reboot and attempt to install the restricted drivers. There was no "Searching for Drivers" window each time and it will open up with "There are no restricted drivers in use."

I don't know if it is because I updated my machine, or I rebooted but here is the steps for both machines.

Get "Restricted Drivers not in Use"
Open update manager
update my repositories
open restricted driver manager
Get "restricted Drivers not in use."
Open restricted driver manager
Presented with option to download Nvidia drivers

From the looks of it, the only way I can get the drivers to be detected is from updating, then restarting.

Another thing to note, this bug was not present in any of the beta / RC releases. Only in the "Gold" release

affects: ubuntu → linux (Ubuntu)
Jeremy Foshee (jeremyfoshee) wrote :

Hi traist120,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 366842

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-expired
Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers