Description of problem: In Dolphin, I browse a network share on a Windows server. When I click to open a document, Libreoffice splash screen shows, then Libreoffice disappears again without any message. Version-Release number of selected component (if applicable): Dolphin 4.3.13, Libreoffice 4.2.6.2 How reproducible: Always Steps to Reproduce: 1. Browse network share 2. Click word-document Actual results: Libreoffice splash screen Expected results: To open document Additional info:
The easiest approach to find out more would be as follows: In a command line terminal, type soffice --strace which starts up a LibreOffice window; keep that open. Then use Dolphin to click-to-open a document with LibreOffice, wait a while until LibreOffice has silently failed to display the document, then close the LibreOffice window. At that time, the prompt will return in the command line terminal, and ls -l strace.log will show that there is now a (large) log file. Make that available for inspection (adding it as an attachment here or sending it directly to me).
Created attachment 940298 [details] --strace log as requested This is the log file you requested. I opened soffice from the command line, opened Dolphin and clicked on a Word document on a Windows share. The interesting stuff seems to start on line 32298 in the log file.
so it directly passes an smb URL to LibreOffice to open, so is a duplicate of 1054952 *** This bug has been marked as a duplicate of bug 1054952 ***
Created attachment 940821 [details] errors a few problems: 1. strace isn't in the system path; i have to designate the full path to run the program 2. the log file does not get created as a regular user. should this be done as root?
(In reply to bob from comment #4) > a few problems: > 1. strace isn't in the system path; i have to designate the full path to run > the program > 2. the log file does not get created as a regular user. should this be done > as root? Hm, you don't have /usr/bin/soffice? That would be strange, as it should be installed as part of the libreoffice-core package. Or, less likely, you don't have /usr/bin in PATH? What does entering echo $PATH give? Anyway, the reason you don't see a log file is that in the full-path invocation /opt/libreoffice4.2/program/soffice you didn't add the --strace parameter.
1. You have mail. 2. can you provide a hint as to what i should be looking for in the log file? 3. path info: echo $PATH /usr/lib64/qt-3.3/bin:/usr/lib64/ccache:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/home/bob/bin:/home/bob/.local/bin:/home/bob/bin:/home/bob/.local/bin:/home/bob/bin:/home/bob/.local/bin
Ach, I should have seen that immediately when you mentined "/opt/libreoffice4.2"---you're not using the Fedora libreoffice package, but some other LibreOffice package you obtained from somewhere else. Please use the "official" Fedora LibreOffice. (There is variance enough in how differently configured LibreOffice builds access URL schemas like smb that any speculation as of why that "other" LibreOffice does not work for you is futile.)
Thanks again for your time. I'd like to correct the misconception that I am not using the redhat builds. I am indeed using redhat's version of LO. It's installation to the /opt location occurred because of a lack of drive space on the root partition. Since it's installation several versions ago, yum update has reinstalled one fedora release of LO after another onto the system. So I think it's unfair to assume that the problem is that I'm using some "other" version of LO. Perhaps there is a path problem because the fedora version expects things to be in another path, but the software itself is 100% redhat.
(In reply to bob from comment #8) > Thanks again for your time. I'd like to correct the misconception that I am > not using the redhat builds. I am indeed using redhat's version of LO. > It's installation to the /opt location occurred because of a lack of drive > space on the root partition. Installation of the packages using rpm's --prefix option is unsupported. If you do it, you are on your own.
But when you once managed to somehow install the Fedora libreoffice packages to /opt (maybe via rpm directly), subsequent "yum update" will /not/ update those /opt files. From attachment 940821 [details] it looks like you ended up with some mess, you have files in both your non-standard /opt/libreoffice4.2 and in /usr/lib64/libreoffice (where the Fedora libreoffice packages put files), but are apparently missing the /usr/bin/soffice symlink (that is part of the Fedora libreoffice-core package). We cannot really help you with that setup of yours. [setting this issue back from WONTFIX to DUPLICATE, the original issue got somewhat accidentally hijacked starting with comment 4] *** This bug has been marked as a duplicate of bug 1054952 ***
thanks for the time you've spent in analysis. Since you think my installation is causing trouble, I'll just wipe it and start over, reinstalling F20 and LO on a larger disk.
When I build the box from scratch i'm going to be doing a network install. Can you tell me the specific yum command that is required to assure that I have properly installed LO on a basic F20 installation? I'm assuming that it is: "yum install libre-office-kde" I ask this becuase I know that the commands occasionally change from one Fedora version to another, and I want to be sure that if my problem should recur, that I haven't done the install in an improper way that chould make me vulnerable to non-support as the result of an improper install. thanks.