Description: I have a new installation of the current KDE Neon 'distro', which is based on Ubuntu. LibreOffice installs normally from the repositories. I have tried 2 different LO versions. The Start Center always opens normally. In LibreOffice 5.1.6.2, choosing to create a new document of any type, regardless whether using the sidebar buttons or the menu, will not open the LibreOffice component. In LibreOffice 5.3.4.0, the sidebar buttons to create new documents are grayed out. I tried starting a component from the command line, using "libreoffice --writer" and "libreoffice --calc", in v. 5.1.6.2, will briefly display the splash logo, which then disappears, and nothing further happens. The task does not end by itself, so I have to terminate it. I have deleted the profile and temporary files, without effect. Version information: Tried LO versions: libreoffice 5.1.6.2, libreoffice-dbg 5.1.6.2, libreoffice 5.3.4.0 Distro: KDE neon LTS 5.8 KDE Plasma: 5.8.7 KDE Frameworks: 5.36.0 QT: 5.7.1 Kernel: 4.8.0-58-generic OS: 64 bit X-Server: 11.0 (11,804,000) Open-GL: 3.0 Mesa 17.07 Hardware: CPU: i5-5200U Mem: 7.7 GB GPU: NVIDIA GM108M (GeForce 940M) Steps to Reproduce: A. The default way: A1. Install KDE neon LTS 5.8 A2. Install LibreOffice the default way using Discover (open Application Launcher/Applications/System/Software Center) or alternatively via "sudo apt-get install libreoffice". B. Installing the lates version the manual way: B1. sudo add-apt-repository ppa:libreoffice/ppa B2. sudo apt-get update B3. sudo add-apt-repository ppa:libreoffice/ppa # apt-get seemed to need it twice to find the latest version B4. sudo apt-get install libreoffice C. When trying different versions, clean apt information C1. sudo apt-get purge libreoffice C2. sudo add-get autoremove C3. sudo apt-get clean # should not be necessary, but... C4. sudo add-apt-repository -r ppa:libreoffice/ppa # if applicable C5. sudo apt-get update Actual Result: No response from components using either the Start Center or the command line. When opening a template document using the Start Center (Templates / Writer Templates / select any...), the Start Center closes and a crash notice pops up (LibreOffice Document Recovery. Due to an unexpected error, LibreOffice crashed. [...] The following files will be recovered: <empty>). Then clicking "Ok" will reopen the Start Center. Expected Result: Opening LibreOffice components, or at least an error message in case of any incompatibilities. Additional Information: I have now installed libreoffice-dbg, but I do not know how to use the debug functionality. If advised how, I will be happy to provide more information.
I'm not sure, does "apt purge" also purge LO directory profile? If not, could you rename it (see https://wiki.documentfoundation.org/UserProfile) and give a new try? You may also disable OpenGL (see https://wiki.documentfoundation.org/QA/FirstSteps) If you still reproduce the crash, would it be possible you attach a bt? (see https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_backtrace)
Created attachment 135047 [details] 4 different gdb traces
Please find attached the gdb traces of various scenarios (packed in 1 file). General: - I deleted the profile folder before every try. - OpenGL is already disabled (Start Center / Help / About LibreOffice says 'OpenGL: default'). - Procedure followed according to https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_backtrace 1. gdbtrace-StartCenter.log - Reproduction: Pressing some buttons on the left in Start Center (Writer, Calc, Impress). - Quitted application. 2. gdbtrace-StartCenter_opening_Writer_Template.log - Reproduction: Opening a Writer template from Start Center. - Actual Result: Hung process. - Killed the process according to above procedure. 3. gdbtrace-Writer.log and gdbtrace-Calc.log - Reproduction: Started application using 'soffice --writer --backtrace' and 'soffice --calc --backtrace' - Actual result: flashy (brief) appearance of splash info, then nothing (I also tried waiting a while, and monitored the CPU which was idle). - Killed the process according to above procedure. Apologies for the delay.
I don't know how you compressed you gdbtrace-Calc.log is in fact a gz file a bit corrupted. None of them show a complete bt. The only interesting line I saw is this one: OutputDevice::LogicToPixel (this=this@entry=0x0, rLogicSize=Size = {...}, rMapMode=...) at /build/libreoffice-hXb58c/libreoffice-5.1.6~rc2/vcl/source/outdev/map.cxx:1129 The pb is we need the stack of callers because this one shows that the manipulated object here is null (this@entry=0x0).
Oh, I must have done some mistake. However, gdbtrace-Calc.log looked like gdbtrace-Writer.log. Strangely, that didn't show any error. How can I produce a stack of callers? I followed the instructions in your link.
push
I don't know how to help you to retrieve some useful bt. Since I don't have more questions, I'll put back to unconfirmed. I also uncc myself since I got no idea here. Certainly somebody else may help.
Created attachment 135898 [details] Full Backtrace I tried again and got a full backtrace (dunno what I did differently). Reproduction: 1. Install libreoffice-dbg on KDE neon distro (which is based on Ubuntu 5.8) 2. Run `$ soffice --backtrace` 3. From StartCenter open any Writer template (I selected Templates/Writer Templates/Business.../Moderate...)
Ok, the trace looks useful now. What if you use an AppImage, does it work without problems? http://libreoffice.soluzioniopen.com/index.php/daily-version/ To run it, just chmod +x or right-click - properties - executable and then you can double-click to run or ./ from the command line.
Dear Henning, KDE5 support has been added recently to LibreOffice. Could you please try to reproduce it with a master build from http://dev-builds.libreoffice.org/daily/master/ ? You can install it alongside the standard version. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the master build
Dear Xisco, apologies for the late reply. :-( I tried the latest master. All components start, the bug does not appear anymore. The used version is: Version: 6.1.0.0.alpha0+ Build ID: d2c9b749503ef0763a6140a7b509f73adb6015d2 I hope I'm doing the right thing by setting the status back to UNCONFIRMED, as a green note on this page is telling me to.
Let's set to WFM as it's the problem is gone :)
Thank you :-)