This bug was fixed in the package jockey - 0.5~beta3-0ubuntu9
---
jockey (0.5~beta3-0ubuntu9) jaunty; urgency=low
* Merge from trunk:
- jockey-gtk: Enlarge driver list if there are more than 3 available
drivers. (LP: #291028)
- ui.py: If an activated driver has a
trunk t508
** Changed in: jockey (Ubuntu)
Status: In Progress = Fix Committed
--
Deactivate removes driver
https://bugs.launchpad.net/bugs/284435
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Will fix the button text.
** Changed in: jockey (Ubuntu)
Status: Incomplete = Won't Fix
** Changed in: jockey (Ubuntu)
Assignee: (unassigned) = Martin Pitt (pitti)
Status: Won't Fix = In Progress
** Changed in: jockey (Ubuntu)
Importance: Undecided = Low
--
Deactivate
That's actually the way it's intended to work. Should the button rather
say Remove?
** Changed in: jockey (Ubuntu)
Status: New = Incomplete
--
Deactivate removes driver
https://bugs.launchpad.net/bugs/284435
You received this bug notification because you are a member of Ubuntu
Bugs,
Yes, if that is what it does...
(or it should just deactivate it, why remove it? I actually reported
this after I pressed the button on a pc without internet connection and
lost the driver.)
--
Deactivate removes driver
https://bugs.launchpad.net/bugs/284435
You received this bug notification
Sometimes it's ok to just deactivate a driver, sometime the driver
should really be uninstalled. The fglrx driver falls under the latter
case (therefore I believe that Jockey's current behaviour is correct).
For example, a user wants to disable the fglrx driver so as to use the
open source driver
