Hi, I would like to report a bug that become major with the last release. It's nearly impossible to play a game without losing several times the mouse click and keyboard control. This problem can occurs during game or at the begining, when generating planet. When it happend, I must restart the game. When it occurs at the begining of the game, it's possible to click into the drop area (a small red circle shows that mouse click works) but the games does'nt start. Nothing happends if you try to click on the planetary icon (top right). When the problem occurs during the game, you can move the cursor and the scroll button is responding but any selection with the mouse is disabled. if you started to do a drag operation to select units, the first point is selected but it's impossible to select the second point. It is like the mouse process cannot finish the selection. The keyboard is also not responding except the "alt +tab" keys to swap to another windows and the arrows. The mouse and the keyboard still works properly in Ubuntu even if a blocked game is still running in another windows --> The problem is only in the game. It seems that a small PC configuration help to produce the bug. My configuration is the smallest allowed : Dual core 1.86Ghz, 4Go of ram DDR2 @266Mhz, ATI Ge Force 430 as graphic board. The Os is Ubuntu Mint petra 16, but a friend of mine has the same problem with windows 7. His configuration is also a Dual core with 4 Go.
Welcome to the forum and here is the thread talking about the bug tracker. https://forums.uberent.com/threads/bug-repository-pa-tracker.46855/
For Linux this sounds like bug FS#2392. The Coherent UI crashes, while the game engine itself is still going. That effectively means you lose the ability to issue commands, but you can still navigate the planets and such. Do you get a BadAccess error in your logs as well? This wouldn't apply to the Windows 7 user though.
Yes it's the same bug, but before the error "The program 'CoherentUI_Host' received an X Window System error", there is many other problems (see the log below). In the log below, the problem occurs when generating planet. I copy only some problems report but there is many ! .... 2480 21:32:29.632526 W | PID: 2488 | 2488 21:32:29.609679 Requesting resource read for coui://ui/main/_i18n/locales/fr/shared.json with internal id 868 reported FAIL .... 2480 21:32:29.999909 W | PID: 2488 | 2508 21:32:29.955117 Could not recognize the mime type of coui://ui/main/_i18n/locales/dev/shared.json .... [23:32:28.883] INFO processUICommand [23:32:28.884] INFO ClientWorld::updateObservability - Updating [6782] [23:32:28.907] INFO processUICommand [23:32:28.907] INFO handleLandingZones [23:32:28.907] INFO {"landing_zones":[{"position":[0,349,0],"planet_index":0,"radius":70},{"position":[220,51,273],"planet_index":0,"radius":70},{"position":[220,51,272],"planet_index":1,"radius":70},{"position":[0,346,0],"planet_index":1,"radius":70}]} [23:32:29.166] INFO ClientInterface::updateObservableArmySet - Updating [6782] entities 2480 21:32:29.292479 W | PID: 2488 | 2488 21:32:28.908728 Requesting resource read for coui://ui/main/_i18n/locales/fr/live_game_selection.json with internal id ... and at the end : The program 'CoherentUI_Host' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAccess (attempt to access private resource denied)'. (Details: serial 2988 error_code 10 request_code 130 minor_code 1) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.)
Just after these errors the mouse was blocked in a "drag and drop" state (I can't finish my group selection, blue square) : 3848 22:42:40.224533 W | Argument conversion failed: Wrong type - expected Integer, got Null while converting argument 0 for handler holodeck.setCommanderId 3848 22:42:51.342107 W | PID: 3861 | 3879 22:42:51.288256 Could not recognize the mime type of coui://ui/main/_i18n/locales/fr/game_over.json 3848 22:42:51.410350 W | PID: 3861 | 3879 22:42:51.346796 Could not recognize the mime type of coui://ui/main/_i18n/locales/dev/game_over.json 3848 22:42:51.530783 W | PID: 3861 | 3861 22:42:51.470625 Requesting resource read for coui://ui/main/_i18n/locales/fr/shared.json with internal id 1357 reported FAIL 3848 22:42:51.664144 W | PID: 3861 | 3879 22:42:51.611718 Could not recognize the mime type of coui://ui/main/_i18n/locales/dev/shared.json 3848 22:48:48.760677 W | PID: 3861 | 4120 22:48:48.690437 [3861:4120:WARNING:accelerated_surface_linux_coherent.cc(250)] could not update shared memory image The program 'CoherentUI_Host' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAccess (attempt to access private resource denied)'. (Details: serial 57774 error_code 10 request_code 130 minor_code 1) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.)
I'm getting this in maybe 1/3 of my games. Any workaround? For me it always seems to happen after 20mins or so when there is a lot going on. *edit: Also I can't reconnect to games ever.
It seems to be related to mousing over the build menus somehow. I have NVidia as well, but in my case it happens much more rarely. A friend of mine runs on AMD and for him it occurs quite frequently. He claims to be able to stop the UI freeze from happening by closing the build menu before selecting a new unit. So for example, he would select the commander, which opens the build menu. Then he does whatever he needs to and then closes the build menu with <Esc> before selecting any other unit. It would be interesting to know if you can prevent the UI freeze in the same way.
Thanks, I tried pressing ESC whenever I had opened a build menu before selecting a unit, and I had no crash (will report if I get some). Not to say that this slows down my command rate significantly (not that it was fast enough before...)
