Is zandronum bugged on ubuntu?

[ibm5155]

So I was making a virtual machine with ubuntu (for study), and, I decided to test zandronum there lol.
One thing I got disapointed was that there was no window showing that zandronum is loading '-' (if you load it by terminal you will only read some printf messages '-')
and sometimes, when I tried to play online, opened the menu and closed and reapeated it and, i got stucked at menu D: (I could see the things moving but i couldnt controll the menu D:)

So, is it only happening because it's a virtual machine or does it happen with an ubuntu installed? :S

Also, zandronum runs quite good with opengl O_o (I expected no support and 0fps, but i got 30xD)

[PkmX]

The bug is not specific to Ubuntu, I also have the same problem on Arch Linux (not in a VM). You can also trigger this bug by opening the console or simply chatting in-game, which is probably the #1 reason I very rarely talk in multiplayer games unless I absolutely need to. The window simply won't accept any inputs, but the game runs totally fine (e.g. multiplayer still goes on normally) in the background.

It should be noted that it is not specific to Zandronum at all, I got the exact same problem on GZDoom as well.

Anyway, I opened this issue on the bug tracker a while ago: http://zandronum.com/tracker/view.php?id=1440, but there is no response yet.

[mr fiat]

The bug is not specific to Ubuntu, I also have the same problem on Arch Linux (not in a VM). You can also trigger this bug by opening the console or simply chatting in-game, which is probably the #1 reason I very rarely talk in multiplayer games unless I absolutely need to. The window simply won't accept any inputs, but the game runs totally fine (e.g. multiplayer still goes on normally) in the background.

It should be noted that it is not specific to Zandronum at all, I got the exact same problem on GZDoom as well.

Anyway, I opened this issue on the bug tracker a while ago: http://zandronum.com/tracker/view.php?id=1440, but there is no response yet.

zandronum runs 100% fine on my end, i run linux mint 15 on my linux pc. and i chat and abuse the console ALLOT.

[Dark-Assassin]

Possibly some problem related to the 3.1x.x kernels.
Of course people with older operating systems/kernels wouldn't run in to this trouble, as shown above.

[Klofkac]

Could not reproduce this. Runnink on Linux Mint 16 Petra, kernel 3.11.0-12-generic.

[Chang-Joe-Rim]

I also have same problem, I think This problem depend on what input method you use(just I think).
I currently use Manjaro linux(Manjaro Minimal Net Edition base on Arch linux) with scim and it's freeze somtimes.
Before I use Manjaro I used linux mint with nabi(Korean Input method). And I didn't feel freezing problem.
Also I heard Some game(minecraft. but not currently) has problem with scim.
So If you use scim, How about changing your Input method?

[Dark-Assassin]

Do you have the correct drivers installed?
Also, IIRC but there may currently be a bug with the Intel drivers with certain chipsets on the later linux versions. It's what forced me to downgrade my Media Centre.

[ibm5155]

Well, I was running the latest ubuntu 13 and the latest opensuse. both running on hyperv, and both works fine with opengl (intel hd 3000), and it works fine, but the only thing is that you'll get stucked on menu sometimes ;S, but, everything will still run fine ...
idk my drivers, i didnt installed one xD
EDIT: the menu stucked were online, i didnt tested it offline...

[Klofkac]

About drivers, I am using the default ones and GPU is intel GMA (not sure which version but it is Intel) + intel chipset, CPU is Core 2 Duo. Distro was Mint 16 Cinnamon x86_64.
Created a quick localhost server and conencted to it, then spammed chat, menu and console. Never got stuck. So I really don't know.
Could be window manager possibly? Because Ubuntu is using Compiz, and about OpenSUSE... Not sure.

[PkmX]

There has been some update on the bug tracker here. The bug turned out to be a problem with how SDL interacts with input method engines (ibus in my case). Currently I'm playing with the XMODIFIERS environment variable unset and haven't triggered this bug so far, so I guess that's the temporal fix until Zandronum switches to SDL 2.