Summary: | KDEConnect reply to Signal message crashed on Wayland | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | pyro4hell |
Component: | general | Assignee: | David Edmundson <kde> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | christian.rohmann, nate, plasma-bugs |
Priority: | NOR | Keywords: | drkonqi |
Version: | 5.18.0 | ||
Target Milestone: | 1.0 | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi |
Description
pyro4hell
2020-02-16 09:14:29 UTC
Is it reproducible in a reliable way? If so can I see output of WAYLAND_DEBUG=1 plasmashell --replace and triggering can't reproduce. May be one of those other bugs that crash plasma on login and it was just coincidence Created attachment 126996 [details]
New crash information added by DrKonqi
plasmashell (5.18.3) using Qt 5.14.1
- What I was doing when the application crashed:
Using two displays and switching / left-right scrolling between the desktops.
-- Backtrace (Reduced):
#8 0x00007f99f0eb496c in () at /usr/lib/libQt5Core.so.5
#9 0x00007f99ec447128 in () at /usr/lib/libQt5WaylandClient.so.5
#10 0x00007f99ec457b51 in QtWaylandClient::QWaylandDisplay::flushRequests() () at /usr/lib/libQt5WaylandClient.so.5
#11 0x00007f99f1101540 in () at /usr/lib/libQt5Core.so.5
#12 0x00007f99f1104d62 in QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) () at /usr/lib/libQt5Core.so.5
Created attachment 127101 [details]
New crash information added by DrKonqi
plasmashell (5.18.3) using Qt 5.14.1
Using a Meet in Chrome while having Firefox, Thunderbird and an instance of VSCode open.
-- Backtrace (Reduced):
#8 0x00007f203f92b96c in () at /usr/lib/libQt5Core.so.5
#9 0x00007f203aefe128 in () at /usr/lib/libQt5WaylandClient.so.5
#10 0x00007f203af0eb51 in QtWaylandClient::QWaylandDisplay::flushRequests() () at /usr/lib/libQt5WaylandClient.so.5
#11 0x00007f203fb78540 in () at /usr/lib/libQt5Core.so.5
#12 0x00007f203fb7bd62 in QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) () at /usr/lib/libQt5Core.so.5
> #9 0x00007f203aefe128 in () at /usr/lib/libQt5WaylandClient.so.5 > #10 0x00007f203af0eb51 in QtWaylandClient::QWaylandDisplay::flushRequests() () at /usr/lib/libQt5WaylandClient.so.5 We will need to know what goes inside () to have any hope of debugging this any further. If you're still experiencing it, can you please install debug symbols and get a new backtrace? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Thanks! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |