Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#48167 - [bumblebee] PLEASE ENTER SUMMARY
Attached to Project:
Community Packages
Opened by Colin Keenan (colinkeenan) - Saturday, 13 February 2016, 17:04 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 13 February 2016, 19:17 GMT
Opened by Colin Keenan (colinkeenan) - Saturday, 13 February 2016, 17:04 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 13 February 2016, 19:17 GMT
|
DetailsDescription:
Another release of the package is needed in order to rebuild both 32 bit and 64 bit versions of libGL.so.1 Current libGL.so.1 is out of date so that optirun fails (applications hang or fail with various errors) with both 64 bit and 32 bit applications. See https://bbs.archlinux.org/viewtopic.php?id=208759. The solution is to do another release of this package. I built it again using abs, and everything works again. Additional info: bumblebee 3.2.1-10 primus 20151110-5 lib32-primus 20151110-3 lib32-libglvnd 0.0.0.20160210-2 lib32-mesa 11.1.2-1 lib32-mesa-libgl 11.1.2-1 lib32-nvidia-utils 361.28-3 libglvnd 0.0.0.20160210-2 mesa 11.1.2-1 mesa-libgl 11.1.2-1 nvidia-utils 361.28-4 Steps to reproduce: Update system & try to run 32-bit or 64-bit applications with optirun. (Fails for sure with the primus bridge, probably with default bridge too) |
This task depends upon
Closed by Doug Newgard (Scimmia)
Saturday, 13 February 2016, 19:17 GMT
Reason for closing: Not a bug
Additional comments about closing: User requested: I though the problem was fixed by rebuilding this package, but it was actually fixed by yet another build of the nvidia-utils packages being released and installed by me. Should've paid more attention.
Saturday, 13 February 2016, 19:17 GMT
Reason for closing: Not a bug
Additional comments about closing: User requested: I though the problem was fixed by rebuilding this package, but it was actually fixed by yet another build of the nvidia-utils packages being released and installed by me. Should've paid more attention.