Bug 508479 - No help pages are shown with Qt 6.10.0 beta 2
Summary: No help pages are shown with Qt 6.10.0 beta 2
Status: RESOLVED UPSTREAM
Alias: None
Product: khelpcenter
Classification: Applications
Component: general (other bugs)
Version First Reported In: 6.0.25080
Platform: Arch Linux Linux
: NOR major
Target Milestone: ---
Assignee: Documentation Editorial Team
URL:
Keywords:
: 509035 509357 509365 (view as bug list)
Depends on:
Blocks:
 
Reported: 2025-08-19 15:11 UTC by Paul Worrall
Modified: 2025-09-11 05:39 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Screenshot with Qt 6.10.0 beta 2 (82.56 KB, image/png)
2025-08-19 15:11 UTC, Paul Worrall
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Worrall 2025-08-19 15:11:22 UTC
Created attachment 184264 [details]
Screenshot with Qt 6.10.0 beta 2

SUMMARY
With Qt 6.10.0 beta 2 installed, all help pages are blank (screenshot attached).  After downgrading to 6.9.1, all is OK

So this seems like a regression in Qt.  I'm reporting it here so that someone with sufficient knowledge (i.e. not me) can confirm that and identify the existing Qt bug, or raise a useful new one.
Comment 1 Albert Astals Cid 2025-08-20 16:31:58 UTC
How did you get those qt and khelpcenter packages? Was khelpcenter rebuilt with new Qt? (not sure if it's needed but may be worth checking)
Comment 2 David C. Bryant 2025-08-20 18:04:49 UTC
I'm seeing a related problem. On my Gentoo Linux system (Qt 6.9.1, Frameworks 6.16.0, Plasma 6.3.6, most apps 25.04.3) the local "Help" files were not being accessed via the "help" menu. Instead, I was referred to the internet (Firefox). After digging into this, I found that khelpcenter was no longer installed on my sytem. It used to be there, but now it's gone. When I reinstalled khelpcenter, the local docbook files started coming up from the help menus again. Maybe something similar is happening with other distros.

I'll dig into my installation logs and see if I can figure out when khelpcenter was dropped.
Comment 3 Paul Worrall 2025-08-21 07:39:18 UTC
(In reply to Albert Astals Cid from comment #1)

Qt 6.10.0 is from the Arch "kde-unstable" repository and khelpcenter is built against Qt 6.9.1

Help Centre: 6.0.25080
KDE Frameworks: 6.17.0
Qt: Using 6.10.0 and built against 6.9.1
Arch Linux (Wayland)
Build ABI: x86_64-little_endian-lp64
Kernel: linux 6.16.1-arch1-1

(In reply to David C. Bryant from comment #2)
No, I don't think it's that, when I revert to Qt 6.9.1 it loads the local docbook files OK
Comment 4 Albert Astals Cid 2025-08-23 09:04:21 UTC
Do you get any special warning when run from the command line?
Comment 5 Paul Worrall 2025-08-23 12:46:48 UTC
(In reply to Albert Astals Cid from comment #4)

❯ khelpcenter 
rr600 device_uuid output is based on invalid pci bus info.
 View::langLookup "kdoctools6-common/kde-default.css"
 View::langLookup "khelpcenter/glossary/index.docbook"
Backend texture is not a Vulkan texture.
Compositor returned null texture

The last two lines get repeated many times when I resize the window
Comment 6 Paul Worrall 2025-08-23 12:50:43 UTC
I also noticed just now that if I drag the mouse across the white area where the help page should be, the "Copy" button activates.

If I then press Copy, and then do edit - paste in Kate, I get the text of the help document. So it's as if the help page is there but being rendered white - on - white
Comment 7 Antonio Rojas 2025-08-23 12:52:15 UTC
Is webengine working at all in other applications?
Comment 8 Paul Worrall 2025-08-23 13:21:28 UTC
(In reply to Antonio Rojas from comment #7)
I'm not 100% sure which apps use qtwebengine, but trying some at random:

1. The preview pane in Klevernotes seems to misbehave similarly
2. The viewer pane in Akregator also has the problem

... so I guess the answer is no, webengine isn't working
Comment 9 Paul Worrall 2025-08-23 13:38:33 UTC
It renders the help pages OK if I do:

> QTWEBENGINE_CHROMIUM_FLAGS="--disable-gpu" khelpcenter

(I got that idea from https://bugreports.qt.io/browse/QTBUG-138131, but that's raised against Qt 6.9.1 so not the same bug)
Comment 10 Paul Worrall 2025-08-23 13:47:17 UTC
I'm using an AMD GPU:

Operating System: Arch Linux 
KDE Plasma Version: 6.4.4
KDE Frameworks Version: 6.17.0
Qt Version: 6.10.0
Kernel Version: 6.16.2-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 2 × AMD A6-6400K APU with Radeon(tm) HD Graphics
Memory: 8 GiB of RAM (7.7 GiB usable)
Graphics Processor: AMD CEDAR
Comment 11 Albert Astals Cid 2025-08-23 14:37:48 UTC
If you create a file named main.qml with this contents


import QtWebEngine

WebEngineView {
    url: "https://kde.org"
}


and then on the console you run

qml6 main.qml

does it show something?

If not webengine is broken and there's nothing we can do, you should update to beta3 and if it still fails report a bug upstream Qt. Also maybe instead of trying the arch packages try the ones from the Qt installer in case it's a Arch miscompilation.
Comment 12 Paul Worrall 2025-08-23 17:10:37 UTC
(In reply to Albert Astals Cid from comment #11)

Thanks for your help.  
That script shows only a blank white window, so I'll raise a Qt bug if it's still present with beta 3

Closing this bug now, I'll update it with the Qt bug reference when I've raised it.
Comment 13 Paul Worrall 2025-08-24 07:22:42 UTC
... well, beta 3 arrived and plasma wouldn't launch at all.  Going back to 6.9.1 for now.
Comment 14 Antonio Rojas 2025-08-24 08:33:40 UTC
(In reply to Paul Worrall from comment #13)
> ... well, beta 3 arrived and plasma wouldn't launch at all.  Going back to
> 6.9.1 for now.

This is caused by an ABI break in beta 3, should be fixed now in kde-unstable. As for the webengine issue, it is triggered by the mesa 25.2 update - downgrading to 25.1 fixes it.
Comment 15 Paul Worrall 2025-08-24 08:53:50 UTC
(In reply to Antonio Rojas from comment #14)
Thank you Antonio, I'm now on Qt 6.10.0 beta 3 with mesa 25.1.7 and all seems good :-)
Comment 16 Antonio Rojas 2025-08-24 12:19:29 UTC
Reported to https://bugreports.qt.io/browse/QTBUG-139424
Comment 17 Antonio Rojas 2025-09-10 12:09:20 UTC
*** Bug 509035 has been marked as a duplicate of this bug. ***
Comment 18 Antonio Rojas 2025-09-10 19:58:53 UTC
*** Bug 509357 has been marked as a duplicate of this bug. ***
Comment 19 Antonio Rojas 2025-09-11 05:39:12 UTC
*** Bug 509365 has been marked as a duplicate of this bug. ***