You might have read my post in the Programming forum. But I just did a fresh install of Mandrake 10.0 and then installed Allegro from the sources. I did what Thomas told me to in my last post. And now when I run anything when I exit it pretty much makes it to seem like it is continuosly pushing enter. No errors or anything. Any ideas?

Thanks!

Sounds like an error in your terminal. Try using a different one.

Actually, I guess it is a GNOME error. Just tried it in BlackBox and it works fine... I really do not want to stop using gnome just so I can use Allegro.

Thanks!

You were using the same terminal in both blackbox and GNOME?

Yes, in KDE RXvt works fine. In GNOME it does not. And when not running out of a terminal it works fine in KDE, but again, not in GNOME.

There appears to be a bug in the Allegro DGA2 driver (or perhaps DGA2 itself) which causes any keys which are held down when you call set_gfx_mode() to get "stuck" after the program exits.

The only fix I know for this (aside from fixing the DGA2 driver, which I've looked at but can't make head or tail of), is to not press any keys while your program starts up.

The problem with this is that the return key is often pressed down if you started the program from a terminal.

This is not unique to Mandrake, it probably happens on most other Linux distros too.

I normally use

sleep 1; ./myallegrogame

Which of course waits long enough for you to release the enter key.

Mark

Wow! Nice find. Thank you very much. But how come it only does that in GNOME?

Gnome sucks?

I can't get Mozzila's (?) font's to look correct in KDE. And I also learned in GNOME.

Mozilla/Firefox looks fine here.

I just needed to use the text zoom function. Can I make that stick after closing the browser?

Maybe I should install Gnome just to hunt for that bug... anyway, Gnome was the default desktop on the workstation I use at work. I kept thinking `geez, RedHat screwed up KDE pretty badly to make it look and feel this horrible', until I realized what was going on and I switched desktops.

Oh, no problems with Firefox here either.

I'm guessing it's a race condition or something caused by the time it takes the window manager to respond once the new window opens.

Perhaps the different window managers actually affect this bug slightly differently - but I think it's still a bug.

Yes, I use Gnome, but I don't believe that the bug is caused by gnome itself.

Mark

Evert, you are so very quotable