Description of problem: First I started the radeon-profile-daemon.service. Then I started radeon-profile GUI in Gnome. It didn't start and I had a stacktrace in journal. I have two graphicscards, both amd: 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 31 [Radeon RX 7900 XT/7900 XTX] (rev cc) 13:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Raphael (rev c3) Version-Release number of selected component: radeon-profile-20200824-8.fc38 Additional info: reporter: libreport-2.17.11 type: CCpp reason: radeon-profile killed by SIGSEGV journald_cursor: s=48aebf4fbb1c4cd197fcfd58e66b9884;i=53233;b=bd3542fd8c414412b5e63c10bb55b823;m=299dfdbe;t=5ffd544282fce;x=b8a89663c72f7622 executable: /usr/bin/radeon-profile cmdline: /usr/bin/radeon-profile cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-radeon\x2dprofile-8723.scope rootdir: / uid: 1000 kernel: 6.3.11-200.fc38.x86_64 package: radeon-profile-20200824-8.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: QString::toIntegral_helper<unsigned int> Truncated backtrace: Thread no. 1 (14 frames) #0 QString::toIntegral_helper<unsigned int> at ../../include/QtCore/../../src/corelib/text/qstring.h:1038 #1 QString::toUInt at text/qstring.cpp:7457 #2 dXorg::parseOcTable at /usr/src/debug/radeon-profile-20200824-8.fc38.x86_64/radeon-profile/dxorg.cpp:820 #3 dXorg::readOcTableAndRanges at /usr/src/debug/radeon-profile-20200824-8.fc38.x86_64/radeon-profile/dxorg.cpp:832 #4 dXorg::figureOutDriverFeatures at /usr/src/debug/radeon-profile-20200824-8.fc38.x86_64/radeon-profile/dxorg.cpp:646 #5 dXorg::dXorg at /usr/src/debug/radeon-profile-20200824-8.fc38.x86_64/radeon-profile/dxorg.cpp:18 #6 gpu::initialize at /usr/src/debug/radeon-profile-20200824-8.fc38.x86_64/radeon-profile/gpu.cpp:90 #7 radeon_profile::initializeDevice at /usr/src/debug/radeon-profile-20200824-8.fc38.x86_64/radeon-profile/radeon_profile.cpp:76 #8 radeon_profile::daemonConnected at /usr/src/debug/radeon-profile-20200824-8.fc38.x86_64/radeon-profile/radeon_profile.cpp:100 #10 doActivate<false> at kernel/qobject.cpp:3937 #11 QMetaObject::activate at kernel/qobject.cpp:3985 #12 QLocalSocket::connected at .moc/moc_qlocalsocket.cpp:225 #13 QLocalSocketPrivate::_q_connectToSocket at socket/qlocalsocket_unix.cpp:336 #14 QLocalSocket::connectToServer at socket/qlocalsocket_unix.cpp:255
Created attachment 1974336 [details] File: proc_pid_status
Created attachment 1974337 [details] File: maps
Created attachment 1974338 [details] File: limits
Created attachment 1974339 [details] File: environ
Created attachment 1974340 [details] File: open_fds
Created attachment 1974341 [details] File: mountinfo
Created attachment 1974342 [details] File: os_info
Created attachment 1974343 [details] File: cpuinfo
Created attachment 1974344 [details] File: core_backtrace
Created attachment 1974345 [details] File: exploitable
Created attachment 1974346 [details] File: dso_list
First I started the radeon-profile-daemon.service. Then I started radeon-profile GUI in Gnome. It didn't start and I had a stacktrace in journal. I have two graphicscards, both amd: 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 31 [Radeon RX 7900 XT/7900 XTX] (rev cc) 13:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Raphael (rev c3) reporter: libreport-2.17.11 type: CCpp reason: radeon-profile killed by SIGSEGV journald_cursor: s=48aebf4fbb1c4cd197fcfd58e66b9884;i=53233;b=bd3542fd8c414412b5e63c10bb55b823;m=299dfdbe;t=5ffd544282fce;x=b8a89663c72f7622 executable: /usr/bin/radeon-profile cmdline: /usr/bin/radeon-profile cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-radeon\x2dprofile-8723.scope rootdir: / uid: 1000 kernel: 6.3.11-200.fc38.x86_64 package: radeon-profile-20200824-8.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: QString::toIntegral_helper<unsigned int>
Seems like there is issues in general with latest 7000 series cards https://github.com/marazmista/radeon-profile/issues/293 App more like abandomware and have no updates since 2020. Probably time to retire package from Fedora.
OK, thanks for the information. Then I'll remove the app.
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21. Fedora Linux 38 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.