Package Details: ckb-next 0.6.0-1

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: 59
Popularity: 1.99
First Submitted: 2018-12-29 16:24 (UTC)
Last Updated: 2023-06-22 21:36 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 Next › Last »

mithrial commented on 2020-08-06 09:42 (UTC)

The prepare function fails for me because it doesn't find the provided patch file (it's not copied into the source directory).

Adding the patch file to the list of sources will fix it:

source=(
    "https://github.com/ckb-next/$pkgname/archive/v$pkgver.tar.gz"
    "a9f41cd8b8f5b04c0c66c6d94f96a9725943831e.patch"
)
sha256sums=(
    '75b6908d5590c293dee8258a83d4ebe206306d3df9f867596e953ef7c6a86440'
    '33eb682dfb0b0651fcf7e922978fb09ae07f072dabe538976a3b1ecf9115120f'
)

Magotchi commented on 2020-05-21 14:00 (UTC)

The "Linking C executable" part of the build fails for me as follows:

[ 24%] Linking C executable ../../bin/ckb-next-daemon
/usr/bin/ld: CMakeFiles/ckb-next-daemon.dir/device_keyboard.c.o:(.rodata+0x0): multiple definition of `devpath'; CMakeFiles/ckb-next-daemon.dir/command.c.o:(.rodata+0x120): first defined here
/usr/bin/ld: CMakeFiles/ckb-next-daemon.dir/device_mouse.c.o:(.rodata+0x0): multiple definition of `devpath'; CMakeFiles/ckb-next-daemon.dir/command.c.o:(.rodata+0x120): first defined here
/usr/bin/ld: CMakeFiles/ckb-next-daemon.dir/devnode.c.o:(.data.rel.ro.local+0x0): multiple definition of `devpath'; CMakeFiles/ckb-next-daemon.dir/command.c.o:(.rodata+0x120): first defined here
/usr/bin/ld: CMakeFiles/ckb-next-daemon.dir/firmware.c.o:(.rodata+0x1e0): multiple definition of `devpath'; CMakeFiles/ckb-next-daemon.dir/command.c.o:(.rodata+0x120): first defined here
/usr/bin/ld: CMakeFiles/ckb-next-daemon.dir/main.c.o:(.rodata+0x8): multiple definition of `devpath'; CMakeFiles/ckb-next-daemon.dir/command.c.o:(.rodata+0x120): first defined here
/usr/bin/ld: CMakeFiles/ckb-next-daemon.dir/notify.c.o:(.rodata+0x0): multiple definition of `devpath'; CMakeFiles/ckb-next-daemon.dir/command.c.o:(.rodata+0x120): first defined here
/usr/bin/ld: CMakeFiles/ckb-next-daemon.dir/usb.c.o:(.rodata+0x40): multiple definition of `devpath'; CMakeFiles/ckb-next-daemon.dir/command.c.o:(.rodata+0x120): first defined here
/usr/bin/ld: CMakeFiles/ckb-next-daemon.dir/usb_linux.c.o:(.rodata+0xf8): multiple definition of `devpath'; CMakeFiles/ckb-next-daemon.dir/command.c.o:(.rodata+0x120): first defined here
collect2: error: ld returned 1 exit status
make[2]: *** [src/daemon/CMakeFiles/ckb-next-daemon.dir/build.make:451: bin/ckb-next-daemon] Error 1
make[1]: *** [CMakeFiles/Makefile2:374: src/daemon/CMakeFiles/ckb-next-daemon.dir/all] Error 2
make: *** [Makefile:172: all] Error 2
==> ERROR: A failure occurred in build().
    Aborting...

Tanghe commented on 2020-05-18 20:57 (UTC) (edited on 2020-05-18 20:58 (UTC) by Tanghe)

this package is broken for me i get allot of errors during the build. not as manny zhen installing from git and that install doesn't fail.

Roken commented on 2019-11-05 19:19 (UTC)

Good call. /usr/bin was owned by $USER.

