Description: LibreOffice applications crash with error message reported on terminal: "Gdk-Message: 11:28:57.886: Error flushing display: Broken pipe" sometimes when pasting big chunks of text or images under a Wayland Session. Mostly happened with LibreOffice Impress. Good reproducibility, I've been using Impress for the past 4 days and I got at least one crash per hour (and I was not copying constantly). System Fedora 35, Gnome Wayland, Mesa, Radeon card. LibreOffice version 7.2.6.2 latest on Fedora Steps to Reproduce: 1. Gnome Wayland 2. Copy and paste for a while. 3. Crash (I got one once every hour or so or normal use). Actual Results: Crash (and loses around 5 minutes of work when recovering) Expected Results: Not crash Reproducible: Sometimes User Profile Reset: No OpenGL enabled: Yes Additional Info: Happened mostly with Impress, but likely affects the others. Fedora 35, Gnome Wayland, Mesa Radeon card.
Created attachment 179858 [details] Error message and system
I suspect "error flushing display: Broken pipe" happens when we basically hang and events accumulate and we are eventually killed off due to not processing them. It's not something I've seen on cut and paste so not easy for me to reproduce. Do you know what application you were pasting from? Maybe we are hanging on pasting from some particular source.
Thank you for your reply. It happened when pasting from Impress itself. Yesterday it too crashed later but this time was different than the others, it happened when doing multiple CTRL-Z Undos. I didn't have Impress opened in the terminal but ABRT picked the crash (for the first time) and prompted me to generate a stack trace, but I didn't know what I was doing and couldn't do it. So you say that that error gives no information about the source of the crash? I'll try later to see if I can cause the crash faster (up until now everything happened doing normal use) and see if I can get more information or clues.
(In reply to pepewow3000 from comment #3) > Thank you for your reply. > > It happened when pasting from Impress itself. Yesterday it too crashed later > but this time was different than the others, it happened when doing multiple > CTRL-Z Undos. > > I didn't have Impress opened in the terminal but ABRT picked the crash (for > the first time) and prompted me to generate a stack trace, but I didn't know > what I was doing and couldn't do it. > > So you say that that error gives no information about the source of the > crash? I'll try later to see if I can cause the crash faster (up until now > everything happened doing normal use) and see if I can get more information > or clues. Just after posting this, got a crash (after almost 3hrs of continuous use). Error this time is: Gdk-Message: 12:51:45.307: Lost connection to Wayland compositor. The only thing I did was click save and changed to another slide and it crashed. I'll do more testing as I've said in my last comment and see if I can find something. Is there any script or something that can automatically use Impress to test stability?
I've been able to reproduce the issue reasonably quickly by just opening the file and copying, pasting and moving objects constantly, as you can see in the terminal screenshot I've posted. I've also been able to reproduce on another computer, a Thinkpad W541 running Fedora 35 and Intel Mesa Wayland stack. I had troubles reproducing the issue first: I couldn't get a crash on a fresh new file on both computers and when I copied the original file that caused the crashes to the Thinkpad I couldn't get a crash either. I then realised that I didn't have the customs fonts installed that I used in my file. Immediately after installing these fonts I got a crash in about 2 minutes. So it seems that the crashes are related to customs fonts. I was using two: FiraCode Nerd Font and TempleOS Rendello's font conversion. Both OTF fonts. Not sure how to continue investigating from now on.
Created attachment 179875 [details] Reproducibility of the issue - Terminal screenshot
Created attachment 179876 [details] Same crash on my Thinkpad W541 laptop - Terminal screenshot
pepewow, can you attach the file in question for us to test in the same conditions? I tried: 1. Installing the extra fonts: - https://github.com/Trzcin/Fira-Code-Nerd/blob/master/Regular/complete/Fira%20Code%20Regular%20Nerd%20Font%20Complete.otf - https://github.com/rendello/templeos_font/blob/master/templeos_font.otf 2. Adding some text in both fonts in several slides 3. Copying, pasting, moving objects No crash in 7.2.0.4 nor in recent trunk build. (using Wayland and Gnome on Ubuntu 20.04). Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: fd69b546ad36452560cb11ccb28e78632d65f045 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Please also re-test in a recent version.
Dear pepewow3000, 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 pepewow3000, 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