To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=105384
User cloph changed the following:
What |Old value |New value
================================================================================
Status|UNCONFIRMED |RESOLVED
--------------------------------------------------------------------------------
Resolution| |INVALID
--------------------------------------------------------------------------------
------- Additional comments from [email protected] Tue Mar 23 18:08:31 +0000
2010 -------
No response → invalid.
The lockfiles by themselves are useless as well, as they are only flag files.
The only info they contain are by whom (user and hostname), when (timestamp)
and
with what instance of OOo (which user-profile directory) was used to open the
file.
This info is used in case another user tries to open the same file, the other
user will then be alerted that <user> did open the file already and thus cannot
be opened for writing.
Those files surely do not affect any other software besides OOo.
Also OOo freezing Gnome is very unlikely as well. OOo can cause 100% CPU usage,
or can use a huge amount of RAM if stuff goes wrong, but both scenario won't
freeze your Desktop, it would make it slow as molasses when you're running out
of RAM, but you should still be able to kill OOo/switch to another window, etc.
More likely is a fault in your video driver/other core X-components that is
triggered and thus freezes your X-Server.
---------------------------------------------------------------------
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]
