Skip to content
This repository has been archived by the owner on Oct 10, 2022. It is now read-only.

Camera > Open menu not working #59

Closed
src386 opened this issue Jul 1, 2018 · 9 comments · Fixed by #86
Closed

Camera > Open menu not working #59

src386 opened this issue Jul 1, 2018 · 9 comments · Fixed by #86

Comments

@src386
Copy link

src386 commented Jul 1, 2018

  • Planetary Imager built from sources 2e4357a
  • Fedora 28 x86_64, MATE

Steps to reproduce:

  1. Plug USB camera (ASI 120MC)
  2. Start planetary_imager
  3. Camera > Open (nothing)

Logs:

Start planetary_imager with USB Camera:

$ planetary_imager
Starting PlanetaryImager - version 0.7.70 (x86_64)
Writing full output to logfile: /home/xavier/.cache/PlanetaryImager/PlanetaryImager.log
 WARNING -  QWidget::setLayout: Attempting to set QLayout "" on QWidget "statsWidget", which already has a layout
 WARNING -  QMainWindow::saveState(): 'objectName' not set for QToolBar 0x182be60 'Help'
 WARNING -  QMainWindow::saveState(): 'objectName' not set for QToolBar 0x182be60 'Help'
 WARNING -  QMainWindow::saveState(): 'objectName' not set for QToolBar 0x182be60 'Help'
 WARNING -  QMainWindow::saveState(): 'objectName' not set for QToolBar 0x182be60 'Help'
corrupted size vs. prev_size
Error: signal 6:

Start planetary_imager, plug USB camera, then rescan (crashes):

$ planetary_imager
Starting PlanetaryImager - version 0.7.70 (x86_64)
Writing full output to logfile: /home/xavier/.cache/PlanetaryImager/PlanetaryImager.log
 WARNING -  QWidget::setLayout: Attempting to set QLayout "" on QWidget "statsWidget", which already has a layout
 WARNING -  QMainWindow::saveState(): 'objectName' not set for QToolBar 0x1881ac0 'Help'
 WARNING -  QMainWindow::saveState(): 'objectName' not set for QToolBar 0x1881ac0 'Help'
 WARNING -  QMainWindow::saveState(): 'objectName' not set for QToolBar 0x1881ac0 'Help'
 WARNING -  QMainWindow::saveState(): 'objectName' not set for QToolBar 0x1881ac0 'Help'
corrupted size vs. prev_size
Error: signal 6:
corrupted size vs. prev_size
Error: signal 6:
munmap_chunk(): invalid pointer
Error: signal 6:
[0]: address: 0x7fe6f37a5fb0, file: /lib64/libc.so., function: +0x36fb
[1]: address: 0x7fe6f37a5f2b, file: /lib64/libc.so., function: gsignal+0x10
[2]: address: 0x7fe6f3790561, file: /lib64/libc.so., function: abort+0x12
[3]: address: 0x7fe6f37e8917, file: /lib64/libc.so., function: +0x7991
[4]: address: 0x7fe6f37eedec, file: /lib64/libc.so., function: +0x7fde
[5]: address: 0x7fe6f37ef344, file: /lib64/libc.so., function: +0x8034
[6]: address: 0x7fe6e394b6c0, file: /lib64/libusb-1.0.so., function: libusb_exit+0x22
[7]: address: 0x7fe6b07f342b, file: /usr/lib/PlanetaryImager/drivers/libzwo_asi_imager.s, function: ASICloseCamera+0x21
[8]: address: 0x7fe6b07f449d, file: /usr/lib/PlanetaryImager/drivers/libzwo_asi_imager.s, function: ASIGetCameraProperty+0x2a
[9]: address: 0x7fe6b07b3565, file: /usr/lib/PlanetaryImager/drivers/libzwo_asi_imager.s, function: ZWO_ASI_Driver::cameras() const+0xa
[10]: address: 0x628850, file: planetary_image, function: SupportedDrivers::cameras() const+0xb
[11]: address: 0x5ec3eb, file: planetary_image, function: 
[12]: address: 0x5ed3bf, file: planetary_image, function: 
[13]: address: 0x5f3c93, file: planetary_image, function: std::function<QList<std::shared_ptr<Driver::Camera> > ()>::operator()() const+0x3
[14]: address: 0x5f3acd, file: planetary_image, function: QtConcurrent::StoredFunctorCall0<QList<std::shared_ptr<Driver::Camera> >, std::function<QList<std::shared_ptr<Driver::Camera> > ()> >::runFunctor()+0x2
[15]: address: 0x5f39c4, file: planetary_image, function: QtConcurrent::RunFunctionTask<QList<std::shared_ptr<Driver::Camera> > >::run()+0x4
[16]: address: 0x7fe6f4529431, file: /lib64/libQt5Core.so., function: +0xbd43
[17]: address: 0x7fe6f452c11d, file: /lib64/libQt5Core.so., function: +0xc011
[18]: address: 0x7fe6f81be594, file: /lib64/libpthread.so., function: +0x759
[19]: address: 0x7fe6f386902f, file: /lib64/libc.so., function: clone+0x3
Error: signal 11:
[0]: address: 0x7fe6f37a5fb0, file: /lib64/libc.so., function: +0x36fb
[1]: address: 0x7fe6f61f704a, file: /lib64/libQt5Gui.so., function: +0xd304
[2]: address: 0x7fe6f641f149, file: /lib64/libQt5Gui.so., function: QPainterState::QPainterState()+0x4
[3]: address: 0x7fe6f640907d, file: /lib64/libQt5Gui.so., function: +0x2e507
[4]: address: 0x7fe6f6410bfd, file: /lib64/libQt5Gui.so., function: QRasterPaintEngine::createState(QPainterState*) const+0x4
[5]: address: 0x7fe6f6422919, file: /lib64/libQt5Gui.so., function: QPainter::begin(QPaintDevice*)+0x15
[6]: address: 0x7fe6f67b41f8, file: /lib64/libQt5Widgets.so., function: QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*)+0xbb
[7]: address: 0x7fe6f678a6bc, file: /lib64/libQt5Widgets.so., function: +0x1746b
[8]: address: 0x7fe6f678a871, file: /lib64/libQt5Widgets.so., function: +0x17487
[9]: address: 0x7fe6f67a26b5, file: /lib64/libQt5Widgets.so., function: QWidgetPrivate::syncBackingStore()+0xa
[10]: address: 0x7fe6f67bace8, file: /lib64/libQt5Widgets.so., function: QWidget::event(QEvent*)+0x30
[11]: address: 0x7fe6f68d0a68, file: /lib64/libQt5Widgets.so., function: QMainWindow::event(QEvent*)+0x6
[12]: address: 0x7fe6f677ae95, file: /lib64/libQt5Widgets.so., function: QApplicationPrivate::notify_helper(QObject*, QEvent*)+0x8
[13]: address: 0x7fe6f678283a, file: /lib64/libQt5Widgets.so., function: QApplication::notify(QObject*, QEvent*)+0x21
[14]: address: 0x7fe6f46da376, file: /lib64/libQt5Core.so., function: QCoreApplication::notifyInternal2(QObject*, QEvent*)+0x8
[15]: address: 0x7fe6f46dd09b, file: /lib64/libQt5Core.so., function: QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*)+0x20
[16]: address: 0x7fe6f472aec7, file: /lib64/libQt5Core.so., function: +0x2beec
[17]: address: 0x7fe6f0e8f8ad, file: /lib64/libglib-2.0.so., function: g_main_context_dispatch+0x15
[18]: address: 0x7fe6f0e8fc78, file: /lib64/libglib-2.0.so., function: +0x4cc7
[19]: address: 0x7fe6f0e8fd10, file: /lib64/libglib-2.0.so., function: g_main_context_iteration+0x3
[20]: address: 0x7fe6f472ac13, file: /lib64/libQt5Core.so., function: QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)+0x6
[21]: address: 0x7fe6bda39065, file: /lib64/libQt5XcbQpa.so., function: +0xd306
[22]: address: 0x7fe6f46d912b, file: /lib64/libQt5Core.so., function: QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>)+0x13
[23]: address: 0x7fe6f46e15b6, file: /lib64/libQt5Core.so., function: QCoreApplication::exec()+0x9
[24]: address: 0x5bd646, file: planetary_image, function: main+0x99
[25]: address: 0x7fe6f379218b, file: /lib64/libc.so., function: __libc_start_main+0xe
[26]: address: 0x5bcb3a, file: planetary_image, function: _start+0x2

