Ubuntu
restricted-manager package

nvidia_new and _legacy not detected as 'in use'

Bug #105812 reported by Martin Pitt
8
Affects Status Importance Assigned to Milestone
restricted-manager (Ubuntu)
Fix Released
High
Martin Pitt
Ubuntu ubuntu-7.04

Bug Description

Binary package hint: restricted-manager

I just discovered an oddity with the nvidia modules: when modprobing _legacy or _new, lsmod still shows 'nvidia' without a suffix. r-m needs to be taught about this special case so that the status column and the 'used' check for the notification work properly.

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

http://codebrowse.launchpad.net/~ubuntu-core-dev/restricted-manager/trunk/revision/martin.pitt%40ubuntu.com-20070412083610-xrojqlgiqx250ftc?start_revid=martin.pitt%40ubuntu.com-20070412083610-xrojqlgiqx250ftc

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

 restricted-manager (0.20) feisty; urgency=low
 .
   * RestrictedManager/nvidia.py: Override is_loaded() and check for the
     "nvidia" module also for legacy and new, since all three modules appear as
     just "nvidia" in lsmod. (LP: #105812)

Changed in restricted-manager:
status: Fix Committed → Fix Released
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.