Package Details: ckb-next 0.4.4-3

Git Clone URL: https://aur.archlinux.org/ckb-next.git (read-only, click to copy)
Package Base: ckb-next
Description: Corsair Keyboard and Mouse Input Driver, release version
Upstream URL: https://github.com/ckb-next/ckb-next
Licenses: GPL2
Conflicts: ckb-git, ckb-git-latest, ckb-next-git
Provides: ckb-next
Submitter: tatokis
Maintainer: tatokis (steinex)
Last Packager: tatokis
Votes: 33
Popularity: 1.44
First Submitted: 2018-12-29 16:24
Last Updated: 2021-09-21 14:59

Latest Comments

1 2 3 4 Next › Last »

G4Zz0L1 commented on 2021-10-06 20:47

It's possible to include the cmake parameters to build with mviz enabled by default?

source: https://github.com/ckb-next/ckb-next/wiki/CMake-Options#with_mvizboolon

abcalphabet commented on 2021-09-21 15:38

Yup, can confirm it works now. Thanks!

tatokis commented on 2021-09-21 15:00

@abcalphabet It should be fixed now.

abcalphabet commented on 2021-09-21 11:25

The newest version (commit 0bdce625033c590a0eab76ec1781452672c61b38) leads to the following error when making package:

CMake Error at src/gui/CMakeLists.txt:28 (add_executable):
  Target "ckb-next" links to target "QuaZip::QuaZip" but the target was not
  found.  Perhaps a find_package() call is missing for an IMPORTED target, or
  an ALIAS target is missing?

clfarron4 commented on 2021-01-04 09:51

Rebuilding ckb-next against the latest version of quazip should resolve the issue.

neutronst4r commented on 2020-12-04 16:39

Concerning the missing quazip.h library, see this github issue: https://github.com/ckb-next/ckb-next/issues/646

temporary solution: sudo ln -s /usr/lib/libquazip1-qt5.so.1.1 /usr/lib/libquazip5.so.1

lordkarl commented on 2020-12-04 11:27

The recent upgrade caused this version of ckb-next to stop working. If the daemon is active the keyboard does not work, which means you are doing every thing with the on screen keyboard and the mouse, not fun. The other version ckb-next-git does work.

I tried unloading this and recompiling but it still did not work.

Pillgar commented on 2020-11-22 02:14

Not sure if this is the right place to post this, but it appears libxkbcommon and libxkbcommon-x11 v1.0.2 causes ckb-next to crash on start up after pressing any key on the keyboard. I noticed core-dumps referencing these two packages after ckb-next tray-applet loads on startup. The keyboard is still functioning after crash, and I can reload the applet manually.

Downgrading both packages fixes the bug.

TYVM

Edit: I think it's just related to libxkbcommon-x11 v1.0.2. Upgrading libxkbcommon didn't cause any crash (just libxkbcommon-x11)

yochananmarqos commented on 2020-08-26 03:10

@tatokis: Thank you for the detailed explanation.

tatokis commented on 2020-08-25 21:31

If libpulse is not installed during build, it complains:

That is intentional, since people didn't want to pull in pulse as a dependency. If we add pulse to makedepends, then it'll be installed no matter what. I've been wondering if there's a way to add it in makedepends and make it easy for people to disable it by editing the PKGBUILD.

This does not require libappindicator-gtk2 to display the icon, libappindicator-gtk3 works fine.

It only searches for the gtk2 version of appindicator (not appindicator3) [0], and only prefers it if certain conditions are met [1] [2]. You were most likely not using appindicator in the first place. It's also why it's optional. In the end, it doesn't matter, since appindicator support was removed in git. [3]

[0] https://github.com/ckb-next/ckb-next/blob/v0.4.2/cmake/modules/FindAppindicator.cmake#L51 [1] https://github.com/ckb-next/ckb-next/blob/v0.4.2/src/gui/CMakeLists.txt#L91 [2] https://github.com/ckb-next/ckb-next/blob/v0.4.2/src/gui/mainwindow.cpp#L180-L189 [3] https://github.com/ckb-next/ckb-next/commit/4c070c5d3619416d5c7866ce29f546911ffe8faa