Bug 506481

Summary:	"Gathering crash information failed..." bar completely breaks the layout
Product:	[Applications] drkonqi	Reporter:	Riccardo Robecchi <sephiroth_pk>
Component:	general	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	REPORTED ---
Severity:	minor	CC:	kdedev, nate, sitter
Priority:	NOR
Version First Reported In:	6.4.0
Target Milestone:	---
Platform:	Neon
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	Screenshot of the issue

Description Riccardo Robecchi 2025-07-02 10:45:44 UTC

Created attachment 182860 [details]
Screenshot of the issue

SUMMARY
Whenever there is an issue with drkonqi that makes it stop for unknown reasons (see bug 504388), the bar completely breaks the layout of the window. See screenshot for reference.

STEPS TO REPRODUCE
1. Have drkonqi display the "Gather crash information failed..." message display

OBSERVED RESULT
The layout is broken: the rest of the window is displayed with a huge space under the bar; it reverts to normal once you resize the window.

EXPECTED RESULT
The layout is not impacted and does not require a window resize to be shown correctly.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE Neon
KDE Plasma Version: 6.4.0
KDE Frameworks Version: 6.15.0
Qt Version: 6.9.0

ADDITIONAL INFORMATION

Comment 1 Harald Sitter 2025-07-02 13:27:10 UTC

Can't reproduce on git master. I doubt we'll be able to get to the bottom of this without a way to reproduce :(

Comment 2 Nate Graham 2025-09-17 02:32:44 UTC

Also can't reproduce on git master while drbugging and fixing other layour issues.

This kind of resize-based issue is usually caused by a binding loop or a Qt bug. Can you by any chance reproduce it with Qt 6.9.2 or later

Comment 3 Riccardo Robecchi 2025-09-17 09:24:46 UTC

Yes, it is reproducible with Qt 6.9.2.

Comment 4 Nate Graham 2025-09-17 14:21:54 UTC

Is this 100% reproducible, every time you see that bar? Or does it only sometimes happen?

Comment 5 Riccardo Robecchi 2025-09-17 14:25:51 UTC

It is 100% reproducible.

Comment 6 Nate Graham 2025-09-17 14:27:50 UTC

That's really weird; for me it's 0% reproducible. :(

Are you using any non-default fonts, styles, etc that could help to explain this?