Description of problem: Just installed aterm on F22 and getting: X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 154 (GLX) Minor opcode of failed request: 3 (X_GLXCreateContext) Value in failed request: 0x0 Serial number of failed request: 42 Current serial number in output stream: 44 Version-Release number of selected component (if applicable): aterm-1.0.1-20.fc22.x86_64 How reproducible: Always Steps to Reproduce: 1. Install aterm on F22 2. Try to run it Actual results: It crashes Expected results: It should run
I tried on my install also, with same response. Freshly updated as of 2015-09-18. It seems not to be an aterm problem, but an OpenGL/mesa problem? Probably connected to NVIDIA drivers as well. Since upgrade to f22, I cannot run openGL-applications from a remote host E.g. glxgears or glxinfo does not run over an ssh connection anymore: How reproducible: Always Steps to reproduce: Hardware: - fedora22 on client machine. NVIDIA or Intel graphics, does not matter. - NVIDIA drivers on server machine. Tested Centos 6.5, Centos 7, Ubuntu # ssh -X server # glxgears X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 153 (GLX) Minor opcode of failed request: 3 (X_GLXCreateContext) Value in failed request: 0x0 Serial number of failed request: 24 Current serial number in output stream: 25 I will try to file this as a separate bug report, since it is not aterm's fault.
I must also add, that e.g. glxgears runs fine when the remote host (server) is equipped with intel graphics (as opposed to NVIDIA dito) That is: # ssh -X server-with-intel-graphics # glxgears WORKS FINE! Best regards Niklas
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.