I was just using xaos in aa mode. All I did was look around in the help a bit and then exit. It left the keyboard in mediumraw mode. Luckily I have a terminal -- otherwise I wouldn't even have been able to find that out.
Robert Carboneau wrote: You don't say what terminal you were running xaos in. I tried it at the console and in an xterm and the keyboard was ok. Can you reproduce the problem? If so, reproduce it in script and send me a typescript of the xaos output.
Whoops. Sorry. I'm running in an i810 fbdev console, at 128x48 text resolution. I run xaos with no arguments. I'm not sure I understand. If you want the piped output from the program, well.. I expect it might be a bit big, so I'll ask you to confirm that before I send it to you :) I'm able to reproduce it easily -- even if I just start it up and exit it immediately, the keyboard is borked. Sorry it took me so long to respond -- I'm not usually in a hurry to -try- and crash my console. Let me know if you got two of this. I'm sort-of new at this..
Robert Carboneau wrote: Just run the "script" command, reproduce it, and send me the typescript file.
Just tried that. When I ran it under script, the problem didn't happen.
Robert Carboneau wrote: That's very weird, AFAIK script does not change the terminal settings, and it passes all output through to the terminal.
One thing it does change is the TTY itself. Instead of being a console, it's a PTY. That would affect libaa's behaviour.
This bug occurs on my system too. I'm using a framebuffer console (matroxfb @ 1024x768x32, ie 128x48 chars). I tried to reproduce the error using "script", but it doesn't happen then. The bug always occurs when I run xaos from console, eg. $ xaos When I exit it seems like the keyboard doesn't work anymore. One thing I've noticed: if I do $ xaos; chvt 2 instead (where 2 can be replaced with any existing tty number as long as it's not the one I'm running xaos in), I get switched to another tty as I exit xaos. There the keyboard works ok. Then I can switch back to whatever terminal I ran xaos in. The keyboard will work otherwise normally but my typing won't be echoed (ie I don't see what I type). I can logout and when I get to the login screen everything works normally again. Hope this additional information is useful.
I get this same bug from the console; unfortunately I wasn't running from a terminal, and therefore had to hit the 'reset' button on the PC case -- thank goodness for 'ext3'. Should a system crasher bug be rated a mere 'normal' severity?
package xaos tags 270186 + moreinfo thanks Hi, some time ago you reported (or mentioned you were affected by) a bug for Xaos in Debian's bug tracking system [1]. I recently took over maintenance of the package and would like to know if you can still reproduce the problem in the current version. Regards, Ansgar [1] http://bugs.debian.org/270186
package xaos tags 270186 + moreinfo thanks Hi, some time ago you reported (or mentioned you were affected by) a bug for Xaos in Debian's bug tracking system [1]. I recently took over maintenance of the package and would like to know if you can still reproduce the problem in the current version. Regards, Ansgar [1] http://bugs.debian.org/270186
It seems to have been a problem that specifically came up when using xaos in ascii-art mode in a framebuffer console. I don't have access to one anymore, so I can't test it.
Package: xaos Version: 3.5+ds1-1 Severity: normal console, worked fine; quit, the terminal is hung and the keyboard was too, no three fingered salute, nada. Mouse was still working, but there's no system menus in a console, so I was stuck. Had to hit 'reset'. HTH...