FS#50492 - [qt5-base] stellarium segfaults

Attached to Project: Arch Linux
Opened by Bernhard Landauer (oberon) - Tuesday, 23 August 2016, 01:23 GMT
Last edited by Antonio Rojas (arojas) - Saturday, 27 August 2016, 00:30 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Antonio Rojas (arojas)
Felix Yan (felixonmars)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

$ stellarium
Segmentation fault (core dumped)

package version 0.15.0-1
rebuild with current PKGBUILD does not help.
This task depends upon

Closed by  Antonio Rojas (arojas)
Saturday, 27 August 2016, 00:30 GMT
Reason for closing:  Upstream
Comment by siphr (siphr) - Tuesday, 23 August 2016, 09:51 GMT
Tested extra/stellarium 0.15.0-1 on Lenovo x230.
No segfaults, runs smoothly.
Comment by Bernhard Landauer (oberon) - Wednesday, 24 August 2016, 01:27 GMT
For some people on Manjaro the package is working, some have the same issue - strange!
https://forum.manjaro.org/t/stable-update-2016-08-17-texlive-kernels-lumina-calamares-mate/7567/77
Comment by Doug Newgard (Scimmia) - Wednesday, 24 August 2016, 14:59 GMT
Backtrace? Are you on Arch or Manjaro?
Comment by Bernhard Landauer (oberon) - Wednesday, 24 August 2016, 15:16 GMT
I'm running the package in Manjaro, yes...
Looks like a qt error?

==13252== Memcheck, a memory error detector
==13252== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==13252== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==13252== Command: stellarium
==13252==
==13252== Invalid read of size 8
==13252== at 0x65AB6BF: ??? (in /usr/lib/libQt5Widgets.so.5.7.0)
==13252== by 0x65AC58E: QApplication::setStyle(QStyle*) (in /usr/lib/libQt5Widgets.so.5.7.0)
==13252== by 0x15847919: Qt5CTPlatformTheme::Qt5CTPlatformTheme() (in /usr/lib/qt/plugins/platformthemes/libqt5ct.so)
==13252== by 0x15844CFF: Qt5CTPlatformThemePlugin::create(QString const&, QStringList const&) (in /usr/lib/qt/plugins/platformthemes/libqt5ct.so)
==13252== by 0x6D999D1: ??? (in /usr/lib/libQt5Gui.so.5.7.0)
==13252== by 0x6DA4347: QGuiApplicationPrivate::createPlatformIntegration() (in /usr/lib/libQt5Gui.so.5.7.0)
==13252== by 0x6DA4CEC: QGuiApplicationPrivate::createEventDispatcher() (in /usr/lib/libQt5Gui.so.5.7.0)
==13252== by 0x78EA3BE: QCoreApplicationPrivate::init() (in /usr/lib/libQt5Core.so.5.7.0)
==13252== by 0x6DA67AE: QGuiApplicationPrivate::init() (in /usr/lib/libQt5Gui.so.5.7.0)
==13252== by 0x65ACAE8: QApplicationPrivate::init() (in /usr/lib/libQt5Widgets.so.5.7.0)
==13252== by 0x56B463: main (in /usr/bin/stellarium)
==13252== Address 0x0 is not stack'd, malloc'd or (recently) free'd
==13252==
==13252==
==13252== Process terminating with default action of signal 11 (SIGSEGV): dumping core
==13252== Access not within mapped region at address 0x0
==13252== at 0x65AB6BF: ??? (in /usr/lib/libQt5Widgets.so.5.7.0)
==13252== by 0x65AC58E: QApplication::setStyle(QStyle*) (in /usr/lib/libQt5Widgets.so.5.7.0)
==13252== by 0x15847919: Qt5CTPlatformTheme::Qt5CTPlatformTheme() (in /usr/lib/qt/plugins/platformthemes/libqt5ct.so)
==13252== by 0x15844CFF: Qt5CTPlatformThemePlugin::create(QString const&, QStringList const&) (in /usr/lib/qt/plugins/platformthemes/libqt5ct.so)
==13252== by 0x6D999D1: ??? (in /usr/lib/libQt5Gui.so.5.7.0)
==13252== by 0x6DA4347: QGuiApplicationPrivate::createPlatformIntegration() (in /usr/lib/libQt5Gui.so.5.7.0)
==13252== by 0x6DA4CEC: QGuiApplicationPrivate::createEventDispatcher() (in /usr/lib/libQt5Gui.so.5.7.0)
==13252== by 0x78EA3BE: QCoreApplicationPrivate::init() (in /usr/lib/libQt5Core.so.5.7.0)
==13252== by 0x6DA67AE: QGuiApplicationPrivate::init() (in /usr/lib/libQt5Gui.so.5.7.0)
==13252== by 0x65ACAE8: QApplicationPrivate::init() (in /usr/lib/libQt5Widgets.so.5.7.0)
==13252== by 0x56B463: main (in /usr/bin/stellarium)
==13252== If you believe this happened as a result of a stack
==13252== overflow in your program's main thread (unlikely but
==13252== possible), you can try to increase the size of the
==13252== main thread stack using the --main-stacksize= flag.
==13252== The main thread stack size used in this run was 8388608.
==13252==
==13252== HEAP SUMMARY:
==13252== in use at exit: 399,494 bytes in 4,377 blocks
==13252== total heap usage: 10,785 allocs, 6,408 frees, 1,976,952 bytes allocated
==13252==
==13252== LEAK SUMMARY:
==13252== definitely lost: 272 bytes in 2 blocks
==13252== indirectly lost: 335 bytes in 5 blocks
==13252== possibly lost: 384 bytes in 1 blocks
==13252== still reachable: 398,503 bytes in 4,369 blocks
==13252== suppressed: 0 bytes in 0 blocks
==13252== Rerun with --leak-check=full to see details of leaked memory
==13252==
==13252== For counts of detected and suppressed errors, rerun with: -v
==13252== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
Killed
Comment by siphr (siphr) - Wednesday, 24 August 2016, 15:20 GMT
I think the right place to report this would be: https://bugs.manjaro.org/.
Comment by Bernhard Landauer (oberon) - Wednesday, 24 August 2016, 15:28 GMT
I've done that. https://bugs.manjaro.org/index.php?do=details&task_id=16
Just since we run the same qt environment with archlinux packages I thought it would be the same. But if there are no issues in arch with this, we'll have to looks elsewhere...
Comment by Antonio Rojas (arojas) - Friday, 26 August 2016, 14:27 GMT
is this reproducible if you unset QT_QPA_PLATFORMTHEME?
Comment by Bernhard Landauer (oberon) - Friday, 26 August 2016, 16:36 GMT
You nailed it of course! Solved by unsetting QT_QPA_PLATFORMTHEME. I was using qt5ct.
Comment by Antonio Rojas (arojas) - Saturday, 27 August 2016, 00:29 GMT
Please report this upstream to the qt5ct developers

Loading...