[27181] in Athena Bugs
Re: OpenOffice on Suns
daemon@ATHENA.MIT.EDU (William Cattey)
Tue Feb 5 18:45:41 2008
In-Reply-To: <952EE3D1-2C51-40F5-B5F1-CB34B2673D56@mit.edu>
Mime-Version: 1.0 (Apple Message framework v753)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <10EEDE73-14DC-4E47-80F3-08834EB216E3@mit.edu>
Content-Transfer-Encoding: 7bit
From: William Cattey <wdc@mit.edu>
Date: Tue, 5 Feb 2008 18:45:27 -0500
To: William Cattey <wdc@mit.edu>
X-Spam-Flag: NO
X-Spam-Score: 0.00
Cc: austein@mit.edu, Alex T Prengel <alexp@mit.edu>, bugs@mit.edu
Errors-To: bugs-bounces@mit.edu
I confirm that Alex's fix corrects the problem.
-Bill
----
William Cattey
Linux Platform Coordinator
MIT Information Services & Technology
N42-040M, 617-253-0140, wdc@mit.edu
http://web.mit.edu/wdc/www/
On Jan 31, 2008, at 8:14 PM, William Cattey wrote:
> I tried to reproduce this bug, but the system I used had a
> DIFFERENT problem that had kept it at Athena 9.4.15 since 2005.
> There was an __db. file in my home directory which was created by
> OpenOffice in 2006, but when I ran OpenOffice this afternoon it did
> not touch the file, nor did it create a new one when I moved the
> old one aside.
>
> I was going to re-test on that system after it updated to a more
> current Athena release and then report my findings, but Alex's
> information prompted me to speak now.
>
> -Bill
>
> ----
>
> William Cattey
> Linux Platform Coordinator
> MIT Information Services & Technology
>
> N42-040M, 617-253-0140, wdc@mit.edu
> http://web.mit.edu/wdc/www/
>
>
> On Jan 31, 2008, at 6:49 PM, Alex T Prengel wrote:
>
>>
>> Hi, you reported:
>>
>>> It seems that there is a bug with OpenOffice on Sun machines:
>>> Loading
>>> OpenOffice (from file or create a new document) on a Sun causes the
>>> file __db. to be created in the pwd. Also, when loading
>>> OpenOffice on
>>> a Sun, the presence of the file __db. in the pwd causes
>>> OpenOffice to
>>> hang.
>>
>> Indeed you are correct. Thanks for reporting this! I worked around
>> it by
>> having the launch script delete this file if found in the current
>> directory
>> before launching ooffice. It should reach users by the next
>> overnight AFS
>> propagation tonight.
>>
>> Oddly, googling on this doesn't turn up any relevant hits, so the
>> problem
>> must be uncommon, perhaps peculiar to our environment for some
>> reason.
>>
>> Alex
>>
>
