openSuse Tumbleweed not showing login screen after boot

[XAvW]

OK, that’s me tripping up … dumb. Sorry!

Another thing I said wrong in my previous post: the old home was an xfs partition (not btrfs), which I deleted after the move.

I will try what you say!

Thx again

[dcurtisfra]

@XAvW

I now get the idea that “KERNEL COMMAND LINE” is not the same thing as what I modified after being pointed to “remove ‘single’”.

Please post the result of “cat /proc/cmdline”.

---

You can also determine the current Kernel Command Line from the 2nd line of each systemd Journal boot record and, from the 2nd line of “dmesg”.

---

And, please be aware that, the Kernel Command Line option we’re looking for could be any one of the following values:

• rescue
• rd.rescue
• single
• s
• S
• 1

[XAvW]

@OrsoBruno

I entered E on grub menu, but no “single”.
![20250829_115108_809 6|666x500](uploa
d://luxCabPQXccbTXZYqjdnLYS mmIn.jpeg)

The total mess came only after “zypper dup”.
So I booted from it’s “pre” snapshot into rescue mode, entered password, entered “startx” (which did start), did Logout, entered “exit” to quit rescue mode and voilâ I could login normally.

So I did a “snapper rollback”, rebooted (again in rescue mode and with the “inappropriate” “startx” and could login normally.

So, I must conclude that:

• there was no kernel option “single”
• maybe “zypper dup” did cause a mess, because of the real underlying issue in the first place.

Maybe somebody can hint me at which logs to show here (and how to get them)?

If not, or if the issue persists after maybe trying other tips, I am planning to do a fresh install on a bigger SSD, so without fhe need to move /home, since that really is the only thing (apart from ssd failures) I can think of as the cause.

Again, glad y’all are willing to help out!

[XAvW]

What happned with my photo’s?
I uploaded them from my phone …

[XAvW]

I just went thru the journalctl logfile and found this error:

Aug 29 11:48:04 ubuntu.home dbus-broker-launch[1970]: Service file '/usr/share/dbus-1/services/obex-data-server.service' is not named after the D-Bus name 'org.openobex'.
░░ Subject: Invalid service file
░░ Defined-By: dbus-broker
░░ Support: https://groups.google.com/forum/#!forum/bus1-devel
░░ 
░░ A service file is a ini-type configuration file.
░░ 
░░ It has one required section
░░ named [D-BUS Service]. The section contains the required key 'Name', which
░░ must be a valid D-Bus name that is unique across all service files. It also
░░ contains at least one of the two optional keys 'SystemdService' and 'Exec',
░░ as well as optionally the key 'User'. Exec must be a valid shell command and
░░ User must be a valid user on the system.
░░ 
░░ A service file should be named after the D-Bus name it configures. That is
░░ a file containing Name=org.foo.bar1 should be named org.foo.bar1.service.
░░ For backwards compatibility, we only warn when files do not follow this
░░ convention when run as a user bus. The system bus considers this an error
░░ and ignores the service file.

[XAvW]

Today I bit the bullet, and reinstalled openSuse TumbleWeed one a bigger SSD.

While installing I chose KDE Plasma instead of XFCE.

Installation went well. I managed to resetup Qemu-KVM, and “restored” my Windows 11 VM without a hitch.

But I noticed that Plasma was much heavier on my system, which made my W11 VM a bit sluggish.

So I installed XFCE, logged out and uninstalled KDE Plasma completely, all without any problems

In short, I am a happy user again, not knowing what went wrong the first time at all!

I really want to thank this community for their willingness to help out. During this issue I picked up some useful ideas and tricks of more advanced users. Thanks!

So, no solution, but this issue may be closed.