nvidia-common should trigger gmenucache for Jockey
Bug #548751 reported by
Alberto Milone
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| nvidia-common (Ubuntu) |
Fix Released
|
High
|
Alberto Milone | ||
Bug Description
Binary package hint: nvidia-common
When Jockey enables a graphics driver which is already installed, the gmenucache trigger is not called (as it's usually called in the postinst script of the package). This can prevent amdcccle and nvidia-settings icons from showing up in the menu.
| Changed in nvidia-common (Ubuntu): | |
| status: | New → Triaged |
| assignee: | nobody → Alberto Milone (albertomilone) |
| importance: | Undecided → High |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in nvidia-common (Ubuntu): | |
| status: | Triaged → Fix Released |
To post a comment you must log in.
This bug was fixed in the package nvidia-common - 0.2.22
---------------
nvidia-common (0.2.22) lucid; urgency=low
* debian/control:
- Add dependency on fglrx-modaliases.
* debian/
- Put back the config script with only one line to source
debconf so that the template file is loaded when
nvidia-common is triggered by kernel hooks (LP: #533970).
Thanks to Colin Watson for the advice.
* NvidiaDetector/
- Add the update_gmenu method and call it in set_alternative
so that the gnome menu is updated when we switch between
drivers (LP: #548751).
- Add the resolve_
module name from the alias (relevant to #547066).
-- Alberto Milone <email address hidden> Mon, 15 Mar 2010 16:44:17 +0100