Created attachment 185058 [details] Configuration of the samba Server I cannot open or save files to a smb share which is mounted via gvfs. This happens on a up to date Debian 11.6. (Specifically a machine configured as a Debian-Edu Workstation but I don't think that makes any difference) I also attached the configuration of the samba server in case that is relevant. This was first observed on a Debian-Edu deployment which is already in use for a while but I could also reproduce this on a fresh install on VMs. Saving with with other programs like gimp, inkscape, gnumeric works just fine. gvfs Version: 1.46.2-1 LibreOffice 7.0.4.2 00(Build:2) When saving from LibreOffice with File-Save as to the gvfs mount. ============================================================== Error saving the document Test: Object not accessible. The object cannot be accessed due to insufficient user rights. ============================================================== After saving locally, copying to gvfs mount and then trying to open from Thunar with right click "Open with LibreOffice Writer" ================================================== Document file 'Test.odt' is locked for editing by: Unknown User ================================================== If I try open with double clicking the LO splash screen briefly shows but nothing else happens. When trying to open the file from within LibreOffice via File->Open nothing happens. I attached the strace.log from the following command. lowriter --strace /run/user/1007/gvfs/smb-share\:server\=tjener.local\,share\=transfer-students/s1/Test.odt Related Bugs: Bug 128505 Bug 115747
Created attachment 185059 [details] strace log when opening the file on the smb share
I also just tested this with LibreOffice from bullseye-backports which is version LibreOffice 7.4.4.2 40(Build:2) The same behavior occurs. On Ubuntu 22.04 with LibreOffice 7.3.7.2 30(Build:2) this behavior does not occur.
I narrowed this down a little further. It seems to depend on what URI is passed to LibreOffice. When the path to the gvfs mount at /run/user/1000/gvfs/... is used, LO tries to write to lock file using the pwrite system call which is apparently not supported by gvfs: 3189 09:39:01.222996 openat(AT_FDCWD, "/run/user/1007/gvfs/smb-share:server=tjener.local,share=transfer-students/s1/.~lock.write-test.odt#", O_RDONLY) = -1 ENOENT (No such file or directory) 3189 09:39:01.224609 openat(AT_FDCWD, "/run/user/1007/gvfs/smb-share:server=tjener.local,share=transfer-students/s1/.~lock.write-test.odt#", O_RDWR|O_CREAT|O_EXCL, 0666) = 24 3189 09:39:01.231861 fstat(24, {st_mode=S_IFREG|0700, st_size=0, ...}) = 0 3189 09:39:01.231986 pread64(24, "", 4096, 0) = 0 3189 09:39:01.235114 pwrite64(24, ",testes,am-5254007fbccd.intern,03.02.2023 09:39,file:///home/testes/.config/libreoffice/4;", 90, 0) = -1 EOPNOTSUPP (Operation not supported) But when passing a smb:// URI LibreOffice uses some other method to read and write the files. There are no reads or writes to the file in the strace in that case but recvmsg and sendmsg calls. I guess it uses some DBUS Interface. What URI LO recieves depends on the Desktop Environment. With gnome this works properly but it does not on xfce and Mate.
Thank you for having such a close look at it, Nico, especially regarding the difference between desktop environments. For example, in bug 140488, the use of Caja probably means Mate is used. I assume you were using Xfce on Debian-Edu?
Dear nico.winkelstraeter, 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
Dear nico.winkelstraeter, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp