Problem description: After the last libreoffice upgrade on Gentoo Linux, I'm unable to open any libreoffice related file from a samba share. I just see the libreoffice logo and no more. This is reproducible also on suse. Steps to reproduce: 1. Go into a samba share directory 2. Open a file (doc,xls) Current behavior: Libreoffice is unable to open the file. Expected behavior: The file is opened. Operating System: Linux (Other) Version: 4.2.3.3 release
It worked for me at least in the 4.1.4.2 release
Hi, It works for me on the latest Fedora/Ubuntu with different file managers (dolphin, nautilus, caja). Given that you have the dependencies installed (gvfs or gnome-vfs, depending on the libreoffice build flags), I have no idea what could go wrong. Maybe strace could give us some hints? As a workaround you could try to disable the remote url forwarding by commenting 'X-GIO-NoFuse' (for GNOME) or 'X-KDE-Protocols' (for KDE) lines in the libreoffice .desktop files.
Created attachment 100971 [details] strace (In reply to comment #2) > It works for me on the latest Fedora/Ubuntu with different file managers > (dolphin, nautilus, caja). Given that you have the dependencies installed > (gvfs or gnome-vfs, depending on the libreoffice build flags), I have no > idea what could go wrong. Maybe strace could give us some hints? I have the dependencies installed because it works with the provious version. > As a workaround you could try to disable the remote url forwarding by > commenting 'X-GIO-NoFuse' (for GNOME) or 'X-KDE-Protocols' (for KDE) lines > in the libreoffice .desktop files. Your workaround works.
Sorry for not being clear enough, but we need the strace of the actual libreoffice process. "localc" as well as other lo* files, and even "soffice" are just a shell scripts wrapping the actual binary ("soffice.bin"). The easiest way to get this is to run "soffice --strace smb://server/share/somedoc". This will create a file called "strace.log" in the current directory.
Created attachment 101152 [details] strace.log (In reply to comment #4) > Sorry for not being clear enough, but we need the strace of the actual > libreoffice process. "localc" as well as other lo* files, and even "soffice" > are just a shell scripts wrapping the actual binary ("soffice.bin"). The > easiest way to get this is to run "soffice --strace > smb://server/share/somedoc". This will create a file called "strace.log" in > the current directory. Done.
What returns "ls /usr/lib64/libreoffice/program/*ucpgio*.so"? If you don't have this file, it means that you didn't build with "--enable-gio". I'm not familiar with the Gentoo build system, but it seems that you need to have "gnome" in the USE variable. And since you're a KDE user, I can only guess that you don't have it?
(In reply to comment #6) > What returns "ls /usr/lib64/libreoffice/program/*ucpgio*.so"? If you don't > have this file, it means that you didn't build with "--enable-gio". I'm not > familiar with the Gentoo build system, but it seems that you need to have > "gnome" in the USE variable. And since you're a KDE user, I can only guess > that you don't have it? I do not have this file. Let's summarize a bit: I clearly state that the program works if I comment X-KDE-Protocols=file,http,smb,ftp,webdav in the .desktop file. So the program is _able_ to open the file over a samba share. You asked me a strace and I provided that. I don't guess that NEEDINFO is the correct state.
(In reply to comment #7) > I clearly state that the program works if I comment > X-KDE-Protocols=file,http,smb,ftp,webdav in the .desktop file. So the > program is _able_ to open the file over a samba share. No, it doesn't mean that. In that case dolphin downloads the file to the cache dir, and passes this temp file to libreoffice. Have a look at File->Properties..., where you can find the actual file location. > You asked me a strace and I provided that. I don't guess that NEEDINFO is > the correct state. It's still in NEEDINFO because I asked whether you built libreoffice without "--enable-gio"?
(In reply to comment #8) > It's still in NEEDINFO because I asked whether you built libreoffice without > "--enable-gio"? It was built with: --disable-gio
(In reply to comment #9) > It was built with: --disable-gio OK, in that case it works as expected. You can't expect for a feature to work, if you disable it at build time. If for some reason you're not interested in gio/gnome-vfs, you can continue to use the workaround with .desktop files.