Open Writer new document Open Sidebar in Navigator. Click Styles deck. Crash Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 7379decd74f9f66011f0023d8903430293dc0532 CPU threads: 16; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded Mentioned in 156978 but different one.
Confirm with in Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: cf1cdc00e1e2d2684cfe57ac002a37c5f3d100c5 CPU threads: 16; OS: Linux 6.2; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded
commit 6fd755fb36472938757b2581cbe99f5e5fe1ae40 [log] author Noel Grandin <noel.grandin@collabora.co.uk> Tue Aug 22 14:44:38 2023 tdf#100894 lots of Conditional formatting freeze calc Styles sidebar cc Noel please see
Created attachment 189273 [details] bt On pc Debian x86-64 with master sources updated today + gtk3 rendering, I got an assertion.
This was working with an older version of gtk, but now it crashes on my machine too, deep inside gtk -> glib -> cairo The assert that triggers seems to indicate that something is double-releasing a cairo surface, which means we might be tickling a gtk bug. Caolan, any ideas?
I don't know if there is a v. quick fix. I think I suggested using set_text and some explicit column number in the first place to avoid a vcl edge case, but what I think is happening here is that the gtk treeviews, for the other edge case of a custom rendering preview, have a pixmap/cairo-surface at the expected index so the two edge cases show a bit of contradictory poor implementation by me there. I probably need to do something like remove the pixmap/cairo-surface for custom rendering out of the .ui file, so the column mapping stuff we do works as it normally does for these treeviews in gtk, and bung it at the end at run-time (or something of that nature) when togged into the custom-render more. Might be easiest to revert for now and if I get a chance then sort it out with a bit of thought.
Caolan, can you please revert? This makes master unusable for testing in GTK, and switching to other is tedious. Also, later bibisects will be trubled.
It was reverted as far as I know with https://cgit.freedesktop.org/libreoffice/core/commit/?id=ff66803ec9ec26c918ef652a1478ff9d7da0c97b leaving this as a to-do in order to get it reapplied
Thanks, I did not look, somehow expected a notification here. OK now.
Dear Timur, 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 https://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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug