After update, when I reboot Rome boots to terminal

Support
1

Hello,

Requirements:

<x!-- (write a x between the brackets, like this: [x] ) →

I have Searched the forum for my issue and found nothing related or helpful
I have checked the Resources category (Resources Index)
I have reviewed the Wiki for relevant information
I have read the the Release Notes and Errata

OpenMandriva Lx version:

Lx release 25.11 (ROME) Rolling for x86_64

Slim ISO

Desktop environment (KDE, LXQT…):

kde

Description of the issue (screenshots if relevant):

After update, when I reboot Rome boots to terminal

Relevant informations (hardware involved, software version, logs or output…):

Operating System: OpenMandriva ROME 25.11
KDE Plasma Version: 6.5.2
KDE Frameworks Version: 6.19.0
Qt Version: 6.10.0
Kernel Version: 6.14.2-desktop-3omv2590 (64-bit)
Graphics Platform: X11
Processors: 12 × Intel® Core™ i7-8700 CPU @ 3.20GHz
Memory: 16 GiB of RAM (15.5 GiB usable)
Graphics Processor: AMD Radeon RX 6700 XT

The update went well on my kids computer so I finally got around to updating my own. I updated through “system update” in the application menu. When I did the update I got a black screen with no way to run any commands. I let it do its thing for about 10 minutes and powered off and on. When it powers back on and reboots it takes me to the terminal. To get the desktop environment up and running I have to give the the command

sudo systemctl restart sddm

and the desktop environment seems fine and updated and everything seems to work, except for when I try to run the “system update” in the application menu. When I do this I get

Removed 15 files, 20 directories (total of 23 MiB). 0 errors occurred.
repo id repo name
brave-browser Brave Browser
rolling-x86_64 OpenMandriva Rolling - x86_64
rolling-x86_64-extra OpenMandriva Rolling - Extra - x86_64
rolling-x86_64-non-free OpenMandriva Rolling - Non-free - x86_64
rolling-x86_64-restricted OpenMandriva Rolling - Restricted - x86_64
Updating and loading repositories:
OpenMandriva Rolling - Restricted - x86_64 100% | 8.9 KiB/s | 38.6 KiB | 00m04s
OpenMandriva Rolling - Non-free - x86_64 100% | 7.7 KiB/s | 33.3 KiB | 00m04s
Brave Browser 100% | 82.0 KiB/s | 54.7 KiB | 00m01s
OpenMandriva Rolling - Extra - x86_64 100% | 306.2 KiB/s | 1.5 MiB | 00m05s
OpenMandriva Rolling - x86_64 100% | 2.8 MiB/s | 5.7 MiB | 00m02s
Repositories loaded.
Failed to resolve the transaction:
Problem: The operation would result in removing the following protected packages: systemd
You can try to add to command line:
--skip-broken to skip uninstallable packages
Press enter to close konsole

How do I fix this?

I know this problem happened to a couple of people on our Matrix chat and Im pretty sure I know the problem, our systems were not already completely up to date when we did the new big update. That was mentioned in the Matrix chat and was the big difference between my kids computer and mine, which are really similar computers.

1 Like
2

Same here. I just installed last night and after full upgrade it happened. You have to do a sudo systemctl enable plasma-sddm. If you are at the screen just add —now after “enable” (systemctl enable –now plasma-sddm) and it will start sddm immediately.

2 Likes
3

OK, after putting

sudo systemctl enable sddm

into konsole my computer will now reboot without having to maually restart sddm in the terminal.

4

cool, I hope it fixes the problem

5

So that solves one problem, but system update still fails. In the matrix chat we figured out I have a ton of duplicated system files from my semi-failed system upgrade and we are waiting on higher ups to figure that one out.

6

10-4, but you can get into graphical mode now?

8

Yep I am in the desktop environment and everything seems to be working fine.

9

Heck yeah. Also there is a command to use here to properly update the system: how_to_update

10

Yes any system update fails, same log as in my OP.

11

