Package Details: asusctl 6.0.10-0.1

Git Clone URL: (read-only, click to copy)
Package Base: asusctl
Description: A control daemon, CLI tools, and a collection of crates for interacting with ASUS ROG laptops
Upstream URL:
Keywords: anime asus matrix rog
Licenses: MPL-2.0
Conflicts: gnome-shell-extension-asusctl-gnome
Submitter: fabiscafe
Maintainer: fabiscafe
Last Packager: fabiscafe
Votes: 16
Popularity: 1.66
First Submitted: 2021-09-18 11:01 (UTC)
Last Updated: 2024-05-25 13:43 (UTC)

Pinned Comments

fabiscafe commented on 2023-06-13 21:53 (UTC) (edited on 2024-05-11 23:43 (UTC) by fabiscafe)

Official Setup Guide

Merge/Pull Requests / Bugreports

Known Issues

Latest Comments

1 2 3 4 5 6 Next › Last »

fabiscafe commented on 2024-05-21 07:46 (UTC)

@evilred You have to ask upstream.

pheki commented on 2024-05-14 20:54 (UTC)

On 6.0.7 a new feature for X11 was added and it looks like it's enabled by default on the Makefile:

On the README:

Discussions: - -

fabiscafe commented on 2024-05-11 23:51 (UTC)

@anonymix007 You need to add that yourself. This PKGBUILD will follow upstream as close as possible. I learned my lesson :P

But I might add a "wayland only" to the description

anonymix007 commented on 2024-05-11 21:53 (UTC)

X11 support was removed since version 6.0.3. Developer doesn't care about the users, apparently. I found their actions to be quite thoughtless and inconsiderate.

@fabiscafe can you add the patch to fix it? It's available here: I highly doubt it'll be merged any time soon (or even ever).

redsolja commented on 2024-05-10 19:31 (UTC) (edited on 2024-05-10 19:32 (UTC) by redsolja)

cannot run after build:

asusctl (master)$ RUST_BACKTRACE=full rog-control-center 
[WARN  rog_control_center::notify] Did not find a dGPU on this system, dGPU status won't be avilable
[WARN  rog_control_center::tray] supergfxd version = 5.2.1
thread 'main' panicked at /build/asusctl/src/asusctl/target/release/build/rog-control-center-7aeab502c6e151cc/out/
called `Result::unwrap()` on an `Err` value: Other("Error opening device: Resource temporarily unavailable")
stack backtrace:
Found aura device at /org/asuslinux/19b6_3_3, org.asuslinux.Aura
   0:     0x5f2f785679cf - <unknown>
   1:     0x5f2f77e26813 - <unknown>
   2:     0x5f2f78531372 - <unknown>
   3:     0x5f2f785695aa - <unknown>
   4:     0x5f2f78568d17 - <unknown>
   5:     0x5f2f78569e8d - <unknown>
   6:     0x5f2f785698d4 - <unknown>
   7:     0x5f2f78569829 - <unknown>
   8:     0x5f2f78569816 - <unknown>
   9:     0x5f2f77d91d45 - <unknown>
  10:     0x5f2f77d92115 - <unknown>
  11:     0x5f2f77dca2e3 - <unknown>
  12:     0x5f2f77e91057 - <unknown>
  13:     0x5f2f784fd924 - <unknown>
  14:     0x5f2f77de153d - <unknown>
  15:     0x5f2f77dd69b9 - <unknown>
  16:     0x5f2f77dc8a73 - <unknown>
  17:     0x5f2f77de2c06 - <unknown>
  18:     0x79f8bc30ac88 - <unknown>
  19:     0x79f8bc30ad4c - __libc_start_main
  20:     0x5f2f77dc5c45 - <unknown>
  21:                0x0 - <unknown>
Aborted (core dumped)

fabiscafe commented on 2024-05-04 19:16 (UTC)

@callegar Yes. The 'SKIP' was just needed because we didn't had checksum support for VCS source, that we have now with pacman 6.1

callegar commented on 2024-05-04 06:33 (UTC)

Should these two items actually go together as they do now in the PKGBUILD?


I am getting a checksum validation error, with a notice that there is no asusctl to check. Guess this is because rather than downloading an archive (single file), the git+https protocol ends up directly in an expanded source tree via git.

Apparently suggests that when sources are obtained from a VCS, the sums should be set to SKIP. This is not so clear to me though, because the general case where sources are derived from a VCS is the case of getting a branch tip, while here a tagged tree is targeted that is static rather than dynamic.