#3 aalib 1.4rc5 "-driver linux" bug


When running any aalib program on my custom-installed
slackware 8.0 box as a non-root user and not specifying
any -driver (so it used the "linux" driver by default) the
program sits, not displaying anything, but exiting when i
hit "q" in aview and any key with aafire. After running
these programs I checked the current directoy and
always found a file ls called ???@???@??, but rm would
never seem to be able to find it. So after trying a couple
ways of deleting it I used mc which displayed it with a
different filename using many extended characters as
well as some control sequences using the ^ character
and a letter. Using -driver slang everything worked fine.

The drive is formatted with reiserfs, and the computer
has 40 megs of memory. Just some information I
thought may be of some use.

Also in the case that there is a bug in the first driver
listed, would it be possible to add a way in which one
could globally specify the default driver?



Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.

No, thanks