There is also this post here: How To use dnf

12

Thanks for the help, On the matrix chat we figured out I have 1762 duplicate packages from when the update hung on me and some of the packages are protected. We are waiting people who know a lot more about this on how to get rid of the duplicates without nuking my system, after that is done I should be able to update normally I would think,

13

Glad to be of help. I’m gonna join the matrix chat also.

1 Like
14

Hi.

I had these same problems, or at least seemingly the exact same symptoms.
I think posting in this thread is the right call because my hardware, and therefore the install itself?, are different, so it may be useful for troubleshooting for others.

Differences are

Hardware
MoBo: MSI MAG X870E tomahawk wifi.
CPU: AMD 9950X3D
GPU1: Radeon RX 9070XT
GPU2: Radeon Integrated
OS: OMLx ROME 2

It was a fresh install of
OpenMandrivaLx.rolling-snapshot.20250615.4119-plasma6x11.znver1.iso
(I think it was build 4119, I wrote it on the usb but it’s a little smudged and I have since overwritten the usb with build 4292

It installed and booted fine. Then the first thing I did was

sudo dnf distro-sync --refresh --allowerasing

I then got the exact same behaviour as described above, both the booting to tty, restarting sddm bringing back the gui, and the (as yet unresolved) updates giving the

Failed to resolve the transaction:
Problem: The operation would result in removing the following protected packages: systemd

errors.

I noticed at this point that neofetch was reporting the OS as

OpenMandriva Lx 25.11 (ROME) Rolling x86-64

I thought x86-64 was the intell version only, so thinking I may have burned the wrong iso last time (was sort of rushed at the time), I re-downloaded the latest version of the correct zen version ISO

OpenMandrivaLx.rolling-snapshot.20251109.4292-plasma6x11.znver1

I check the download against both the md5 and sha256 checksums and both matched.

I reinstalled again using ventoy, and a second time using a directly burned USB (using BalenaEtcher)

Both times have produced the same behaviours.

  • The system boots to log-in screen fine
  • After log-in it sits on tty1 with nothing but a blinking cursor
  • I can switch to tty2, 3 etc
  • tty2 shows what I assumeis the OMLx Live environment since the “Install OpenMandriva” shortcut is there.
  • Running the installer from there requests my password, then the installer pops up a warning “There are no partitions to install on.”
  • Neofetch is still reporting the OS as Rolling x86-64

So I am now thoroughly confused.

I am still thinking this could be directly related to the issues reported in this thread, so I will put this post in here just on the off chance it helps at all.

If the mods think it would be best in it’s own support thread, let me know.

1 Like
System froze/hung. No inputs worked. Hardware restart required. (ROME)
15

Sounds like these are related to me.

Do you have a bunch of doubled files like I do. Throw this in the terminal and see what it says.

sudo dnf check --duplicates

16

returned nothing.

Keep in mind, this is (currently) in the still fresh, direct install of build 4292, so if those duplicate entries were a result of the dsync I guess they wouldn’t show up.

I am going to install an older version of the znver iso (build 4011) to check whether

  1. A properly functional install of the zen version doesn’t report x86-64 in neofetch (I thought x86-64 was a reference to the 64bit instruction set used for both amd and intel cpu’s, which might mean that that reference in neofetch under OS: doesn’t necessarily mean it’s the wrong OS version.
  2. Whether updating from the older build will reproduce the same errors as last time.

I will run that command again after the reinstall and update and get back to you.
I will also try doing the

command first.

Ps.
When this fist happened yesterday I didn’t even know what I was looking at when I first saw the “tty1” etc
I’m Learning!!!
lol

1 Like
17

Well I have what seems to be a fully functional system in build 4011.

Neofetch is still reporting the OS as Rolling x86-64, so it must not be a reference to the OMLx version.

Do you think I should I do anything else to pull info from this install before I do the update? Just for the sake of comparison?

18

I am too and can tell that your ahead of me when it comes to this. A to what you should do I dont know.

19

I am doubtful on that myself (-:
This could be fun, like the blind leading the blind into dark rooms looking for black cats that may or may not be there lol

On topic
I’m wondering if my situation might be useful for the actually capable troubleshooters in here. New build & new install may mean…

  • Less clutter in the system files to sort through in looking for problems.
  • Freedom to reinstall multiple times (without fear of loosing files/setting/configurations etc) might offer opportunity to eliminate possibilities during the process.

If this is the case, I don’t mind offering my time and my new shiny (My New PC) to help.
This build has already taken over 2 weeks longer than I expected, so a bit more wont really make much difference.

20

I’m going to do the update on this now anyway. I can always reinstall build 4011 again later anyway.

Edit:
Well this is interesting. I ran

sudo dnf clean all ; clean all ; dnf repolist

then

sudo dnf distro-sync --refresh --allowerasing

And the mouse and k/b have dropped out, tried 2 different of each, and in different usb ports, no inputs at all.

Terminal is still on

Total download size: 1.8 G
Is this ok [y/N]:

WtF

Hard restart I guess.

Edit 2:
I restarted.

Konsole remembers

sudo dnf clean all ; clean all ; dnf repolist

as the last entered command, it doesn’t remember the distro-sync command.
I guess this means the system crashed because of the command?

Would this even be related to the actual problem this thread is supposed to be about?

Edit3:
Distro-sync is working this time.

21

Ok, so far it seems the same as last time.

dsync finished, or at least stopped.
Dropped to blank screen with flashing cursor on tty1
tty2 - 6 are all asking for log-in
I have not restarted or anything else yet.
I will try logging in directly from tty2 before restarting.

….

Interesting, tty is refusing my log-in. Tried 3 times and I’m sure I have name/pw right.

tty3 no luck logging in either. Restarting now

….

Restarted. Straight to tty1. asking for log-in twice. As in, the terminal looks like this

OpenMandriva Lx 25.11 (ROME) Rolling for x86_64
Kernel 6.14.2-desktop-3omv2590 on 127.0.1.1 / tty1
mycomputername login:
OpenMandriva Lx 25.11 (ROME) Rolling for x86_64
Kernel 6.14.2-desktop-3omv2590 on 127.0.1.1 / tty1
mycomputername login: (cursor here)

Logging in and restarting sddm now

….

Took me to the gui log-in screen, which seems odd since I thought I had already logged in.
Logging in again now from the gui

….

Logged in. straight to black screen blinking cursor on tty1
tty2 is the gui desktop (background or wallpaper or whatever is not the usual OMLx flowers, it’s some purple image with different sized ribbons unrolling from the top right, toward the bottom left) tty3 etc. can be switched to as normal and show the usual terminal log-in screen.
Trying
sudo systemctl enable sddm
in Konsole now and restarting

….

Hmm, interesting.
Enabled sddm and restarted.
The blinky-cursor on tty1 flashed, then the Plasma log-in screen came up.
I could still switch to tty2, 3 etc.
Went back to tty1 and logged in.
The desktop with new wallpaper loaded, but it is on tty3 and I can still switch to tty1, 2, 4 etc. Either this is not normal, or I have just never hit Ctrl+Alt+F1 on desktop before.
I think I remember reading something, somewhere, some time ago, about virtual terminals, maybe being related to different run levels? Don’t know, so don’t know if this is relevant at all.

Sorry, this is long, thought I’d just journal observations through this process straight into here. Hopefully it wasn’t just a waste of space lol

Have to pop off now, thunderings sound like a storm coming.

EDIT:
Firstly: {it’s a laptop, it can keep running while it’s unplugged :boggle eyes:} lol
B: Just tried switching to tty1, 2 etc on my little old-new-revived-from-the-dead-experiment-media pc. running mint and what-do-you-know IT WORKED (wow! meme) Main log-in /workspace or whatever it’s called is on tty7 though, not tty3 like OMLx on the new system. So, maybe that’s as significant as anything else I’ve mentioned.