Bug 1870137 - plasmashell aborted with the error The Wayland connection experienced a fatal error: Invalid argument
Summary: plasmashell aborted with the error The Wayland connection experienced a fatal...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: plasma-workspace
Version: 33
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: KDE SIG
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-08-19 12:28 UTC by Matt Fagnani
Modified: 2021-11-30 16:21 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2021-11-30 16:21:14 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
KDE Software Compilation 424879 0 NOR UNCONFIRMED plasmashell aborted shortly after logging in with the error The Wayland connection experienced a fatal error: Invalid ar... 2021-02-04 04:27:38 UTC

Description Matt Fagnani 2020-08-19 12:28:18 UTC
Description of problem:

I was using Plasma 5.19.4 on Wayland in Fedora 33. I set the desktop to use the Application Menu by right-clicking on the button at the bottom left of the screen, selecting Show Alternatives > Application Menu > Switch. I quickly left-clicked to open the Application Menu more than 20 times. The Task Manager at the bottom of the screen disappeared and reappeared automatically. plasmashell aborted with the message The Wayland connection experienced a fatal error: Invalid argument

Aug 19 07:33:06 plasmashell[7233]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
Aug 19 07:33:06 plasmashell[7233]: kf.plasma.quick: Couldn't create KWindowShadow for PlasmaQuick::Dialog_QML_183(0x55cfa49ab270, name="popupWindow")
Aug 19 07:33:06 plasmashell[7233]: kf.plasma.quick: Couldn't create KWindowShadow for PlasmaQuick::Dialog_QML_183(0x55cfa49ab270, name="popupWindow")
Aug 19 07:33:06 plasmashell[7233]: kf.plasma.quick: Couldn't create KWindowShadow for PlasmaQuick::Dialog_QML_183(0x55cfa49ab270, name="popupWindow")
Aug 19 07:33:06 plasmashell[7233]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
Aug 19 07:33:06 plasmashell[7233]: kf.plasma.quick: Couldn't create KWindowShadow for PlasmaQuick::Dialog_QML_183(0x55cfa49ab270, name="popupWindow")
Aug 19 07:33:06 plasmashell[7233]: kf.plasma.quick: Couldn't create KWindowShadow for PlasmaQuick::Dialog_QML_183(0x55cfa49ab270, name="popupWindow")
Aug 19 07:33:06 plasmashell[7233]: kf.plasma.quick: Couldn't create KWindowShadow for PlasmaQuick::Dialog_QML_183(0x55cfa49ab270, name="popupWindow")
Aug 19 07:33:07 plasmashell[7233]: The Wayland connection experienced a fatal error: Invalid argument

Application: Plasma (plasmashell), signal: Aborted

[KCrash Handler]
#4  __GI_raise (sig=<optimized out>) at ../sysdeps/unix/sysv/linux/raise.c:49
#5  0x00007f47478438a4 in __GI_abort () at abort.c:79
#6  0x00007f4747c65a7f in qt_message_fatal (message=<synthetic pointer>..., context=...) at global/qlogging.cpp:1914
#7  QMessageLogger::fatal (this=this@entry=0x7fffc8df3260, msg=msg@entry=0x7f4736413dc8 "The Wayland connection experienced a fatal error: %s") at global/qlogging.cpp:893
#8  0x00007f47363a3640 in QtWaylandClient::QWaylandDisplay::checkError (this=<optimized out>) at /usr/include/qt5/QtCore/qlogging.h:90
#9  0x00007f47363a368e in QtWaylandClient::QWaylandDisplay::flushRequests (this=0x55cfa32d54a0) at qwaylanddisplay.cpp:209
#10 0x00007f4747e5dfb0 in doActivate<false> (sender=0x55cfa32fae50, signal_index=4, argv=0x7fffc8df3340, argv@entry=0x0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:395
#11 0x00007f4747e587f8 in QMetaObject::activate (sender=sender@entry=0x55cfa32fae50, m=m@entry=0x7f47480e6ee0 <QAbstractEventDispatcher::staticMetaObject>, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at kernel/qobject.cpp:3930
#12 0x00007f4747e2baf7 in QAbstractEventDispatcher::awake (this=this@entry=0x55cfa32fae50) at .moc/moc_qabstracteventdispatcher.cpp:149
#13 0x00007f4747e7abac in QEventDispatcherGlib::processEvents (this=0x55cfa32fae50, flags=...) at kernel/qeventdispatcher_glib.cpp:430
#14 0x00007f4747e2d91b in QEventLoop::exec (this=this@entry=0x7fffc8df3460, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136
#15 0x00007f4747e355a6 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:118
#16 0x000055cfa15b9705 in main (argc=<optimized out>, argv=0x7fffc8df3670) at /usr/src/debug/plasma-workspace-5.19.4-2.fc33.x86_64/shell/main.cpp:224
[Inferior 1 (process 7233) detached]

Version-Release number of selected component (if applicable):
plasma-workspace-5.19.4-2.fc33.x86_64
plasma-wayland-protocols-1.1.1-1.fc33.x86_64
kf5-kwayland-5.73.0-1.fc33.x86_64
qt5-qtbase-5.14.2-8.fc33.x86_64

How reproducible:
I've seen plasmashell abort 3 times with this error. The crash occurred a low proportion of times I've clicked on the Application Menu Button

Steps to Reproduce:
1. Boot a Fedora 33 KDE Plasma installation with kwin-wayland, plasma-workspace-wayland, and their dependencies installed
2. Log in to Plasma on Wayland from sddm
3. set the desktop to use the Application Menu by right-clicking on the menu button at the bottom left of the screen, selecting Show Alternatives > Application Menu > Switch. 
4. quickly left-click to open the Application Menu until plasmashell crashes.

Actual results:
plasmashell aborted with the error The Wayland connection experienced a fatal error: Invalid argument

Expected results:
No crash would happen.

Additional info:

I reported this problem at https://bugs.kde.org/show_bug.cgi?id=424879
David Edmundson wrote "Can you confirm your version of plasma-wayland-protocols please" there. plasma-wayland-protocols wasn't installed the first time I saw plasmashell crash with this error. I installed plasma-wayland-protocols-1.1.1-1.fc33.x86_64 which was present during the last 2 crashes. 

plasmashell segmentation faulted when I've quickly left-clicked to open the Application Menu at other times in the last day with traces like those I reported at https://bugzilla.redhat.com/show_bug.cgi?id=1777733 and https://bugzilla.redhat.com/show_bug.cgi?id=1723018 The crashes might involve a race condition in which the Wayland surface of the Application menu was occasionally freed or corrupted before it was used.

Comment 1 Ben Cotton 2021-11-04 17:34:35 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Ben Cotton 2021-11-30 16:21:14 UTC
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.