Bug 436939 - startkde: "Could not start Plasma session" xmessage in Wayland session in VirtualBox
Summary: startkde: "Could not start Plasma session" xmessage in Wayland session in Vir...
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-crash (show other bugs)
Version: 5.21.3
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: drkonqi, wayland
Depends on:
Blocks:
 
Reported: 2021-05-11 17:25 UTC by Eric R
Modified: 2022-01-17 19:35 UTC (History)
3 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eric R 2021-05-11 17:25:14 UTC
Application: kde-open5 (5.21.3)

Qt Version: 5.15.2
Frameworks Version: 5.80.0
Operating System: Linux 5.11.12-300.fc34.x86_64 x86_64
Windowing System: Wayland
Drkonqi Version: 5.21.3
Distribution: Fedora 34 (KDE Plasma)

-- Information about the crash:
- What I was doing when the application crashed:
I had just installed Fedora 34 Plasma in a VM in VirutualBox. I added the Guest Additions CD to the VM, and I was mounting the CD when the session went black, and showed an xmessage dialog with the message "startkde: Could not start Plasma session." I am running a Wayland session.
FWIW, the host is Ubuntu MATE 20.04.2
Also FWIW, I saw this a few times during installation, and using an Xsession worked better.

- Unusual behavior I noticed:
The black screen with xmessage dialog described above.
Thanks!

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: KIO Client (kde-open5), signal: Aborted

[KCrash Handler]
#4  0x00007f7884b6e292 in raise () from /lib64/libc.so.6
#5  0x00007f7884b578a4 in abort () from /lib64/libc.so.6
#6  0x00007f7884fd042d in QMessageLogger::fatal(char const*, ...) const () from /lib64/libQt5Core.so.5
#7  0x00007f78810d6ef3 in QtWaylandClient::QWaylandDisplay::checkError() const [clone .cold] () from /lib64/libQt5WaylandClient.so.5
#8  0x00007f78810e56fa in QtWaylandClient::QWaylandDisplay::flushRequests() () from /lib64/libQt5WaylandClient.so.5
#9  0x00007f78851ce4fd in void doActivate<false>(QObject*, int, void**) () from /lib64/libQt5Core.so.5
#10 0x00007f78851ea6d2 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#11 0x00007f788519c9b2 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#12 0x00007f78851a4544 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5
#13 0x000055c9322474f5 in main ()
[Inferior 1 (process 2370) detached]

Possible duplicates by query: bug 436863, bug 435427, bug 433524, bug 432084, bug 431077.

Reported using DrKonqi
This report was filed against 'kde' because the product 'kde-open5' could not be located in Bugzilla. Add it to drkonqi's mappings file!
Comment 1 Nate Graham 2022-01-12 18:14:38 UTC
A lot has changed since then, and I don't recommend using the Wayland session in any Plasma version prior to 5.23. Can you try again in 5.23 to see if it's still happening? Thanks!
Comment 2 Eric R 2022-01-17 19:02:15 UTC
(In reply to Nate Graham from comment #1)
> A lot has changed since then, and I don't recommend using the Wayland
> session in any Plasma version prior to 5.23. Can you try again in 5.23 to
> see if it's still happening? Thanks!

I haven't been able to update my Fedora 34 VM to try this again. The X11 session isn't working much better than the Wayland session, and I can't run much of anything on this VM. I think we should close this bug, because I think my VM setup is the real problem, and there doesn't seem to be a way for me to provide more useful info.

Thanks anyhow!
Comment 3 Nate Graham 2022-01-17 19:35:32 UTC
OK, thanks for checking again.