Changed to root:root and all good. This seems to stem from a "minor" error some 3 -4 years ago (which I thought I'd by now fully fixed). Wonder why it only just became a problem.

Nevertheless, update now built and installed.

WorMzy commented on 2019-11-05 10:02 (UTC) 

/usr/include/wchar.h:835:2: error: #endif without #if
  835 | #endif /* wchar.h  */
      |  ^~~~~

Looks like your /usr/include/wchar.h is malformed. Check your glibc package for problems pacman -Qkk glibc

Roken commented on 2019-11-04 22:07 (UTC)

Thank you for the tip about code tags. I'm so used to [code][/code]

Anyhoo, pastebin log https://pastebin.com/R4UdCfm9

WorMzy commented on 2019-11-04 20:32 (UTC)

@Roken, three backticks before and after the output encapsulates the output in code tags (like Dr. Deaths output).

I can't reproduce your build failure in a clean chroot, and you're missing out the actual error in the output you've posted. Search back through the output for the first instance of "error:" and post everything from that point onwards (or better yet, just upload the entire output to a pastebin, see makepkg's --log flag to make getting the output easier.

Roken commented on 2019-11-04 20:02 (UTC) (edited on 2019-11-04 20:05 (UTC) by Roken)

Build failure:

make[2]: [src/gui/CMakeFiles/ckb-next.dir/build.make:266: src/gui/CMakeFiles/ckb-next.dir/colormap.cpp.o] Error 1 make[2]: Waiting for unfinished jobs.... make[2]: [src/gui/CMakeFiles/ckb-next.dir/build.make:201: src/gui/CMakeFiles/ckb-next.dir/ckbsettingswriter.cpp.o] Error 1 make[2]: [src/gui/CMakeFiles/ckb-next.dir/build.make:175: src/gui/CMakeFiles/ckb-next.dir/autorun.cpp.o] Error 1 make[2]: [src/gui/CMakeFiles/ckb-next.dir/build.make:188: src/gui/CMakeFiles/ckb-next.dir/ckbsettings.cpp.o] Error 1 make[2]: [src/gui/CMakeFiles/ckb-next.dir/build.make:214: src/gui/CMakeFiles/ckb-next.dir/ckbsystemtrayicon.cpp.o] Error 1 make[2]: [src/gui/CMakeFiles/ckb-next.dir/build.make:149: src/gui/CMakeFiles/ckb-next.dir/animscript.cpp.o] Error 1 make[2]: [src/gui/CMakeFiles/ckb-next.dir/build.make:253: src/gui/CMakeFiles/ckb-next.dir/colorbutton.cpp.o] Error 1 make[2]: [src/gui/CMakeFiles/ckb-next.dir/build.make:227: src/gui/CMakeFiles/ckb-next.dir/ckbupdater.cpp.o] Error 1 make[2]: [src/gui/CMakeFiles/ckb-next.dir/build.make:123: src/gui/CMakeFiles/ckb-next.dir/animadddialog.cpp.o] Error 1 make[2]: [src/gui/CMakeFiles/ckb-next.dir/build.make:162: src/gui/CMakeFiles/ckb-next.dir/animsettingdialog.cpp.o] Error 1 make[2]: [src/gui/CMakeFiles/ckb-next.dir/build.make:136: src/gui/CMakeFiles/ckb-next.dir/animdetailsdialog.cpp.o] Error 1 make[2]: [src/gui/CMakeFiles/ckb-next.dir/build.make:240: src/gui/CMakeFiles/ckb-next.dir/ckbupdaterwidget.cpp.o] Error 1 make[2]: [src/gui/CMakeFiles/ckb-next.dir/build.make:279: src/gui/CMakeFiles/ckb-next.dir/extrasettingswidget.cpp.o] Error 1 make[2]: [src/gui/CMakeFiles/ckb-next.dir/build.make:110: src/gui/CMakeFiles/ckb-next.dir/ckb-next_autogen/mocs_compilation.cpp.o] Error 1 make[1]: [CMakeFiles/Makefile2:829: src/gui/CMakeFiles/ckb-next.dir/all] Error 2 make: *** [Makefile:152: all] Error 2 ==> ERROR: A failure occurred in build(). Aborting... Error making: ckb-next

I have no idea re this

tatokis commented on 2019-11-04 12:11 (UTC)

@DrDeath It's normal and expected, but it should be fixed now.

DrDeath commented on 2019-10-08 14:20 (UTC) (edited on 2019-10-08 14:24 (UTC) by DrDeath)

Hello, latest update 0.4.2-1 produces an error while it seems to be installed. 


:: Processing package changes...
==> Terminating ckb-next GUI
==> Terminating ckb-next daemon
Failed to get unit file state for ckb-daemon.service: No such file or directory
(1/1) reinstalling ckb-next                                                   [################] 100%
:: Running post-transaction hooks...
(1/5) Reloading system manager configuration...
(2/5) Reloading device manager configuration...
(3/5) Arming ConditionNeedsUpdate...
(4/5) Updating icon theme caches...
(5/5) Updating the desktop file MIME type cache...

@ ckb-next.install there are references for ckb-daemon.service while checking service status and not ckb-next-daemon.service as it should be (i think).


msg_blue "Terminating ckb-next daemon"

    running="$(systemctl is-active ckb-daemon.service)"
    if [[ "$running" = "active" ]]; then
        systemctl stop ckb-daemon.service
    fi

    running="$(systemctl is-active ckb-next-daemon.service)"
    if [[ "$running" = "active" ]]; then
        systemctl stop ckb-next-daemon.service
    fi

    running="$(systemctl is-enabled ckb-daemon.service)"
    if [[ "$running" = "enabled" ]]; then
        systemctl disable ckb-daemon.service
    fi

« First ‹ Previous 1 2 3 4 5 Next › Last »