<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [Wayland] plasmashell gets SIGSEGV after clicking on Application Menu for second time"
href="https://bugs.freedesktop.org/show_bug.cgi?id=107058#c19">Comment # 19</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [Wayland] plasmashell gets SIGSEGV after clicking on Application Menu for second time"
href="https://bugs.freedesktop.org/show_bug.cgi?id=107058">bug 107058</a>
from <span class="vcard"><a class="email" href="mailto:magiblot@hotmail.com" title="magiblot <magiblot@hotmail.com>"> <span class="fn">magiblot</span></a>
</span></b>
<pre>Created <span class=""><a href="attachment.cgi?id=142379" name="attach_142379" title="debug log having applied the patch above">attachment 142379</a> <a href="attachment.cgi?id=142379&action=edit" title="debug log having applied the patch above">[details]</a></span>
debug log having applied the patch above
(In reply to Danylo from <a href="show_bug.cgi?id=107058#c18">comment #18</a>)
It was very kind of you to provide a specific PKGBUILD for this purpose. It
indeed compiled much faster than I expected.
I was able to test the crash again, but got different results. I have been
unable to catch plasmashell getting SIGSEGV. It is just Xwayland who gets
SIGABRT twice and then exits.
I have already seen this before (not back when I opened this report) but
plasmashell would at times still get SIGSEGV. This doesn't seem to be the case
anymore.
Some time ago I found the crash this report is about can be worked around with
'QT_QPA_PLATFORM=wayland-egl', which will force all Qt applications into native
Wayland rendering (and I guess plasmashell is one of them). So Xwayland can be
considered suspect of this issue.
If there is a bug in Qt, Xwayland or another library, then I imagine the
SIGSEGV was caused by either of these messing up before mesa finished rendering
their items (and thus causing the miptree not to be created properly). I guess
your patches just make mesa less vulnerable against this.
I'm enclosing the log for one of the crashes, with INTEL_DEBUG=fbo,mip. I have
no actual knowledge about rendering, so maybe you find more meaning in it.
Thank you very much.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>