"Deactivate" removes driver

That's actually the way it's intended to work. Should the button rather say "Remove"?

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.)

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 or to install the nvidia driver (e.g. if she changed her graphics card). Only the uninstallation of the fglrx driver will allow her to use either driver since fglrx, ati and nvidia use different "versions" (put simply) of the same libraries.

Will fix the button text.

trunk t508

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 package, label the action "Remove",
      not "Deactivate". (LP: #284435)
    - Update German translations.
  * backend/com.ubuntu.DeviceDriver.service: Write debug log to
    /var/log/jockey.log by default when starting the backend. (LP: #290036)
  * Add debian/jockey-common.logrotate for rotating jockey.log.
  * data/handlers/broadcom_wl.py: If b44 is loaded, don't disable the entire
    handler, but instead install a "wl" modprobe handler which removes ssb and
    b44 first, then loads wl, and reloads b44 again, which makes both devices
    work. (LP: #289845)

 -- Martin Pitt <email address hidden> Fri, 28 Nov 2008 11:57:56 +0100