The following results all obtained on virtual machines running in virtualbox
By selecting KDE in the Agama installer under Software. From what I see you skipped that part.
See my original post. The problem arises upon migration from 16.0 to 16.1 using the migration tool. Agama is not involved in this migration. The original 16.0 installation, installed with agama, works perfectly well with the specified d.e. (KDE). The trouble is that the migration tool appears not to pick up the d.e. from the original installation.
Sorry, missed that, being in two similar threads. Eh, what happens if
sudo systemctl enable sddm.service? Does that fix it?startplasma-wayland?i am having a leap 16.0 host with virtualbox 7.2.20 (suse repos) and never managed to bring up not the alpha beta nor the todays RC1 of leap 16.1 up in graphical mode
virtualbox graphics settings are set to “vmsvga”
sddm service is dead (but enabled, green) and its logs show it crashing in x11 or similar output)
i am not very familar with the technical aspects of this situation
a current debian stable works on the same virtualbox on this same leap 16.0 host nicely in graphics runlevel
interesting, the calling from console (logged in as root) with startplasma-wayland brings up graphical.
whats wrong then with some settings that its not directly booting up into this state?
while inside this KDE (whole stuff is as root, right?) systemctl status sddm is still showing as dead. i am a noob.
i can also login oon the console as my testuser and then startplasma-wayland that way as well giving me the testuser desktop i guess. sddm service still dead though.
The sddm service is running fine, the behaviour is normal. Most important is that it is enabled. Once it stated the greeter ( the login screen ) it doesn’t have to “live” any longer. Have a look at what sudo journalctl -b 0 | grep -i sddm shows
If I understand you right, you’re testing Leap 16.1 as a VBox guest, and SDDM doesn’t start properly? Crashes before login?
Also, do you know whether SDDM itself is configured to use Wayland or X11 for the greeter?
If you’re not sure, show the current SDDM configuration cat /etc/sddm.conf.d/*
i was beginning a fresh leap 16.1 alpha somewhen back some months ago and i installed it into a virtualbox 7.x (hosted on a leap 16.0) and then always tried to zypper dup instide the leap 16.1 guest.
Ok, that clarifies the history.
For this VM guest, could you please check whether SDDM itself is enabled and what display server configuration it has?
It would be useful to see
sudo systemctl status display-manager --no-pager
and
cat /etc/sddm.conf.d/*
Share screen shots if it is easier for you.
You should not be starting this as root. Do this as regular user instead.
That may cause issues. The emphasis needs to be on getting the DM working. People have, on other platforms already mentioned font issues. That in itself might be some race condition, just wanted to mention it.
I’ve just upgraded my Leap VBox guest (to Leap 16.1 RC) using the opensuse-migration-tool, and my first time using it.
No issues here. I’m running SDDM with Wayland and Plasma Wayland. (Not sure what race conditions you’re referring to.)
I was not clear. Bypassing the (SD)DM with startplasma-wayland is not resulting in the exact same experience. I’ll see if I can make some screenshots tomorrow.
Yes, that would be helpful (assuming @abittner is experiencing the same issue you’re describing). I’m specifically interested if those having issues are using SDDM with X11 or Wayland.
OK, since I’m awake: Yesterday I received a firmware update for my Lenovo P16s Gen 2 Thinkpad and it all seemed to be fine. Laptop booted fine, until a black screen with no SDDM. I logged in as my user on tty2, and decided to first test a reboot. All fine, so I moved on. Today this happened again, I ran the startplasma-wayland as my user and found that some settings were not respected. From that session I rebooted and SDDM came up fine again. I did start looking at the journal but haven’t done a good analysis (yet). I was triggered by your startplasma-wayland, but I see my posts did not make much sense. Sorry
All good. My comment was specifically about not running startplasma-wayland as root.
Anyway, sounds like SDDM is working for you now?
What caught my attention was @abittner mentioning Leap (16.1) as a VBox guest, so I was seeing if I could help with that specifically. (These threads can get a bit confusing when several people are describing different problems that initially sound similar.)
Yeah, all good now. Anyways I saw what I saw on real HW, my 16.0 → 16.1 VM works fine, but that is KVM/Qemu. I’ll see if there is some generic bug going on.
In reply to Deano’s post
Actually, I was responding to the second user (who unfortunately piggybacked onto your topic). Anyway, the output you shared shows SDDM is running, but Xorg then crashes when it starts. The backtrace points to vmware_drv.so, so this looks like a VirtualBox graphics driver issue rather than an SDDM startup problem.
FWIW, I’m using SDDM with the Wayland display server in my VBox guest. My /etc/sddm.conf.d/10-wayland.conf is…
[General]
DisplayServer=wayland
GreeterEnvironment=QT_WAYLAND_SHELL_INTEGRATION=layer-shell
[Wayland]
CompositorCommand=kwin_wayland --drm --no-lockscreen --no-global-shortcuts --locale1
I also have these KWin settings in /etc/profile.d/vm_graphics.sh…
export KWIN_DRM_NO_AMS=1
export KWIN_FORCE_SW_CURSOR=1
These were what I needed to get a stable SDDM/Plasma Wayland environment in my VBox guest when I was using Leap 16. I kept this as is when I upgraded to Leap16.1 via the opensuse-migration-tool.