I'll disown the package since I don't the app anymore and it seems abandoned :(
Search Criteria
Package Details: tuxclocker 0.1.1-2
Package Actions
Git Clone URL: | https://aur.archlinux.org/tuxclocker.git (read-only, click to copy) |
---|---|
Package Base: | tuxclocker |
Description: | Qt5 GPU overclocking GUI utility. |
Upstream URL: | https://github.com/Lurkki14/tuxclocker |
Keywords: | gpu nvidia overclocking |
Licenses: | GPL3 |
Conflicts: | tuxclocker-git |
Submitter: | murlakatamenka |
Maintainer: | None |
Last Packager: | murlakatamenka |
Votes: | 5 |
Popularity: | 0.032391 |
First Submitted: | 2019-02-21 13:08 (UTC) |
Last Updated: | 2019-10-06 22:28 (UTC) |
Dependencies (4)
- libxnvctrl (libxnvctrl-beta-gtk2, libxnvctrl-430xx, libxnvctrl-340xx, libxnvctrl-470xx, libxnvctrl-510xx, libxnvctrl-390xx)
- nvidia-settings (nvidia-settings-beta-gtk2, nvidia-430xx-settings, nvidia-340xx-settings, nvidia-vulkan-utils, nvidia-vulkan-utils-nvlax, nvidia-settings-beta, nvidia-merged-settings, nvidia-470xx-settings, nvidia-510xx-settings, nvidia-390xx-settings)
- nvidia-utils (nvidia-410xx-utils, nvidia-340xx-utils, nvidia-440xx-utils, nvidia-430xx-utils, nvidia-vulkan-utils, nvidia-vulkan-utils-nvlax, nvidia-utils-beta, nvidia-utils-beta-nvlax, nvidia-merged-utils, nvidia-470xx-utils, nvidia-390xx-utils, nvidia-510xx-utils, nvidia-utils-nvlax)
- qt5-x11extras (qt5-x11extras-git)
Required by (0)
Sources (2)
Latest Comments
murlakatamenka commented on 2022-04-25 05:29 (UTC)
GraphZal commented on 2022-04-23 12:33 (UTC)
I have the same problem as @allexj, but am running a dedicated GPU (Radeon RX5600XT).
014 commented on 2022-02-04 23:50 (UTC)
The upstream source says this software is for Nvidia and for AMD. Would you consider making the nvidia-settings and nvidia-utils optional?
allexj commented on 2021-08-23 08:19 (UTC)
$ sudo tuxclocker QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' QMetaObject::connectSlotsByName: No matching signal for on_newProfile_clicked() QMetaObject::connectSlotsByName: No matching signal for on_newProfile_closed() QMetaObject::connectSlotsByName: No matching signal for on_editProfile_closed() Segmentation fault
I have Ryzen 3500U with integrated gpu
murlakatamenka commented on 2019-11-20 16:07 (UTC)
You can remove all but qt5-x11extras
from depends
section of PKGBUILD
and overall adjust it to follow https://github.com/Lurkki14/tuxclocker#installation-amd.
It can't be achieved within this AUR package, but you can submit a separate one or just use it yourself. Do you need some help with it?
KlavKalashj commented on 2019-11-18 20:01 (UTC)
Is there any way to get this to build without installing all the nvidia-stuff? My system is all AMD...
murlakatamenka commented on 2019-10-06 21:59 (UTC) (edited on 2019-10-06 22:32 (UTC) by murlakatamenka)
@jaap, yeah, sure, I'll update the package in a day.
edit: done! Feedback is welcome.
jaap commented on 2019-10-05 11:45 (UTC)
Could you make /usr/bin/tuxclocker a symlink to /opt/tuxclocker/bin/tuxclocker?? That is where make install puts it and it would make it compatible with building manually.
murlakatamenka commented on 2019-02-23 14:12 (UTC) (edited on 2019-02-23 14:14 (UTC) by murlakatamenka)
@t87rrg, @Forum_Liker
The "issue" is Manjaro specific since there is no nvidia-settings
package in its repos (unlike on Arch), it's shipped as part of nvidia-utils
. So, removing nvidia-settings
from PKGBUILD
's depends
section is a true workaround for Manjaro users.
Next time, please do mention you use Manjaro right away, this can help. Arch and Manjaro have separate repositories and it does matter.
Huge thanks to /u/RAZR_96 for tracking down the root of the "issue"!
commented on 2019-02-22 09:24 (UTC)
Same issue. Nvidia-settings is already installed and available on my system, yet I get the same error.
edit: temporarily fixed this by removing "nvidia-settings" from the depends in pkgbuild. I am on Manjaro and saw the following posted on Reddit: "Manjaro's package for nvidia-utils contains nvidia-settings but hasn't added it to provides."
murlakatamenka commented on 2019-02-21 19:52 (UTC) (edited on 2019-02-22 07:05 (UTC) by murlakatamenka)
Hi, nvidia-settings
is available in the official repos - https://www.archlinux.org/packages/extra/x86_64/nvidia-settings/
It should be automatically installed by your package manager. Like this:
yay -S tuxclocker
:: Checking for conflicts...
:: Checking for inner conflicts...
[Repo: 1] nvidia-settings-415.27-1
[Aur: 1] tuxclocker-0.1.1-1
:: Downloaded PKGBUILD (1/1): tuxclocker
1 tuxclocker (Build Files Exist)
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==> Diffs to show?
==>
:: Parsing SRCINFO (1/1): tuxclocker
resolving dependencies...
looking for conflicting packages...
Packages (1) nvidia-settings-415.27-1
Total Installed Size: 1.67 MiB
:: Proceed with installation? [Y/n]
Forum_Liker commented on 2019-02-21 16:18 (UTC)
error: target not found: nvidia-settings
where to get nvidia-settings in AUR? (Ошибка подготовки транзакции: не удалось удовлетворить зависимости: невозможно удовлетворить зависимость 'nvidia-settings', необходимую для tuxclocker)
Pinned Comments
murlakatamenka commented on 2019-02-23 14:12 (UTC) (edited on 2019-02-23 14:14 (UTC) by murlakatamenka)
@t87rrg, @Forum_Liker
The "issue" is Manjaro specific since there is no
nvidia-settings
package in its repos (unlike on Arch), it's shipped as part ofnvidia-utils
. So, removingnvidia-settings
fromPKGBUILD
'sdepends
section is a true workaround for Manjaro users.Next time, please do mention you use Manjaro right away, this can help. Arch and Manjaro have separate repositories and it does matter.
Huge thanks to /u/RAZR_96 for tracking down the root of the "issue"!