restricted-manager fails to install driver wen the package list is not up-to-date

Bug #133398 reported by Pim Nijdam
2
Affects Status Importance Assigned to Milestone
Restricted Manager
Fix Released
Undecided
Unassigned

Bug Description

Using a fresh, clean Xubuntu gutsy tribe4 install. Package list isn't updated after the installation.

Starting the restricted-manager and trying to enable the closed ati driver doesn't work: the enabled box stays unticked and no error message is displayed. (Trying to manually install the closed ati driver fails also, because the package list isn't up-to-date) However, when the package list is updated, the restricted-manager installs the closed ati driver nicely.

Revision history for this message
Nanley Chery (nanoman) wrote :

I think it's only normal that the installation from r-m fails if you don't reload the source list. When r-m prompts that a repository needs to be enabled for the driver to be downloaded, the user would open up "Software Sources," enable the right repositories and on clicking exit, be notified to reload their source list. If this did not happen to you in Tribe 4, did it happen in Tribe 5?

Changed in restricted-manager:
status: New → Incomplete
Revision history for this message
Pim Nijdam (pim-n) wrote :

It did not happen in Tribe 4. In Tribe 5 r-m indeed displayed a message that a repository needed to be enabled.

However, when I opened up "Software Sources", all repositories except "Source code" were enabled; the package list just wasn't updated. Since I changed nothing, I wasn't notified to reload the source list and still couldn't install the driver.

It seems to me that r-m now does the right thing: notify the user. Still, the package list needs to be updated to install the restricted driver. Maybe during the ubuntu installation, or the "Software Sources" app should notice that the repositories are enabled, but the package lists not retrieved. Anyway, r-m seems to be working properly and I'll close this bug.

Revision history for this message
Pim Nijdam (pim-n) wrote :

Fix was merged to trunk even before this bug was reported. Commited: revision 157.2.42 Merged: revision 186

Changed in restricted-manager:
status: Incomplete → Fix Released
Revision history for this message
Matteo Z (matteozandi) wrote :

Pim: please be careful when setting "fix released", I'm marking this bug as duplicated since I believe this is the same problem as reported in #134918, where we also involved update-manager.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.