Bug 2252806 - LibreOffice Impress launches with main window active, but template selection window blocking it - keyboard navigation is difficult
Summary: LibreOffice Impress launches with main window active, but template selection ...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: kwin
Version: 40
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Rex Dieter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: openqa
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-12-04 19:12 UTC by Adam Williamson
Modified: 2025-05-16 22:59 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-05-16 07:48:21 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Adam Williamson 2023-12-04 19:12:10 UTC
Since Plasma 6 landed, there's a problem with LibreOffice Impress' state on startup. When it starts up, it shows a "Select a Template" window, which blocks interaction with the main window. However, almost always, the main window - not the "Select a Template" window - is active (this may be a timing thing; it's been causing the openQA test to fail consistently, testing locally, about 4 out of 5 times, it loads this way. The other time, the Select a Template window is active and things work as expected).

Unless you hit 'alt-tab' to activate the Select a Template window, this blocks some keyboard interaction - I think keypresses are being sent to the main window, but the Select a Template window is blocking interaction with it, so they do nothing. Tab does nothing, enter does nothing, alt-f4 does nothing (though hitting Esc does close the window). Hitting random letter keys seems to affect the category drop-down, but I can't find any way to actually cycle through the templates and select one, for instance.

I think the Select a Template window should always be active at startup (when it's configured to be shown at all).

Comment 1 Neal Gompa 2023-12-08 16:32:15 UTC
I'm not sure who this bug actually belongs to, but if it belongs with kwin, can this be reported upstream?

Comment 2 Aoife Moloney 2024-02-15 23:06:51 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 40 development cycle.
Changing version to 40.

Comment 3 Aoife Moloney 2025-04-25 10:11:51 UTC
This message is a reminder that Fedora Linux 40 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 40 on 2025-05-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '40'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 40 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 4 Aoife Moloney 2025-05-16 07:48:21 UTC
Fedora Linux 40 entered end-of-life (EOL) status on 2025-05-13.

Fedora Linux 40 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 5 Adam Williamson 2025-05-16 22:59:05 UTC
It looks like, for whatever reason, this isn't an issue lately. The openQA test isn't failing and I didn't reproduce it in a few tries with a current Rawhide KDE live.


Note You need to log in before you can comment on or make changes to this bug.