ottergauze
ottergauze
PostsComments
UBUniversal Blue
Created by ottergauze on 9/8/2024 in #🛟bazzite-help
KDE Plasma "Could not connect to display" / "Could not load the Qt platform plugin xcb"
KWin is loading correctly which is allowing me to run in a graphical environment, but plasmashell is failing to load. 
qt.qpa.xcb: could not connect to display
qt.qpa.plugin: From 6.5.0, xcb-cursor0 or libxcb-cursor0 is needed to load the Qt xcb platform plugin.
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt plugin could be initialised. Reinstalling the application may fix this problem.
qt.qpa.xcb: could not connect to display
qt.qpa.plugin: From 6.5.0, xcb-cursor0 or libxcb-cursor0 is needed to load the Qt xcb platform plugin.
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt plugin could be initialised. Reinstalling the application may fix this problem.
4 replies
UBUniversal Blue
Created by ottergauze on 8/13/2024 in #🛟bazzite-help
"Failed to get system egl display" for some Flatpak applications.
Some Flatpak applications seem to crumble when attempting to achieve GPU acceleration of some kind, such as KopiaUI and Blender. For example, when launching KopiaUI, the application seems to respond under the hood, but the UI fails to load alongside this error 
[46:0813/134003.174167:ERROR:angle_platform_impl.cc(44)] Display.cpp:1052 (initialize): ANGLE Display::initialize error 12289: Failed to get system egl display
ERR: Display.cpp:1052 (initialize): ANGLE Display::initialize error 12289: Failed to get system egl display
[46:0813/134003.174359:ERROR:gl_display.cc(515)] EGL Driver message (Critical) eglInitialize: Failed to get system egl display
[46:0813/134003.174411:ERROR:gl_display.cc(786)] eglInitialize OpenGL failed with error EGL_NOT_INITIALIZED, trying next display type
[46:0813/134003.174167:ERROR:angle_platform_impl.cc(44)] Display.cpp:1052 (initialize): ANGLE Display::initialize error 12289: Failed to get system egl display
ERR: Display.cpp:1052 (initialize): ANGLE Display::initialize error 12289: Failed to get system egl display
[46:0813/134003.174359:ERROR:gl_display.cc(515)] EGL Driver message (Critical) eglInitialize: Failed to get system egl display
[46:0813/134003.174411:ERROR:gl_display.cc(786)] eglInitialize OpenGL failed with error EGL_NOT_INITIALIZED, trying next display type
I have the appropriate Nvidia runtime flatpaks installed, I'm running under Wayland (I vaguely remember this working under X11). Additionally, I had a seemingly similar issue with Anki that was resolved by disabling "Wayland windowing system", "Fallback to X11 windowing system" and enabling "D-Bus session bus", but this solution doesn't seem to work for both Blender and KopiaUI.
7 replies
UBUniversal Blue
Created by ottergauze on 8/6/2024 in #🛟bazzite-help
TF2 sudden FPS stuttering after 15-20 minutes in-game.
I'm not sure what is causing this, but running the native build of TF2 directly through Steam, the only unusual things being using gamemode and mastercomfig (https://comfig.app, a common performance config for TF2), and the game runs seemingly perfectly up until about 15-20 minutes of gameplay where I seem to have very sudden and fleeting FPS drops, and as far as I can tell it is coinciding with whenever i give any mouse input. For prosperity the mouse is a Logitech G402. My system is in performance mode, is plugged into mains power (important seeing as it's a laptop), and doesn't have this issue with any other game from what I can see. My mouse is still at 125Hz (I know it's a gaming mouse but generally I haven't seen high polling rates have any significant benefit for me, so I thought it was best to free up my CPU from being bombarded by interrupts).
7 replies