Created attachment 187149 [details] Console output when trying to open a file via the file dialog on an SMB share. Hi I use LibreOffice on openSUSE Tumbleweed with KDE desktop environment. I created a bookmark to an SMB share in KDE's Dolphin file manager. This bookmark of the SMB share also appears in the KDE file dialog used by LibreOffice, where you can select a file to open. Clicking on this SMB share bookmark was the starting point of my selection of an .odt file to open in LibreOffice Writer. Unfortunately, LibreOffice Writer does not open the selected .odt file when you click "Open". There is also no error message in the graphical user interface. In the shell, however, a bunch of messages appear. The messages are in the attached "Console.log" file.
Works OK for me on Debian testing with a bookmark to an SMB share on the same machine ( smb://michi@localhost/test-smbshare/subdir/ ) and the current development version of LO. When opening from Dolphin, the file is opened right away. When opening from LO ("File" -> "Open"), I am asked for credentials for the SMB share, and after entering these, the file is shown in Writer. Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 89ad9b9df1c54f29d3619e4342b70aa137ba7acc CPU threads: 12; OS: Linux 6.5; UI render: default; VCL: kf5 (cairo+xcb) Locale: en-GB (en_GB.UTF-8); UI: en-US Calc: threaded Also works with LO 7.6.2 as provided on the LO website: Version: 7.6.2.1 (X86_64) / LibreOffice Community Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333 CPU threads: 12; OS: Linux 6.5; UI render: default; VCL: kf5 (cairo+xcb) Locale: en-GB (en_GB.UTF-8); UI: en-US Calc: threaded Opening from within LO does not work with the Debian-provided LO 7.5, though. Version: 7.5.6.2 (X86_64) / LibreOffice Community Build ID: 50(Build:2) CPU threads: 12; OS: Linux 6.5; UI render: default; VCL: kf5 (cairo+xcb) Locale: en-GB (en_GB.UTF-8); UI: en-GB Debian package version: 4:7.5.6-1 Calc: threaded So this looks like the issue might have been fixed in the meanwhile (or it's some distro-package-specific problem). Can you please retest with 7.6?
Did you use KDE as desktop environment?
(In reply to Ettore Atalan from comment #2) > Did you use KDE as desktop environment? Yes, this is in a KDE Plasma X11 session.
(In reply to Michael Weghorn from comment #1) > So this looks like the issue might have been fixed in the meanwhile (or it's > some distro-package-specific problem). Can you please retest with 7.6? LibreOffice 7.6.1 still has this problem on my system. No sign of improvement.
> LibreOffice 7.6.1 still has this problem on my system. No sign of > improvement. Can you please try 7.6.2 from the LibreOffice website? https://wiki.documentfoundation.org/Installing_in_parallel/Linux has instructions on how to use that in parallel to a distro-provided version and this would also help identify whether it may be related to your distro packages. Does this also happen with a local SMB share, e.g. set up in Dolphin's properties tab for a folder? What happens when you try using "File" -> "Open Remote" instead of "File" -> "Open"? (Choose "Windows share" as type when adding the share via "Add service".)
(In reply to Michael Weghorn from comment #5) > Can you please try 7.6.2 from the LibreOffice website? > https://wiki.documentfoundation.org/Installing_in_parallel/Linux has > instructions on how to use that in parallel to a distro-provided version and > this would also help identify whether it may be related to your distro > packages. What has changed in LibreOffice version 7.6.2 compared to version 7.6.1 in dealing with SMB shares?
(In reply to Ettore Atalan from comment #6) > What has changed in LibreOffice version 7.6.2 compared to version 7.6.1 in > dealing with SMB shares? I don't know. I only see that it works for me with the 7.6.2 from the LO website while it doesn't work for you with 7.6.1 (from whatever source you have it, maybe from your distro?). So it would be interesting to know whether the same version that I'm using on Debian testing also works for you on OpenSUSE. If it doesn't, it might be some distro-specific thing, or related to the kind of SMB share, or ... (It would at least help to narrow potential causes down further. Same rationale for the other questions in comment 5.)
LibreOffice 7.6.1 was installed from the openSUSE Tumbleweed repositories.
[Automated Action] NeedInfo-To-Unconfirmed
I installed LibreOffice 7.6.2 from Flathub, but every time I access an SMB share in the LibreOffice 7.6.2 file dialog, an error message appears. Opening files or attempting to do so is impossible.
(In reply to Ettore Atalan from comment #10) > I installed LibreOffice 7.6.2 from Flathub, but every time I access an SMB > share in the LibreOffice 7.6.2 file dialog, an error message appears. > Opening files or attempting to do so is impossible. Thanks for testing. What does the error message say? Can you please try out and answer the other questions from comment 5 as well?
Given that flatpak apps are sandboxed, it might be that the Flathub version suffers from additional restrictions. Could you still try 7.6.2 from the LibreOffice website as well?
(In reply to Michael Weghorn from comment #5) > Does this also happen with a local SMB share, e.g. set up in Dolphin's > properties tab for a folder? Yes, it happens with that too. > What happens when you try using "File" -> "Open Remote" instead of "File" -> > "Open"? (Choose "Windows share" as type when adding the share via "Add > service".) Accessing the SMB share does not work. The problem still exists using LibreOffice 7.6.2 installed from the openSUSE Tumbleweed repository.
(In reply to Ettore Atalan from comment #13) "Does not work" in the sense that the files are not listed at all, or the files are listed, but opening the file fails the same way as when using the file dialog? > The problem still exists using LibreOffice 7.6.2 installed from the openSUSE > Tumbleweed repository. Thanks, could you still give the version provided on the LibreOffice website a try to see whether that's related to the distro packages?
(In reply to Michael Weghorn from comment #15) > (In reply to Ettore Atalan from comment #13) > "Does not work" in the sense that the files are not listed at all, or the > files are listed, but opening the file fails the same way as when using the > file dialog? The files are not listed at all.