Call for testing new ROME isos

ben79 · February 14, 2026, 2:01am

These are very new after the recent ROME Major Upgrade.

_Call for Testing New and we hope improved ROME isos:

We have a good tranche of new ROME isos in ABF now. Mostly untested and we could use your help testing these. I did check that #4403 and #4403 boot on my Ryzen5 laptop, Calamares and OM-Welcome open and appear normal functioning. The most visible desktop stuff at lease opens and appears working.

Where to get 'em, two locations:

In the OM Development Testing forum: Most recent ROME (rolling) ISO
Direct from ABF: Products Monitoring - Openmandriva ABF

What the OM Contributor group wants is user testing and reporting of problems. General rule is one problem per thread so if you encounter something not yet reported please start a new thread with a descriptive title and as much info as you can manage.

And keep in mind folks if the problem is major technical issue that needs developer help it is still best to bug report it.

kLF · February 15, 2026, 9:04am

Hi Ben,
Bare metal install of #4403 from Ventoy usb stick.
Trouble free install.
Post install update as per instructions unremarkable.

Welcome opens & functions correctly.
Excellent work.

``
Operating System: OpenMandriva ROME Cooker
KDE Plasma Version: 6.5.5
KDE Frameworks Version: 6.22.0
Qt Version: 6.10.2
Kernel Version: 6.19.0-desktop-1omv2690 (64-bit)
Graphics Platform: X11
Processors: 5 × AMD Ryzen 5 5600 6-Core Processor
Memory: 16 GiB of RAM (15.6 GiB usable)
Graphics Processor: NVIDIA GeForce RTX 3050
Manufacturer: Micro-Star International Co., Ltd.
Product Name: MS-7C52
System Version: 2.0

ben79 · February 15, 2026, 12:38pm

Thanks @kLF.

ben79 · February 15, 2026, 1:11pm

I am also using Ventoy. Have done 2 installs on hw (AMD Ryzen 5 7530U with Radeon Graphics).

ROME P6 X11 x86_64 from iso # 4403
ROME P6 Wayland Ryzen from iso # 4407

This is from one of those:

Everything is working except virtualbox-7.2.6. That has no kernel modules for kernel 6.19.0-1. If I use a kernel 6.18.x I can load kernel modules but there is another problem reported here. VBox is also broken in Cooker.

stefluni · February 16, 2026, 6:27pm

Hi! I downloaded the Wayland 4418 ISO, put it on a USB stick, and launched it live on my new PC (Lenovo I7 16GB RAM). It booted up and everything seems to work (at least what’s there). However, I’m having the same problem I have on my OM Rome Plasma 6 Wayland installed on my laptop and updated yesterday… when I launch a video on Facebook or something else, the audio is heard, but the video window remains white (in the Helium browser). This problem doesn’t occur on my other PC where I updated the Rome X11. Here, however, I use the Chrome browser… Maybe I’m missing a plugin?

ben79 · February 16, 2026, 10:16pm

As I understand it, or this is I think not I know: Helium is somehow Chromium and OM ships an ungoogled version of Chromium. I suspect for videos to work Helium would need the google bits or for user to install things like Widevine and perhaps other video apps or widgets or whatever they are.

DD15 · February 17, 2026, 2:56am

@ben79, I tore open my ASUS K55A laptop and swapped out the SSD with a working OM Rome that I installed last February for a spare I had sitting here. That way I don’t have to worry about blowing up something on that drive. I installed 4404, Rome Plasma 6 Wayland. No problem installing from Ventoy.

I got two errors.

The first one was with the Welcome Center:

No idea as to how to resolve that. So I kept going. That happened in the KDE Plasma 6 Welcome Center. Not the OM Welcome Center.

For the most part, everything seems to work. Installed Vivaldi after enabling that repo and it worked. Went to YouTube and played a short video with picture and sound as intended in 720p. That is about all that can be expected from that old ASUS without introducing choppiness.

I figured I would give VirtualBox a try. It installed, or so I thought. This is the error I received when I tried to run a virtual machine:

