Hide Forgot
Description of problem: In both rawhide and F15 java-1.6.0-openjdk-1.6.0.0-59.1.10.3 is causing problems with the colossus UI. When I click on a button, the button is highlighted, but the action often doesn't occur until I hit it repeatedly. In F15 I tested downgrading to java-1.6.0-openjdk-1.6.0.0-58.1.10.2 and things went back to working as expected again. Version-Release number of selected component (if applicable): How reproducible: I haven't tested this with anything other than colossus. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
This does not appear to happen when using java-1.7.0-openjdk-1.7.0.0-0.1.20110803.fc17.i686.
This problem isn't happening for me (or I am misunderstanding the problem). I have no idea how this colossus game is played, but I can navigate the UI to add a couple AI players and start a new game without any need to repeatedly click buttons. Currently using java-1.6.0-openjdk-devel-1.6.0.0-59 I am on a x86_64 system. I notice your 1.7 package is i686. I'll try on such a system soon (probably tomorrow), but in the meantime is it possible that anything else may have changed on your system to produce the symptom?
I haven't been seeing a problem with 1.7, just the latest 1.6. (It may be that there is a problem with colossus, but the rate at which the problem manifests itself is much higher with the latest java 1.6 than previously. So that while in the past one might question if one hit the button correctly, there is clearly an issue with it now.) I can try it on on an x86_64 system later today and report on whether I see the problem there as well. I have only been noticing the problems with popup menus. Hitting "done" on the menu bar seems to work. Sometimes I see it with splitting choosing the new legion marker, and commonly with the popup warnings about not splitting 7 high legions, not moving all legions and the notice about winning.
I tried it on an x86_64 machine and wasn't seeing the problem. I have seen it on two significantly different i686 machines (AMD Athlon MP desktop and a Pentium M laptop) and I'll try to make sure I also see it on an i686 Xeon desktop I also have. (I think I tested it there, but want to double check.)
I just poked around a bit on an i686 VM. While I admittedly didn't spend a lot of time, I didn't once see the issue described. I did hit most of the popups described a couple times each at least, including choosing new marker, splitting legions, warnings about not splitting. (not winning; I did not play long enough and additionally still don't have any idea what this game is about). How frequently are you seeing this happen?
Something very roughly on the order of half of the time on popups. Once I have trouble with a specific popup, I usually have to hit it a few times. In some cases I think I see patterns in how I can get it to work, but that may just be selective memory and luck. I would have expected you to see it in your tests if it was happening at all. I have tested reverting just java and the problem went away, so I believe there is some tie in to that particular release. If nothing else is affected, this is probably a low priority item. I don't think there are many people playing colossus on Fedora. For F16 and rawhide, people will probably be using java 7 which hasn't exhibited the issue.
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping