Hello,
Requirements:
OpenMandriva Lx version:6
Desktop environment (KDE):
My welcome app loads with video all distorted, I have screenshots of my pc info and the screen byut can’t upload them(screenshots if relevant):
KDE wayland 6.3.4, kernel 6.14.2, primary video card is amd radeon RX 550
Try again now.
You can just drag and drop the screenshots to the text box. If not possible, use something like Imgur. Also, the 6.14.2 kernel has been acting weird a lot lately, try switching to something like 6.13.9 in the GRUB boot screen.
I’m not seeing any options when it boots up for any other kernel?
Also my discover software center won’t let me install anything.
When you boot up, instead of booting the default option, go to the Advanced Options part and select 6.13.9.
There wasn’t an option there for another kernel
Advanced options for OpenMandriva Lx > , you should see a couple listed kernels. If it’s just 6.14.2, you need to increase the number of kernels that the system lets you have. Don’t remember where you do that, but @WilsonPhillips may be able to help!
I’m only showing the one
In the first screenshot, you showed you were running kernel 6.14.2-3. That is the correct kernel and should not have any problems. Where did it go?
Please post the output of
rpm -qa|grep kernel
lib64absl_kernel_timeout_internal-20250127.1-1.x86_64
kernel-desktop-6.14.2-3.x86_64
kernel-firmware-extra-20250413-1.noarch
kernel-firmware-20250413-1.noarch
I can confirm, and it’s a QtWebEngine issue. @bero is working on a patch. There are build issues with it.
Instead of one back tic, you need 3 to post code as code.
That is the right kernel. It looks like the desktop is loading properly and the only issue is the welcome app is having a problem. Let’s get your repos set. You can do that with the Software Repository Selector.
Open it and set the repos. DO NOT CHANGE THE UPDATE CHANNEL. Set the repos as you need. I use all three. Do not change repos any other way than this.
Now, you will be able to do updates. Although, for right now, you will need to do them from the command line. Paste this command in and use it.
sudo dnf clean all ; dnf clean all ; sudo dnf distro-sync --refresh --allowerasing 2>&1| tee dsync2-log.txt
I don’t think you will see any updates yet, but as soon as the welcome app is fixed, you will be able to download it. 
Do:
sudo dnf clean all;dnf clean all
sudo dnf --refresh --enablerepo=rock-testing-x86_64 --allowerasing distro-sync 2>&1 | tee rock-sync.log.txt
I don’t think this is working out for my home desktop. I wanted stable, not adding testing.
Thx anyway
Not really, command would do the distro-sync pulling the latest fix 
The fix is not yet published to release main repository, so you can grab it from /testing repo (don’t worry) or to wait some time. Either way it will be exactly the same stuff.
Postedit
Correction: it’s published now.
Just distro-sync system.
It sounds like you have some expectations we were not made aware of. Which makes it difficult to meet them. Rock should be stable, but we don’t have employees to test every possible outcome. There isn’t a Linux distribution out there that does not have some bug in their Stable version. The difference here is, we do our best to resolve it instead of waiting until the next point release.
You are also running wayland which will be a test use case in OM. Discover is also not 100% supported, also in any distribution including Neon. The primary use case for Discover is installing user level permission software in a similar way to Play or App Store. We are attempting to patch it to use it in a way it wasn’t intended. Even in Neon, they recommend you use the CLI to update (which will come from Ubuntu).
Hopefully this helps you reassess your expectations and we hope you will help us “test” things so OM can be better for everyone, not just you.
To me it sounds like the person did not even take the time to understand what we actually were suggesting. Explanation followed but I’m afraid that it wasn’t read 
It was a strange thing to nit pick. Most people ignore things that pop up at them when they boot into their OS. I wonder if the point was to not fix it and spread FUD.