[Bug 170669] Every Time i Open a file on my NAS via smb share i get the message "This file has ben Locked by another user"

2026-04-29 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=170669

Timur  changed:

   What|Removed |Added

 Blocks||114300

--- Comment #7 from Timur  ---
Please see bug 131401 and advice given there.
Does it change if oyu turn off client-side caching for that share, and veto
oplock files = /*.ods/*.xlsx/*.xls/*.ots/ .


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=114300
[Bug 114300] [META] Bugs and enhancements involving lock files or file locking
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 170669] Every Time i Open a file on my NAS via smb share i get the message "This file has ben Locked by another user"

2026-02-12 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=170669

--- Comment #6 from Gerhard  ---
Same Problem.
See also:
Bug 170705 - When closing the file, . lock.12.03.2025.ods# is not closed either

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 170669] Every Time i Open a file on my NAS via smb share i get the message "This file has ben Locked by another user"

2026-02-12 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=170669

--- Comment #5 from Gerhard  ---
Same Problem.
See also:
Bug 162751 - FiLEOPEN a xlsx file do not load - load blocked - only solution is
to close / kill the application

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 170669] Every Time i Open a file on my NAS via smb share i get the message "This file has ben Locked by another user"

2026-02-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=170669

--- Comment #4 from Dorian Gaensslen  ---
It seems, that the GVFS mount does something, that a regular cifs mount does
not. Because with cifs it works...


With this mount, it works:
//synology.local/home /media/synology cifs
credentials=/etc/samba/smbcredentials-syno,uid=1000,gid=1000,iocharset=utf8,vers=3.0,file_mode=0664,dir_mode=0775,nofail,_netdev
 0 0

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 170669] Every Time i Open a file on my NAS via smb share i get the message "This file has ben Locked by another user"

2026-02-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=170669

[email protected] changed:

   What|Removed |Added

Version|24.2.7.2 release|26.2.0.3 release
 Ever confirmed|0   |1
 OS|Linux (All) |Windows (All)
 Status|UNCONFIRMED |NEW

--- Comment #3 from [email protected] ---
I have the same problem that every time I want to create or edit a file on my
SNB share, the read-only permission and the “lock file” are no longer removed
when saving. The problem only occurs on my Windows 11 PC. I don't have this
problem on my Linux Mint PC. I can then remove the read-only flag manually, but
it is set again the next time I save. The problem only arose with the upgrade
to version 26.2.0.3. The NAS DMS is on the latest version. The problem occurs
with all modules.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 170669] Every Time i Open a file on my NAS via smb share i get the message "This file has ben Locked by another user"

2026-02-08 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=170669

--- Comment #2 from Dorian Gaensslen  ---
Created attachment 205427
  --> https://bugs.documentfoundation.org/attachment.cgi?id=205427&action=edit
Error Message

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 170669] Every Time i Open a file on my NAS via smb share i get the message "This file has ben Locked by another user"

2026-02-08 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=170669

--- Comment #1 from Dorian Gaensslen  ---
I checked also Apparmor Log entrys, but they seem to be ok (only Allowed, no
denied).

-- 
You are receiving this mail because:
You are the assignee for the bug.