I will try to build a previous or stable version of planetary imager.

@src386
Copy link
Author

src386 commented Jul 1, 2018

No luck with Planetary Imager 0.7.0 :(
I will try with debian 9.

@src386
Copy link
Author

src386 commented Jul 1, 2018

Works with debian 9.
So it's an issue with Fedora 28.

@src386
Copy link
Author

src386 commented Jul 8, 2018

I dockerize Planetary Imager so I can use it on Fedora 28.
https://hub.docker.com/r/src386/docker-planetaryimager/

@GreatAttractor
Copy link
Collaborator

Does it only happen with the ZWO camera? Do you have a regular USB webcam you could try?

@src386
Copy link
Author

src386 commented Jul 8, 2018

Works with laptop webcam.

@Plutonium5793
Copy link

I too use Fedora 28 and have had this problem since Fedora 26 (26 was ok; 27 was not). Works with webcam on my computer, not with my zwo cameras (178c and 120m). It runs fine on Linux-Astronomy which uses Ubuntu 16. All that info gathered on the same laptop computer.

@GuLinux
Copy link
Owner

GuLinux commented Jun 3, 2019

Hi,
I put a new builds system in place, with builds for Fedora 29, 30 and 31 (28 is EOL).

I had a go with virtual machines on both fedora 29 and 30, and didn't encounter the issue. Can you confirm whether I can close it?

Cheers,
Marco

@pijulius
Copy link

pijulius commented Jun 4, 2019

Hi Marco,

I can confirm this on Fedora 30 and the latest PI release. Also have an ASI183MC and not sure if its because the camera isn't recognized or because of this bug on fedora.

Another thing that I noticed is that the program never exits even on pressing the Quit menu, have to kill it to make it exit.

Please let me know if there is anything I can help to track down these, already compiled PI from source so can test easily if needed.

Thank you in advance!
Julius

@GuLinux
Copy link
Owner

GuLinux commented Jun 9, 2019

Hi,
I was able to isolate the behaviour and fixed the issue in master, please look at 0.7.70_20190609_ci120.
It's worth noting that compiling from source won't work, as you also need to compile opencv and libusb from scratch instead of using fedora packages.
You might also need to remove the $HOME/.ZWO directory since I noticed that when the app crashes when scanning for cameras it creates an invalid XML file in that directory that makes the ASI SDK crash again.

Please let me know if this works for you,
Marco

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

Successfully merging a pull request may close this issue.

5 participants