Description: Running on Kubuntu 21.10 the Libreoffice Main Programm and Writer crash on the attempt to insert a jpeg file and they crash repeatedly afterwards. Starting in secure mode and deaktivating user add-ons changed nothing for that error to happen. Ausführbare Datei: soffice PID: 14265 Signal: Aborted (6) Datum: 20.11.21 09:46:17 CET Steps to Reproduce: 1.open libreoffice writer 7.2.2.2 2.open dialogue to insert a graphic file 3.wait up to 5 seconds Actual Results: none Expected Results: I expect a working procedure to insert a picture file (e.g. jpeg). Reproducible: Always User Profile Reset: No Additional Info: Version 7.2.2.2 / Libreoffice Community Build 02b2acce88a210515b4a5.... https://git.libreoffice.org/core/+log/02b2acce88a210515b4a5bb2e46cbfb63fe97d56 CPU Threads 4 /BS: Linux 5.15 Surface: UI Render:Standard;VCL:kf5 (cairo+wayland) Theme: de-DE(de_DE.UTF8); UI:de-DE Calc: Threaded
First could you try this: https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_backtrace ? Then could you try this to know if it's specific to kfe: - open a term/console - export SAL_USE_VCLPLUGIN=gen - soffice --writer - open dialogue to insert a graphic file - wait up to 5 seconds ? Finally, would it be possible you attach a backtrace ? (see https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_backtrace)
Created attachment 176372 [details] A error dump from the Kubuntu crash tool
[Automated Action] NeedInfo-To-Unconfirmed
Cannot reproduce with a current master build on Debian testing in a Plasma Wayland session. This works fine: * start Writer * "Insert" -> "Image" * select an image Version: 7.3.0.0.alpha1+ / LibreOffice Community Build ID: 96d19777abfdf74c9776470e39ee3ec7e1b2e256 CPU threads: 12; OS: Linux 5.14; UI render: default; VCL: kf5 (cairo+wayland) Locale: en-GB (en_GB.UTF-8); UI: en-US Calc: threaded Can you try the steps that Julien suggested in comment 1 to see whether it also happens when using the gen VCL plugin? Also, can you try starting LO with environment variable QT_QPA_PLATFORM=xcb set, which will force the use of the X11 Qt platform plugin instead of the Wayland one? Alternatively, you can use a Plasma X11 instead of a Wayland session and start LibreOffice there. (Please double-check that "Help" -> "About LibreOffice" contains "VCL:kf5 (cairo+xcb)" instead of "VCL:kf5 (cairo+wayland)" then)
Dear Christian Haunert, 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
Dear Christian Haunert, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA 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 our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp