To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=105065
                 Issue #|105065
                 Summary|Fontwork Stalls Computer
               Component|Word processor
                 Version|OOo 3.1.1
                Platform|PC
                     URL|
              OS/Version|Linux
                  Status|UNCONFIRMED
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P3
            Subcomponent|formatting
             Assigned to|writerneedsconfirm
             Reported by|munguanaweza





------- Additional comments from [email protected] Mon Sep 14 
17:26:33 +0000 2009 -------
When I set fontwork onto a page, moving the fontwork will cause the computer to
chug.  The %cpu readout in top is 56% soffice.bin and Xorg 42% until the problem
resolves itself.  Then readouts are about 1-2% for both.  Also, once the
fontwork is set, if I try to scroll the page past the fontwork it will also
cause the computer to chug.

I asked on the mailing list for my linux distro (OpenSuse 11.1) if anyone else
had this problem and found that they did.  They were able to resolve it by going
to tools>options>view>deselect antialiasing.  That has caused the problem I
described above to stop.  However, I was asked on the list to submit this as a
bug to Open Office, which you can read that I have done.

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to