Yep, it's normal. Flatpak is usually installing it's own dependencies, even if you already have those packages in your system. And yes, I think I've seen Flatpak installing it's own graphical drivers (or, say, it's own Wine) before.

Not a big expert on Flatpak, but I think they are doing it to maintain their "Consistent environment for each application" and "Full control over dependencies" they are proud for. Like, Flatpak developer should have everything, including even drivers, under his control. And yes, from what I understand, you can have more than one flatpaked GPU driver at the same time, but each one should be sandboxed and isolated, and only (normally?) accessible from one isolated Flatpak application.

How the system can even use different GPU drivers for different programs at the same time? That's where I'm confused also. IDK, but I guess it can do it somehow... :).

Thanks. That reduces my concerns a good deal.

How the system can even use different GPU drivers for different programs at the same time? That's where I'm confused also. IDK, but I guess it can do it somehow... :).

The userspace part of the driver is a library loaded each time for each Vulkan/OpenGL application. So it's not one driver process handling everything on the system.

How the system can even use different GPU drivers for different programs at the same time? That's where I'm confused also. IDK, but I guess it can do it somehow... :).

The userspace part of the driver is a library loaded each time for each Vulkan/OpenGL application. So it's not one driver process handling everything on the system.

Aha. Thanks for clarification.