Bug 431274

Summary: Client KIO Error in opening help files for LibreOffice in Firefox
Product: [KDE Neon] neon Reporter: Valter Mura <valtermura>
Component: Packages Testing EditionAssignee: Neon Bugs <neon-bugs-null>
Status: RESOLVED WAITINGFORINFO    
Severity: normal CC: jr, kdelibs-bugs-null, nate, neon-bugs-null, sitter
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Neon   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Valter Mura 2021-01-07 19:09:51 UTC 
SUMMARY

Cannot open the help guide in LibreOffice, the system returns to me an error.

STEPS TO REPRODUCE
1. Open LibreOffice
2. Go to "Help > LibreOffice Help Guide"
3. Try to open it

OBSERVED RESULT
A warning window opens with warning:

"Unknown Error Code: 100
Could not find the program «/usr/bin/_neon.firefox»
Send a detailed bug report to https://bugs.kde.org."

EXPECTED RESULT
The help should open without problems.

SOFTWARE/OS VERSIONS
Operating System: KDE neon Testing Edition
KDE Plasma Version: 5.20.5
KDE Frameworks Version: 5.78.0
Qt Version: 5.15.2
Kernel Version: 5.4.0-58-generic
OS Type: 64-bit

LibreOffice version
Versione: 6.4.6.2
Build ID: 1:6.4.6-0ubuntu0.20.04.1
Thread CPU: 8; SO: Linux 5.4; Resa interfaccia: predefinito; VCL: kf5; 
Versione locale: it-IT (it_IT.UTF-8); Lingua interfaccia: it-IT
Calc: threaded

ADDITIONAL INFORMATION

"libreoffice-qt5" integration is installed
"libreoffice-kf5" integration is installed
"libreoffice-kde5" integration is installed
Comment 1 Nate Graham 2021-01-08 00:14:15 UTC 
> /usr/bin/_neon.firefox
Seems related to Neon packaging. Works for me on openSUSE Tumbleweed.
Comment 2 Carlos De Maine 2025-09-20 09:35:38 UTC 
Thank you for your bug report! 
However this bug report was created/provided previous to 01/01/2023 and also has not received any updates since  before 01/01/2025. 
Unfortunately KDE neon no longer provides updates for anything older than noble 24.04 based edition's.
Please upgrade to KDE neon noble and if you can reproduce the issue after upgrading to an active version, feel free to re-open this bug report.
Thanks for understanding!