Yesterday I have downloaded the just released LibreOffice 3.0 - the rpm version. After I have checked the check sums of the packages I have installed it in my openSUSE Leap 42.2. This is my second LibreOffice installation, because before this installation I have already installed on the same computer LibreOffice 5.2.5.1 downloaded from the The Document Foundation site. This installation works just fine, contrary to my LibreOffice 5.3.0 installation. The problem is visible when I try to start the LibreOffice 5.3.0 while LibreOffice 5.2.5.1 is not started. During the LibreOffice 5.3 starting I saw on the screen the initial green picture with LibreOffice 5 logo for a econd and after it it disappear without any notification. Same happens by starting it from CLI. In the release notes the information about the possibility of parallel installation with LibreOffice 5.2.5 is missing. So I believe this will work as before, so did not test 5.3.0 installed without LibreOffice 5.2.5.1.
please use a separate user folder: https://wiki.documentfoundation.org/Installing_in_parallel/Linux#Step_4_-_Optional.2C_but_Recommended_when_Testing:_Changing_the_User_Profile_location Set to NEEDINFO. Change back to UNCONFIRMED, if the problem persists. Change to RESOLVED WORKSFORME, if the problem went away.
You could also try launching 5.3 from command line with the switch --safe-mode
Buovjaga, This is a good hint (to check also this new possibility --safe-mode). I will try this next days. Probably during the weekends.
Today I have tested your suggestion. The button in the start menu of openSUSE in KDE is using this command "libreoffice5.3 %U" to start the office. Trying it from CLI gives the results explained in my bug report. 1. So I tried libreoffice5.3 %U --safe-mode. It helped LibreOffice 3.0 to start and show the form about safe mode choices. I choose "continue with safe mode". Then I get a popup a message like "LibreOffice can not found libreoffice5.3 %U - not available" and stop working. 2. Then I tryied "libreoffice5.3 --safe-mode". It worked well and the LibreOffice could start. I found out that when I choose "continue in safe mode" it could wok. But if I choose to start in normal mode it can not work. As I do not know how to use properly this new safe mode, I did nothing more there. But decide to export my profile as ZIP format. If needed I could provide it.
You could continue in Safe mode and check, if you happen to have OpenGL enabled: Tools - Options - LibO - View - Use OpenGL for all rendering If it is enabled, disable it and restart in normal mode.
Just to add something I had forgotten in my past message. The CLI session when I start successfully the LibreOffice 3.0 in safe mode, and close it successfully looks like following: #:~/Свалени/ libreoffice5.3 --safe-mode X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 42 (X_SetInputFocus) Resource id: 0x9600036 X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 42 (X_SetInputFocus) Resource id: 0x9600036 #:~/Свалени>
I have started the LibreOffice 3.0 in safe mode, then choose to continue in safe mode and try to change the settings. There I found that OpenGL was not enabled, but Open CL was enabled. So I have switched it off and restart the LibreOffice 3.0. After it LibreOffice 3.0 again did not start normal way. Then I started it again in safe mode and choose in the Safe Mode form 'Configure' and both options there - to disable all user extensions and to disable hardware acceleration (Open GL and Open CL). Then after restart my LibreOffice 3.0 get starting normally and works normally. This way the reported problem is solved, but new questions are coming as follows: 1. Now I am asking my self why when I switched out Open CL via Tools - Options etc ... it dud not help, but when I switched it out from the 'Safe Mode' form, it worked? 2. I had found in past that my computer is capable to provide OpenGL and Open CL to LibreOffice 5.2.x and I have used them every day with LibreOffice 5.2.x without troubles. So I am asking my self now why the same computer can not provide OpenGL and Open CL to LibreOffice 3.0.? Based on above I suspect in my case the reason of trouble may be not the Open CL but some extension I used. So I will try to check this and will report about later. Thank you very much for your prompt answer and your good suggestions in helping me to overcome this trouble.
Yes, the problem is not OpenCL, because it is only used by Calc and you would only see problems with a Calc sheet with some formulas. Instead of disabling many options at once in Safe mode, you should try one by one. First disable only hw acceleration. If it doesn't help, then disable extensions.
After updating LO to 5.3rc3 via the ppa:libreoffice/ppa, it doesn't start exactly as described by the bug opener. Kubuntu 16.10 64bit
(In reply to Boaz Dodin from comment #9) > After updating LO to 5.3rc3 via the ppa:libreoffice/ppa, it doesn't start > exactly as described by the bug opener. > > Kubuntu 16.10 64bit Ok, what's your experience with the --safe-mode switch, then (following the discussion)?
After starting with the --safe-mode switch and manually disabling hw acceleration and OpenCL, LO starts! Although GL status in safe mode was "GL is currently disabled" and "OpenCL is not used". So maybe the problematic option is Software Interpreter of OpenCL?
Boaz, kivi, what kind of GPU are you using? Could either of you test with a recent daily build from [1]? There's been a recent bug with the initialization of OpenGL mode in LibreOffice (bug 105514), which is now fixed (the fix will come in 5.3.1). To verify, grab a daily build and test with that, it can be installed separately from the current version, the details are linked in comment 1. Thanks! [1] http://dev-builds.libreoffice.org/daily/master/
(In reply to Aron Budea from comment #12) > Boaz, kivi, what kind of GPU are you using? Mine is AMD A8-6500T APU with Radeon HD 8550D.
(In reply to Boaz Dodin from comment #13) > Mine is AMD A8-6500T APU with Radeon HD 8550D. Ok, not too old. I encountered the other, similar bug with GPUs lacking/having limited OpenGL capabilities). Could you try getting a backtrace as described here, and attach it: https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_backtrace
I can't reproduce the crash anymore...
Even after deleting your user profile? (after backing it up if there's anything in there you might want to keep)
(In reply to Aron Budea from comment #16) > Even after deleting your user profile? (after backing it up if there's > anything in there you might want to keep) It's my main pc, so I prefer to not delete the profile.
(In reply to Boaz Dodin from comment #17) > It's my main pc, so I prefer to not delete the profile. How about installing it in a different directory in parallel? You can do it with the exact same version, the details are in comment 1. The wiki page in whole describes the process, and that particular step makes sure its profile is also stored separately.
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 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-20170830
Mean time my mother board get defective and the notebook get not operable. Now I use a new Lenovo laptop but can not provide any additional information about the repported bug, as I can not reproduce it any more.
(In reply to kivi from comment #20) > Mean time my mother board get defective and the notebook get not operable. > Now I use a new Lenovo laptop but can not provide any additional information > about the repported bug, as I can not reproduce it any more. Well I guess that is good news :) closing..