When I ran the installer for 4404 from Ventoy, Secure Boot was disabled and I kept it set to disabled in the UEFI settings. One less thing to deal with.

When I try to execute /sbin/vboxconfig as sudo, I am informed there is no such file. I have no idea what is happening.

I am able to wipe the SSD and try another .iso. Or should I wait for any suggestions? This is not mission critical by any means. A Phillips screwdriver and 8 screws later is all it takes to swap out the SSD for a different one.

Or should I post this information as multiple issues in Support?

stefluni · February 17, 2026, 7:42am

Exactly. Before Helium, there was another ungoogled browser (Falkon); now the plain ISO only has Helium. I tried it live.
I have the same problem on my laptop… I installed Chrome and everything works. Before the latest update, however, Helium worked fine.

ben79 · February 17, 2026, 1:24pm

Given that other people are not seeing that would it be possible that the problem is on your end? Like a corrupted download or burn to installation media? Without logs or some evidence no way to know. Maybe it is a real problem, don’t know.

VirtualBox 7.2.6 does not open VM’s #3433

Bug report? Preferably with logs or some other evidence.

ben79 · February 17, 2026, 1:35pm

Uh, oh, I wrote without investigating enough…

That is one page. I never worried or thought about because why? I have not idea why that page does not load. But I also have a negative opinion of that KDE Welcome Center. It seems useless fluff that should be eliminated. Just my opinion though.

stefluni · February 17, 2026, 3:04pm

Another small problem… installing the Rome Plasma 6 Wayland 44418 ISO on physical hardware, I encountered an old issue, already noted with previous ISOs.
The keyboard is not mapped correctly, and I need to enable the mapping manually. In my case, the @ key didn’t work.

provetta007 · February 17, 2026, 4:30pm

Hi,

Problem:

I have installed in new partition disk with Ventoy. I have used “OpenMandrivaLx.rolling-snapshot.20260213.4403-plasma6x11.x86_64.iso”.

I see that the system Rome is Cooker not Rolling, is it correct? I want Rome Rolling.

My system is:

Operating System: OpenMandriva ROME Cooker
KDE Plasma Version: 6.5.5
KDE Frameworks Version: 6.22.0
Qt Version: 6.10.2
Kernel Version: 6.19.0-desktop-1omv2690 (64-bit)
Graphics Platform: X11
Processors: 24 × 13th Gen Intel® Core™ i7-13700HX
Memory: 16 GiB of RAM (15.3 GiB usable)
Graphics Processor 1: Intel® UHD Graphics
Graphics Processor 2: NVIDIA GeForce RTX 4060 Laptop GPU
Manufacturer: MEDION
Product Name: Defender P40

Thanks

DD15 · February 17, 2026, 5:16pm

Digging a little deeper on the Internet, it seems several other big-name distros are having the same issue with the KDE Welcome Center. Not a good look for KDE. I believe this it their problem.

I tried this on the installation that I performed back in March last year on my other laptop, the ASUS X555UA. Guess what? Same KDE Welcome Center error message. Anyone can replicate it simply by running this app if using Plasma 6. It seems X11 or Wayland doesn’t matter as I just did it running X11.

I reported this to KDE. Will see where this goes. I highly suspect it is not a high priority for them right now.

Added edit:

Two messages from KDE:

Nate Graham nate@kde.org changed:

       What    |Removed                     |Added

             CC|                            |

— Comment #4 from Nate Graham nate@kde.org —
*** Bug 516153 has been marked as a duplicate of this bug. ***

–
You are receiving this mail because:
You are on the CC list for the bug.

–

Nate Graham nate@kde.org changed:

       What    |Removed                     |Added

         Status|REPORTED                    |RESOLVED
     Resolution|---                         |DUPLICATE

— Comment #1 from Nate Graham nate@kde.org —
This is a packaging issue in your distro; see Bug 511809. Please tell them to
install the QtNetworks QML module as a mandatory dependency for plasma-welcome.

*** This bug has been marked as a duplicate of bug 511809 ***

–
You are receiving this mail because:
You reported the bug.

–

End edit.

