| Summary: | OpenGL TCM module doesn't start | ||
|---|---|---|---|
| Product: | TDE | Reporter: | Q4OS Team <q4os> |
| Component: | tdebase | Assignee: | Michele Calgaro <michele.calgaro> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | bugwatch, michele.calgaro, q4os, slavek.banko |
| Priority: | P5 | ||
| Version: | R14.0.0 [Trinity] | ||
| Hardware: | Other | ||
| OS: | Linux | ||
| Compiler Version: | TDE Version String: | ||
| Application Version: | Application Name: | ||
| Bug Depends on: | |||
| Bug Blocks: | 2696 | ||
|
Description
Q4OS Team
2016-09-23 04:12:59 CDT
Please, you can test it with R14.0.4~preliminary? Virtualbox 64bit Debian Stretch TDE: R14.0.4 [DEVELOPMENT] The same issue Q4OS, can you try using R14.1.x? I can not reproduce on debian/stretch + TDE R14.1 The issue still persists in Debian Jessie, TDE 14.0.4 stable. Just tried this in buster using R14.1 under VM. When I run tdecmshell opengl from terminal, I get some error messages like below and no window at all. @Q4OS team: is this what you also see? Sample of error: X Error: BadValue (integer parameter out of range for operation) 2 Major opcode: 154 Minor opcode: 3 Resource id: 0x0 X Error: GLXBadContext 169 Major opcode: 154 Minor opcode: 5 Resource id: 0x4200008 X Error: 0 0 Major opcode: 154 Minor opcode: 26 Resource id: 0x0 "is this what you also see?" Yes, it is thanks Q4OS team. As further info, I noticed this when running in VirtualBox. If 3D hardware acceleration is enabled in VBox settings, the following error message is displayed in the CLI when running 'tdecmshell opengl' "OpenGL Warning: vboxCall failed with VBox status code VERR_BUFFER_OVERFLOW" and the tdm window opens. If 3D hardware acceleration is disabled in VBox settings, the error message described in comment 5 is displayed in the CLI when running 'tdecmshell opengl' and no window gets opens, although the process does not exit to CLI. R14.1 commit: b5741b36 R14.0 commit: be0069e3 This should now be fixed. Could you please test and let me know before I close the bug. Thanks I can confirm, the module now opens. I have noticed another small glitch, as there is two identical "Direct Rendering" entries below each other in the list. Except this glitch, the module works fine, thanks for all your work. Commits 19d18dfe (R14.1) and 3b0afd6c (R14.0) remove the double entry of "Direct Rendering". I should have noticed in first place, sorry for that. Please check again and let me know if it is ok to close the bug. Works fine now, thanks |