Summary: | lxqt-base/lxqt-panel segfaults since qt 5.9.2 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | acab |
Component: | Current packages | Assignee: | LxQt maintainers <lxqt> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | chiitoo, jarymut+gentoo.bugs, orzel, paolo.pedroni, tdalman |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://github.com/gentoo/gentoo/pull/7026 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | emerge info (qt and panel) |
Description
acab
2017-10-10 10:15:17 UTC
I can confirm. Not only that, but it doesn't compile anymore. I tried re-emerging lxqt-panel hoping to fix the crash, but I got : cd /tmp/portage/lxqt-base/lxqt-panel-0.11.0/work/lxqt-panel-0.11.0_build/plugin-volume && /usr/bin/x86_64-pc-linux-gnu-g++ -DLXQT_DATA_DIR=\"/usr/share\" -DLXQT_ETC_XDG_DIR=\"/etc/xdg\" -DLXQT_GRAPHICS_DIR=\"/usr/share/lxqt/graphics\" -DLXQT_RELATIVE_SHARE_DIR=\"lxqt\" -DLXQT_RELATIVE_SHARE_TRANSLATIONS_DIR=\"lxqt/translations\" -DLXQT_SHARE_DIR=\"/usr/share/lxqt\" -DLXQT_SHARE_TRANSLATIONS_DIR=\"/usr/share/lxqt/translations\" -DLXQT_VERSION=\"0.11.0\" -DPLUGIN_DIR=\"/usr/lib64/lxqt-panel\" -DQT_CORE_LIB -DQT_DBUS_LIB -DQT_GUI_LIB -DQT_NO_DEBUG -DQT_SVG_LIB -DQT_USE_QSTRINGBUILDER -DQT_WIDGETS_LIB -DQT_X11EXTRAS_LIB -DQT_XML_LIB -DUSE_ALSA -DWITH_CLOCK_PLUGIN -DWITH_DESKTOPSWITCH_PLUGIN -DWITH_MAINMENU_PLUGIN -DWITH_QUICKLAUNCH_PLUGIN -DWITH_SHOWDESKTOP_PLUGIN -DWITH_STATUSNOTIFIER_PLUGIN -DWITH_TASKBAR_PLUGIN -DWITH_TRAY_PLUGIN -Dvolume_EXPORTS -I/tmp/portage/lxqt-base/lxqt-panel-0.11.0/work/lxqt-panel-0.11.0_build/plugin-volume -I/tmp/portage/lxqt-base/lxqt-panel-0.11.0/work/lxqt-panel-0.11.0/plugin-volume -I/tmp/portage/lxqt-base/lxqt-panel-0.11.0/work/lxqt-panel-0.11.0_build/plugin-volume/volume_autogen/include -isystem /usr/include/qt5 -isystem /usr/include/qt5/QtWidgets -isystem /usr/include/qt5/QtGui -isystem /usr/include/qt5/QtCore -isystem /usr/lib64/qt5/mkspecs/linux-g++ -isystem /usr/include/lxqt -isystem /usr/include/lxqt/LXQt -isystem /usr/include/KF5/KWindowSystem -isystem /usr/include/KF5 -isystem /usr/include/qt5/QtDBus -isystem /usr/include/qt5/QtX11Extras -isystem /usr/include/qt5xdg -isystem /usr/include/qt5/QtXml -isystem /usr/include/qt5xdgiconloader -isystem /usr/include/qt5xdgiconloader/2.0.0 -isystem /usr/include/qt5/QtSvg -isystem /usr/include/lxqt-globalkeys -DNDEBUG -march=native -pipe -O2 -std=c++11 -fvisibility=hidden -fvisibility-inlines-hidden -fno-exceptions -fPIC -Wall -fPIC -std=gnu++11 -o CMakeFiles/volume.dir/volume_autogen/mocs_compilation.cpp.o -c /tmp/portage/lxqt-base/lxqt-panel-0.11.0/work/lxqt-panel-0.11.0_build/plugin-volume/volume_autogen/mocs_compilation.cpp /tmp/portage/lxqt-base/lxqt-panel-0.11.0/work/lxqt-panel-0.11.0/plugin-kbindicator/src/x11/kbdlayout.cpp:36:18: error: ‘_explicit’ does not name a type #define explicit _explicit ^ /tmp/portage/lxqt-base/lxqt-panel-0.11.0/work/lxqt-panel-0.11.0/plugin-kbindicator/src/x11/kbdlayout.cpp:36:18: error: ‘_explicit’ does not name a type #define explicit _explicit ^ /tmp/portage/lxqt-base/lxqt-panel-0.11.0/work/lxqt-panel-0.11.0/plugin-kbindicator/src/x11/kbdlayout.cpp:36:18: error: ‘_explicit’ does not name a type #define explicit _explicit ^ /tmp/portage/lxqt-base/lxqt-panel-0.11.0/work/lxqt-panel-0.11.0/plugin-kbindicator/src/x11/kbdlayout.cpp:36:18: error: ‘_explicit’ does not name a type #define explicit _explicit ^ /tmp/portage/lxqt-base/lxqt-panel-0.11.0/work/lxqt-panel-0.11.0/plugin-kbindicator/src/x11/kbdlayout.cpp:36:18: error: ‘_explicit’ does not name a type #define explicit _explicit ^ /tmp/portage/lxqt-base/lxqt-panel-0.11.0/work/lxqt-panel-0.11.0/plugin-kbindicator/src/x11/kbdlayout.cpp:36:18: error: ‘_explicit’ does not name a type #define explicit _explicit ^ Until I (or someone else) gets the 0.12.0 packages sorted and out (hopefully it's not too far away from now), if one feels adventurous enough, one could try the live ebuilds from the qt-overlay. They should be especially interesting in cases like this, where it's not even possible to re-build the current packages. One should note though, that there definitely may be issues lurking about, that I'm not aware of at the time of writing, and that they're only for those willing to break their system. :] Just drop the patch in the github issue referenced in the original bug report in /etc/portage/patches/lxqt-base/lxqt-panel/ and you're good to go, without messing with overlays and live ebuild... I've been running the 0.12 ebuilds from this PR for a while now: https://github.com/gentoo/gentoo/pull/5806 Segfaults are gone in both the panel and lxqt-runner (while a rebuild with the patch did not help with those, at least for me) (In reply to Andy Kittner from comment #4) > I've been running the 0.12 ebuilds from this PR for a while now: > https://github.com/gentoo/gentoo/pull/5806 Ah, they've gone for a full bump with that one. Thanks for the heads-up; this saves me from duplicating work! dev-qt/qtgui-5.9 is now stable, but lxqt-0.12 is not in the tree; after clean upgrade, lxqt is not starting I'm also broken. My desktop environment won't start with similar back traces to the original post here. Is lxqt testing part of the qt stabilization process? I suppose not? lxqt in gentoo is basically unmaintained, it's been broken in various ways for quite some time now. I've moved to another desktop ;-( Same thing here. lxqt-panel causes segfaults like: lxqt-panel[7290]: segfault at 7f71e8ba23b3 ip 00007f71eb5d0990 sp 00007ffff49049e0 error 7 in libQt5Gui.so.5.9.4[7f71eb476000+48d000] Maybe version bump request in Bug 605266 - lxqt-base/lxqt-meta-0.12.0 version bump could be addressed. I use the ebuilds from https://github.com/gentoo/gentoo/pull/7026 and it work fine for me on amd64. The ebuilds from that pull request worked for me on x86, too, though it was a bit tedious to integrate them into my local repository. Useful hint how to check out that branch: https://stackoverflow.com/a/14969986 Since 0.13.0 is finally in Portage, it should be safe to say this is fixed with it. I imagine we'll get the stable 0.11.0 replaced with it as soon as possible. |