[plasmashell] [Bug 417732] KDEConnect reply to Signal message crashed on Wayland
https://bugs.kde.org/show_bug.cgi?id=417732 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|BACKTRACE |WORKSFORME --- Comment #7 from Bug Janitor Service --- 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! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417732] KDEConnect reply to Signal message crashed on Wayland
https://bugs.kde.org/show_bug.cgi?id=417732 --- Comment #6 from Bug Janitor Service --- 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! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417732] KDEConnect reply to Signal message crashed on Wayland
https://bugs.kde.org/show_bug.cgi?id=417732 Nate Graham changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |BACKTRACE CC||n...@kde.org --- Comment #5 from Nate Graham --- > #9 0x7f203aefe128 in () at /usr/lib/libQt5WaylandClient.so.5 > #10 0x7f203af0eb51 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! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417732] KDEConnect reply to Signal message crashed on Wayland
https://bugs.kde.org/show_bug.cgi?id=417732 --- Comment #4 from christian.rohm...@gmx.de --- Created attachment 127101 --> https://bugs.kde.org/attachment.cgi?id=127101&action=edit 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 0x7f203f92b96c in () at /usr/lib/libQt5Core.so.5 #9 0x7f203aefe128 in () at /usr/lib/libQt5WaylandClient.so.5 #10 0x7f203af0eb51 in QtWaylandClient::QWaylandDisplay::flushRequests() () at /usr/lib/libQt5WaylandClient.so.5 #11 0x7f203fb78540 in () at /usr/lib/libQt5Core.so.5 #12 0x7f203fb7bd62 in QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) () at /usr/lib/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417732] KDEConnect reply to Signal message crashed on Wayland
https://bugs.kde.org/show_bug.cgi?id=417732 christian.rohm...@gmx.de changed: What|Removed |Added CC||christian.rohm...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417732] KDEConnect reply to Signal message crashed on Wayland
https://bugs.kde.org/show_bug.cgi?id=417732 --- Comment #3 from christian.rohm...@gmx.de --- Created attachment 126996 --> https://bugs.kde.org/attachment.cgi?id=126996&action=edit 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 0x7f99f0eb496c in () at /usr/lib/libQt5Core.so.5 #9 0x7f99ec447128 in () at /usr/lib/libQt5WaylandClient.so.5 #10 0x7f99ec457b51 in QtWaylandClient::QWaylandDisplay::flushRequests() () at /usr/lib/libQt5WaylandClient.so.5 #11 0x7f99f1101540 in () at /usr/lib/libQt5Core.so.5 #12 0x7f99f1104d62 in QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) () at /usr/lib/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417732] KDEConnect reply to Signal message crashed on Wayland
https://bugs.kde.org/show_bug.cgi?id=417732 --- Comment #2 from pyro4h...@gmail.com --- can't reproduce. May be one of those other bugs that crash plasma on login and it was just coincidence -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417732] KDEConnect reply to Signal message crashed on Wayland
https://bugs.kde.org/show_bug.cgi?id=417732 --- Comment #1 from David Edmundson --- Is it reproducible in a reliable way? If so can I see output of WAYLAND_DEBUG=1 plasmashell --replace and triggering -- You are receiving this mail because: You are watching all bug changes.
