Bug 433767 - Crash while moving panel to second display
Summary: Crash while moving panel to second display
Status: RESOLVED DUPLICATE of bug 438839
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-crash (show other bugs)
Version: 5.20.5
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2021-03-01 01:15 UTC by Ashton
Modified: 2021-10-04 14:24 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
New crash information added by DrKonqi (2.86 KB, text/plain)
2021-04-19 11:06 UTC, Martin Ueding
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ashton 2021-03-01 01:15:13 UTC
Application: plasmashell (5.20.5)

Qt Version: 5.15.2
Frameworks Version: 5.79.0
Operating System: Linux 5.10.18-200.fc33.x86_64 x86_64
Windowing system: Wayland
Distribution: Fedora 33 (Workstation Edition)

-- Information about the crash:
- What I was doing when the application crashed:
Moving the default panel to the left display.
- Unusual behavior I noticed:
Both screens went black, panel disappeared, can not open apps (except for crash reporting assistant and from there opened web browser), can not easily logout or do anything really.

-- Backtrace:
Application: Plasma (plasmashell), signal: Aborted

[KCrash Handler]
#4  0x00007fcdf8d859d5 in raise () from /lib64/libc.so.6
#5  0x00007fcdf8d6e8a4 in abort () from /lib64/libc.so.6
#6  0x00007fcdf91b148f in QMessageLogger::fatal(char const*, ...) const () from /lib64/libQt5Core.so.5
#7  0x00007fcdf7088ed4 in QtWaylandClient::QWaylandDisplay::checkError() const () from /lib64/libQt5WaylandClient.so.5
#8  0x00007fcdf70890ea in QtWaylandClient::QWaylandDisplay::flushRequests() () from /lib64/libQt5WaylandClient.so.5
#9  0x00007fcdf93b13c0 in void doActivate<false>(QObject*, int, void**) () from /lib64/libQt5Core.so.5
#10 0x00007fcdf93ce72c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#11 0x00007fcdf938057b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#12 0x00007fcdf93881b4 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5
#13 0x00005579ee6e47ca in main ()
[Inferior 1 (process 2320) detached]

Possible duplicates by query: bug 433486, bug 432584, bug 432560, bug 432358, bug 432261.

Reported using DrKonqi
Comment 1 Nate Graham 2021-03-08 21:43:36 UTC
Not much we can say about this with no debug symbols. Can you install some, reproduce the crash, and attach a new symbolicated backtrace? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Fedora

Thanks!
Comment 2 Bug Janitor Service 2021-03-23 04:33:44 UTC
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!
Comment 3 Bug Janitor Service 2021-04-07 04:33:38 UTC
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!
Comment 4 Martin Ueding 2021-04-19 11:06:48 UTC
Created attachment 137701 [details]
New crash information added by DrKonqi

plasmashell (5.20.5) using Qt 5.15.2

What I was doing when the application crashed:

I have just launched Plasma on Wayland. I have set up my two external screens. They are connected via an USB-C Dock (Lenovo) to a Lenovo ThinkPad T490.

When dragging the main panel (window switcher, clock, indicators) to a different screen, it looked like plasmashell has crashed. The screen went black. Then one window re-appeared centered on the middle screen. The windows were still there, I can launch applications with krunner. There is just no panel. I'll try to restart plasmashell once I have submitted this report such that I don't lose the trace.

-- Backtrace (Reduced):
#6  0x00007f832097148f in qt_message_fatal (message=<synthetic pointer>..., context=...) at global/qlogging.cpp:1914
#7  QMessageLogger::fatal(char const*, ...) const (this=this@entry=0x7fffce10bf70, msg=msg@entry=0x7f831e979ed0 "The Wayland connection experienced a fatal error: %s") at global/qlogging.cpp:893
#8  0x00007f831e8fded4 in QtWaylandClient::QWaylandDisplay::checkError() const (this=<optimized out>) at qwaylanddisplay.cpp:211
#9  0x00007f831e8fe0ea in QtWaylandClient::QWaylandDisplay::flushRequests() (this=0x564600d51360) at qwaylanddisplay.cpp:222
#10 0x00007f8320b713c0 in doActivate<false>(QObject*, int, void**) (sender=0x564600d6fc00, signal_index=4, argv=0x7fffce10c080, argv@entry=0x0) at kernel/qobject.cpp:3898
Comment 5 Martin Ueding 2021-04-19 11:09:13 UTC
I have just restarted plasmashell, it came right back up. And then I have dragged the panel to the middle screen; this time without any issues.

Hopefully the backtrace will be of some use. I'll come back if it should appear again.
Comment 6 Nate Graham 2021-08-31 19:43:44 UTC
No, it is still not actionable. :( There's just no information there.
Comment 7 David Edmundson 2021-10-03 19:51:38 UTC

*** This bug has been marked as a duplicate of bug 439321 ***
Comment 8 Nate Graham 2021-10-04 14:24:23 UTC

*** This bug has been marked as a duplicate of bug 438839 ***