Package Details: ckb-next-git 1:0.6.2.r16.gb1075bc1-1

Git Clone URL: https://aur.archlinux.org/ckb-next-git.git (read-only, click to copy)
Package Base: ckb-next-git
Description: Corsair Keyboard and Mouse Input Driver, git master branch
Upstream URL: https://github.com/ckb-next/ckb-next
Licenses: GPL2
Conflicts: ckb-git, ckb-git-latest, ckb-next
Provides: ckb-next
Submitter: tatokis
Maintainer: tatokis (steinex)
Last Packager: tatokis
Votes: 18
Popularity: 0.46
First Submitted: 2018-12-29 16:32 (UTC)
Last Updated: 2025-05-22 13:58 (UTC)

Latest Comments

1 2 3 4 Next › Last »

dilapitatedstone commented on 2025-07-06 16:49 (UTC)

Hi, thanks for your reply! I wouldn't be surprised if nvidia ends up being at fault. However, running QT_QPA_PLATFORM=xcb ckb-next yields exactly the same results & output Obviously the numbers numbers denoting org.kde.StatusNotifierItem are different, as are the non-opengl surface numbers, but everything else is identical.

tatokis commented on 2025-07-06 07:57 (UTC)

This sounds like it might be an issue with the nvidia driver. What happens if you run it under xwayland? QT_QPA_PLATFORM=xcb ckb-next

dilapitatedstone commented on 2025-07-03 12:20 (UTC)

Hey hey. Starting a little over a month ago, I can no longer pull up the GUI. I am using Hyprland, and have ckb-next set to launch automatically, but even when quitting and launching manually, the GUI won't come up. Right clicking the tray icon and clicking 'Restore' doesn't do anything.

It DOES successfully apply the custom animation I'd previously created, though. Here is the output when launching from terminal:

ckb-next 0.6.2-40-gb2fa1708
Using "NVIDIA Corporation" "NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2"
Path to settings: "/home/[user]/.config/ckb-next/ckb-next.conf"
service is "org.kde.StatusNotifierItem-3962-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 0x55b197339c90
QRhiGles2: Failed to make context current. Expect bad things to happen.
Failed to create QRhi for QBackingStoreRhiSupport
QOpenGLContext::makeCurrent() called with non-opengl surface 0x55b197339f70
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

I'm guessing it has something to do with the openGL errors? But I'm not really sure what to make of them. Thank you for taking the time to read this, and, hopefully reply!

tatokis commented on 2025-05-22 17:24 (UTC)

@BS86 Thank you for testing, I appreciate it.

I'll switch the release package soon to Qt6 as well if no issues arise.

BS86 commented on 2025-05-22 16:11 (UTC)

@tatokis Thanks for the Qt6 Update - didn't see any issues so far after 1,5 hours of trying to break things while using a K100 and a Nightsword

jcrowell commented on 2025-04-01 06:05 (UTC) (edited on 2025-04-01 06:06 (UTC) by jcrowell)

@BS86 The package maintainer is the lead developer I think, so they just haven't gotten around to updating the packages yet.

BS86 commented on 2025-02-10 09:58 (UTC) (edited on 2025-02-10 09:58 (UTC) by BS86)

in the github repo I can see commits that ported this project to Qt6 - are the Dependencies still correct?

albert-softie commented on 2024-03-12 23:34 (UTC)

@tatokis figured it out after running which pkg-config, it was my homebrew installation that was messing it up. i ended up uninstalling homebrew since i don't think i was using it anyways and now it builds no problem. thank you for pointing me in the right direction

tatokis commented on 2024-03-12 19:40 (UTC)

@albert-softie it's okay for PKG_CONFIG_PATH to be unset. Make sure you're not running a third party pkg-config, (perhaps which pkg-config will tell you) and also check if /usr/lib/pkgconfig/xcb-ewmh.pc exists on your system and isn't a blank file.

albert-softie commented on 2024-03-12 18:53 (UTC)

@tatokis first command returns nothing, the second tells me it can't find the package in the pkg config path, probably because it's not set. i should probably do something about that shouldn't i

1 2 3 4 Next › Last »