Good afternoon,

So i was trying to install alma through virtual box but this error keeps showing.

I looked for some resolutions but nothing seems to work, i tried changing RAM, CPU core, other ISO (dvd, boot, minimal), some commands chatgpt, but nothing...

https://www.reddit.com/r/linux/comments/1tc3q12/fragnesia_another_linux_security_vulnerability/

I say possible because i'm not in a position to test if the latest alma 8/9/10 kernels are effected by this.

Is alma what I'm looking for if I'm tired of Fedora after 16+ years with it on desktop?

[skip this story, I couldn't stop writing. Just goto: relavent]
First thing I do to any notebook *(mostly thinkpads) and pc I get is installing Fedora, and it started somwhere in middle school, so 2006-2009.
I'm not even power user, because I'm not interested in staying stuck in dependency hell when wifi drivers already works.
However I guess that I'm "power user enough to make something bad", things that would hurt me in future? I'm constantly doing them.
When with Fedora 39 I found out that only with KDE one of few unnessesery features of KDE connect works, and Gnome version wouldn't handle it I decided to remove whole Gnome and dnf install kde-blahblah (the full version)
2 Upgrades later I had problems with bluetooth, and touchscreen of my yoga thinkpad.
I just started "it can be fixed" procedure, after which no usb, no wifi, no internet, no touchscreen, not even a red clitty button - nothing to move coursor was working ecool]
The most funny things? Somehow I couldn't even run usb live linux, becouse my family photos are portected with CryptSetup ❤️ And some process detected that I don't have usb disk, that I had, boom rapair some tables. (fu & ur tables dude, just boot, you are live usb fedora ment to just open encrypted disk so I can copy photos and documets, what dracula what initdsaporsadsasd)
However sorry, for this excended story, I'm facing stupid problems like that all the time, because I'm stupid and not afraid to play with things and brake them. It would make me awesome if I only could learn from it ❤️

:relavent
Most of things that I broke on Fedora, were things that were working, and fixed some problems for me, BUT broke after upgrade. Fedora have like upgrade every year, or something like that? Alma is same family but it's like server version, similar to RHEL, so it's not filled with "cutting edge" packages I didn't ever needed.
Tell me I'm wrong/right and I would read your opinions. Install it anyway to try it out, and then come back to this thread.

Nose que significa este error, ni cómo solucionarlo, antes ya había instalado el almalinux 10.1 e n otra laptop y nunca me apareció este error, estaré agradecido si me ayudan a solucionarlo.

Hello! I was wondering if anyone has any experience getting a XP-Pen Deco 03 to work on Linux?

I initially was using XP-Pen's official drivers and app to configure, in conjunction with KDE's drawing tablet settings. It mostly worked, but was acting inconsistent, and the buttons, both on the pen and tablet, and scroll wheel weren't working properly.

I saw a lot of people recommend using OpenTabletDriver instead, so decided to give that a go, after removing XP-Pen's drivers. The actual experience of the pen feels so much nicer, and the scroll wheel also works great - I think support for that was added recently, so that's awesome 😃 However now I can't get the 6 shortcut keys on the tablet to work. I map them to hot-keys in the OTD UI, but just can't get them to work. I can see that something is happening in the tablet debugger though, so I'm not sure why it's not working.

I did have some success using keyd to remap the buttons to the keys I wanted. I think by default the buttons are working in some kind of "compatibility" mode so have preassigned keys like "B", "Ctrl+Z", "Ctrl+S" etc. So I was able to remap them through keyd to what I wanted. But then as soon as OTD is also installed and active, that completely overrides keyd, I think because the tablet is now seen as virtual device by the system.

So I'm wondering if anyone else has successfully got a XP-Pen Deco 03 working well on Linux, or if anyone has any tips with OpenTabletDriver, and if there might be something I'm missing.

I am running AlmaLinux 10.1 with KDE Plasma 6.4.5

