Closed Xeo23 closed 1 year ago
Pls provide the log located in /tmp/ar.log
$ mokutil --sb-state SecureBoot disabled $ chmod +x /tmp/legacy07.aurora/permission_checker.sh $ type pkexec pkexec is /bin/pkexec $ chmod +x /tmp/legacy07.aurora/battery_manager.sh $ chmod +x /tmp/legacy07.aurora/mainline_controller.sh $ /tmp/legacy07.aurora/permission_checker.sh /sys/class/leds/asus::kbd_backlight/kbd_rgb_state true $ /tmp/legacy07.aurora/permission_checker.sh /sys/class/leds/asus::kbd_backlight/kbd_rgb_mode $ /tmp/legacy07.aurora/permission_checker.sh /sys/class/leds/asus::kbd_backlight/brightness true $ /tmp/legacy07.aurora/mainline_controller.sh brightness 1 $ /tmp/legacy07.aurora/mainline_controller.sh mode 1 0 104 15 226 0 $ /tmp/legacy07.aurora/mainline_controller.sh state 1 1 1 0 0 saved 0 0 $ /tmp/legacy07.aurora/mainline_controller.sh mode 1 0 223 205 249 0 1 0 223 205 249 0 saved $ /tmp/legacy07.aurora/mainline_controller.sh mode 1 0 104 15 226 0 1 0 104 15 226 0 saved $ /tmp/legacy07.aurora/mainline_controller.sh state 1 1 1 1 0 1 1 1 1 0 saved $ /tmp/legacy07.aurora/mainline_controller.sh state 1 1 1 0 0 1 1 1 0 0 saved $ /tmp/legacy07.aurora/mainline_controller.sh mode 1 9 104 15 226 0 1 9 104 15 226 0 saved $ /tmp/legacy07.aurora/mainline_controller.sh mode 1 0 104 15 226 0 1 0 104 15 226 0 saved $ /tmp/legacy07.aurora/mainline_controller.sh brightness 3 $ /tmp/legacy07.aurora/mainline_controller.sh brightness 0 $ /tmp/legacy07.aurora/mainline_controller.sh brightness 1 $ /tmp/legacy07.aurora/mainline_controller.sh mode 1 1 104 15 226 0 1 1 104 15 226 0 saved $ /tmp/legacy07.aurora/mainline_controller.sh mode 1 2 104 15 226 0 1 2 104 15 226 0 saved $ /tmp/legacy07.aurora/mainline_controller.sh mode 1 2 104 15 226 2 1 2 104 15 226 2 saved $ /tmp/legacy07.aurora/mainline_controller.sh mode 1 2 104 15 226 0 1 2 104 15 226 0 saved $ /tmp/legacy07.aurora/mainline_controller.sh mode 1 0 104 15 226 0 1 0 104 15 226 0 saved
the log seems fine. You had passed the Authorization screen with proper permissions and had reached the control screen, according to the log you provided
Su permissions required to run it ? When I normally opened it from menu, it stucked on the grant access screen but then i tried to run it from terminal with sudo and it worked
Yes. Sudo permissions are required but it doesn't need to be run from terminal with sudo. It can be normally opened like any other app and it uses pkexec to get the sudo permission if required. Provide the log while running the app without sudo permissions.
$ mokutil --sb-state SecureBoot disabled $ chmod +x /tmp/legacy07.aurora/permission_checker.sh $ type pkexec pkexec is /usr/bin/pkexec $ chmod +x /tmp/legacy07.aurora/battery_manager.sh $ chmod +x /tmp/legacy07.aurora/mainline_controller.sh $ /tmp/legacy07.aurora/permission_checker.sh /sys/class/leds/asus::kbd_backlight/kbd_rgb_state $ pkexec --disable-internal-agent /tmp/legacy07.aurora/mainline_controller.sh init /tmp/legacy07.aurora 50 Refusing to render service to dead parents. $ /tmp/legacy07.aurora/permission_checker.sh /sys/class/leds/asus::kbd_backlight/kbd_rgb_state false $ /tmp/legacy07.aurora/permission_checker.sh /sys/class/leds/asus::kbd_backlight/kbd_rgb_state $ pkexec --disable-internal-agent /tmp/legacy07.aurora/mainline_controller.sh init /tmp/legacy07.aurora 50 Refusing to render service to dead parents. $ /tmp/legacy07.aurora/permission_checker.sh /sys/class/leds/asus::kbd_backlight/kbd_rgb_state false
I'm unable to reproduce this issue on my f38-kernel 6.3.8-200.
Are you getting the same error when running the command
pkexec --disable-internal-agent /tmp/legacy07.aurora/mainline_controller.sh init /tmp/legacy07.aurora 50
by manually in the terminal?
I got the password prompt and this is the terminal output.
❯ pkexec --disable-internal-agent /tmp/legacy07.aurora/mainline_controller.sh init /tmp/legacy07.aurora 50 modprobe: FATAL: Module faustus not found. 50 Setting charging threshold to 50 %... Created symlink /etc/systemd/system/multi-user.target.wants/aurora-controller.service → /usr/lib/systemd/system/aurora-controller.service. Created symlink /etc/systemd/system/suspend.target.wants/aurora-controller.service → /usr/lib/systemd/system/aurora-controller.service. Created symlink /etc/systemd/system/hibernate.target.wants/aurora-controller.service → /usr/lib/systemd/system/aurora-controller.service. Created symlink /etc/systemd/system/hybrid-sleep.target.wants/aurora-controller.service → /usr/lib/systemd/system/aurora-controller.service. Created symlink /etc/systemd/system/suspend-then-hibernate.target.wants/aurora-controller.service → /usr/lib/systemd/system/aurora-controller.service.
does running /usr/bin/aurora/aurora
by terminal without the root privileges also have the same result?
Now it is stucked on checking compatibility screen.
❯ /usr/bin/aurora/aurora Gtk-Message: 01:06:54.061: Failed to load module "appmenu-gtk-module" [ERROR:flutter/runtime/dart_vm_initializer.cc(41)] Unhandled Exception: PathAccessException: Cannot delete file, path = '/tmp/ar.log' (OS Error: Operation not permitted, errno = 1)
[ERROR:flutter/runtime/dart_vm_initializer.cc(41)] Unhandled Exception: PathAccessException: Deletion failed, path = '/tmp/legacy07.aurora' (OS Error: Permission denied, errno = 13)
You must have run aurora with root privileges at some point which made the ar.log created by root, which cannot be deleted without root privileges
Ok I got it working fine without root privileges. Thanks
I have installed it using copr on f38 it stucked on the grant access page and nothing happens when i click the button (grant access).