This bug was fixed in the package jockey - 0.9.7-0ubuntu7.7
---------------
jockey (0.9.7-0ubuntu7.7) precise-proposed; urgency=low
* data/handlers/fglrx.py:
- Fix typo which caused the handler to fail (LP: #1080588).
jockey (0.9.7-0ubuntu7.6) precise-proposed; urgency=low
* jockey/oslib.py, jockey/xorg_driver.py:
- Add some checks for quantal's backported xserver so as not to
provide drivers which don't support it (LP: #1080588).
* data/handlers/fglrx.py:
- Make sure to mark the experimental driver as such (LP: #1078290).
- Always pass "fglrx" to get the alternative name or jockey will
fail to set the correct alternative.
jockey (0.9.7-0ubuntu7.5) precise-proposed; urgency=low
* data/handlers/fglrx.py:
- Add support for the experimental-9 flavour (LP: #1078290).
-- Alberto Milone <[email protected]> Mon, 07 Jan 2013 10:55:32
+0100
** Changed in: jockey (Ubuntu Precise)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to jockey in Ubuntu.
https://bugs.launchpad.net/bugs/1078290
Title:
Add package fglrx-experimental for tracking fglrx beta drivers
Status in “fglrx-installer-experimental-9” package in Ubuntu:
Confirmed
Status in “jockey” package in Ubuntu:
Invalid
Status in “fglrx-installer-experimental-9” source package in Precise:
Fix Released
Status in “jockey” source package in Precise:
Fix Released
Status in “fglrx-installer-experimental-9” source package in Quantal:
Confirmed
Status in “jockey” source package in Quantal:
Invalid
Status in “fglrx-installer-experimental-9” source package in Raring:
Confirmed
Status in “jockey” source package in Raring:
Invalid
Bug description:
[Impact]
AMD posts beta versions of their drivers to be tested over several weeks.
These drivers usually include important features and fixes but also sometimes
include known issues or regressions that make them unsuitable or too risky for
us to consider inclusion in the fglrx-updates package.
However certain commercial Linux games require features/fixes present
only in these AMD beta drivers at the time of their release. Ubuntu
users who purchase these games currently have to manually install the
beta driver (or wait a month or two for it to appear in -updates).
Providing these drivers via fglrx-experimental will enable them to
install and run the game within the Ubuntu packaging system.
[Fix]
The fglrx-experimental-NNN binary package is established (provided by the
fglrx-installer-experimental source package) for quantal 12.10 and precise
12.04. This uses the packaging scripts from fglrx-updates, with the renamed
package and new .run files.
The fglrx-experimental-NNN package will be visible to users via Jockey
as normal. When a user installs the experimental package, any other
fglrx drivers will be disabled. They will remain on the selected
fglrx-experimental-NNN until they upgrade to a new Ubuntu release or
LTS point release, at which point they'll be returned to fglrx-
current. They can of course manually switch from fglrx-experimental-
NNN back to fglrx or fglrx-updates (or some newer fglrx-experimental-
MMM) if they wish.
The control file for the experimental package proposed for precise has
some differences from the one in quantal, and also has some
differences against the non-experimental fglrx driver in precise. Here
is an explanation of those differences in turn:
* Conflicts/Replaces on fglrx-*-modaliases (from precise's fglrx
package) are no longer needed. The modaliases packages were used in
previous releases but no longer exist in precise. Since people can't
upgrade from those previous versions directly to fglrx*experimental,
there is no need to have Conflicts/Replaces.
* Conflicts/Replaces/Provides of various nvidia/fglrx packages (from
quantal's fglrx-experimental package) are only needed for quantal
forward. These are required by the new restricted drivers UI in
quantal. Since that UI is not in precise, we don't need it in precise.
[Regression Potential]
The reason we're adding this package in the first place is because of
concerns that beta drivers will have a high risk of regressions. Thus, users
need to be aware they are taking these risks when they opt-in to the driver.
As mentioned above, fglrx and fglrx-updates will still be available to
them in case they have problems. In a worst case scenario they may
need to do this from a recovery session.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-experimental-9/+bug/1078290/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
