To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=98361
                 Issue #|98361
                 Summary|.lock file is not always removed correctly when loggin
                        |g out
               Component|framework
                 Version|OOo 2.4.1
                Platform|All
                     URL|
              OS/Version|Unix, X11
                  Status|NEW
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P3
            Subcomponent|code
             Assigned to|mav
             Reported by|mla





------- Additional comments from [email protected] Thu Jan 22 13:00:50 +0000 
2009 -------
When users logout of their session (which should close all applications) with
OOo still open, upon relogging back in, they get the "Another session is
running" message when they open OOo. This means that the documents weren't
closing properly as it leaves a lock file.

I.e. the user logs out without closing OOo before. StarOffice gets a signal from
the session to close (save documents and other things). Removing the .lock file
would be the last thing, but sometimes this isn't done fast enough before the
before it is really finished, so that the office process gets killed by the 
session.

Now the lock files get deleted a bit earlier in the process of shutdown.

---------------------------------------------------------------------
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