Package Details: system76-power 1.2.1-1

Git Clone URL: https://aur.archlinux.org/system76-power.git (read-only, click to copy)
Package Base: system76-power
Description: System76 Power Management
Upstream URL: https://github.com/pop-os/system76-power
Licenses: GPL
Provides: power-profiles-daemon
Submitter: ebobby
Maintainer: tleydxdy
Last Packager: tleydxdy
Votes: 13
Popularity: 0.68
First Submitted: 2018-07-05 23:47 (UTC)
Last Updated: 2024-08-22 18:09 (UTC)

Dependencies (7)

Required by (22)

Sources (2)

Latest Comments

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

tleydxdy commented on 2021-09-19 18:19 (UTC)

@yochananmarqos it is how it was done upstream, this is just a temporary hack before they make the next release. 1.1.18 has a mistake in it and won't actually build

yochananmarqos commented on 2021-09-19 18:16 (UTC)

@tleydxdy: Why are you specifying a static toolchain version? Just use:

export RUSTUP_TOOLCHAIN=stable

See Rust package guidelines

tleydxdy commented on 2021-06-20 08:13 (UTC)

@hossamdash pushed a fix

hossamdash commented on 2021-06-19 23:13 (UTC)

@tleydxdy yes i just checked out the commit that was 7 weeks ago and installed it. it works fine and the service starts without any problems.

tleydxdy commented on 2021-06-19 22:44 (UTC)

@hossamdash does reverting back to the old package fixes it? did you reboot? it does read like a transient issue looks similar to, nothing substantial changed in the package afaik.

hossamdash commented on 2021-06-19 22:12 (UTC)

can confirm that this package is no longer working for me after upgrade to this latest version 1.1.16.4 here's what i get when i try to start the system76-power.service via doas systemctl status system76-power.service

Job for system76-power.service failed because the control process exited with error code.
See "systemctl status system76-power.service" and "journalctl -xeu system76-power.service" for details.

and here's the output of systemctl status system76-power.service

× system76-power.service - System76 Power Daemon
     Loaded: loaded (/usr/lib/systemd/system/system76-power.service; disabled; vendor preset: disabled)
     Active: failed (Result: exit-code) since Sun 2021-06-20 00:10:32 EET; 20s ago
    Process: 10187 ExecStart=/usr/bin/system76-power daemon (code=exited, status=1/FAILURE)
   Main PID: 10187 (code=exited, status=1/FAILURE)
        CPU: 29ms

Jun 20 00:10:32 arch-boii systemd[1]: system76-power.service: Scheduled restart job, restart counter is at 5.
Jun 20 00:10:32 arch-boii systemd[1]: Stopped System76 Power Daemon.
Jun 20 00:10:32 arch-boii systemd[1]: system76-power.service: Start request repeated too quickly.
Jun 20 00:10:32 arch-boii systemd[1]: system76-power.service: Failed with result 'exit-code'.
Jun 20 00:10:32 arch-boii systemd[1]: Failed to start System76 Power Daemon.

kucksdorfs commented on 2021-06-19 22:11 (UTC)

My bad... I updated my my comment below with the text tag.

yochananmarqos commented on 2021-06-19 21:32 (UTC) (edited on 2021-06-19 21:33 (UTC) by yochananmarqos)

@kucksdorfs: That's really hard to read. Markdown is supported here (sort of). You can use three bacticks to format terminal output:

```

text

```

kucksdorfs commented on 2021-06-19 21:30 (UTC) (edited on 2021-06-19 22:01 (UTC) by kucksdorfs)

@yochananmarqos, I ran that and rebooted a few times.

When I did the upgrade, yay told me there were some merge conflicts, so I had it do a clean build (rm -rf the directory and does a fresh git clone).

Below are results of systemctl status and the full journalctl.

> systemctl status system76-power.service 
× system76-power.service - System76 Power Daemon
     Loaded: loaded (/usr/lib/systemd/system/system76-power.service; enabled; vendor preset: disabled)
     Active: failed (Result: exit-code) since Sat 2021-06-19 14:52:46 CDT; 1h 33min ago
   Main PID: 1205 (code=exited, status=1/FAILURE)
        CPU: 53ms

Jun 19 14:52:46 laptop systemd[1]: system76-power.service: Scheduled restart job, restart counter is at 5.
Jun 19 14:52:46 laptop systemd[1]: Stopped System76 Power Daemon.
Jun 19 14:52:46 laptop systemd[1]: system76-power.service: Start request repeated too quickly.
Jun 19 14:52:46 laptop systemd[1]: system76-power.service: Failed with result 'exit-code'.
Jun 19 14:52:46 laptop systemd[1]: Failed to start System76 Power Daemon.

>sudo journalctl -xeu system76-power.service
Jun 19 14:52:46 laptop system76-power[1205]: [INFO] 0000:01:00.0: Removing
Jun 19 14:52:46 laptop system76-power[1205]: [INFO] 0000:01:00.3: Removing
Jun 19 14:52:46 laptop system76-power[1205]: [INFO] 0000:01:00.1: Removing
Jun 19 14:52:46 laptop system76-power[1205]: [INFO] Initializing with the balanced profile
Jun 19 14:52:46 laptop system76-power[1205]: [INFO] Registering dbus name com.system76.PowerDaemon
Jun 19 14:52:46 laptop system76-power[1205]: Connection ":1.25" is not allowed to own the service "com.system76.PowerDaemon" due to security policies in the configuration file
Jun 19 14:52:46 laptop systemd[1]: system76-power.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ An ExecStart= process belonging to unit system76-power.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
Jun 19 14:52:46 laptop systemd[1]: system76-power.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit system76-power.service has entered the 'failed' state with result 'exit-code'.
Jun 19 14:52:46 laptop systemd[1]: Failed to start System76 Power Daemon.
░░ Subject: A start job for unit system76-power.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit system76-power.service has finished with a failure.
░░ 
░░ The job identifier is 1815 and the job result is failed.
Jun 19 14:52:46 laptop systemd[1]: system76-power.service: Scheduled restart job, restart counter is at 5.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ Automatic restarting of the unit system76-power.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Jun 19 14:52:46 laptop systemd[1]: Stopped System76 Power Daemon.
░░ Subject: A stop job for unit system76-power.service has finished
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A stop job for unit system76-power.service has finished.
░░ 
░░ The job identifier is 1947 and the job result is done.
Jun 19 14:52:46 laptop systemd[1]: system76-power.service: Start request repeated too quickly.
Jun 19 14:52:46 laptop systemd[1]: system76-power.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit system76-power.service has entered the 'failed' state with result 'exit-code'.
Jun 19 14:52:46 laptop systemd[1]: Failed to start System76 Power Daemon.
░░ Subject: A start job for unit system76-power.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit system76-power.service has finished with a failure.
░░ 
░░ The job identifier is 1947 and the job result is failed.

yochananmarqos commented on 2021-06-19 21:21 (UTC)

@Kucksdorfs: I can't reproduce that. Did you restart the service after updating? Nothing really changed. Sometimes systemctl daemon-reload might be necessary as well.

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