[Libreoffice-bugs] [Bug 101409] FILEOPEN lock status being incorrectly (and dangerously) reported

https://bugs.documentfoundation.org/show_bug.cgi?id=101409 Aron Budea changed: What|Removed |Added Blocks||114300 CC|

[Libreoffice-bugs] [Bug 101409] FILEOPEN lock status being incorrectly (and dangerously) reported

https://bugs.documentfoundation.org/show_bug.cgi?id=101409 Nigel Arnot changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Libreoffice-bugs] [Bug 101409] FILEOPEN lock status being incorrectly (and dangerously) reported

https://bugs.documentfoundation.org/show_bug.cgi?id=101409 --- Comment #10 from QA Administrators --- Dear Nigel Arnot, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been

[Libreoffice-bugs] [Bug 101409] FILEOPEN lock status being incorrectly (and dangerously) reported

https://bugs.documentfoundation.org/show_bug.cgi?id=101409 --- Comment #9 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug

[Libreoffice-bugs] [Bug 101409] FILEOPEN lock status being incorrectly (and dangerously) reported

https://bugs.documentfoundation.org/show_bug.cgi?id=101409 --- Comment #8 from Nigel Arnot --- Mostly fixed 5.2.5.1 (and 5.3.0.3) The dangerous bit is mercifully gone. What isn't fixed: only the username locking the file is displayed in the dialog, and not the hostname

[Libreoffice-bugs] [Bug 101409] FILEOPEN lock status being incorrectly (and dangerously) reported

https://bugs.documentfoundation.org/show_bug.cgi?id=101409 Aron Budea changed: What|Removed |Added Blocks||104742

[Libreoffice-bugs] [Bug 101409] FILEOPEN lock status being incorrectly (and dangerously) reported

https://bugs.documentfoundation.org/show_bug.cgi?id=101409 --- Comment #7 from Eugene Kin --- Seems to be problem solved in LibO 5.2.3.2 -- You are receiving this mail because: You are the assignee for the bug.___

[Libreoffice-bugs] [Bug 101409] FILEOPEN lock status being incorrectly (and dangerously) reported

https://bugs.documentfoundation.org/show_bug.cgi?id=101409 --- Comment #6 from Eugene Kin --- LibO 5.3.0.0.alpha1 dialog shows correct information. So, in my case problem reproducible with LibO 5.2 only. -- You are receiving this mail because: You are the assignee

[Libreoffice-bugs] [Bug 101409] FILEOPEN lock status being incorrectly (and dangerously) reported

https://bugs.documentfoundation.org/show_bug.cgi?id=101409 --- Comment #5 from Eugene Kin --- Disagree about network bug. Steps to reproduce in multi-session Windows 7/Server 2008 R2 environment: 1. Login as User1, open document on local disk 2. Change user/Login as

[Libreoffice-bugs] [Bug 101409] FILEOPEN lock status being incorrectly (and dangerously) reported

https://bugs.documentfoundation.org/show_bug.cgi?id=101409 rob...@familiegrosskopf.de changed: What|Removed |Added CC|

[Libreoffice-bugs] [Bug 101409] FILEOPEN lock status being incorrectly (and dangerously) reported

https://bugs.documentfoundation.org/show_bug.cgi?id=101409 Eugene Kin changed: What|Removed |Added Status|UNCONFIRMED |NEW

[Libreoffice-bugs] [Bug 101409] FILEOPEN lock status being incorrectly (and dangerously) reported

https://bugs.documentfoundation.org/show_bug.cgi?id=101409 --- Comment #2 from Eugene Kin --- Created attachment 127765 --> https://bugs.documentfoundation.org/attachment.cgi?id=127765=edit Document in Use (LibO 5.2.0.1) -- You are receiving this mail because: You

[Libreoffice-bugs] [Bug 101409] FILEOPEN lock status being incorrectly (and dangerously) reported

https://bugs.documentfoundation.org/show_bug.cgi?id=101409 --- Comment #1 from Eugene Kin --- Created attachment 127764 --> https://bugs.documentfoundation.org/attachment.cgi?id=127764=edit Document in Use (LibO 5.1.5.2) -- You are receiving this mail because: You