Posted - 2011.03.28 11:03:00 - [1
Edited by: CraigGamerPsycho on 28/03/2011 11:05:07
Edited by: CraigGamerPsycho on 28/03/2011 11:04:30
I'm using Ubuntu 10.04 - the Lucid Lynx. The problem is that i can't seem to click on certain parts of the interface at specific times. For example when my ship is flying in space and i i try to right click anywhere on it, usually (at least when i had windows) it give the option to open cargohold or set autopilot. However i can't seem to do that while on ubuntu. I have to zoom right in and make sure the cursor is right at the center of the ship in order to do this.
Another example of the problem is when i try to scan and i have probes out. When i go in to scan map mode where it shows the whole system and your probes, i can't actually interact with the probes. Normally if you hover your cursor over the 4 white arrows that probes have (in order to make their probing radius wider) the arrows turn to a light blue. It doesn't seem to do this which doesn't really allow me to move the probes around.
When i say it doesn't let me do this, i mean i click on the arrows - hold it and try to move it but it doesn't move. The arrows don't even go blue.
One last example is in Planetary Interactions. When i place the Command Center on the planet i can see it placed as a round pin with blue and red around out (signifying CPU and power). But when i try clicking on the command center i can't access any options, when usually it will open a small window giving options which include to destroy the command center.
Has anyone had this problem or knows how to fix it? Help is appreciated.
Posted - 2011.03.28 16:19:00 - [2
That kind of happened to me 4 kernels ago.
Some stuff was not clickable sometime like the chat channel (impossible to change channel) or the overview. When that append, I relaunch EVE...
Last time I got this bug on the kernel 2.6.38-rc6 and some of the linux-next but this did not append with the 2.6.38-rc8 and the three 2.6.39-rc0 I used (I did not try the "stable" 2.6.38)
I suspect that's from the kernel DRM or Mesa... Or it can be related to Xinput or something like that but I did not replace my xorg since... Maybe that's a different bug that the one you got.