Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Alpha7 Crashes on Fedora 32 #984

Closed
1 task done
evfool opened this issue Aug 29, 2020 · 2 comments
Closed
1 task done

Alpha7 Crashes on Fedora 32 #984

evfool opened this issue Aug 29, 2020 · 2 comments

Comments

@evfool
Copy link

evfool commented Aug 29, 2020

  • I confirm that this is an issue rather than a question.

Bug report

When trying to start hyperiond on Fedora32 with an adalight device, it crashes. Doublechecked, the arduino I am using has DATA_PIN 6, connected to PC via /dev/ttyUSB0, user running hyperion has access to the port (successfully read the Ada\n magic word from a python console)

Steps to reproduce

  • Install alpha7 on Fedora
  • Change device to adalight
  • Change port to ttyUSB0 (as I don't have ttyACM0) - LED HW is arduino UNO using PIN6 for data output, connected on USB
  • Restart hyperion

What is expected?

Hyperion starts and can use the Leds

What is actually happening?

hyperiond crashes

System

Hyperion Server:

Hyperion Server OS:

  • Distribution: Fedora 32 (Workstation Edition)
  • Arch: x86_64
  • Kernel: linux (5.7.15-200.fc32.x86_64 (WS: 64))
  • Browser: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:79.0) Gecko/20100101 Firefox/79.0
@NickStallman
Copy link

Just adding my 2c, I'm getting this as well instantly after configuring adalight.

....more dtuff above here....
2020-08-30T13:15:58.165 hyperiond QTGRABBER    : <ERROR> No displays found to capture from!
2020-08-30T13:15:58.165 hyperiond QTGRABBER    : <INFO> Capture interface is now disabled
2020-08-30T13:15:58.271 hyperiond HYPERION     : <DEBUG> PriorityMuxer.cpp:238:setInputImage() | Priority 250 is now active
2020-08-30T13:15:59.589 hyperiond LEDDEVICE    : <DEBUG> ProviderRs232.cpp:180:tryOpen() | delayAfterConnect for 1500 ms - finished
2020-08-30T13:15:59.589 hyperiond COMPONENTREG : <DEBUG> ComponentRegister.cpp:36:setNewComponentState() | LED device: enabled

Hyperion caught signal :SIGSEGV
2020-08-30T13:15:59.650 hyperiond CORE         : <ERROR>        /lib/x86_64-linux-gnu/libpthread.so.0(+0x153c0) [0x7fad3f5fd3c0]
2020-08-30T13:15:59.650 hyperiond CORE         : <ERROR>        /usr/share/hyperion/bin/../lib/libQt5Core.so.5(QRingBuffer::reserve(long long)+0x2a) [0x7fad3e50ec3a]
2020-08-30T13:15:59.650 hyperiond CORE         : <ERROR>        /usr/share/hyperion/bin/../lib/libQt5SerialPort.so.5(+0xacec) [0x7fad3f61acec]
2020-08-30T13:15:59.650 hyperiond CORE         : <ERROR>        /usr/share/hyperion/bin/../lib/libQt5SerialPort.so.5(+0xb5eb) [0x7fad3f61b5eb]
2020-08-30T13:15:59.650 hyperiond CORE         : <ERROR>        hyperiond(ProviderRs232::writeBytes(long long, unsigned char const*)+0x24e) [0x560f45a6950e]
2020-08-30T13:15:59.650 hyperiond CORE         : <ERROR>        hyperiond(LedDevice::updateLeds(std::vector<ColorRgb, std::allocator<ColorRgb> > const&)+0xa7) [0x560f45aa9027]
2020-08-30T13:15:59.650 hyperiond CORE         : <ERROR>        hyperiond(QtPrivate::QSlotObject<int (LedDevice::*)(std::vector<ColorRgb, std::allocator<ColorRgb> > const&), QtPrivate::List<std::vector<ColorRgb, std::allocator<ColorRgb> > const&>, int>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*)+0x49) [0x560f45a642f9]
2020-08-30T13:15:59.650 hyperiond CORE         : <ERROR>        /usr/share/hyperion/bin/../lib/libQt5Core.so.5(QObject::event(QEvent*)+0xe9) [0x7fad3e68a659]
2020-08-30T13:15:59.650 hyperiond CORE         : <ERROR>        /usr/share/hyperion/bin/../lib/libQt5Core.so.5(QCoreApplication::notifyInternal2(QObject*, QEvent*)+0xfb) [0x7fad3e65dc0b]
2020-08-30T13:15:59.650 hyperiond CORE         : <ERROR>        /usr/share/hyperion/bin/../lib/libQt5Core.so.5(QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*)+0x2dd) [0x7fad3e6603bd]
2020-08-30T13:15:59.650 hyperiond CORE         : <ERROR>        /usr/share/hyperion/bin/../lib/libQt5Core.so.5(+0x2d1cb3) [0x7fad3e6b1cb3]
2020-08-30T13:15:59.650 hyperiond CORE         : <ERROR>        /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x27d) [0x7fad3bf99fbd]
2020-08-30T13:15:59.650 hyperiond CORE         : <ERROR>        /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x52240) [0x7fad3bf9a240]
2020-08-30T13:15:59.650 hyperiond CORE         : <ERROR>        /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x33) [0x7fad3bf9a2e3]
2020-08-30T13:15:59.651 hyperiond CORE         : <ERROR>        /usr/share/hyperion/bin/../lib/libQt5Core.so.5(QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)+0x5f) [0x7fad3e6b20bf]
2020-08-30T13:15:59.651 hyperiond CORE         : <ERROR>        /usr/share/hyperion/bin/../lib/libQt5Core.so.5(QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>)+0xfa) [0x7fad3e65bc0a]
2020-08-30T13:15:59.651 hyperiond CORE         : <ERROR>        /usr/share/hyperion/bin/../lib/libQt5Core.so.5(QThread::exec()+0xc3) [0x7fad3e48a093]
2020-08-30T13:15:59.651 hyperiond CORE         : <ERROR>        /usr/share/hyperion/bin/../lib/libQt5Core.so.5(+0xaed48) [0x7fad3e48ed48]
2020-08-30T13:15:59.651 hyperiond CORE         : <ERROR>        /lib/x86_64-linux-gnu/libpthread.so.0(+0x9609) [0x7fad3f5f1609]
2020-08-30T13:15:59.651 hyperiond CORE         : <ERROR>        /lib/x86_64-linux-gnu/libc.so.6(clone+0x43) [0x7fad3dd0a103]
Segmentation fault (core dumped)

This is on a x86_64 Ubuntu 20.04.1 LTS machine, not a Pi or SBC.
This is also encountered when I'm root typing hyperiond directly.

@Lord-Grey
Copy link
Collaborator

Closed, as duplicate to QRingBuffer issue in #903

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants