Restricted Manager

Requests restricted-modules package

Bug #107705 reported by Mårten Woxberg
10
Affects Status Importance Assigned to Milestone
Restricted Manager
Invalid
Low
Martin Pitt
restricted-manager (Ubuntu)
Fix Released
Low
Martin Pitt

Bug Description

Instead of requesting the linux-restricted-modules for the current kernel
can't it just tell the user that the linux-restricted-modules-generic is required and then ask
the user if it want's to install this?

Why should the user need to open up synaptic and find 7 packages with similar name
when there's only one needed for it to work with further kernel upgrades too.

Revision history for this message
Martin Pitt (pitti) wrote :

Indeed.

Changed in restricted-manager:
assignee: nobody → pitti
importance: Undecided → Low
status: Unconfirmed → In Progress
Revision history for this message
Martin Pitt (pitti) wrote :

Using distro task.

Changed in restricted-manager:
status: In Progress → Rejected
assignee: nobody → pitti
importance: Undecided → Low
status: Unconfirmed → In Progress
Revision history for this message
Christian Page (mudfly) wrote :

I agree this need fixing, I ran into the same bug and just came out to report it.

Revision history for this message
Martin Pitt (pitti) wrote :

Fixed in bzr head.

Changed in restricted-manager:
status: In Progress → Fix Committed
Revision history for this message
Martin Pitt (pitti) wrote :

restricted-manager (0.24) gutsy; urgency=low

  [ Matteo Zandi ]
  * RestrictedManager/lrm_driver.py: load_lrmc_disabled() and
    save_lrmc_disabled() now handle trailing spaces in
    /etc/default/linux-restricted-modules-common. (LP: #122359)
  * RestrictedManager/bcm43xx.py: remove fake firmware file when
    disabling bcm43xx.
  * restricted-manager: Added new class DefaultHandlerMessageDialog that can be
    used to give messages from handlers.

  [ Martin Pitt ]
  * debian/restricted-manager.postinst: Do not call addgroup if the admin
    group already exists. In some corner cases, addgroup fails at this
    condidion. (LP: #122892)
  * Add man/restricted-manager.8: man page for r-m, thanks to Cesare
    Tirabassi! (LP: #128697)
  * restricted-manager: Check for l-r-m-generic package instead of the kernel
    ABI specific one. (LP: #107705)
  * debian/control: Add dependency to l-r-m-{generic,i386} on i386/amd64, since
    r-m does not work without it anyway and it just creates confusion.
  * RestrictedManager/bcm43xx.py: Check if bcm43xx-fwcutter could actually get
    installed before proceeding.
  * RestrictedManager/core.py, install_package(): Check that package is
    actually available; if not, point out that the software source for this
    needs to be enabled. Based on original patch of Matteo, but simplified and
    robustified. (LP: #123061, LP: #124304)

 -- Martin Pitt <email address hidden> Wed, 01 Aug 2007 12:20:55 +0200

Changed in restricted-manager:
status: Fix Committed → Fix Released
Revision history for this message
zeddock (zeddock) wrote :

I believe this impacts me. I am on an nVidia GeForce4 Go 4200 Ti 8x AGP on a Dell Latitude D800.

The restricted Drivers Manager seems to not give me the correct option for a driver. As I recall, Feisty had similar issue but before release it was decided to have several different drivers available... including a NEW driver and a Legacy. I know that I need the 1.0.9639 version but am now unsure in the Gusty development cycle.

Perhaps that new kernel created this newest issue for me?
I would really appreciate anyone who could finally wrap this issue up in Gusty.

zeddock

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

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

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