Description: When Impress crashes while the document template selection window is open, the window is kept open when impress crashes. When you want to close the window with UI elements the window does not respond Steps to Reproduce: 1. Open eg. calc 2. Open Impress (do NOT close the template selection window) 3. Crash LO as described in bug 149114 ( https://bugs.documentfoundation.org/show_bug.cgi?id=149114 ) Actual Results: The window of the template selection stays open and does not respond when you want to close it. Expected Results: The window crashes/is closed when impress crashes. Reproducible: Always User Profile Reset: No Additional Info: Version: 7.3.5.2 / LibreOffice Community Build ID: 184fe81b8c8c30d8b5082578aee2fed2ea847c01 CPU threads: 16; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: de-AT (de_AT.UTF-8); UI: de-DE Flatpak Calc: threaded -------------------------------------------------------------------------------- Operating System: KDE neon 5.25 KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 Kernel Version: 5.15.0-43-generic (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 4800H with Radeon Graphics Memory: 30.8 GiB of RAM Graphics Processor: AMD RENOIR -------------------------------------------------------------------------------- Note that the crash occured on X11. Wayland is not tested yet (I will test this soon) Windows is not tested yet either (I will test this soon as well)
Created attachment 181677 [details] Impress - document template selection window-bug Steps as described in the report: 1) Open a LO application (eg. calc) 2) Open an Impress window 3) Display the Tip of the Day in the first window 4) Crash LO per bug report 149114 ( https://bugs.documentfoundation.org/show_bug.cgi?id=149114 ) -> Impress crashes and the window of the document template selection is kept open and does no longer respond to UI interactions. 2) and 3) do not have to be done in that order and can be exchanged (so: first display the tip of the day and then open a new Impress window)
Test on Wayland (same system logged in with Wayland): Same bug as on X11. The windows look as if they are unresponsive for a shorter time, but this could just be a coincidence or my false judgement. When I tried to replicate this bug on Wayland the first time it worked as you would think it should (document template selection window is closed on crash of Impress). When I tried it a few more times the bug could be reproduced every following try.
No repro with Windows Version: 7.5.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 86b2bfd34a4f07c54f03c8c8dfe48e0810834628 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL
Not repro with KDE Version: 7.3.5.2 / LibreOffice Community Build ID: 30(Build:2) CPU threads: 12; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb) Locale: pt-BR (pt_BR.UTF-8); UI: en-US Ubuntu package version: 1:7.3.5-0ubuntu0.22.04.1 Calc: threaded Let's see if anyone can test with Gtk.
no repro in LibreOffice 7.3.5 with vcl:gtk3 on Ubuntu 22.04.1 no repro in LibreOffice 7.5-alpha0 with vcl:gtk3 in KDE environment may be hardware related (AMD Ryzen 7 4800H with Radeon Graphics is the fresh hardware with unstable linux kernel support, of course I only assume)
Not reproduced. BDF: do you still see this with 7.5? One way to try is using an appimage https://www.libreoffice.org/download/appimage/ Arch Linux 64-bit, X11 Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 173ba4dedd16785506a635949fe6aef3424a3b64 CPU threads: 8; OS: Linux 6.1; UI render: default; VCL: gtk3 Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded Built on 28 February 2023
I just saw your comment and I will re test it as soon as possible
[Automated Action] NeedInfo-To-Unconfirmed
I have tested around with my system and I am no longer able to reproduce the bug. Since even I can no longer reproduce the bug, I closing the report. When the bug reappears I'll reopen it (or should I create a new one?).
(In reply to BDF from comment #9) > I have tested around with my system and I am no longer able to reproduce the > bug. > > Since even I can no longer reproduce the bug, I closing the report. When the > bug reappears I'll reopen it (or should I create a new one?). If the exact same problem reappears, change back to unconfirmed.