Bug 2227440

Summary: [abrt] openrgb: memset(): openrgb killed by SIGABRT
Product: [Fedora] Fedora Reporter: jrdmellow
Component: openrgbAssignee: Artem <ego.cordatus>
Status: CLOSED EOL QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 38CC: ego.cordatus, jrdmellow
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/dfabd87522a85f0372f1ed34b01f2a7633f6d52
Whiteboard: abrt_hash:a06c315f0f0b3c660cff5f95304fd2edfa8503c1;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-05-28 13:37:25 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: proc_pid_status
none
File: maps
none
File: limits
none
File: environ
none
File: open_fds
none
File: mountinfo
none
File: os_info
none
File: cpuinfo
none
File: core_backtrace
none
File: dso_list
none
File: var_log_messages
none
File: backtrace none

Description jrdmellow 2023-07-29 17:22:22 UTC
Description of problem:
Attempting to set any individual LED color on "Logitech G915TKL Wireless RGB Mechanical Gaming Keyboard". Using "Entire Zone" instead works.

Version-Release number of selected component:
openrgb-0.9-1.fc38

Additional info:
reporter:       libreport-2.17.11
type:           CCpp
reason:         openrgb killed by SIGABRT
journald_cursor: s=190a54a3cce344e0b9722cdb4aef9213;i=7b826;b=1f025d40ca254e888297ca601ec98697;m=231f840ae7;t=601a31ed2eace;x=b5b8bdd9ddd54a1d
executable:     /usr/bin/openrgb
cmdline:        /usr/bin/openrgb
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-gnome-OpenRGB-283097.scope
rootdir:        /
uid:            1000
kernel:         6.4.4-200.fc38.x86_64
package:        openrgb-0.9-1.fc38
runlevel:       N 5
comment:        Attempting to set any individual LED color on "Logitech G915TKL Wireless RGB Mechanical Gaming Keyboard". Using "Entire Zone" instead works.
backtrace_rating: 4
crash_function: memset

Truncated backtrace:
Thread no. 1 (5 frames)
 #7 memset at /usr/include/bits/string_fortified.h:59
 #8 RGBController_LogitechG915::DeviceUpdateLEDs() at ../Controllers/LogitechController/RGBController_LogitechG915.cpp:533
 #9 RGBController::DeviceCallThreadFunction() at ../RGBController/RGBController.cpp:1716
 #10 std::execute_native_thread_routine(void*) at ../../../../../libstdc++-v3/src/c++11/thread.cc:104
 #12 clone3 at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Comment 1 jrdmellow 2023-07-29 17:22:25 UTC
Created attachment 1980618 [details]
File: proc_pid_status

Comment 2 jrdmellow 2023-07-29 17:22:26 UTC
Created attachment 1980619 [details]
File: maps

Comment 3 jrdmellow 2023-07-29 17:22:28 UTC
Created attachment 1980620 [details]
File: limits

Comment 4 jrdmellow 2023-07-29 17:22:29 UTC
Created attachment 1980621 [details]
File: environ

Comment 5 jrdmellow 2023-07-29 17:22:30 UTC
Created attachment 1980622 [details]
File: open_fds

Comment 6 jrdmellow 2023-07-29 17:22:31 UTC
Created attachment 1980623 [details]
File: mountinfo

Comment 7 jrdmellow 2023-07-29 17:22:32 UTC
Created attachment 1980624 [details]
File: os_info

Comment 8 jrdmellow 2023-07-29 17:22:33 UTC
Created attachment 1980625 [details]
File: cpuinfo

Comment 9 jrdmellow 2023-07-29 17:22:34 UTC
Created attachment 1980626 [details]
File: core_backtrace

Comment 10 jrdmellow 2023-07-29 17:22:36 UTC
Created attachment 1980627 [details]
File: dso_list

Comment 11 jrdmellow 2023-07-29 17:22:37 UTC
Created attachment 1980628 [details]
File: var_log_messages

Comment 12 jrdmellow 2023-07-29 17:22:38 UTC
Created attachment 1980629 [details]
File: backtrace

Comment 13 Artem 2023-07-29 17:34:29 UTC
Thanks for reporting. Can you report this upstream in your spare time please? https://gitlab.com/CalcProgrammer1/OpenRGB/-/issues

Comment 14 Aoife Moloney 2024-05-28 13:37:25 UTC
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.