On Fri, Sep 18, 2009 at 6:04 AM, Petr Mladek
On Friday 18 September 2009, Mark Misulich wrote:
On Mon, 2009-09-14 at 11:26 +0200, Petr Mladek wrote:
On Friday 11 September 2009, Clayton wrote:
On my system, moving Fontwork can hit the CPU hard unless I turn off antialiasing - I've never noticed this since I've never used Fontworks before. There might be a bug open on this... don't know, but it'd be worth a search in the OpenOffice.org website.
Could you please report this at https://bugzilla.novell.com against the product OpenOffice.org?
Hi Petr, I opened a bug on this problem at OpenOffice because I was using a different computer and didn't have this email to reference. I will open the bug at novell as you have requested.
Do you mean that you reported the bug at http://www.openoffice.org/? What is the issue number?
It might be enough if the bug happens also with the upstream build. I expect that this bug should be common. Thorsten knowns about it, so he would look at it if time permits. It is possible that an upstream developer will be faster, ...
-- Best Regards,
Petr Mladek software developer --------------------------------------------------------------------- SUSE LINUX, s. r. o. e-mail: pmladek@suse.cz Lihovarská 1060/12 tel: +420 284 028 952 190 00 Prague 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/
Hi Petr, Ok, here is what I did. I opened the bug at Openoffice.org, issue number 105065. I opened it up there because I opened it up using my desktop computer at home when I returned from my last business trip. I had the problem originally on my laptop when I was on the road trying to get some work done on the newsletter I write for an organization. I forwarded the newsletter to my desktop from my laptop to see if I had the same problem there. I did, so I opened up the bug from memory at openoffice.org forgetting that you asked me to open it up at novel. The issue of that bug is 105065. The openoffice.org bug was closed a day or two after I opened it. They asked me to download the tarball open office 3.1.1 from open office directly and install it on my computer. In the meantime, I had left on another business trip, so I told them I would do it in a week and a half when I returned home. I think they didn't want to wait, so they tried it out on Ubuntu and didn't have the problem, so they closed the bug. Here is the final report: I checked with 32bit on Suse and 64bit OOo 3.1.1 on ubuntu but I could not detect a problem like the described. Highest OOo cpu peak was 12%. I think it is a problem of the OOo build provided by Novell or something with the XServer. Please use the OOo from our download page. I looked up the original email stored on my laptop computer after I saw that response, and realized that you wanted me to file the bug with Novell, not openoffice. So I did that and sent out the email to let you know. Here is the number for that bug: 540147 Here is the url for that bug: https://bugzilla.novell.com/show_bug.cgi?id=540147 I hope that this makes things clear now. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org