Trying to run LibreOffice 6.0.0.0.alpha1+ (git from today) with SAL_USE_VCLPLUGIN=qt5 results in an immediate crash: *** Error in `/usr/lib64/libreoffice/program/soffice.bin': malloc(): memory corruption: 0x0000000001454280 *** The splash screen and a window with title "soffice.bin" remain open (but there's nothing in the window). The build works well with SAL_USE_VCLPLUGIN=default or SAL_USE_VCLPLUGIN=gtk This is on OpenMandriva Cooker x86_64 -- linux 4.14, glibc 2.26, Qt 5.10.0-beta4, KF5 5.40.0, Plasma Desktop 5.11.3
slightly different behavior when rebuilt with --enable-debug: Window doesn't even open, error message isn't printed, but before aborting an extra warning is printed: warn:opencl:54163:54163:desktop/source/app/opencl.cxx:137: Failed to initialize OpenCL for test Seems unrelated though, Qt doesn't require OpenCL...
Would it be possible you attach a backtrace by following this link? https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_backtrace
Created attachment 137945 [details] gdb trace log
FWIW since it shows up in the backtrace, harfbuzz version is 1.7.1
Thank you for your feedback. I noticed several times "CRC mismatch", I wonder if the install of debug package is ok.
Happens here, too. Behavior is as described in the opening message. [01/12/2017 19:30:14 - fincer: ~ ]$ export SAL_USE_VCLPLUGIN=qt5 [01/12/2017 19:30:18 - fincer: ~ ]$ libreoffice *** Error in `/usr/lib/libreoffice/program/soffice.bin': malloc(): memory corruption: 0x000055b808392200 *** Application Error ---------- Arch Linux x86_64 glibc 2.26 qt5-base 5.9.1 KF5 5.37.0 plasma-desktop 5.10.5 Reproducible with and without '--enable-64-bit' configure flag.
Still happens with Qt 5.10.0-rc1 and libreoffice 6.0.0-beta1
Yeah...that's sad. I have enabled '--enable-qt5' flag in my build configuration, and set 'qt5-base' + 'kcoreaddons' as dependencies for LibreOffice. I am using GIT version of the software. Is there still some extra/special configuration or specific dependency package versions needed for working Qt5 build?
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
I haven build LO 6.2.0.0beta1 with Qt5 5.11.2 but not under plasma desktop but under kde4 desktop. (--enable-qt5 within my buildscript) Starting from the console with "bash-4.4# SAL_USE_VCLPLUGIN=qt5 /root/slackbuild\ libreoffice/libreoffice\ 6.2/soffice --calc" i have no error messages nor a crash Version: 6.2.0.0.beta1+ Build ID: 80fdc2491df857c910afbd30c025b4594cb1cf83 CPU threads: 8; OS: Linux 4.19; UI render: default; VCL: kde4; Locale: nl-BE (en_US.UTF-8); UI-Language: en-US Calc: threaded
I can't reproduce here with a current master build and running Debian testing with Plasma. Bernhard, Pekka: The following might help to narrow down the issue: 1) Are you running your Plasma session under X11 or Wayland? 2) Does the issue also occur when you directly run (adapt path as needed) e.g. SAL_USE_VCLPLUGIN=qt5 soffice.bin --writer i.e. you call 'soffice.bin' directly rather than using the 'soffice' shell wrapper that sets several environment variables (in '${instdir}/program/ooenv') that might cause the crash (for a reason, though...)?
I'm running Plasma with X11, soffice.bin fails the same way as the wrapper. Note I'm still on 6.1 though, haven't built the 6.2 beta or git master yet (currently updating, should have news on that soon).
OK, thanks for the info. If you're building yourself, it would be helpful if you can add the '--enable-debug' configure option, since that will make it possible to get a backtrace that shows more helpful information.
6.2 beta1 fixes the issue for me. I'm having some other unrelated issues (weird font sizes with SAL_USE_VCLPLUGIN=qt5 or SAL_USE_VCLPLUGIN=kde5), but they're obviously unrelated to this issue. Will open new reports for those. Is this still reproducable with versions >= 6.2-beta1 for anyone else?
Thanks for retesting! I'll set this bug to WORKSFORME then, since the issue no longer appears now. Should the problem come back or anybody else still has it, please reopen or open a new bug report.