View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005565 | Spring engine | General | public | 2017-05-20 09:12 | 2017-05-28 00:29 |
| Reporter | Google_Frog | Assigned To | Kloot | ||
| Priority | normal | Severity | crash | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Product Version | 103.0 +git | ||||
| Fixed in Version | 103.0 +git | ||||
| Summary | 0005565: 103.0.1-924 could not create SDL GL-context | ||||
| Description | Someone had https://springrts.com/mantis/view.php?id=5547 and I told them to retry with 103.0.1-924. They have a different issue: https://github.com/ZeroK-RTS/CrashReports/issues/1101 They said that they could start the lobby once but that it did not start after that attempt. I have some communication with them so I should be able to get more information as required. | ||||
| Tags | No tags attached. | ||||
| Checked infolog.txt for Errors | |||||
|
|
These logs have a little more information about how their SDL window was failed to be created. * https://github.com/ZeroK-RTS/CrashReports/issues/1116 * https://github.com/ZeroK-RTS/CrashReports/issues/1114 * https://github.com/ZeroK-RTS/CrashReports/issues/1118 * https://github.com/ZeroK-RTS/CrashReports/issues/1119 * https://github.com/ZeroK-RTS/CrashReports/issues/1120 |
|
|
for 1114, "No matching GL pixel format available" usually means the screen color depth is not set to 32 (bits per pixel). the others are context-creation failures for which there could be many reasons. |
|
|
Are there settings I could tell them to set to learn something about the problem? |
|
|
only a few engine-side, but first ask this player to run 2b38a482 and relay the output. |
|
|
I've applied 103.0.1-939-g2b3f946 generally so reports should come in. |
|
|
seems to have vanished since requesting the context version explicitly. |
|
|
I also thought it had vanished until I recently received two new sets of reports. Perhaps some aspect of the issue was fixed as it was a while before these appeared. All the same user so the reports seem to be redundant: * https://github.com/ZeroK-RTS/CrashReports/issues/1168 * https://github.com/ZeroK-RTS/CrashReports/issues/1169 * https://github.com/ZeroK-RTS/CrashReports/issues/1170 * https://github.com/ZeroK-RTS/CrashReports/issues/1171 * https://github.com/ZeroK-RTS/CrashReports/issues/1172 * https://github.com/ZeroK-RTS/CrashReports/issues/1173 A report from someone else: * https://github.com/ZeroK-RTS/CrashReports/issues/1188 |
|
|
current upstream now has an automatic fallback to handle 1168-1173, the 1188 case would still fail but can only occur with ancient or missing (i.e. not installed at all) drivers. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2017-05-20 09:12 | Google_Frog | New Issue | |
| 2017-05-21 03:40 | Google_Frog | Note Added: 0017667 | |
| 2017-05-21 11:14 | Kloot | Note Added: 0017670 | |
| 2017-05-21 12:06 | Kloot | Note Edited: 0017670 | |
| 2017-05-21 13:41 | Google_Frog | Note Added: 0017671 | |
| 2017-05-21 15:35 | Kloot | Note Added: 0017672 | |
| 2017-05-21 15:38 | Kloot | Note Edited: 0017672 | |
| 2017-05-21 15:46 | Kloot | Note Edited: 0017672 | |
| 2017-05-22 15:02 | Google_Frog | Note Added: 0017674 | |
| 2017-05-25 11:49 | Kloot | Assigned To | => Kloot |
| 2017-05-25 11:49 | Kloot | Status | new => resolved |
| 2017-05-25 11:49 | Kloot | Resolution | open => fixed |
| 2017-05-25 11:49 | Kloot | Fixed in Version | => 103.0 +git |
| 2017-05-25 11:49 | Kloot | Note Added: 0017691 | |
| 2017-05-27 15:22 | Google_Frog | Status | resolved => feedback |
| 2017-05-27 15:22 | Google_Frog | Resolution | fixed => reopened |
| 2017-05-27 15:22 | Google_Frog | Note Added: 0017697 | |
| 2017-05-27 15:32 | Kloot | Note Added: 0017699 | |
| 2017-05-28 00:29 | Kloot | Status | feedback => resolved |
| 2017-05-28 00:29 | Kloot | Resolution | reopened => fixed |
