Comment 10 for bug 731987

Ok, based on the recent comments, I take it this is limited to virtual machines. Therefore I'm reverting the importance to initial settings. The reasoning is; while it should be fixed, I can live with full screen problems in virtual machines, but if it affected physical machines as well, it would be a bigger concern.

I agree that #6 sounds like it should be reported as a new bug.

>what exactly is not working?
The cursor is either invisible or stuck to one of the sides, which makes it impossible to move it to and click on any of the menu items. I have not seen the white point LAZA talks about in #8, but I may have simply missed it.
When I set Widelands to full screen, and come back to the main menu, I'm not able to do anything, so I need to force quit (ctrl+f10) and edit the widelands config-file to set fullscreen back to false.

I also tried wesnoth, which worked fine in fullscreen on the same system which has problems with widelands.