Re: Problem with dosemu

CASE CLOSED, DOSEMU WORKS NOW!

Thank you all for your help and inspiration. There was nothing wrong 
with dosemu, the problem was my corrupted FC3 system, and I can blame 
only myself for corrupting it. Learning curve...

I started to review my system which I corrupted by removing some rpm-s 
and compiling updated software in the past few years. Now I know a 
little more and am more careful how to do things. Repairing and cleaning 
my fc3 installation is a slow and painstaking process. This is why I did 
not give an update recently. Franta's message today made me try dosemu 
again, and this time it worked. Apparently the partial repair fixed it. 
I don't know what and how, but the main thing is that it works. 
Originally I planned to try dosemu after I finished my system repair.

Thank you all on this mailing list - Janos

Just to answer Franta's points:

On 05/04/2014 07:20 AM, Frantisek Hanzlik wrote:
> Your strace seems normal. FYI, on my
> and my shm kernel settings are:
>
> # cat /proc/sys/kernel/{shmall,shmmax,shmmni}
> 2097152
> 33554432
> 4096
2097152
2147483647
4096
> 2) Your error message: '"/usr/share/dosemu/Xfonts": error scanning'
> is perhaps caused by fc-cache problem. What You obtain on command:
> fc-cache -v -f /usr/share/dosemu/Xfonts
/usr/share/dosemu/Xfonts: caching, new cache contents: 2 fonts, 0 dirs
/usr/local/var/cache/fontconfig: cleaning cache directory
/root/.cache/fontconfig: not cleaning non-existent cache directory
/root/.fontconfig: not cleaning non-existent cache directory
fc-cache: succeeded

> It should be successfull and in '/usr/share/dosemu/Xfonts' directory
> should be created (empty) file 'fonts.cache-1'.
> You should also verify dosemu RPM package right installation by cmd:
> rpm -V dosemu
> On my PC it produce only one line (which is OK):
> .......T.   /usr/share/dosemu/Xfonts/fonts.dir
My system produces no output.
> Also, are You using xfs - X font server?
Yes, see more below.
>
> Maybe You have somehow broken Your system - e.g. missing some files
> or directories, bad ownership or permissions on them etc.
> You can verify it by 'rpm -Va' command. This should not produce any
> serious problems (it is necessary assessed output individually).
rpm -Va xfs produces no output, but I do have a problem with xfs. When I 
boot and xfs service starts I get an error message stating that "error 
scanning". But otherwise my system works, and apparently this is not 
related to dosemu. Hopefully, as I clean up my system this is going to 
be resolved as well.
> 3) Did You tried run dosemu in console and/or in Xterm in terminal
>   mode ('dosemu -t')? What is result?
It works both from console (Ctr-Alt-f1) or from xterm