You are not logged in.
Hello!
In Discover on KDE I keep seeing an update for org.freedesktop.Platform.GL.nvidia from flatpak, and I am not sure what this is for. I installed the nvidia-dkms package from extra and I thought I am using that, but I ran flatpak list --runtime and it shows like the flatpak is used? Can I safely remove the flatpak?
EDIT: same with mesa. I also have installed the normal mesa from our repos (though this one probably came in as a dependency for something else)
Last edited by andrei1015 (2024-04-26 13:58:00)
I'm just happy to be here!
Offline
The flatpak might be a dependency for some other flatpak - I doubt that it has any relevance for your display server or anything else from the repos. Let alone the kernel.
You could remove that and see whether and which flatpak breaks - even in the (implausible) worst case scenario you can still boot the multi-user.target (2nd link below) "nomodeset" and re-install the flatpak from there.
Offline
Will try but shouldn't arch-chroot also be a solution?
Thank you for your answer!
I'm just happy to be here!
Offline
Will try but shouldn't arch-chroot also be a solution?
Thank you for your answer!
Using a live boot disk, then mounting your system and then chroot'ing into it would probably take longer than to just start your system it up with no graphics driver and a shell
Offline
A flatpak application only uses libraries that are part of a flatpak runtime or a platform extension like GL.nvidia. It will never use system libraries like libGL or libEG. If you have a flatpak application that uses GL, then you need those flatpaks.
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |
Online
Using a live boot disk, then mounting your system and then chroot'ing into it would probably take longer than to just start your system it up with no graphics driver and a shell
Oh yes for sure, but I have done that in the past and I know how to do it, and changing kernel parameters still scares me!
A flatpak application only uses libraries that are part of a flatpak runtime or a platform extension like GL.nvidia. It will never use system libraries like libGL or libEG. If you have a flatpak application that uses GL, then you need those flatpaks.
makes sense to me! Thank you!
Last edited by andrei1015 (2024-04-26 13:57:46)
I'm just happy to be here!
Offline
Actually got to the bottom of this. All these multiple flatpaks were gone when I removed the Discord flatpak.
And I just wanted to express a bit of frustration about the platform that's supposed to not have dependencies, have dependencies.
I moved to the Extra package, not entirely sure why I even did the flatpak to begin with...
I'm just happy to be here!
Offline
Because you hadn't read any of
https://web.archive.org/web/20230525163 … rs-matter/
https://flatkill.org/2020/
https://ludocode.com/blog/flatpak-is-not-the-future
Those container systems are an elaborate way to bundle *some* depedencies in a secondary, very bloated package management system that often almost, but not really, runs a second OS layer (still often depending on and therefore making assumptions about the underlying system) …
I'd personally rather take the beenfits of an actual VM over this mess if you cannot integrate the software otherwise.
Offline