| Summary: | KDE help pages cannot be oppened | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Cyril Levet <cyril.levet0780> |
| Component: | RPM Packages | Assignee: | KDE maintainers <kde> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | critical | ||
| Priority: | Normal | CC: | geiger.david68210, office |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | khelpcenter-24.02.2-1.mga10.src.rpm | CVE: | |
| Status comment: | |||
|
Description
Cyril Levet
2024-05-26 09:28:29 CEST
Cannot reproduce this. I tried two applications which seemed to have built-in Help (no separate doc pkg), which worked; and two which had a separate handbook package, which I did not have; but the Help mechanism worked and said the necessary document was not to be found. I installed the doc packages, then Help worked correctly. I notice that your version of khelpcenter is not current: khelpcenter-23.04.3-1.mga9 Please update it and try again. Ever confirmed:
1 =>
0 This bug is about cauldron. And there the help function is broken as described by Cyril. Ever confirmed:
0 =>
1 Hi, it also affects kmail and akonadiconsole, the error message is identical. CC:
(none) =>
office Have you the Core/Updates_testing repo enabled? If yes, have installed new, AND NOT YET READY, Qt 6.7.1? If yes, now you have to waiting for a full KDE stack update and building against new Qt 6.7.1! I can't do more as this for now. CC:
(none) =>
geiger.david68210 (In reply to sturmvogel from comment #2) > This bug is about cauldron. And there the help function is broken as > described by Cyril. Silly me! Thanks for noting it. My comment about versions was not sensible: Cyril reported a version more recent than what I suggested. And all that time I wasted by not noticing... Cauldron is always 'at risk'. CC:
lewyssmith =>
(none) Additional info, my initial post was not clear enough. kmail and akonadiconsole will not start at all while throwing this error. QT version 6.6.2. (In reply to Lewis Smith from comment #5) > Cauldron is always 'at risk'. I know. I never use Cauldron in production, only for testing. It's not urgent to fix this bug. Should be fixed now with new Qt 6.7.1 update! Yes, it is fixed. Resolution:
(none) =>
FIXED |