| View previous topic :: View next topic |
| Author |
Message |
shadowfly
n00b
Joined: 21 Feb 2024
Posts: 25
|
 Posted: Thu Sep 12, 2024 8:56 pm Post subject: OpenRGB 0.9 Crashing |
 |
|
Hello there!
OpenRGB runs fine on my PC when i start it using the dektop entry or the terminal. I can even switch to the server tab and start a local server. However, when i run openrgb --server to start OpenRGB with a local server in headless mode, then the program crashes:
Without starting server during program start:
| Code: | user#openrgb
Attempting to connect to local OpenRGB server.
Connection attempt failed
Local OpenRGB server unavailable.
Running standalone.
[i2c_smbus_linux] Failed to read i2c device PCI device ID
<h2>WARNING:</h2><p>One or more I2C/SMBus interfaces failed to initialize.</p><p>RGB DRAM modules and some motherboards' onboard RGB lighting will not be available without I2C/SMBus.</p><p>On Linux, this is usually because the i2c-dev module is not loaded. You must load the i2c-dev module along with the correct i2c driver for your motherboard. This is usually i2c-piix4 for AMD systems and i2c-i801 for Intel systems.</p><p>See <a href='https://help.openrgb.org/'>help.openrgb.org</a> for additional troubleshooting steps if you keep seeing this message.<br></p> |
With starting server during program start:
| Code: | user#openrgb --server
Attempting to connect to local OpenRGB server.
Connection attempt failed
Local OpenRGB server unavailable.
Running standalone.
[i2c_smbus_linux] Failed to read i2c device PCI device ID
Network connection thread started on port 6742
Segmentation fault (core dumped) |
gdb:
| Code: | [Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib64/libthread_db.so.1".
Core was generated by `openrgb --server'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007fb6e0150fb6 in libusb_control_transfer () from /usr/lib64/libusb-1.0.so.0
[Current thread is 1 (Thread 0x7fb6daa186c0 (LWP 14065))] |
Until two months ago, everything worked fine for at least a year or so. I ran the openrgb --server command during startup using a systemd service. Interestingly i also run openrgb --server after returning from sleep, and there it actually starts.
- OS: Gentoo
- Wayland
- KDE Plasma 5, then upgraded to 6
|
|
| Back to top |
|
 |
shadowfly
n00b
Joined: 21 Feb 2024
Posts: 25
|
| Posted: Mon Sep 23, 2024 11:13 pm Post subject: |
|
|
I just learned how to enable debug symbols, so maybe this helps someone:
| Code: | (gdb) bt
#0 0x00007f261326ab5b in libusb_control_transfer (dev_handle=dev_handle@entry=0x7f26080647b0, bmRequestType=bmRequestType@entry=128 '\200', bRequest=bRequest@entry=6 '\006',
wValue=wValue@entry=768, wIndex=wIndex@entry=0, data=data@entry=0x7f260dcbf570 "", wLength=64, timeout=1000)
at /usr/src/debug/dev-libs/libusb-1.0.27-r1/libusb-1.0.27/libusb/sync.c:111
#1 0x00007f2611ca8d1b in libusb_get_string_descriptor (length=64, data=0x7f260dcbf570 "", langid=0, desc_index=0 '\000', dev_handle=0x7f26080647b0)
at /usr/include/libusb-1.0/libusb.h:2086
#2 is_language_supported (dev=dev@entry=0x7f26080647b0, lang=lang@entry=0) at /usr/src/debug/dev-libs/hidapi-0.13.1-r1/hidapi-hidapi-0.13.1/libusb/hid.c:380
#3 0x00007f2611caa010 in get_usb_string (dev=dev@entry=0x7f26080647b0, idx=3 '\003') at /usr/src/debug/dev-libs/hidapi-0.13.1-r1/hidapi-hidapi-0.13.1/libusb/hid.c:423
#4 0x00007f2611caa1df in create_device_info_for_device (device=device@entry=0x7f2608086a60, handle=0x7f26080647b0, desc=desc@entry=0x7f260dcbfca0, config_number=1, interface_num=7)
at /usr/src/debug/dev-libs/hidapi-0.13.1-r1/hidapi-hidapi-0.13.1/libusb/hid.c:682
#5 0x00007f2611caa2e0 in hid_enumerate (vendor_id=vendor_id@entry=0, product_id=product_id@entry=0) at /usr/src/debug/dev-libs/hidapi-0.13.1-r1/hidapi-hidapi-0.13.1/libusb/hid.c:800
#6 0x0000559c5bc8079c in ResourceManager::DetectDevicesThreadFunction (this=0x559c5d4b61c0) at /usr/src/debug/app-misc/openrgb-0.9/OpenRGB-release_0.9/ResourceManager.cpp:1274
#7 0x0000559c5bc7ac28 in std::__invoke_impl<void, void (ResourceManager::*)(), ResourceManager*> (__f=<optimized out>, __t=<optimized out>)
at /usr/lib/gcc/x86_64-pc-linux-gnu/13/include/g++-v13/bits/invoke.h:74
#8 0x0000559c5bc7ac43 in std::__invoke<void (ResourceManager::*)(), ResourceManager*> (__fn=<optimized out>) at /usr/lib/gcc/x86_64-pc-linux-gnu/13/include/g++-v13/bits/invoke.h:90
#9 std::thread::_Invoker<std::tuple<void (ResourceManager::*)(), ResourceManager*> >::_M_invoke<0ul, 1ul> (this=<optimized out>)
at /usr/lib/gcc/x86_64-pc-linux-gnu/13/include/g++-v13/bits/std_thread.h:292
#10 std::thread::_Invoker<std::tuple<void (ResourceManager::*)(), ResourceManager*> >::operator() (this=<optimized out>)
at /usr/lib/gcc/x86_64-pc-linux-gnu/13/include/g++-v13/bits/std_thread.h:299
#11 std::thread::_State_impl<std::thread::_Invoker<std::tuple<void (ResourceManager::*)(), ResourceManager*> > >::_M_run (this=<optimized out>)
at /usr/lib/gcc/x86_64-pc-linux-gnu/13/include/g++-v13/bits/std_thread.h:244
#12 0x00007f2611ae3203 in std::execute_native_thread_routine (__p=0x559c5d56b410) at /usr/src/debug/sys-devel/gcc-13.3.1_p20240614/gcc-13-20240614/libstdc++-v3/src/c++11/thread.cc:104
#13 0x00007f26118dff6e in start_thread (arg=<optimized out>) at pthread_create.c:447
#14 0x00007f2611941b8c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78 |
|
|
| Back to top |
|
|
Banana
Moderator
Joined: 21 May 2004
Posts: 1729
Location: Germany
|
|
| Back to top |
|
|
shadowfly
n00b
Joined: 21 Feb 2024
Posts: 25
|
| Posted: Thu Sep 26, 2024 7:05 pm Post subject: |
|
|
Thanks, this seems to work!
I had not installed https://packages.gentoo.org/packages/sys-apps/i2c-tools, because when i installed OpenRGB a year (or so) ago, enabling the modules by doing
| Code: | root# modprobe i2c-dev
root# modprobe i2c-piix4 (for AMD) |
and then starting OpenRGB crashed my PC.
But now i have i2c-tools installed and the modules loaded, and the PC did not crash. Even better: OpenRGB has not crashed once in the last 48h, even though OpenRGB used to crash like 10 times a day since 2 months ago. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Desktop Environments
