tuxclocker icon indicating copy to clipboard operation
tuxclocker copied to clipboard

Segmentation fault

Open All3xJ opened this issue 3 years ago • 4 comments

$ 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

All3xJ avatar Aug 23 '21 08:08 All3xJ

Same error :, Ryzen 5 4600H, Radeon Vega 8, RX 5600M

sudo /opt/tuxclocker/bin/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()
[1]    3345 segmentation fault  sudo /opt/tuxclocker/bin/tuxclocker

madhavpcm avatar Aug 26 '21 18:08 madhavpcm

Same error:

# AMD® Ryzen 7 4800u with radeon graphics
sudo /opt/tuxclocker/bin/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()
[1]    9615 segmentation fault  sudo /opt/tuxclocker/bin/tuxclocker

ferstar avatar Oct 26 '21 01:10 ferstar

Seems to be related to this issue: https://gitlab.freedesktop.org/mesa/mesa/-/issues/2424

I modified amd.cpp:29 to be fd = open(path, O_RDWR | O_CLOEXEC); and tuxclocker opens without a segfault. I'm running this on a 5700XT so this may not work on your GPUs, but I doubt it because the original link appears to solve for Polaris GPUs. Either way, lmk if it works on your systems.

rayphee avatar Dec 13 '21 21:12 rayphee

I am on a 5700XT, and I still get the error. But perhaps I am doing something wrong.

tuxclocker  SEGV ✘ Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway. 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() zsh: segmentation fault (core dumped) tuxclocker    ~  sudo tuxclocker  SEGV ✘ [sudo] password for christopher: 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() zsh: segmentation fault sudo tuxclocker

Is there a solution?

Hansard avatar Jun 23 '22 00:06 Hansard

Running into this problem, as well. Same segmentation fault and error logs.

alexdelorenzo avatar Mar 05 '23 03:03 alexdelorenzo

Closing as outdated

Lurkki14 avatar Nov 25 '23 14:11 Lurkki14