Package Details: rog-control-center 6.1.2-0.1

Git Clone URL: https://aur.archlinux.org/asusctl.git (read-only, click to copy)
Package Base: asusctl
Description: App to control asusctl
Upstream URL: https://asus-linux.org
Keywords: anime asus matrix rog
Licenses: MPL-2.0
Submitter: fabiscafe
Maintainer: fabiscafe
Last Packager: fabiscafe
Votes: 19
Popularity: 1.82
First Submitted: 2021-09-18 11:01 (UTC)
Last Updated: 2025-02-10 13:11 (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

https://asus-linux.org/guides/arch-guide/

Merge/Pull Requests / Bugreports

https://gitlab.archlinux.org/fabiscafe/asusctl_aur

Known Issues

Latest Comments

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

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/main_window.rs:89584:49:
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?

source=("git+https://gitlab.com/asus-linux/asusctl.git#tag=$pkgver")
b2sums=('2be7cd61489d223e511e71c8d62b4f68903a6efed98848491d7824cceb87e4cd3c90db015c1159020ec493aa088472572549126ac36349c475098ded0842fe88')

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 https://wiki.archlinux.org/title/VCS_package_guidelines 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.

fabiscafe commented on 2024-04-02 21:33 (UTC)

@labaman In case someone imports it to Arch it can be pushed with pkgrel of 1 instead of 2

labaman commented on 2024-04-02 06:58 (UTC)

Can you tell me why to use fractional $pkgrel?

redsolja commented on 2024-03-18 20:12 (UTC)

@fabiscafe: worked! Thanks! Any idea how to not need such an environment? I mean, I haven't changed anything at mine at all. How to "reset" it to a clean one that is clean by default?

yochananmarqos commented on 2024-03-14 00:06 (UTC)

@fabiscafe: Yes, the old libappindicator; i.e., libappindicator-gtk3 / libappindicator-gtk2 hasn't seen a release since 2017. Since I do a lot of packaging, I've noticed many projects are switching to libayatana-appindicator. There's still a transition with a fallback in some cases. In this case, ASUS uses libappindicator and libappindicator-sys crates built into the binary. I just noticed that the Ubuntu dependencies mentioned libayatana-appindicator3-1, so apparently that will work now with ROG Control Center.

fabiscafe commented on 2024-03-13 23:19 (UTC)

@yochananmarqos Is there any benefit to use libayatana-appindicator over libappinticator?

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