I've recently switched over to flatpak applications and after an update via Discover neon booted to a black screen. The error was along the lines of "org.freedesktop.Platform.ffmpeg-full/x86_64/22.08 not installed" and "Aborted due to failure (Error pulling from repo: While pulling runtime/org.freedesktop.Sdk/x86_64/22.08 from remote flathub:". Luckily I had a backup image so I could recover. If I manually added the flatpak using "flatpak install org.freedesktop.Platform.ffmpeg-full/x86_64/22.08" and "flatpak install org.freedesktop.Sdk/x86_64/22.08" prior to restarting it seems to fix the issue. If Dolphin can show an error about the missing flatpak files it should also prompt the user to install, or at least warn them if they don't install it can cause instability. Currently if a user has flatpaks installed a simple update can lead to a blank screen after boot which is catastrophic for most users. SOFTWARE/OS VERSIONS Operating System: KDE neon 6.0 KDE Plasma Version: 6.1.3 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 Kernel Version: 6.5.0-45-generic (64-bit) Graphics Platform: X11
Please provide STEPS TO REPRODUCE
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.
(In reply to Harald Sitter from comment #1) > Please provide > > STEPS TO REPRODUCE It's really not possible for me to do that as the error doesn't tell me which program it's complaining about. I'm not sure what's happening or what is causing it, but it is an issue. My point was "If Dolphin can show an error about the missing flatpak files it should also prompt the user to install", essentially that would be a way of fixing the issue without having to track down the exact program that is responsible.