This bug was fixed in the package ubuntu-drivers-common - 1:0.2.98
---------------
ubuntu-drivers-common (1:0.2.98) utopic; urgency=medium
* gpu-manager.c, gpu-manager.py:
- Add support for testing core alternatives. This will be needed
by fglrx.
- Add the --backup-log parameter. This is only used for debugging
and disabled by default.
- Fix a regression that caused the gpu-manager to switch to mesa
after enabling fglrx on hybrid systems (LP: #1310489). Also
add a test case so that we don't regress in the future.
- Check that either fglrx or nvidia is set in xorg.conf when
xorg.conf is needed.
- Check if kernel modules are blacklisted before choosing the
driver (LP: #1310489).
- Enable only GPUs with open drivers that have connected outputs.
Attaching to GPUs that have no connected outputs would result
in a black screen.
- Allow RandR offloading even without bbswitch (LP: #1349282).
- Fall back to mesa when failing to enable prime.
- Do not try to enable prime if the nvidia driver is older than
331.
- Do not abort if the settings for prime cannot be found.
Try creating the file before failing.
- Avoid false positives of unloaded modules.
- Use the cleanup attribute.
- Always use snprintf instead of sprintf.
-- Alberto Milone <alberto.mil...@canonical.com> Wed, 27 Aug 2014 10:39:17
+0200
** Changed in: ubuntu-drivers-common (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1349282
Title:
The gpu-manager should allow RandR offloading without bbswitch
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1349282/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help : https://help.launchpad.net/ListHelp
