search

yagamiram / opennero

Automatically exported from code.google.com/p/opennero
Other
0 stars 0 forks source link

X freezes upon pressing F2 #125

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Start NERO Training
2. Deploy rtNEAT
3. Press F2

What is the expected output? What do you see instead?
According to http://code.google.com/p/opennero/wiki/NeroMod, pressing F2 cycles 
through useful stats and displays each above the agent. However, upon pressing 
F2, X freezes and it can only be restored by killing the OpenNero process from 
terminal.

What version of the product are you using? On what operating system?
Revision 1531. Gentoo Linux.

Please provide any additional information below.

Original issue reported on code.google.com by klan...@gmail.com on 5 Dec 2011 at 12:37

GoogleCodeExporter commented 8 years ago 
Investigating some more, it's not X that freezes but Kwin (the window manager 
for KDE). Temporarily disabling Kwin and F2 now works. However, everything else 
is unclickable until I manual kill the OpenNero process.

Original comment by klan...@gmail.com on 5 Dec 2011 at 8:29

GoogleCodeExporter commented 8 years ago 
One of the things that happens when you press F2 is the window title is changed 
to tell you what is being displayed. My guess is that Kwin has a problem 
dealing with this for some reason...

Original comment by ikarpov on 6 Dec 2011 at 2:10

GoogleCodeExporter commented 8 years ago 
I see... I don't know how to get debug messages from Kwin and there are no 
errors in .xsession-errors. Well, since the CHAMP id is outputted to the 
console, it's okay if I'm not able to use F2 for now.

Original comment by klan...@gmail.com on 6 Dec 2011 at 6:26

GoogleCodeExporter commented 8 years ago 
r1536 fixed a problem that might have made your issue worse - in Battle mode, 
there was a conflict between displaying the damage sustained and displaying the 
rtNEAT stat information.

Original comment by ikarpov on 6 Dec 2011 at 10:28

GoogleCodeExporter commented 8 years ago 
Still getting the same symptom with revision 1538. Kwin freezes upon pressing 
F2. The cursor is still movable but everything else does not respond to clicks. 
Using top at the terminal, I can see that Kwin consumes 100% cpu.

Original comment by klan...@gmail.com on 7 Dec 2011 at 9:47

GoogleCodeExporter commented 8 years ago 
Well, I'm not sure what we are doing to offend Kwin, but until we find out, I 
would suggest using another window manager for opennero if you can...

Original comment by ikarpov on 8 Dec 2011 at 2:39

GoogleCodeExporter commented 8 years ago

Original comment by ikarpov on 9 Dec 2011 at 12:49

GoogleCodeExporter commented 8 years ago 
it is possible that r1563 and the most recent build 2011-12-11 have addressed 
this issue... could you check?

Original comment by ikarpov on 11 Dec 2011 at 5:22

GoogleCodeExporter commented 8 years ago 
Yup, it's fixed with the latest revision (r1565). Thanks!

Original comment by klan...@gmail.com on 12 Dec 2011 at 5:35

GoogleCodeExporter commented 8 years ago 
ok then i'll mark this as fixed =).

Original comment by ikarpov on 12 Dec 2011 at 5:52