Bug 463481

Summary: info: some links within info files not followed correctly
Product: [Frameworks and Libraries] kio-extras Reporter: Christopher Yeleighton <giecrilj>
Component: defaultAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED UPSTREAM    
Severity: normal CC: luigi.toscano, p.r.worrall
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
URL: info:/coreutils/Floating%20point
See Also: https://sourceforge.net/p/info2html/bugs/6
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Christopher Yeleighton 2022-12-26 11:52:57 UTC 
SUMMARY
A hyperlink placed on the info page "COREUTILS: Floating point" gets interpreted as an internal link.


STEPS TO REPRODUCE
1. Follow the hyperlink "(libc)Parsing of Floats".

OBSERVED RESULT
Error
 The Info node (libc)parsing of floats in Info file /usr/share/info/coreutils.info.gz does not exist.

EXPECTED RESULT
LIBC: Parsing of Floats

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: openSUSE Tumbleweed 20221224
(available in About System)
KDE Plasma Version: 5.26.4
KDE Frameworks Version: 5.101.0
Qt Version: 5.15.7

ADDITIONAL INFORMATION
Comment 1 Luigi Toscano 2022-12-26 17:11:05 UTC 
As asked on IRC, does it work with the 'info' tool? I see an error when trying to click that link:

"Cannot find node 'Parsing of Floats'"

So it may be an invalid document.
Comment 2 Paul Worrall 2022-12-27 10:09:03 UTC 
You need to have the glibc info documentation installed (glibc-doc on Ubuntu-based systems, glibc-info on openSUSE).  

Given that, the link can be followed using the stand-alone Gnu Info reader, but still not using the KDE Help Centre.  I therefore think this bug is valid, and should be assigned to kio-extras product which handles the parsing of info files.

The bug can be reproduced by:

         kioclient5 exec 'info:/coreutils/(libc)Parsing of Floats'

Whereas:

         kioclient5 exec 'info:/libc/Parsing of Floats'

works OK.
Comment 3 Paul Worrall 2022-12-27 12:18:58 UTC 
The bug is also present in the upstream info2html.  Created a bug report there:

https://sourceforge.net/p/info2html/bugs/6/