Created attachment 350000 [details] try init with accum first before falling back to non-accum capable mode Description of problem: gnubik aborts when launched with the error given below. A possible patch to fix this is attached. [steve@laptop gnubik-2.3]$ gnubik ** ERROR **: Cannot get a suitable visual aborting... Aborted (core dumped) [steve@laptop gnubik-2.3]$ Version-Release number of selected component (if applicable): gnubik-2.3-6.fc10.x86_64 but the same thing happens with the latest upstream release too. How reproducible: Always Steps to Reproduce: 1. $ yum install gnubik 2. $ gnubik Actual results: [steve@laptop gnubik-2.3]$ gnubik ** ERROR **: Cannot get a suitable visual aborting... Aborted (core dumped) [steve@laptop gnubik-2.3]$ Expected results: Should launch the application or should fail gracefully (ie: calling exit() instead of abort()ing and dumping core) Additional info: I've narrowed the problem down to the fact that for some strange reason, opengl fails to init with accumulation buffer capability although according to glxinfo (output attached) my system is does have accumulation buffers capability. The attached patch tries to init using accumulation buffer and on failure falls back to using a mode without it it. It also checks for accumulation buffer capability before performing any accum. related operations. - steve
Created attachment 350002 [details] "glxinfo -t" which list accum buffer modes exists
Thanks for report and patch, I'll commit it soon.
This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '10'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 10's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 10 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.