Bug 31860

Summary:	A 25s delay before the window raises
Product:	Mageia	Reporter:	papoteur <yvesbrungard>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	lewyssmith
Version:	Cauldron
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	isodumper-1.44-3.mga9.src.rpm	CVE:
Status comment:

Description papoteur 2023-05-02 17:23:09 CEST

Description of problem:
The second time the application is started with
isodumper --gtk
there is a delay of 25 before that the window appears.

Version-Release number of selected component (if applicable):
1.44

How reproducible:
The second launch and further

Context:
LXQt installation only

No report in journal

Comment 1 Lewis Smith 2023-05-02 21:03:40 CEST

Well, running Cauldron LxQt, and trying explicitly:
- isodumper-qt from System Tools menu
- isodumper --gtk from a terminal
both started quickly, first time and subsequently.

OTOH I have noticed recently on starting a session that applications launched first-time from taskbar icons did take extremely long to show. Everything. I think it sorted itself on re-launching them later. I am not even sure whether it was just LxQt, or other desktops (probably LXDE) as well.

I am not seeing it now, having just updated the system with very many updates, mostly to do I think with Gnome 44.

Can you confirm:
- whether it still happens with an up-to-date system
- whether it happens with other applications
- whether it happens with different dsktops.

CC: (none) => lewyssmith

Comment 2 papoteur 2023-05-02 21:41:53 CEST

Hi Lewis,
This an uptodate system in Virtualbox. I don't know if the problem was present before.
I opened the bug report more as a notebook.
I have another VM with LXQt and Plasma, and I don't reproduce the problem with it.
I didn't try another application except Firefox which starts fine.

Comment 3 Lewis Smith 2023-05-02 21:47:54 CEST

I am on real hardware.
For the system showing the problem, you will need to add more cross-checks.

Comment 4 papoteur 2023-05-24 07:57:41 CEST

A workaround has been added in 1.45, now published.
Thus closing.

Resolution: (none) => FIXED
Status: NEW => RESOLVED