[Bug 115747] Can't edit file on samba shares (see comment 28) (fstab nobrl workaround)
https://bugs.documentfoundation.org/show_bug.cgi?id=115747 Justin L changed: What|Removed |Added Summary|Can't edit file on samba|Can't edit file on samba |shares ( see comment 28 ) |shares (see comment 28) ||(fstab nobrl workaround) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 115747] Can't edit file on samba shares ( see comment 28 )
https://bugs.documentfoundation.org/show_bug.cgi?id=115747 --- Comment #51 from The Nation Publishers --- sd -- You are receiving this mail because: You are the assignee for the bug.
[Bug 115747] Can't edit file on samba shares ( see comment 28 )
https://bugs.documentfoundation.org/show_bug.cgi?id=115747 Mike Kaganski changed: What|Removed |Added URL|https://gtaesthetic.com/| -- You are receiving this mail because: You are the assignee for the bug.
[Bug 115747] Can't edit file on samba shares ( see comment 28 )
https://bugs.documentfoundation.org/show_bug.cgi?id=115747 james heal changed: What|Removed |Added URL||https://gtaesthetic.com/ --- Comment #50 from james heal --- Best MedSpa in the Greentree & Pittsburgh area providing superior aesthetic medicine for the face, body, skin and women’s wellness. >From body contouring, laser hair removal, botox, fillers, facials, and solutions for spider & varicose veins, we provide everything you need to feel like the best version of yourself! -- You are receiving this mail because: You are the assignee for the bug.
[Bug 115747] Can't edit file on samba shares ( see comment 28 )
https://bugs.documentfoundation.org/show_bug.cgi?id=115747 Mike Kaganski changed: What|Removed |Added URL|https://gtaesthetic.com/| -- You are receiving this mail because: You are the assignee for the bug.
[Bug 115747] Can't edit file on samba shares ( see comment 28 )
https://bugs.documentfoundation.org/show_bug.cgi?id=115747 james cook changed: What|Removed |Added URL||https://gtaesthetic.com/ --- Comment #49 from james cook --- Best MedSpa in the Greentree & Pittsburgh area providing superior aesthetic medicine for the face, body, skin and women’s wellness. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 115747] Can't edit file on samba shares ( see comment 28 )
https://bugs.documentfoundation.org/show_bug.cgi?id=115747 W Sanders changed: What|Removed |Added CC||wsand...@wsanders.net --- Comment #48 from W Sanders --- See my bug 156628. Still a problem in 7.5.5.2, but mounting "nobrl" is an effective workaround. I have a Fedora Linux CIFS server version 4.18.5-0.fc38. It's my (limited) understanding that BRL (bit range locking) is ignored in Linux Samba, so this issue might be specific to Linux Samba servers only. I don't have any issues with any other apps that use my CIFS shares. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 115747] Can't edit file on samba shares ( see comment 28 )
https://bugs.documentfoundation.org/show_bug.cgi?id=115747 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=55 ||004 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 115747] Can't edit file on samba shares ( see comment 28 )
https://bugs.documentfoundation.org/show_bug.cgi?id=115747 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||3318 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 115747] Can't edit file on samba shares ( see comment 28 )
https://bugs.documentfoundation.org/show_bug.cgi?id=115747 Stéphane Guillou (stragu) changed: What|Removed |Added CC||liz...@126.com --- Comment #47 from Stéphane Guillou (stragu) --- *** Bug 153453 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 115747] Can't edit file on samba shares ( see comment 28 )
https://bugs.documentfoundation.org/show_bug.cgi?id=115747 --- Comment #46 from dunkskicks --- The https://www.snkrspop.com/jordan-4-reps.html has always fit true to size. I can confidently say that the fit of this sneaker has been the same ever since the eighties as I own a pair of ‘Chicago’ Air Jordan 1’s from 1985 that fit the exact same way as an Air Jordan 1 Retro OG High fits today. The Air Jordan 1 is a shoe that’s comfortable enough to wear for an entire day as it’s created with padded ankle support and a soft tongue. Sure, it’s not the most comfortable shoe on the market, but it’s great for people, like me, with wide feet as it’s a very accommodating shoe. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 115747] Can't edit file on samba shares ( see comment 28 )
https://bugs.documentfoundation.org/show_bug.cgi?id=115747 Mike Kaganski changed: What|Removed |Added URL|https://greatassignmenthelp | |er.com/medicare-assignment- | |help/ | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 115747] Can't edit file on samba shares ( see comment 28 )
https://bugs.documentfoundation.org/show_bug.cgi?id=115747 jessicawilliamson...@gmail.com changed: What|Removed |Added URL||https://greatassignmenthelp ||er.com/medicare-assignment- ||help/ --- Comment #45 from jessicawilliamson...@gmail.com --- Having been providing MedicareAssignment Help for longer than a decade now, our bespoke preparations are always plagiarism free and fully in sync with the latest criteria and rubrics of the faculty. We amplify and ensure your chances at the most excellent grades only. https://greatassignmenthelper.com/medicare-assignment-help/ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 115747] Can't edit file on samba shares ( see comment 28 )
https://bugs.documentfoundation.org/show_bug.cgi?id=115747 --- Comment #44 from code-b...@bnavigator.de --- Many duplicates actually closer to bug 55004 point here, so I would like to mention, that https://bugs.documentfoundation.org/show_bug.cgi?id=55004#c37 helped me: Adding nobrl to /etc/fstab was a good workaround to finally be able to save libreoffice documents to Sama cifs shares again. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 115747] Can't edit file on samba shares ( see comment 28 )
https://bugs.documentfoundation.org/show_bug.cgi?id=115747 --- Comment #43 from m1027 --- (In reply to Thorsten Behrens (allotropia) from comment #35) > the question is, does setting UseDocumentOOoLockFile > to false constitute a valid workaround? -> NEEDINFO for the moment In my case yes. I'd just like to share that the root case of that issue is still obscure. We have a dozen linux clients and a dozen windows clients using libreoffice 6.4 to 7.0 on two different samba 4.12 servers: - Windows libreoffice users were never hit - Not all linux users hit; it seems that mostly vfs mounts (like with gnome) never reveal the issue; while fstab/manual mounting users are hit more often - The issue just "appeared" about 6 months ago, roughly when switching from samba 4.11 to 4.12 on one of the servers with a recent and faster hardware. - On one of the samba server's I personally can reproduce the issue but not on the other; with the exact same libreoffice linux client and the exact same smbd.conf for both servers... (server's kernels and HW differ though). If someone want me to do some more tests, expecially with the two samba servers being hit/not hit, let me know. Thanks -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 115747] Can't edit file on samba shares ( see comment 28 )
https://bugs.documentfoundation.org/show_bug.cgi?id=115747 Timur changed: What|Removed |Added CC||b...@atina-asso.org --- Comment #42 from Timur --- *** Bug 127057 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 115747] Can't edit file on samba shares ( see comment 28 )
https://bugs.documentfoundation.org/show_bug.cgi?id=115747 Justin L changed: What|Removed |Added Status|NEEDINFO|NEW -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 115747] Can't edit file on samba shares ( see comment 28 )
https://bugs.documentfoundation.org/show_bug.cgi?id=115747 --- Comment #41 from chuck.pob...@gmail.com --- I have been battling this bug (of if not this bug a similar one) off and on for quite some time. Most recently with Libreoffice 6.4.2.2 on Linux Mint, I can not open a file from my server (SMB share - Ubuntu 16.04). The program crashes almost immediately and never opens the file. The program does not crash with Libreoffice 6.3.5. I can use other programs and open files including copying files with my file manager Nemo or editing and saving text files with xed. So this must be related to libreoffice. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 115747] Can't edit file on samba shares ( see comment 28 )
https://bugs.documentfoundation.org/show_bug.cgi?id=115747 --- Comment #40 from QA Administrators --- Dear Jerome, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 115747] Can't edit file on samba shares ( see comment 28 )
https://bugs.documentfoundation.org/show_bug.cgi?id=115747 Xisco Faulí changed: What|Removed |Added CC||d...@broekstra.nl --- Comment #39 from Xisco Faulí --- *** Bug 123681 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 115747] Can't edit file on samba shares ( see comment 28 )
https://bugs.documentfoundation.org/show_bug.cgi?id=115747 Xisco Faulí changed: What|Removed |Added CC||dejan.rehber...@gmail.com --- Comment #38 from Xisco Faulí --- *** Bug 121678 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 115747] Can't edit file on samba shares ( see comment 28 )
https://bugs.documentfoundation.org/show_bug.cgi?id=115747 --- Comment #37 from Xisco Faulí --- Discussion moved to the dev mailing list for wider audience -> http://document-foundation-mail-archive.969070.n3.nabble.com/Re-Bug-115747-Can-t-edit-file-on-samba-shares-td4255934.html -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 115747] Can't edit file on samba shares ( see comment 28 )
https://bugs.documentfoundation.org/show_bug.cgi?id=115747 --- Comment #36 from Justin L --- (In reply to Thorsten Behrens (CIB) from comment #35) > the question is, does setting UseDocumentOOoLockFile > to false constitute a valid workaround? >From a testing perspective, the result is that files can be saved (no warnings, just a save as normal). Opening files result in a warning and read-only mode. (P.S. no "user" will be able to answer questions about what is an acceptable work-around. Now we have at least 3 variables related to locking - how can anyone know what the implications of any of this are, especially when no definitions have been given? Based on comment 19, this is not a "rare" case, so it would be really hard to determine if preventing ANY use of a dotlock file is valid in every case.) It seems like your concern already had been addressed. Wasn't setting UseDocumentSystemLocking = false a good enough workaround for those who want to require the existence of a lock file? (Perhaps not - I'd guess that the benefit of ALSO using a system lock is that the user CANNOT override it, like they CAN do with an OOo lock file. Probably also worth noting is that it isn't checking if the system SUCCEEDED in using it's own locking mechanism, only that it would try...). UseDocumentSystemFileLocking: Allows to specify whether the OOo document file locking mechanics should use the system file locking (default true). UseDocumentOOoLockFile: Allows to specify whether the OOo document file locking mechanics should use the lock file for locking (default true). UseLocking: Allows to specify whether locking should be used at all. Use this setting only for debugging purpose (default true). UseWebDAVFileLocking: Determines if WebDAV-specific file locking is used for documents on WebDAV shares. It is not recommended to set this option to 'false' in scenarios where multi-user, concurrent read/write access to WebDAV share is required (default true). Because A) this is a regression, B) which already had an alternate solution (SystemLocking = false), C) and the description uses the terminology "Allow" instead of "Mandatory", D) involving an unnecessary file for normal operation, E) caused by undocumented rationale for the changed behaviour, I suggest reverting this bit and introducing a MandatoryLocking variable to handle the very unique situations where locking files actually have any value. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 115747] Can't edit file on samba shares ( see comment 28 )
https://bugs.documentfoundation.org/show_bug.cgi?id=115747 Thorsten Behrens (CIB) changed: What|Removed |Added Status|NEW |NEEDINFO --- Comment #35 from Thorsten Behrens (CIB) --- (In reply to Mike Kaganski from comment #34) > In my opinion, the original fix (and this comment) somehow change the proper > notion of a feature/function that helps to reach some goals (reliably detect > locking/identify locking person) to a requirement for function (=if we > cannot detect locking reliably, then fail to work). Is that what is > intended? and what exact problem was solved by that change, that justifies > making this enforcement? The original problem in tdf#106942 only mentioned a > corner case of "drive full", which could be detected separately and acted > accordingly. That's a fair statement wrt. the scope & wording of the fix. But I conversely consider a setup where arbitrary shell globs of files cannot be written a corner case - the question is, does setting UseDocumentOOoLockFile to false constitute a valid workaround? -> NEEDINFO for the moment -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 115747] Can't edit file on samba shares ( see comment 28 )
https://bugs.documentfoundation.org/show_bug.cgi?id=115747 --- Comment #34 from Mike Kaganski --- (In reply to Thorsten Behrens (CIB) from comment #32) > (In reply to Justin L from comment #31) > > I have no idea why so much code was removed from the exception clause, but > > restore the part with "if ( bUseSystemLock || !IsOOoLockFileUsed() )" solves > > both the read-only problem on loading, and the save failure. > > Because that hides the fact that the lock file could not be created. If in a > deployment people are ok to only use system file locking, the config option > UseDocumentOOoLockFile should be set to false. In my opinion, the original fix (and this comment) somehow change the proper notion of a feature/function that helps to reach some goals (reliably detect locking/identify locking person) to a requirement for function (=if we cannot detect locking reliably, then fail to work). Is that what is intended? and what exact problem was solved by that change, that justifies making this enforcement? The original problem in tdf#106942 only mentioned a corner case of "drive full", which could be detected separately and acted accordingly. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 115747] Can't edit file on samba shares ( see comment 28 )
https://bugs.documentfoundation.org/show_bug.cgi?id=115747 --- Comment #33 from Mike Kaganski --- Is there an option to use locking if possible, so that the lockfile can help on filesystems which allow that, and still be able to work with those filesystems that don't? or do we have only all-or-nothing option? -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 115747] Can't edit file on samba shares ( see comment 28 )
https://bugs.documentfoundation.org/show_bug.cgi?id=115747 --- Comment #32 from Thorsten Behrens (CIB) --- (In reply to Justin L from comment #31) > I have no idea why so much code was removed from the exception clause, but > restore the part with "if ( bUseSystemLock || !IsOOoLockFileUsed() )" solves > both the read-only problem on loading, and the save failure. Because that hides the fact that the lock file could not be created. If in a deployment people are ok to only use system file locking, the config option UseDocumentOOoLockFile should be set to false. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 115747] Can't edit file on samba shares ( see comment 28 )
https://bugs.documentfoundation.org/show_bug.cgi?id=115747 --- Comment #31 from Justin L --- I have no idea why so much code was removed from the exception clause, but restore the part with "if ( bUseSystemLock || !IsOOoLockFileUsed() )" solves both the read-only problem on loading, and the save failure. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 115747] Can't edit file on samba shares ( see comment 28 )
https://bugs.documentfoundation.org/show_bug.cgi?id=115747 --- Comment #30 from Thorsten Behrens (CIB) --- (In reply to Katarina Behrens (CIB) from comment #24) > Workaround (not to be used on mission-critical samba shares, it's really > just that, a workaround): > > Go to Tools > Options > Advanced > Expert configuration > Search for 'UseDocumentSystemFileLocking' and 'UseLocking' keys > Set 1st one to 'false' > If it doesn't help, set also 2nd one to 'false' There's also UseDocumentOOoLockFile which I think is the one that disables writing those lock files. Might be a suitable work-around here. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 115747] Can't edit file on samba shares ( see comment 28 )
https://bugs.documentfoundation.org/show_bug.cgi?id=115747 --- Comment #29 from Thorsten Behrens (CIB) --- Since all versions since the dark ages try to create lock files also on samba shares, that means in pre-6.0 versions the error in writing the lock was simply ignored. With that, I tend to consider this NOTABUG. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 115747] Can't edit file on samba shares ( see comment 28 )
https://bugs.documentfoundation.org/show_bug.cgi?id=115747 Xisco Faulí changed: What|Removed |Added Summary|Can't edit file on samba|Can't edit file on samba |shares |shares ( see comment 28 ) Status|NEEDINFO|NEW -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
