Ken Moffat wrote:
Often, I can go months without using lowriter (but I use localc
frequently, often for simple things which are really just text
notes), but at the moment I'm trying to keep track of fonts (what I
refer to as 'font analysis', i.e. which codepoints they contain and
which languages they support).
And as part of that I'm loading text files into lowriter (all the
codepoints, up to 32 per line) and then changing them to the font,
repeating titles when the unicode block cover more than one page,
and adding footers. And frequently, writertakes 100% of one CPU,
indefinitely.
This happens on 5.1.0.3. It isn't catastrophic, killall -KILL
soffice.bin kills (all) the open office documents, and I can recover
them when I next open an office prog, but it is happening
frequently. The first time, I had opened a file with the contents
of the Baekmuk Batang font (about 50+ pages, I think), selected all
and tried to change the font. I left it for an hour - it did not
recover. Now, I just change a small part at a time, and if it does
not complete quickly then I kill it. After recovery, it seems to be
fine - until the next time.
Anybody else seeing this sort of issue ?
On my workstation I'm using 5.0.4.2. I only use lowriter very
occasionally and then for very short, simple documents. It sounds like an
internal issue that needs to be addressed upstream.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
