gs is ghostscript, the postscript processor. For some reason, it
occasionally keeps running, after it should be killed. When that happens,
the easiest way to deal with it is to simply kill it. Run top to get the
process id, and either kill it in top, or exit top and use
kill -9 pid
where pid i
I'm using Lyx 1.1.4 fix3 (Debian potato). Normally Lyx is not slow on my
PentiumI, but today it was extremly slowed down. When I looked for the
Processeses, causing this enormous "speed", I found, that the process "gs"
used up to 90% of the CPU. In this state, Lyx is absolutely useless for me,
as
I'm using Lyx 1.1.4 fix3 (Debian potato). Normally Lyx is not slow on my
PentiumI, but today it was extremly slowed down. When I looked for the
Processeses, causing this enormous "speed", I found, that the process "gs"
used up to 90% of the CPU. In this state, Lyx is absolutely useless for me,
as
I'm using Lyx 1.1.4 fix3 (Debian potato). Normally Lyx is not slow on my
PentiumI, but today it was extremly slowed down. When I looked for the
Processeses, causing this enormous "speed", I found, that the process "gs"
used up to 90% of the CPU. In this state, Lyx is absolutely useless for me,
