https://bugs.kde.org/show_bug.cgi?id=481937
Martin Riethmayer <rip...@freakmail.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rip...@freakmail.de
--- Comment #5 from Martin Riethmayer <rip...@freakmail.de> ---
I've investigated a bit further. To do so, I enabled 3d acceleration and
installed Neon, then disabled 3d acceleration again.
If you do *not* enable auto-login, you'll get as far as the SDDM login screen.
You can now switch TTYs (e.g. by hitting (Right-)CTRL+F3).
I've updated the guest-additions manually from the command line to match the
version of the VBox on the host (in my case: 7.0.14 is running on host, the
GuestAdditions now are also installed at version 7.0.14 inside the Guest -
check with "(Right-)CTRL+N" and selecting "runtime").
This does not make any difference, but at least I'm fairly certain now, that
the mismatch of the GuestAdditions shipped by Neon (6.0.0) and the actual VBox
Host version are not to blame.
>From journalctl, I can see the failed attempts to log in to a Wayland session
(X session works), but I have no clue if any of the messages actually mean
anything.
When logging in, quite a few things seem to get done, e.g.
Finished KSpash "ready" Stage.
or
Reached target Startup of XDG autostart applications.
A few warnings or suspicious messages that I noticed are:
- VMware: No 3D enables (0, success).
- libEGL warning: egl: failed to create dri2 screen (happens quite often)
- qt.qpa.wayland: Creating a fake screen in order for Qt not to crash (happens
quite often)
I don't know how to debug further ...
--
You are receiving this mail because:
You are watching all bug changes.
