Package Details: auto-cpufreq 2.3.0-1

Git Clone URL: https://aur.archlinux.org/auto-cpufreq.git (read-only, click to copy)
Package Base: auto-cpufreq
Description: Automatic CPU speed & power optimizer
Upstream URL: https://github.com/AdnanHodzic/auto-cpufreq
Licenses: LGPL-3.0-or-later
Submitter: liljaylj
Maintainer: liljaylj (parmjot, MusicalArtist12)
Last Packager: parmjot
Votes: 77
Popularity: 3.18
First Submitted: 2020-10-29 00:09 (UTC)
Last Updated: 2024-05-13 21:42 (UTC)

Pinned Comments

liljaylj commented on 2021-06-03 12:13 (UTC)

@coxe87b you don't need to --install daemon manually, this package contains systemd service already. instead, you need to start and enable service using: systemctl enable --now auto-cpufreq.service

Latest Comments

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

parmjot commented on 2024-02-18 07:00 (UTC)

Pushed 2.2.0. As always, comment if there are issues.

arcpie commented on 2024-02-08 20:26 (UTC) (edited on 2024-02-08 20:26 (UTC) by arcpie)

there's an issue with the update check in win.handle_update() in auto-cpufreq-gtk. For now i've commented the check and the program launches. It seems like it has already been fixed upstream though: https://github.com/AdnanHodzic/auto-cpufreq/issues/614

allen-fisher commented on 2024-01-19 07:18 (UTC)

It is fine with CLI, but when it comes to GUI:

auto-cpufreq-gtk

The error occurs:

Traceback (most recent call last):
  File "/usr/bin/auto-cpufreq-gtk", line 8, in <module>
    sys.exit(main())
             ^^^^^^
  File "/usr/lib/python3.11/site-packages/auto_cpufreq/bin/auto_cpufreq_gtk.py", line 18, in main
    win.handle_update()
  File "/usr/lib/python3.11/site-packages/auto_cpufreq/gui/app.py", line 84, in handle_update
    is_new_update = check_for_update()
                    ^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/site-packages/auto_cpufreq/core.py", line 183, in check_for_update
    latest_version =  latest_release["tag_name"]
                      ~~~~~~~~~~~~~~^^^^^^^^^^^^
KeyError: 'tag_name'

How to fix this?

autoingmycpu commented on 2023-12-16 18:43 (UTC)

@MusicalArtist12 Ran the command sudo mkdir /opt/auto-cpufreq/ but nothing; same result.

Preparing... Cloning auto-cpufreq build files... Generating auto-cpufreq information... Checking auto-cpufreq dependencies... Resolving dependencies... Checking inter-conflicts...

Building auto-cpufreq... ==> Making package: auto-cpufreq 2.1.0-4 (Sun 17 Dec 2023 02:42:20 CST) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Found auto-cpufreq-2.1.0.tar.gz -> Found auto-cpufreq.service -> Found 001-fix-icon-n-style-locations.patch -> Found 002-fix-other-icon-path.patch ==> Validating source files with sha256sums... auto-cpufreq-2.1.0.tar.gz ... Passed auto-cpufreq.service ... Passed 001-fix-icon-n-style-locations.patch ... Passed 002-fix-other-icon-path.patch ... Passed ==> Removing existing $srcdir/ directory... ==> Extracting sources... -> Extracting auto-cpufreq-2.1.0.tar.gz with bsdtar ==> Starting prepare()... /var/tmp/pamac-build-ad/auto-cpufreq/PKGBUILD: line 27: patch: command not found ==> ERROR: A failure occurred in prepare(). Aborting...

thejspr commented on 2023-12-15 08:15 (UTC)

I keep getting an error related to some python libraries:

==> Starting build()...
/home/jesper/.asdf/installs/python/3.12.0/bin/python: No module named build
==> ERROR: A failure occurred in build().
    Aborting...
error: failed to build 'auto-cpufreq-2.1.0-4':
error: packages failed to build: auto-cpufreq-2.1.0-4

Tried all sorts of hacks and googling, to no avail.

MusicalArtist12 commented on 2023-12-10 22:10 (UTC)

@Hkntai I already pushed an update for that, thanks for the update though. glad that worked.

Nekoh commented on 2023-12-10 22:09 (UTC)

indeed sudo mkdir /opt/auto-cpufreq/ works. Maybe create that folder at installation?

MusicalArtist12 commented on 2023-12-10 20:33 (UTC)

@Hkntaim, run sudo mkdir /opt/auto-cpufreq/... i did a little digging, override.pickle is a runttime file...

MusicalArtist12 commented on 2023-12-10 20:29 (UTC)

@autoingmycpu weird, patch should be part of the core package.

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