Bug 480453

Summary: Okular became the default for opening text and image files
Product: [KDE Neon] neon Reporter: John <ilikefoss>
Component: Packages Testing EditionAssignee: Neon Bugs <neon-bugs-null>
Status: RESOLVED FIXED    
Severity: minor CC: carlosd.kde, jr, neon-bugs-null, sitter
Priority: NOR Keywords: qt6
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Neon   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description John 2024-01-28 18:21:10 UTC 
SUMMARY
Okular became the default for opening text and image files


STEPS TO REPRODUCE
1. Install KDE Neon testing edition
2. Use it normally for a day or two
3. Create a few new files, like .txt and .png (screenshots)
4. Install updates

OBSERVED RESULT
At some point Okular becomes the default when trying to open the previously created txt and png files.
Maybe it's related to one of the updates


EXPECTED RESULT
Okular should not become by itself the default app for opening text and image files as there are better apps for that, which I prefer, like Kate and Gwenview.
It should become the default only if I made it that way.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma:
KDE Plasma Version: 5.92.90
KDE Frameworks Version: 5.249.0
Qt Version: 6.6.1

ADDITIONAL INFORMATION
KDE Neon fully updated, showing Plasma 6.0 RC1
Using the Wayland session
Kernel Version: 6.5.0-15-generic (64-bit)
CPU: Intel Core i5-8250U
GPU: Integrated UHD 620
--------------------------------------------
Not sure how reproducible this is and why it was not a problem immediately after I installed KDE Neon
Maybe one of the updates triggered this behavior.
Comment 1 Carlos De Maine 2025-09-21 04:57:35 UTC 
Thank you for your bug report! 
However this bug report was created/provided previous to 01/06/2024 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!
Comment 2 John 2025-10-30 20:21:42 UTC 
I haven't seen this problem again on the latest releases, so I guess it was something only temporary or has been fixed by someone.
I'll close it myself.