If I try to open from the dashboard it just don't do anything, but it spins up a python3 proccess.
If I try to open an impress file it says:
Component cannot be loaded, possibly broken or incomplete installation.
Full error message:
loading component library <file:///usr/lib/libreoffice/program/../program/libsdlo.so> failed.
And if I try to open an writer file it says:
General input/output error.
I'm using Ubuntu 14.04 with PPA. Before I had a 4.2.5 install from the PPA, and then I removed the PPA, the dependencies (libreoffice*), the orphaned packages that surfaced and all the config files. Then I added the prereleases PPA, and after I updated and installed libreoffice, it wont start no matter what.
My Ubuntu 14.04 x86_64 works fine with LibO PPA:
deb http://ppa.launchpad.net/libreoffice/libreoffice-4-2/ubuntu trusty main
deb-src http://ppa.launchpad.net/libreoffice/libreoffice-4-2/ubuntu trusty main
I can't confirm your bug.
Do you have any news after system updates?
Which LibreOffice version is bugged?
The description bring back to 220.127.116.11 but you set 18.104.22.168 rc.
Please, specify the oldest one not the newer.
(need more info from bug reporter, so
Status -> NEEDINFO)
Same error now reported on the Ask site for Oracle Linux 7 + v22.214.171.124:
Well, after the official release I made the update from the "fresh" PPA (libreoffice/ppa) and everything works just fine.
I don't have a clue about the error that ocurred, but now it is "solved" as I have the latest version without any problem.
Same issue on RHEL 7. The solution at http://ask.libreoffice.org/en/question/37825/why-cant-i-open-libreoffice-components-on-oracle-linux-7/
...works for RHEL 7 too. I guess we are missing the dependency on mesa-libGLU in the libobasis4.3-core04.x86_64.rpm package?
My desktop is a fresh RHEL 7 Workstation and I installed LibreOffice_4.3.4_Linux_x86-64_rpm.tar.gz today.
(In reply to Andrew Spurrier from comment #5)
> Same issue on RHEL 7.
Hmm, might be different issue as we're talking two different distros.
The solution at
> ...works for RHEL 7 too. I guess we are missing the dependency on
> mesa-libGLU in the libobasis4.3-core04.x86_64.rpm package?
> My desktop is a fresh RHEL 7 Workstation and I installed
> LibreOffice_4.3.4_Linux_x86-64_rpm.tar.gz today.
Let's get some more information here. Please try out the 126.96.36.199 RC and/or a 4.4 beta build and let us know if those exhibit the same problem:
Status -> NEEDINFO (change back to UNCONFIRMED after you test)
Severity -> major
Dear Bug Submitter,
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 INVALID due to lack of needed information.
For more information about our NEEDINFO policy please read the wiki located here:
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!
This NEEDINFO message was generated on: 2015-07-18
Dear Bug Submitter,
Please read this message in its entirety before proceeding.
Your bug report is being closed as INVALID 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 FDO
Message generated on: 2015-09-03