Arch Linux User Repository

@tatokis done! Thanks again for your help and patience, I truly appreciate it!

@dilapitatedstone Great! That tells us that the issue isn't related to graphics drivers (or nvidia). Please do me a favour and open an issue on GitHub and we can continue there. The AUR comments aren't really meant for debugging software.

@BS86 That isn't the case :) the latter (19.1.7) was just be copy pasting from Tatokis' post to relay that that was NOT showing up for me. Thanks!

@dilapitatedstone you clearly are in a partial update situation that breaks stuff for you, from your two posts:

"llvmpipe (LLVM 20.1.8, 256 bits)"

"llvmpipe (LLVM 19.1.7, 256 bits"

you need to update all packages or rebuild AUR packages against the new llvm/clang

@tatokis So, that did create some change! But only in the logs. It still won't render.

Limiting MSAA to 0 because of "Mesa" "llvmpipe (LLVM 20.1.8, 256 bits)"
ckb-next 0.6.2-48-g55ea82e0
Using "Mesa" "llvmpipe (LLVM 20.1.8, 256 bits)"
Path to settings: "/home/mossy/.config/ckb-next/ckb-next.conf"
service is "org.kde.StatusNotifierItem-70682-1"
Registering a client interface to the KStatusNotifierWatcher
Scanning "/usr/lib/ckb-next-animations/gradient"
Scanning "/usr/lib/ckb-next-animations/heat"
Scanning "/usr/lib/ckb-next-animations/invaders"
Scanning "/usr/lib/ckb-next-animations/life"
Scanning "/usr/lib/ckb-next-animations/mviz"
Scanning "/usr/lib/ckb-next-animations/pinwheel"
Scanning "/usr/lib/ckb-next-animations/pipe"
Scanning "/usr/lib/ckb-next-animations/rain"
Scanning "/usr/lib/ckb-next-animations/random"
Scanning "/usr/lib/ckb-next-animations/ripple"
Scanning "/usr/lib/ckb-next-animations/snake"
Scanning "/usr/lib/ckb-next-animations/wave"
QOpenGLContext::makeCurrent() called with non-opengl surface 0x55c4e81e6f60
QRhiGles2: Failed to make context current. Expect bad things to happen.
Failed to create QRhi for QBackingStoreRhiSupport
QOpenGLContext::makeCurrent() called with non-opengl surface 0x55c4e81e7240
QRhiGles2: Failed to make context current. Expect bad things to happen.
Failed to create QRhi for QBackingStoreRhiSupport
Starting "/usr/lib/ckb-next-animations/gradient"
Creating PulseAudio context
QOpenGLWidget: No fbo, cannot render
QOpenGLWidget: No fbo, cannot render
QOpenGLWidget: No fbo, cannot render

The last 3 lines are after I poked and prodded at the tray icon; as before, they print infinitely.

@dilapitatedstone

I just remembered you're on Wayland, so it's not going to be using GLX, but EGL. How about __EGL_VENDOR_LIBRARY_FILENAMES=/usr/share/glvnd/egl_vendor.d/50_mesa.json LIBGL_ALWAYS_SOFTWARE=1 ckb-next

@tatokis

Thank you for trying, though! I do appreciate it. And yes, I definitely copied the two underscores. The new command string you provided also yields the same results, with the same errors printed on launch and the same looping error when i click the tray icon. No Using "Mesa" "llvmpipe (LLVM 19.1.7, 256 bits)" still just Nvidia.

Could it be because I'm missing some unknown dependency? I do have mesa installed. Arch Wiki says that when MESA_LOADER_DRIVER_OVERRIDE is used, mesa checks in /lib/dri/ by default, and then if it doesn't find it, it falls back to llvmpipe. Not quite sure where llvmpipe itself is supposed to be, because it's not in my /lib/dri/...

@TheBill2001 Both WITH_GUI and PREFER_QT6 are true by default, so there is no need for that change. If anything, Wayland libraries need to be added to this PKGBUILD as dependencies.

@dilapitatedstone The GPG error is likely unrelated. As for the broken graphics, I don't know how to reproduce the issue, or what is causing it... The idea behind those environment variables was to try to use a software renderer (llvmpipe) to see if the issue happens with that too. Had it worked, you'd have seen

ckb-next 0.6.2-40-gb2fa170
Using "Mesa" "llvmpipe (LLVM 19.1.7, 256 bits)"

You did copy the two underscores from the start, right? It is __GLX_VENDOR_LIBRARY_NAME, not GLX_VENDOR_LIBRARY_NAME.

I suspect the issue is a combination of newer Qt and nvidia, but I can't really debug it... I'm throwing stuff at the wall at this point, but does this change anything?

MESA_LOADER_DRIVER_OVERRIDE=llvmpipe GALLIUM_DRIVER=llvmpipe __GLX_VENDOR_LIBRARY_NAME=mesa LIBGL_ALWAYS_SOFTWARE=1 ckb-next

You can add the following build option to CMake to force build Wayland support and get Turn off light when idle working on any Wayland compositor that support ext-idle-notify-v1 protocol. Also requires Qt 6.

-DUSE_WAYLAND=1 -DWITH_GUI=1 -DPREFER_QT6=1

Here is the diff:

diff --git a/PKGBUILD b/PKGBUILD
index 8c920e0..d570241 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -3,7 +3,7 @@
 # Contributor: Light2Yellow <oleksii.vilchanskyi@gmail.com>

 pkgname=ckb-next-git
-pkgver=0.6.2.r16.gb1075bc1
+pkgver=0.6.2.r48.g55ea82e0
 pkgrel=1
 epoch=1
 pkgdesc="Corsair Keyboard and Mouse Input Driver, git master branch"
@@ -38,7 +38,8 @@ build() {
     -DCMAKE_INSTALL_LIBEXECDIR="lib"              \
     -DDISABLE_UPDATER=1                           \
     -DUDEV_RULE_DIRECTORY="/usr/lib/udev/rules.d" \
-    -DFORCE_INIT_SYSTEM="systemd"
+    -DFORCE_INIT_SYSTEM="systemd"                 \
+    -DUSE_WAYLAND=1 -DWITH_GUI=1 -DPREFER_QT6=1
   cmake --build build --target all
 }

Hi, one more update. After today's update I decided to mess with it some more, and turns out that while right click -> restore doesn't print anything to the log, just clicking on the tray icon does:

QOpenGLWidget: No fbo, cannot render

printed infinitely