Problems with latest ROME ISOs (4292)

Development Development Testing
1

Edited (Nov. 17, 2025): To add # 1.

User @Mortistik pointed out some problems with latest ROME X11 Ryzen iso here.

I just installed this on hardware after getting a black screen in a Qemu vm install attempt.

What I found with ROME ISO 4292 after install on hardware system.

Overall the system seems to work just fine. But there is one big problem and some rough edges as follows.

  1. (Applies to booting EFI/UEFI) It seems that regardless of whether user uses Erase Disk or Manual Partitioning there is a warning about the file system type used for the /boot/efi partition. These warnings can be ignored but this is really a bug that needs to be fixed.

  2. After install system logs in to tty1 when graphical desktop is on tty2. On my system this only happens on first boot. (This is a big problem especially for less technical user.) Possibly why I got black screen on Qemu, I did not know how to do the VT’s in Qemu yet.

  3. Calamares is not removed during install process causing wailing and gnashing of teeth. (Or maybe a minor irritation easily remedied.)

  4. Screen Locking is set to occur after 5 min. We used to have this at never by default because some users might get a surprise that confuses them. I believe this should be a user setting not a default.

  5. Debatable if this is actually a problem

# ls -ls /boot/efi/EFI
total 12
4 drwx------ 2 root root 4096 Dec 30  2023  BOOT
4 drwx------ 2 root root 4096 Nov  9 07:07  openmandriva
4 drwx------ 2 root root 4096 May 30 10:24 'OpenMandriva_Lx_[GRUB]'

This is probably a multi-boot thing, not sure. But we keep seeing users ending up with openmandriva and ‘OpenMandriva_Lx_[GRUB]’. This can be confusing and lead to problems especially for less technical users. It would seem consistency would dictate that OMLx systems use only one. Don’t know if anything can be done about this. Also not positive this is a multi-boot issue, maybe it was some change at some point in time? Don’t know.

  1. A pet peeve of mine, Discover is listed as a favorite. No it isn’t.

FWIW if any of these problem have been fixed since iso 4292 was built (11/09/25) that is great. I tested this one because it was user reported. Just let us know the fixes have been made.

Ofc other users may find other problems.

This is the installation log for this test system:

Calamares.log.txt (246.2 KB)

2

Edited (Nov. 17, 2025): To add # 1.

Workarounds:

  1. As noted these warnings can be ignored, at least for me system installed normally. But this is really something that needs to be fixed.

  2. Problem did not occur after first boot, no workaround needed on my system.

  3. sudo dnf rm calamares

  4. Go to SystemSettings>Security & Privacy>Screen Locker and set it as you wish. For me this is ‘never’, I use screen locker but not automatically.

  5. Use the one that works. Granted developers may have a better answer for this but for me this is not new and I just use what works for me.

  6. If you don’t want this remove it from Favorites (right click).

3

Users wishing to use the latest ROME(rolling) ISOs can find them here:

Most recent ROME (rolling) ISO

In spite of the problems noted above I found my installed system works rather well after applying the workarounds.

Edit: My opinion: Using these latest ISOs would be a far better choice resulting in fewer problems rather than using the 24.12 ISOs that are at SourceForge.

Edit-2: At SourceForge under Nightly.Builds there are ROME isos from 2025-06-15. IMO those are still to old one may as well use the latest.

4

If you encounter difficulties with this please make a new forum post or bug report with a descriptive title and enough information like steps to reproduce the issue or logs so we have something to work with. Please only one issue per forum thread. Otherwise user with the same issue may not be able to find any solution and for people trying to help multiple problems at once are to hard to follow. Just good manners.

Be aware we really, really, really, will need to know exactly, exactly, what you have done to your computer before the issue occurred. This is essential information. If you have customized your system we may need to know exactly, exactly, what you have done. Again essential information.

6
  1. is fixed, I can’t reproduce 2.
1 Like