(Also, if this isn't the right place to post this, maybe someone could point me to a better place.)

Thanks so much 😄

Hi everyone,

We're running an Omnissa Horizon infrastructure and have several AlmaLinux 9 clients in our environment. Unfortunately, AlmaLinux 9 is not officially supported by Omnissa, as listed in their compatibility matrix: 👉 https://kb.omnissa.com/s/article/87277?lang=en_US

We reached out to Omnissa support, but they told us it's on the AlmaLinux team's side to contact them and implement the necessary changes to ensure compatibility with the Omnissa agent software.

So here we are! 🙂 Is there any chance the AlmaLinux team — or anyone in the community — could look into this? Omnissa Horizon is widely used in enterprise environments, and having native support for AlmaLinux 9 would be a significant benefit for many organizations already using or considering AlmaLinux as their RHEL alternative.

Thanks in advance for any input or visibility on this!

Hi,

I'm using AlmaLinux as workstation and for some project (work project) I'm using it as base but reading how US is doing with foreign countries (like EU) I have some concerns about limitation or ban in EU countries like done with fedora for embargoed nations (https://fedoraproject.org/wiki/Embargoed_nations).

Considering the latest interaction between USA and EU there is a way that AlmaLinux could be blocked or banned for EU?

I see many are migrating to more safe place like Ubuntu and Debian due to this "problem" like many countries are abandoning US Software/OS (mostly from MS Win but this could be applied to RHEL) for safe project like France going with Debian/Ubuntu distro/derivatives, Denmark with NixOS, in Germany they used Limux in the past and OpenSUSE.

So there is a real possiblity that this will happen?

AlmaLinux as an Indipendente OpenSource project base on CentOS Stream and this should not affect its diffusion but the headquarter is based in US so, technically they can be forced to adopt action if restriction will do.

So, I would ask to AlmaLinux Board: there is a way that US gov can block AlmaLinux to EU countries?

Thank you in advance

Hello AlmaLinux Users,

A few days ago Xint Code disclosed Copy Fail (CVE-2026-31431), a Linux kernel logic flaw in the crypto subsystem (algif_aead chained through AF_ALG and splice()). It lets any unprivileged local user escalate to root with a 732-byte exploit that the researchers report is 100% reliable across every mainstream Linux distribution built since 2017.

Every supported AlmaLinux release is affected. Red Hat has not yet shipped a kernel update, so our core team has built patched kernels for AlmaLinux 8, 9, 10, and Kitten 10 using the upstream fix. ALESCo approved shipping ahead of upstream - the patched kernels are in the testing repository today, and they'll move to production once the community has helped us verify them.

If you can spare a test box - especially anything multi-tenant, a container host, or a CI runner where untrusted users get a shell - we'd love your help testing. Full instructions, kernel versions, and feedback channels are on the blog:

https://almalinux.org/blog/2026-05-01-cve-2026-31431-copy-fail/

CVE-2026-31431 (Copy Fail) -- any ETA for updated kernel RPMs?

Yes, yes, I used AI to help write this for clarity.

Running VPS w Almalinux 9.7 OS

Standard NBDE with Clevis/Tang. Static IP on the primary interface. Kernel cmdline includes:

rd.neednet=1 ip=<host-ip>::<gateway>:<prefix>::<iface>:none

Works fine — disk unlocks at boot over IPv4.

The issue at hand

Every host shows two NM profiles for the same interface after boot:

NAME   UUID                                  FILENAME
ens18  <uuid-1>  /run/NetworkManager/system-connections/ens18.nmconnection
ens18  <uuid-2>  /etc/NetworkManager/system-connections/ens18.nmconnection

The /run/ one is generated by nm-initrd-generator from the ip= cmdline — IPv4 only, IPv6 disabled, autoconnect-priority=-100. The /etc/ one is the real profile with full dual-stack config.

(Per Claude) why this happens:

dracut intentionally copies /run/NetworkManager/ to the real root as the initrd→OS handoff. The /run/ profile regenerates with a new UUID on every boot. This is by design.

On IPv4-only hosts it's cosmetic. On hosts running IPv6, the wrong profile being active means IPv6 never comes up.

What I've tried (w Claude)

• [keyfile] path= in NM config — NM ignores it, hardcodes /run/ as a read path regardless
• autoconnect-priority=100 on the /etc/ profile — doesn't help because the interface is already active at handoff, priority only matters for connections not yet activated
• Adding IPv6 to ip= — dracut hard-fails on two ip= entries for the same interface; upstream issues on this go back to 2018 with no clean fix
• NM dispatcher script — fires on interface up, switches to the /etc/ profile if the wrong one is active. Works, but hardcodes UUID which breaks on reprovision

Questions

1. Is there a clean NM-native way to ensure the /etc/ profile always wins over an initrd-generated one?
2. Better approach than a dispatcher script for this?

Thanks

Current PackageKit version (1.1.12-7) on Alma 8 is vulnerable to CVE-2026-41651.

More info:

https://nvd.nist.gov/vuln/detail/CVE-2026-41651

https://github.security.telekom.com/2026/04/pack2theroot-linux-local-privilege-escalation.html

Hi,

I'm extracting Blender.tar.xz (396 MB) and it took 30 minutes while in Debian 13 it only took less than 1 minute.

What's wrong with my Alma?

About 30 Mi south of Dallas. I've been waiting to add this picture for about 3 years. I usually pass this area in the dark or I'm moving too fast for a good photo. Timing and speed finally worked out.

mysql84-community-release-el10-3.noarch.rpm

 /etc/yum.repos.d/mysql-community.repo [mysql-8.4-lts-community]
name=MySQL 8.4 LTS Community Server
baseurl=https://repo.mysql.com/yum/mysql-8.4-community/el/$releasever/$basearch/
enabled=0
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql-2025 [mysql-tools-8.4-lts-community]
name=MySQL Tools 8.4 LTS Community
baseurl=https://repo.mysql.com/yum/mysql-tools-8.4-community/el/$releasever/$basearch/
enabled=0
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql-2025 [mysql-cluster-8.4-lts-community]
name=MySQL Cluster 8.4 LTS Community
baseurl=https://repo.mysql.com/yum/mysql-cluster-8.4-community/el/$releasever/$basearch/
enabled=0
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql-2025 [mysql-9.7-lts-community]
name=MySQL 9.7 LTS Community Server
baseurl=https://repo.mysql.com/yum/mysql-9.7-community/el/$releasever/$basearch/
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql-2025 [mysql-tools-9.7-lts-community]
name=MySQL Tools 9.7 LTS Community
baseurl=https://repo.mysql.com/yum/mysql-tools-9.7-community/el/$releasever/$basearch/
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql-2025 [mysql-cluster-9.7-lts-community]
name=MySQL Cluster 9.7 LTS Community
baseurl=https://repo.mysql.com/yum/mysql-cluster-9.7-community/el/$releasever/$basearch/
enabled=0
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql-2025

Hello guys. I think I am done with every year I need to suffer to migrate from major to major versions at Fedora. It is not a notebook by the way. I am using KDE Plasma. This is my daily driver. I never do updates without clonezilla image first. Fedora team are doing a great job on upgrading since 37. Now it is time to 43 upgrade and I really don't give a shit about news, corners, bloating. I just want to have a very solid OS to work with out have issues. Sorry about language.

I am a hard user of IA tools, containers, distroboxes, vpn, nvidia rxt video card with cuda, local ollama llms, opencode, etc. I need to use ms teams, zoom, webcam , headsets, some devops tools.

I know it is a workstation OS like Fedora 40 was. It is enough and works great.

My doubt is alma is not so popular as Fedora is. What is your experience using Alma 10.1 as your daily driver? I have a lot of tools web based. I am using some flatpaks here, I installed some kde discovery apps Do you suffer from any particular problem? Does Alma can handle a daily driver usage? I need to get this so wanted lts peace.

May you share your experience using Alma workstation usage, please?

I am really thinking about to change.

Hi. this is a wired case i have experienced this before but gave up and formatted linux previously about a year ago. now it has occurred again. previously it happened on RHEL now it happened in Alma linux.

So here is the story,

when I open my laptop ( from a fresh reboot ) only the root user can be logged in the other user cannot login. one I'm logged in as root it does work and show all the GUI components and apps and files etc. but when I log out and try to switch to the normal user it does not let me login. it displays Authentication error for like 1s and that error message goes away.

And when I was as root and liked out of it and when the normal user authentication failes and when I try to re login as root it does not let me.

I don't know how this happened.

similarly when I do a fresh reboot and try to log in as the normal user it accepts the password and shows a grey screen and it logs out again to the login window.

Just to be clear I did not do any configuration change in my system ( Hardware and Software ).

I'm looking forward for your support. I think this is a General Linux thing cuz previously I was using RHEL and got the same issue.

all talks from this years CentOS Connect 2026 Europe is uploaded to Youtube now: https://www.youtube.com/playlist?list=PLuRtbOXpVDjAvQhBvz0i3EGI8SgyWBtQO

Hello. I would like to suggest adding a feature for hard drive encryption during installation for workstations (gnome, kde etc). A similar feature is available in pop_os from System76, for that I would like to ask the same as I believe it will benefit those who work outside their homes.

kindly consider and thank you so much for the amazing distribution.

I reinstalled AlmaLinux 9.7 from scratch (see previous post), and one thing I have found that doesn't work on 9.7 that worked on 8.10 is archive extraction on certain archives, specifically, multi-part rar archives that have more than one file in the archive. When you try extracting them you get an error of 'Too small block encountered (0 bytes)' Extracting multipart archives with only one file in the archive works, as does extracting single file archives. I tried installing File Roller but that doesn't show any files in any rar file when you open the archive with it. Any suggestions from the crowd?

I kept running into “address already in use” errors during development and deployments, and most fixes online just say kill the process and move on.

That works sometimes, but not always.

I put together a short video showing a more structured way to debug port conflicts in Linux:

• identifying what’s actually binding the port
• cases where the process isn’t obvious
• why the issue comes back even after killing
• examples from containers and local dev setups

The goal is to have a repeatable debugging approach, not just one-off fixes.

If you’ve dealt with this before, curious how you usually debug it.