I tried to go to ~/VirtualBox VM//Logs/VBox.log to locate that log file. It is missing. There is no Logs folder, never mind any .log files. Is this because the virtual machine never ran long enough to generate the .log file?

Just now I tried to run Helium. No crashes for it using the 4404 .iso installation. However, I am not running a live session. Everything has been installed to an SSD. Perhaps Helium doesn’t work from a live session?

As for Falkon, that is available in the repositories. It does install and functions as intended.

ben79 · February 17, 2026, 6:28pm

There are 2 problems. There are no kernel modules for kernel 6.19.0-1 for VBox. That would probably be why you do not see logs.

The problem in the bug report is a different issue that does not allow VBox to start VM’s, I got the information for the bug report using kernel 6.18.9.

I check that Helium works but only briefly when I test ‘Live’ isos. I am not aware of any reports of crashing, did I miss it?

DD15 · February 17, 2026, 6:58pm

Now I am confused. I should try to reboot with kernel 6.18.9?

This may be my fault. I was under the impression that Helium wasn’t working for @stefluni.

rugyada · February 17, 2026, 7:35pm

Mine too.

ben79 · February 17, 2026, 9:32pm

This thread is about testing the isos. Perhaps for conversation about VBox we should go here.

247 · February 17, 2026, 10:02pm

wonder if the latest gnome iso count as testing, as i’m testing it and it works nicely…

ben79 · February 17, 2026, 10:06pm

Yes that counts and good to know.

DD15 · February 18, 2026, 2:46am

Moving forward, I did a clean install of 4409, ROME LXQt. Very interesting results. Running live from Ventoy, everything seems to work. Then I did the install. No issues that I could see from the SDDM login screen, so far.

Then I logged in and hello trouble. Not sure why, but I would keep getting a black screen instead of a desktop. Then the whole show would reboot on its own. After doing that three times, the next time at the login screen I tried switching it up a bit, using LXQt (Wayland) instead. I got desktop and then a crash and reboot one more time. Just for grins and giggles, I changed it the login back to LXQt (X11). Now I got a desktop, sort of.

No window manager. Download and install the xfwm4 window manager. Then go into session settings and enable xfwm4 as the window manager. Log out. Log back in. The desktop is getting better and seems to be stable.

Perhaps the xfwm4 window manager package should be installed when everything else is installed? Or the kwin window manager? I have not tried kwin, yet. This is just an idea. Or installing a window manager with the rest of the installation can’t be done?

The Falkon browser works, along with the file manager. The Wi-Fi and Ethernet port both work. I didn’t try anything else, yet.

One problem is HDMI support. I am doing this on the ASUS K55A laptop. When I try to switch video output over to HDMI, everything goes black on my monitor and the laptop. Disconnect the monitor and the laptop display comes back. The HDMI port does work. I had it working with Plasma 6 yesterday and earlier today. The monitor works when I go into UEFI settings after hitting the F2 key at power on.

I click on the Monitor settings in Preferences and it does nothing. Unlike the other choices inside Preferences, Monitor doesn’t seem to be working. Are one or more files missing at installation? Is there a log file that I can check?

For a reference point to make a comparison for LXQt, over on my other ASUS laptop, the X555UA, I am running Plasma 6 ROME. Both X11 and Wayland are installed. So let’s see what else I can blow up (I failed/no smoke). I installed LXQt and xfwm4 and was able to log into the LXQt desktop. Then set up xfwm4 in Sessions, log out and log back in. This time, the Monitor settings worked. I have monitor connected to the HDMI port and the laptop display working. Are there files in Plasma 6 that are missing in LXQt? On this laptop, I now have Plasma and LXQt as desktop options. If any files are missing in LXQt, it is just using the ones that are in Plasma 6.

So that is what I found with the 4409 .iso installation file for ROME LXQt. After rebooting several times after several failed desktop logins, it does work. The user should not have to reboot and log back in several times just to get it going the first time.

At this point, I would recommend for anyone wanting to use LXQt to first install Plasma 6, log in, install LXQt and xfwm4 from the repositories, and then use LXQt, as this seems to give the best results. As a bonus if your desktop goes sideway, you have the other one to use to get the first one back in working order.