Summary: | [Wayland] plasmashell gets SIGSEGV after clicking on Application Menu for second time | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | magiblot |
Component: | Panel | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED DOWNSTREAM | ||
Severity: | crash | CC: | magiblot |
Priority: | NOR | ||
Version: | 5.13.2 | ||
Target Milestone: | 1.0 | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
magiblot
2018-06-22 16:34:11 UTC
I obtained a new backtrace with mesa debug symbols. In this occasion the version of plasma is 5.13.2 and the version of mesa is git-103087.ab2643e4b0.
If you believe this has nothing to do with the plasma code, I shall report the bug to the mesa developers.
> #0 0x00007fffd25a4476 in intel_miptree_level_has_hiz (mt=0x0, level=0) at intel_mipmap_tree.c:1953
> #1 0x00007fffd25a2890 in intel_renderbuffer_has_hiz (irb=irb@entry=0x555558744d90) at intel_fbo.c:930
> #2 0x00007fffd2577845 in brw_fast_clear_depth (ctx=0x5555561a7660) at brw_clear.c:114
> #3 0x00007fffd2577845 in brw_clear (ctx=0x5555561a7660, mask=50) at brw_clear.c:258
> #4 0x00007ffff575e82d in QSGBatchRenderer::Renderer::renderBatches() () at /usr/lib/libQt5Quick.so.5
> #5 0x00007ffff5764103 in QSGBatchRenderer::Renderer::render() () at /usr/lib/libQt5Quick.so.5
> #6 0x00007ffff57544ee in QSGRenderer::renderScene(QSGBindable const&) () at /usr/lib/libQt5Quick.so.5
> #7 0x00007ffff57549bc in QSGRenderer::renderScene(unsigned int) () at /usr/lib/libQt5Quick.so.5
> #8 0x00007ffff578f030 in QSGDefaultRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () at /usr/lib/libQt5Quick.so.5
> #9 0x00007ffff57f2db5 in QQuickWindowPrivate::renderSceneGraph(QSize const&) () at /usr/lib/libQt5Quick.so.5
> #10 0x00007ffff5781275 in () at /usr/lib/libQt5Quick.so.5
> #11 0x00007ffff57820a5 in () at /usr/lib/libQt5Quick.so.5
> #12 0x00007ffff1f0f935 in QWindow::event(QEvent*) () at /usr/lib/libQt5Gui.so.5
> #13 0x00007ffff57fe65c in QQuickWindow::event(QEvent*) () at /usr/lib/libQt5Quick.so.5
> #14 0x00007ffff799b4a4 in PlasmaQuick::Dialog::event(QEvent*) () at /usr/lib/libKF5PlasmaQuick.so.5
> #15 0x00007ffff2fa6a74 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5
> #16 0x00007ffff2fae341 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5
> #17 0x00007ffff195ccb9 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5
> #18 0x00007ffff1f04146 in QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*) () at /usr/lib/libQt5Gui.so.5
> #19 0x00007ffff1f04e7e in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () at /usr/lib/libQt5Gui.so.5
> #20 0x00007ffff1edeb7c in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Gui.so.5
> #21 0x00007fffe36ed72d in () at /usr/lib/libQt5XcbQpa.so.5
> #22 0x00007ffff195b94c in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
> #23 0x00007ffff1963c46 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5
> #24 0x000055555557064e in ()
> #25 0x00007ffff0fc906b in __libc_start_main () at /usr/lib/libc.so.6
> #26 0x0000555555570aca in _start ()
This is indeed a bug in the intel OpenGL drivers. Please report this issue directly to intel/Mesa developers via https://bugs.freedesktop.org/ Thanks for the answer. (In reply to Christoph Feck from comment #2) > This is indeed a bug in the intel OpenGL drivers. Please report this issue > directly to intel/Mesa developers via https://bugs.freedesktop.org/ I submitted the bug 3 months ago: https://bugs.freedesktop.org/show_bug.cgi?id=107058 Even though I didn't get an answer, I found starting Plasma this way (from the tty) solves the issue: > QT_QPA_PLATFORM=wayland-egl startplasmacompositor Which leads to the questions: how does the QT_QPA_PLATFORM variable affect Plasma (only a KDE developer can answer this), and could this be a QT bug instead? Cheers. |