Hi,

some days ago, after the release of alma9.5 a post was published about the problem that zfs does not compile on 9.5 due to new kernel incompatibility. I don't see any news on this channel about this problem. Is it fixed?

I have 2 server that have zfs and updates are blocked.

Thank you in advance.

Best regards

Is it possible to install docker engine on Almalinux 9 on wsl2? I'm trying to avoid the licence requirement for Docker Desktop on windows.

Hello, I would like to know if any one is using Kitten 10 often or as daily driver. I know it will be as a starting base for Alma Linux 10, but I think their are people who like to explore.

I would use it if it is with KDE DE. But that is a personal preference.

Thanks,

Hi, I have a bootable USB with Almalinux, I was wondering if it's a good choice to use as my desktop OS? What have been other's experience? I have reasonable understanding of way around Linux.

I keep getting this error on fresh install of AlmaLinux 9 for a server (minimal install):

Failed to set locale, defaulting to C.UTF-8

when I run e.g. dnf search <package>. From quick google search, installing glibc-langpack-en should fix this.

System Locale: LANG=en_US.UTF-8
           LC_MEASUREMENT=metric
 VC Keymap: us
 X11 Layout: (unset)

Actually, I believe on a fresh install with the initial boot and installing of packages, this wasn't a problem until I rebooted.

Also tried setting `

The only way I can avoid getting that error is to manually export LC_ALL=en_US.UTF-8, but this doesn't seem like a good solution (it's intended for testing purposes and overrides everything). I'm also not sure where is the appropriate place to add it, /etc/environment didn't work, do I just add it to shell-specific /etc/profile?

Any ideas?

A while back I reported that the alma8 .22 and .27 kernels crashed on two disperate Dell PowerEdge machines. The .16 kernels run fine, nothing was changed just an ordinary yum -y update was run, and curiously there are no corresponding kdump.img under /boot for the .22 and .27 kernels.

To get the error, I had to get the serial port bits right. "... the secret is to bang the rocks together, guys" and to add console=ttyS1,9600 to the kernel line.

https://bugs.almalinux.org/view.php?id=487

This is for the R520 machine.

Cheers.

" [ESC[0;32m OK ESC[0m] Started Show Plymouth Boot Screen.
[ESC[0;32m OK ESC[0m] Started Forward Password Requests to Plymouth Directory Watch.
[ESC[0;32m OK ESC[0m] Reached target Paths.
[ESC[0;32m OK ESC[0m] Started Journal Service.
[ 19.651718] NMI watchdog: Watchdog detected hard LOCKUP on cpu 5Modules linked in: sd_mod t10_pi sg uas usb_storage fuse
[ 19.651722] CPU: 5 PID: 0 Comm: swapper/5 Not tainted 4.18.0-553.27.1.el8_10.x86_64 #1
[ 19.651723] Hardware name: Dell Inc. PowerEdge R520/03P5P3, BIOS 2.9.0 01/09/2020
[ 19.651723] RIP: 0010:__radix_tree_lookup+0x6e/0xa0
[ 19.651724] Code: fd 0f b6 08 49 89 c0 48 89 f0 48 d3 e8 83 e0 3f 4c 8d 0c c5 28 00 00 00 4b 8d 04 08 4d 01 c1 48 8b 00 48 3d 02 04 00 00 74 9f <84> c9 74 0c 48 89 c1 83 e1 03 48 83 f9 02 74 c3 48 85 d2 74 03 4c
[ 19.651724] RSP: 0018:ffff9a7d4655ce28 EFLAGS: 00000086
[ 19.651725] RAX: ffff89e718039b62 RBX: 0000000000000040 RCX: 0000000000000018
[ 19.651726] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff89e38a4065c8
[ 19.651726] RBP: 0000000000000002 R08: ffff89e71803fd98 R09: ffff89e71803fdc0
[ 19.651727] R10: 0000000000000000 R11: ffff89e38a4065d0 R12: ffff8a026bca8140
[ 19.651727] R13: ffff89e479957700 R14: ffff89e38765b2c0 R15: ffff89e3d14506b0
[ 19.651728] FS: 0000000000000000(0000) GS:ffff8a02bf340000(0000) knlGS:0000000000000000
[ 19.651728] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 19.651729] CR2: 000055cf2bab66c8 CR3: 0000001febe10002 CR4: 00000000001706e0
[ 19.651729] Call Trace:
[ 19.651730] <NMI>
[ 19.651730] ? watchdog_overflow_callback.cold.7+0x1e/0x70
[ 19.651730] ? __perf_event_overflow+0x52/0x100
[ 19.651731] ? handle_pmi_common+0x200/0x2d0
[ 19.651731] ? __set_pte_vaddr+0x32/0x50
[ 19.651732] ? __native_set_fixmap+0x24/0x40
[ 19.651732] ? ghes_copy_tofrom_phys+0xf9/0x250
[ 19.651732] ? intel_pmu_handle_irq+0x119/0x450
[ 19.651733] ? perf_event_nmi_handler+0x2d/0x50
[ 19.651733] ? nmi_handle+0x63/0x110
[ 19.651734] ? default_do_nmi+0x49/0x110
[ 19.651734] ? do_nmi+0x19c/0x210
[ 19.651734] ? end_repeat_nmi+0x16/0x69
[ 19.651735] ? __radix_tree_lookup+0x6e/0xa0
[ 19.651735] ? __radix_tree_lookup+0x6e/0xa0
[ 19.651735] ? __radix_tree_lookup+0x6e/0xa0
[ 19.651736] </NMI>
[ 19.651736] <IRQ>
[ 19.651736] handle_tx_event.isra.58+0x5d/0x1290
[ 19.651737] ? usb_giveback_urb_bh+0xb0/0x140
[ 19.651737] xhci_irq+0x1c5/0x3e0
[ 19.651738] __handle_irq_event_percpu+0x40/0x190
[ 19.651738] handle_irq_event_percpu+0x30/0x80
[ 19.651738] handle_irq_event+0x36/0x57
[ 19.651739] handle_edge_irq+0x82/0x190
[ 19.651739] handle_irq+0x1c/0x30
[ 19.651739] do_IRQ+0x49/0xd0
[ 19.651740] common_interrupt+0xf/0xf
[ 19.651740] </IRQ>
[ 19.651740] RIP: 0010:native_safe_halt+0xe/0x20
[ 19.651741] Code: 00 a8 08 75 be e9 23 ff ff ff 31 ff e9 6a ff ff ff 90 90 90 90 90 90 90 90 90 90 90 e9 07 00 00 00 0f 00 2d 16 41 5e 00 fb f4 <c3> cc cc cc cc 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 e9 07 00 00
[ 19.651742] RSP: 0018:ffff9a7d462ffe28 EFLAGS: 00000246 ORIG_RAX: ffffffffffffffdd
[ 19.651743] RAX: 0000000080004000 RBX: ffff89e387458464 RCX: 000000000000001f
[ 19.651743] RDX: ffffffffa59c6b80 RSI: ffffffffa72d1ce0 RDI: 0000000000000001
[ 19.651744] RBP: ffff89e387458464 R08: 0000000000000001 R09: ffff89e387458400
[ 19.651744] R10: 00000355e97d9cb7 R11: ffff8a02bf372484 R12: 0000000000000001
[ 19.651745] R13: ffffffffa72d1ce0 R14: 0000000000000001 R15: 0000000000000001
[ 19.651745] ? acpi_processor_thermal_init.cold.6+0x66/0x66
[ 19.651746] ? acpi_processor_thermal_init.cold.6+0x66/0x66
[ 19.651746] acpi_idle_do_entry+0x93/0xa0
[ 19.651746] acpi_idle_enter+0x5f/0xd0
[ 19.651747] cpuidle_enter_state+0x86/0x470
[ 19.651747] cpuidle_enter+0x2c/0x40
[ 19.651748] do_idle+0x26f/0x2d0
[ 19.651748] cpu_startup_entry+0x6f/0x80
[ 19.651748] start_secondary+0x187/0x1d0
[ 19.651749] secondary_startup_64_no_verify+0xd1/0xdb
[ 19.651749] Kernel panic - not syncing: Hard LOCKUP
[ 19.651750] CPU: 5 PID: 0 Comm: swapper/5 Not tainted 4.18.0-553.27.1.el8_10.x86_64 #1
[ 19.651750] Hardware name: Dell Inc. PowerEdge R520/03P5P3, BIOS 2.9.0 01/09/2020
[ 19.651751] Call Trace:
[ 19.651751] <NMI>
[ 19.651751] dump_stack+0x41/0x60
[ 19.651752] panic+0xe7/0x2ac
[ 19.651752] ? secondary_startup_64_no_verify+0x8c/0xdb
[ 19.651752] nmi_panic.cold.11+0xc/0xc
[ 19.651753] watchdog_overflow_callback.cold.7+0x5c/0x70
[ 19.651753] __perf_event_overflow+0x52/0x100
[ 19.651754] handle_pmi_common+0x200/0x2d0
[ 19.651754] ? __set_pte_vaddr+0x32/0x50
[ 19.651754] ? __native_set_fixmap+0x24/0x40
[ 19.651755] ? ghes_copy_tofrom_phys+0xf9/0x250
[ 19.651755] intel_pmu_handle_irq+0x119/0x450
[ 19.651756] perf_event_nmi_handler+0x2d/0x50
[ 19.651756] nmi_handle+0x63/0x110
[ 19.651756] default_do_nmi+0x49/0x110
[ 19.651757] do_nmi+0x19c/0x210
[ 19.651757] end_repeat_nmi+0x16/0x69
[ 19.651757] RIP: 0010:__radix_tree_lookup+0x6e/0xa0
[ 19.651758] Code: fd 0f b6 08 49 89 c0 48 89 f0 48 d3 e8 83 e0 3f 4c 8d 0c c5 28 00 00 00 4b 8d 04 08 4d 01 c1 48 8b 00 48 3d 02 04 00 00 74 9f <84> c9 74 0c 48 89 c1 83 e1 03 48 83 f9 02 74 c3 48 85 d2 74 03 4c
[ 19.651759] RSP: 0018:ffff9a7d4655ce28 EFLAGS: 00000086
[ 19.651759] RAX: ffff89e718039b62 RBX: 0000000000000040 RCX: 0000000000000018
[ 19.651760] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff89e38a4065c8
[ 19.651760] RBP: 0000000000000002 R08: ffff89e71803fd98 R09: ffff89e71803fdc0
[ 19.651761] R10: 0000000000000000 R11: ffff89e38a4065d0 R12: ffff8a026bca8140
[ 19.651761] R13: ffff89e479957700 R14: ffff89e38765b2c0 R15: ffff89e3d14506b0
[ 19.651762] ? __radix_tree_lookup+0x6e/0xa0
[ 19.651762] ? __radix_tree_lookup+0x6e/0xa0
[ 19.651763] </NMI>
[ 19.651763] <IRQ>
[ 19.651763] handle_tx_event.isra.58+0x5d/0x1290
[ 19.651764] ? usb_giveback_urb_bh+0xb0/0x140
[ 19.651764] xhci_irq+0x1c5/0x3e0
[ 19.651764] __handle_irq_event_percpu+0x40/0x190
[ 19.651765] handle_irq_event_percpu+0x30/0x80
[ 19.651765] handle_irq_event+0x36/0x57
[ 19.651766] handle_edge_irq+0x82/0x190
[ 19.651766] handle_irq+0x1c/0x30
[ 19.651766] do_IRQ+0x49/0xd0
[ 19.651767] common_interrupt+0xf/0xf
[ 19.651767] </IRQ>
[ 19.651767] RIP: 0010:native_safe_halt+0xe/0x20
[ 19.651768] Code: 00 a8 08 75 be e9 23 ff ff ff 31 ff e9 6a ff ff ff 90 90 90 90 90 90 90 90 90 90 90 e9 07 00 00 00 0f 00 2d 16 41 5e 00 fb f4 <c3> cc cc cc cc 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 e9 07 00 00
[ 19.651769] RSP: 0018:ffff9a7d462ffe28 EFLAGS: 00000246 ORIG_RAX: ffffffffffffffdd
[ 19.651769] RAX: 0000000080004000 RBX: ffff89e387458464 RCX: 000000000000001f
[ 19.651770] RDX: ffffffffa59c6b80 RSI: ffffffffa72d1ce0 RDI: 0000000000000001
[ 19.651770] RBP: ffff89e387458464 R08: 0000000000000001 R09: ffff89e387458400
[ 19.651771] R10: 00000355e97d9cb7 R11: ffff8a02bf372484 R12: 0000000000000001
[ 19.651771] R13: ffffffffa72d1ce0 R14: 0000000000000001 R15: 0000000000000001
[ 19.651772] ? acpi_processor_thermal_init.cold.6+0x66/0x66
[ 19.651772] ? acpi_processor_thermal_init.cold.6+0x66/0x66
[ 19.651773] acpi_idle_do_entry+0x93/0xa0
[ 19.651773] acpi_idle_enter+0x5f/0xd0
[ 19.651774] cpuidle_enter_state+0x86/0x470
[ 19.651774] cpuidle_enter+0x2c/0x40
[ 19.651774] do_idle+0x26f/0x2d0
[ 19.651775] cpu_startup_entry+0x6f/0x80
[ 19.651775] start_secondary+0x187/0x1d0
[ 19.651775] secondary_startup_64_no_verify+0xd1/0xdb
[ 20.678937] Shutting down cpus with NMI
[ 20.678937] Kernel Offset: 0x24400000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)

I am running AlmaLinux 9.4. Today, dnf update gave the following error. I would appreciate any help.

Last metadata expiration check: 3:20:48 ago on Thu 21 Nov 2024 09:28:49 AM +03.
Error:
Problem 1: cannot install both libdav1d-1.5.0-2.el9.x86_64 from epel and libdav1d-1.2.1-1.el9.x86_64 from '@System
- package ffmpeg-libs-5.1.6-1.el9.x86_64 from '@System requires libdav1d.so.6()(64bit), but none of the providers can be installed
- cannot install the best update candidate for package libdav1d-1.2.1-1.el9.x86_64
- cannot install the best update candidate for package ffmpeg-libs-5.1.6-1.el9.x86_64
Problem 2: package libavdevice-5.1.6-1.el9.x86_64 from '@System requires ffmpeg-libs(x86-64) = 5.1.6-1.el9, but none of the providers can be installed
- package ffmpeg-libs-5.1.6-1.el9.x86_64 from '@System requires libdav1d.so.6()(64bit), but none of the providers can be installed
- package ffmpeg-libs-5.1.6-1.el9.x86_64 from rpmfusion-free-updates requires libdav1d.so.6()(64bit), but none of the providers can be installed
- cannot install both libdav1d-1.5.0-2.el9.x86_64 from epel and libdav1d-1.2.1-1.el9.x86_64 from '@System
- package libavif-0.11.1-5.el9.x86_64 from epel requires libdav1d.so.7()(64bit), but none of the providers can be installed
- cannot install the best update candidate for package libavif-0.11.1-4.el9.x86_64
- cannot install the best update candidate for package libavdevice-5.1.6-1.el9.x86_64
Problem 3: package ffmpeg-5.1.6-1.el9.x86_64 from '@System requires ffmpeg-libs(x86-64) = 5.1.6-1.el9, but none of the providers can be installed
- package ffmpeg-libs-5.1.6-1.el9.x86_64 from '@System requires libdav1d.so.6()(64bit), but none of the providers can be installed
- package ffmpeg-libs-5.1.6-1.el9.x86_64 from rpmfusion-free-updates requires libdav1d.so.6()(64bit), but none of the providers can be installed
- cannot install both libdav1d-1.5.0-2.el9.x86_64 from epel and libdav1d-1.2.1-1.el9.x86_64 from '@System
- package libheif-1.16.1-2.el9.x86_64 from epel requires libdav1d.so.7()(64bit), but none of the providers can be installed
- cannot install the best update candidate for package libheif-1.16.1-1.el9.x86_64
- cannot install the best update candidate for package ffmpeg-5.1.6-1.el9.x86_64
(try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

After upgrading to AlmaLinux 9.5, I am no longer able to compile the NVidia driver for my (old) Tesla K20c GPU.

I am trying to use the NVidia driver version 460.106.00 (which seems to be the latest version that supports the K20c) and the kernel drivers no longer compile.

I'm getting this error during compilation:

CC [M] /home/.../nvidia/NVIDIA-Linux-x86_64-460.106.00/kernel/nvidia/nv-frontend.o

In file included from /home/.../nvidia/NVIDIA-Linux-x86_64-460.106.00/kernel/nvidia/nv-frontend.c:11:

/home/.../nvidia/NVIDIA-Linux-x86_64-460.106.00/kernel/common/inc/nv-misc.h:20:12: fatal error: stddef.h: No such file or directory

20 | #include <stddef.h> // NULL

| ^~~~~~~~~~

compilation terminated.

Do you have any idea how to fix this, or will I have to give up my old GPU?

Hello. I am done with the almalinux 9.5 kde update and it seems that open zfs is not yet compatible with the kernal.

The ZFS modules are not loaded.
Try running '/sbin/modprobe zfs' as root to load them.
[abc@pc ~]$ sudo /sbin/modprobe zfs
modprobe: FATAL: Module zfs not found in directory /lib/modules/5.14.0-503.11.1.el9_5.x86_64

Should I wait for it to update or I am having a problem?

Thanks,

Hi,

currently I'm using rsync (python scripted) as my backup server. It provides hardlink deduplication, notification, pre/post job, integrity check, simple prune, restore process, systemd timers, but it misses block deduplication, compression, encryption and different backend other than filesystem (like S3/S3 compatible). For encryption I mean encrypt backups for offsite backup on cloud (but locally I would use LUKS) and I would like to use gocrytpfs but it is not seems very strong. Actually I'm backuing up 6 server without problem on top of ZFS pool to accomplish compression thing.

I see there are many software that provides what I reported above but I want perform pull backup (well the server run/delete backup and client cannot access the server) not something like borgbackup that support mainly push backup.

What software are you using successfull for your production server?

Thank you in advance

Hi Folks - On the AWS console I took an AMI of AlmaLinux 9 and made some new LVM's for /var/tmp/, /var/log and /tmp. When the box comes up for the first time I can log on. When I reboot I can' not ssh to it. The console mentions read-only for those new LVM's. I don't see any issues with /etc/fstab. Am I missing a step? Does the kernel boot option need to modified? Banging my head!

Doing the same for RHEL 9 and no issues.

Thanks

I've installed 9.4 on a dozen seven year old HP blades ( ProLiant BL460c Gen9 ) in an enclosure.

On some machines /dev/shm has these permissions:

drwxr-xr-x.  2 root root          40 Oct 28 13:27 shm

On other machines it has:

drwxrwxrwt.  2 root root          40 Nov 15 11:24 shm

On the machines with 755 permissions "mount | grep shm" shows nothing. On the other machines "mount | grep shm" shows:

tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,seclabel,inode64)

Any ideas on what could be causing this difference? I am running an application that fails with this error message only on the machines with the 755 /dev/shm permissions:

OMP: Error #179: Function Can't open SHM2 failed:
OMP: System error #2: No such file or directory

AlmaLinux 9.5 Stable Now Available

The AlmaLinux OS Foundation is announcing the general availability of AlmaLinux OS 9.5 codenamed “Teal Serval”!

Installation ISOs are available on the mirrors now for all 4 architectures:

• Intel/AMD (x86_64)
• ARM64 (aarch64)
• IBM PowerPC (ppc64le)
• IBM Z (s390x)

Torrents are available as well at:

• Intel/AMD (x86_64)
• ARM64 (aarch64)
• IBM PowerPC (ppc64le)
• IBM Z (s390x)

ISOs, Live Images, Cloud and Containers

AlmaLinux also offers a variety of Cloud, Container and Live Images. The builds for these get kicked off as soon as the public repository is ready.

The following images are expected to be available shortly.

• Container images including Platform and UBIs alternatives. We provide a wide variety of containers for your use.
• LXC/LXD
• Live Media for GNOME, GNOME-mini, KDE, XFCE, MATE and more.
• Cloud Images
  • AWS for x86_64 and AArch64 EC2 Instances
  • Azure for x86_64 and AArch64 VMs
  • Google Cloud
  • Generic Cloud/Cloud-init for all 4 architectures
  • OpenNebula for x86_64 and AArch64 architectures
  • Oracle Cloud Infrastructure for x86_64 and AArch64 Instances
• Vagrant Boxes:
  • Libvirt
  • VirtualBox
  • Hyper-V
  • VMWare for x86_64 and AArch64
  • Parallels for AArch64
• Raspberry Pi
• Windows Subsystem for Linux for x86_64 and AArch64

Release Notes and More Information

AlmaLinux 9.5 aims to improve performance, development tooling, and security. Updated module streams offer better support for web applications. New versions of compilers provide access to the latest features and optimizations that improve performance and enable better code generation. The release also introduces improvements to system performance monitoring, visualization, and system performance data collecting. Security updates are directed at strengthening cryptography, while SELinux policies enforce stricter access controls. Additionally, crypto-policies offer stronger encryption, improving the overall security of the system.

You can read the full release notes for this version on the wiki: AlmaLinux OS 9.5 Release Notes.

What can you do to help?

Your input into testing and feedback is crucial and essential for successful production releases. Please, report any bugs you may see on the Bug Tracker. Also, pop into the AlmaLinux Community Chat and join our Testing Channel, post a question on our 9.5 Forum, on our AlmaLinux Community on Reddit or catch us on X.

Please report any bugs you may see on the Bug Tracker.

Enjoy the release and have fun!

https://repo.almalinux.org/almalinux/9.5/isos/

There are NetworkManager-vpnc alike packages on many other distributions, but not on AlmaLinux. I need it to connect to a HPC which uses Cisco vpn. The available script **vpnc** does not practice well.

What is the recommended doc/book on SELinux for a beginner? Is there any implementation difference in AlmaLinux?

I've tried to search all over the internet for a solution but came with none.
My ELevate process to upgrade from CentOS 7 to AlmaLinux 8 is breaking with:

   Stderr: Failed to create directory /var/lib/leapp/el8userspace//sys/fs/selinux: Read-only file system
Failed to create directory /var/lib/leapp/el8userspace//sys/fs/selinux: Read-only file system
No matches found for the following disable plugin patterns: subscription-manager
Repository extras is listed more than once in the configuration
Repository extras-source is listed more than once in the configuration
Warning: Package marked by Leapp to upgrade not found in repositories metadata: gpg-pubkey leapp leapp-upgrade-el7toel8 python2-leapp
RPM: warning: Generating 6 missing index(es), please wait...
Error: Transaction test error:
file /usr/share/mysql/charsets/Index.xml from install of mysql-common-8.0.36-1.module_el8.9.0+3735+82bd6c11.x86_64 conflicts with fi
le from package MariaDB-common-10.4.34-1.el7.centos.x86_64
file /usr/share/mysql/charsets/armscii8.xml from install of mysql-common-8.0.36-1.module_el8.9.0+3735+82bd6c11.x86_64 conflicts with
file from package MariaDB-common-10.4.34-1.el7.centos.x86_64
file /usr/share/mysql/charsets/ascii.xml from install of mysql-common-8.0.36-1.module_el8.9.0+3735+82bd6c11.x86_64 conflicts with fi
le from package MariaDB-common-10.4.34-1.el7.centos.x86_64
file /usr/share/mysql/charsets/cp1250.xml from install of mysql-common-8.0.36-1.module_el8.9.0+3735+82bd6c11.x86_64 conflicts with f
ile from package MariaDB-common-10.4.34-1.el7.centos.x86_64
file /usr/share/mysql/charsets/cp1251.xml from install of mysql-common-8.0.36-1.module_el8.9.0+3735+82bd6c11.x86_64 conflicts with f
ile from package MariaDB-common-10.4.34-1.el7.centos.x86_64
file /usr/share/mysql/charsets/cp1256.xml from install of mysql-common-8.0.36-1.module_el8.9.0+3735+82bd6c11.x86_64 conflicts with f
ile from package MariaDB-common-10.4.34-1.el7.centos.x86_64
file /usr/share/mysql/charsets/cp1257.xml from install of mysql-common-8.0.36-1.module_el8.9.0+3735+82bd6c11.x86_64 conflicts with f
ile from package MariaDB-common-10.4.34-1.el7.centos.x86_64
file /usr/share/mysql/charsets/cp850.xml from install of mysql-common-8.0.36-1.module_el8.9.0+3735+82bd6c11.x86_64 conflicts with fi
le from package MariaDB-common-10.4.34-1.el7.centos.x86_64
file /usr/share/mysql/charsets/cp852.xml from install of mysql-common-8.0.36-1.module_el8.9.0+3735+82bd6c11.x86_64 conflicts with fi
le from package MariaDB-common-10.4.34-1.el7.centos.x86_64
file /usr/share/mysql/charsets/cp866.xml from install of mysql-common-8.0.36-1.module_el8.9.0+3735+82bd6c11.x86_64 conflicts with fi
le from package MariaDB-common-10.4.34-1.el7.centos.x86_64
file /usr/share/mysql/charsets/dec8.xml from install of mysql-common-8.0.36-1.module_el8.9.0+3735+82bd6c11.x86_64 conflicts with fil
e from package MariaDB-common-10.4.34-1.el7.centos.x86_64
file /usr/share/mysql/charsets/geostd8.xml from install of mysql-common-8.0.36-1.module_el8.9.0+3735+82bd6c11.x86_64 conflicts with
file from package MariaDB-common-10.4.34-1.el7.centos.x86_64
file /usr/share/mysql/charsets/greek.xml from install of mysql-common-8.0.36-1.module_el8.9.0+3735+82bd6c11.x86_64 conflicts with fi
le from package MariaDB-common-10.4.34-1.el7.centos.x86_64
file /usr/share/mysql/charsets/hebrew.xml from install of mysql-common-8.0.36-1.module_el8.9.0+3735+82bd6c11.x86_64 conflicts with f
ile from package MariaDB-common-10.4.34-1.el7.centos.x86_64
file /usr/share/mysql/charsets/hp8.xml from install of mysql-common-8.0.36-1.module_el8.9.0+3735+82bd6c11.x86_64 conflicts with file
from package MariaDB-common-10.4.34-1.el7.centos.x86_64
file /usr/share/mysql/charsets/keybcs2.xml from install of mysql-common-8.0.36-1.module_el8.9.0+3735+82bd6c11.x86_64 conflicts with
file from package MariaDB-common-10.4.34-1.el7.centos.x86_64
file /usr/share/mysql/charsets/koi8r.xml from install of mysql-common-8.0.36-1.module_el8.9.0+3735+82bd6c11.x86_64 conflicts with fi
le from package MariaDB-common-10.4.34-1.el7.centos.x86_64
file /usr/share/mysql/charsets/koi8u.xml from install of mysql-common-8.0.36-1.module_el8.9.0+3735+82bd6c11.x86_64 conflicts with fi
le from package MariaDB-common-10.4.34-1.el7.centos.x86_64
file /usr/share/mysql/charsets/latin1.xml from install of mysql-common-8.0.36-1.module_el8.9.0+3735+82bd6c11.x86_64 conflicts with f
ile from package MariaDB-common-10.4.34-1.el7.centos.x86_64
file /usr/share/mysql/charsets/latin2.xml from install of mysql-common-8.0.36-1.module_el8.9.0+3735+82bd6c11.x86_64 conflicts with f
ile from package MariaDB-common-10.4.34-1.el7.centos.x86_64
file /usr/share/mysql/charsets/latin5.xml from install of mysql-common-8.0.36-1.module_el8.9.0+3735+82bd6c11.x86_64 conflicts with f
ile from package MariaDB-common-10.4.34-1.el7.centos.x86_64
file /usr/share/mysql/charsets/latin7.xml from install of mysql-common-8.0.36-1.module_el8.9.0+3735+82bd6c11.x86_64 conflicts with f
ile from package MariaDB-common-10.4.34-1.el7.centos.x86_64
file /usr/share/mysql/charsets/macce.xml from install of mysql-common-8.0.36-1.module_el8.9.0+3735+82bd6c11.x86_64 conflicts with fi
le from package MariaDB-common-10.4.34-1.el7.centos.x86_64
file /usr/share/mysql/charsets/macroman.xml from install of mysql-common-8.0.36-1.module_el8.9.0+3735+82bd6c11.x86_64 conflicts with
file from package MariaDB-common-10.4.34-1.el7.centos.x86_64
file /usr/share/mysql/charsets/swe7.xml from install of mysql-common-8.0.36-1.module_el8.9.0+3735+82bd6c11.x86_64 conflicts with fil
e from package MariaDB-common-10.4.34-1.el7.centos.x86_64

I already tried to remove the MariaDB packages and I confirmed that the directory /user/share/mysql/charsets doesn't exists, but it still gives me the same error. Also I have removed the MariaDB repository from yum and it did nothing at all...

What am I missing?

Hi,

I am using:

Operating System: AlmaLinux 9.4
KDE Plasma Version: 5.27.11
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.9
Kernel Version: 5.14.0-427.42.1.el9_4.x86_64 (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-3610QM CPU @ 2.30GHz
Memory: 15.1 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 4000
Manufacturer: LENOVO
Product Name: 2342A49
System Version: ThinkPad T430

and I am having my bluetooth constantly getting disconnected. The problem goes away when I turn it off and on, but it seems to happen randomly, sometimes every hour, sometimes every 5 minutes, sometimes it takes several hours.

When I get disconected I can still see that the bluetooth is running and the devices are still showing as connected, but the keyboard, mouse, etc do not respond.

On RHEL-based distros, what's the equivalent to Arch's pacnew files where there's an update to the system config file and it's saved as another file because it shouldn't be overwriting your system config file (unless perhaps it's unmodified)?

Also, I'm looking for a way to version control system configs but it doesn't seem as straightforward as using e.g. etckeeper because verson-controlling files with different permissions/ownership seems too tricky for git to handle alone (also I have files at /usr and /var that should be managed as well, not just /etc). For dotfiles at $HOME, I just clone and treat $HOME as a working tree so that's straightforward.

I'm currently looking to use Ansible to easily configure workstations/servers and with that approach, it seems tracking system configs as template files might be more appropriate as the "Ansible" way. It would be preferable (or at least more intuitive) to track the files themselves as opposed to e.g. interacting only with the templates and then running the playbook every time I make changes to system config), but this might be workable given system configs don't change nearly as much as e.g. dotfiles. Any other approaches I should consider?

Any comments much appreciated.

I am not so familiar with working with server but now i got an almalinux8

  Virtualization: kvm
  Operating System: AlmaLinux 8.10 (Cerulean Leopard)
  CPE OS Name: cpe:/o:almalinux:almalinux:8::baseos
  Kernel: Linux 4.18.0-553.16.1.el8_10.x86_64
  Architecture: x86-64

Next, I need to install python3.9 without changing the default version used by the whole system

python3 --version
Python 3.6.8

and I see

sudo dnf module list | grep -i python
[sudo] password for xxxx:
libselinux-python    2.8             common                                   Python 2 bindings for libselinux
python27             2.7 [d]         common [d]                               Python programming language, version 2.7
python36             3.6 [d][e]      build, common [d]                        Python programming language, version 3.6
python38             3.8 [d]         build, common [d]                        Python programming language, version 3.8
python39             3.9 [d]         build, common [d]                        Python programming language, version 3.9
python38-devel       3.8             build, common                            Python programming language, version 3.8
python39-devel       3.9             build, common                            Python programming language, version 3.9

So my idea is enable, install and modify only my bash

sudo dnf module enable python39
sudo dnf install python39
#open ~/.bashrc
# Add Python 3.9 to PATH
export PATH="/usr/bin/python3.9:$PATH"
alias python=python3.9

Is this the correct way to go? Am I missing something? Thanks and I am sorry for this basic question but I just start my journey to work with server.

When I use Google Meet through the Chrome browser, screen sharing doesn't work. The audio works and I can see the other person's screen but I couldn't share mine.

It was working well in the past. Anyone facing this?

Someone told me RHEL 9 ships with ssh's PasswordAuthentication disabled by default. I checked the default sshd_config for Almalinux 9 and it has everything commented out, so the defaults for ssh are used, which is to allow PasswordAuthentication.

It doesn't really matter as users would want to secure ssh and other services anyway, but I was wondering why it's different from RHEL 9. I would think AlmaLinux defaults to RHEL's defaults for the most part. Does this mean AlmaLinux is less opinionated (i.e. respecting upstream choices) even at the expense of more secure defaults like in RHEL 9?

Again, simply talking about defaults, which probably shouldn't be used. Just curious design choices and what can be expected.

I've installed Alma 9.3 on new hardware. Minimal Installation & CIS Level 2 Workstation

It appears that I have massive connectivity problems.

During dnf -y groupinstall workstation the download stalls and reports something like this.

(30/856): avahi-tools-0.8-20.el9.x86_64.rpm      67 kB/s |  38 kB     00:00
(31/856): baobab-40.0-3.el9.x86_64.rpm           65 kB/s | 379 kB     00:05
[MIRROR] adwaita-icon-theme-40.1.1-3.el9.noarch.rpm: Curl error (28): Timeout was reached for https://mirror.alpha-labs.net/almalinux/9.4/AppStream/x86_64/os/Packages/adwaita-icon-theme-40.1.1-3.el9.noarch.rpm [Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds]
[MIRROR] almalinux-backgrounds-90.5.1-1.1.el9.noarch.rpm: Curl error (28): Timeout was reached for https://mirror.alpha-labs.net/almalinux/9.4/AppStream/x86_64/os/Packages/almalinux-backgrounds-90.5.1-1.1.el9.noarch.rpm [Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds]
[MIRROR] bind-libs-9.16.23-18.el9_4.6.x86_64.rpm: Curl error (28): Timeout was reached for https://mirror.alpha-labs.net/almalinux/9.4/AppStream/x86_64/os/Packages/bind-libs-9.16.23-18.el9_4.6.x86_64.rpm [Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds]
(32/856): bind-libs-9.16.23-18.el9_4.6.x86_64.r  21 kB/s | 1.2 MB     01:00
(33/856): bind-license-9.16.23-18.el9_4.6.noarc 678 kB/s |  12 kB     00:00
(34/856): bind-utils-9.16.23-18.el9_4.6.x86_64.  55 kB/s | 201 kB     00:03
(35/856): blktrace-1.2.0-19.el9.x86_64.rpm      500 kB/s | 143 kB     00:00
(36/856): bluez-obexd-5.64-2.el9.x86_64.rpm     541 kB/s | 227 kB     00:00
(37/856): brlapi-0.8.2-4.el9.x86_64.rpm         707 kB/s | 173 kB     00:00
[MIRROR] almalinux-backgrounds-90.5.1-1.1.el9.noarch.rpm: Curl error (28): Timeout was reached for https://mirror.alpha-labs.net/almalinux/9.4/AppStream/x86_64/os/Packages/almalinux-backgrounds-90.5.1-1.1.el9.noarch.rpm [Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds]
[MIRROR] adwaita-icon-theme-40.1.1-3.el9.noarch.rpm: Curl error (28): Timeout was reached for http://ftp.halifax.rwth-aachen.de/almalinux/9.4/AppStream/x86_64/os/Packages/adwaita-icon-theme-40.1.1-3.el9.noarch.rpm [Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds]
[MIRROR] brltty-6.3-4.el9.x86_64.rpm: Curl error (28): Timeout was reached for http://ftp.fau.de/almalinux/9.4/AppStream/x86_64/os/Packages/brltty-6.3-4.el9.x86_64.rpm [Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds]
[MIRROR] adwaita-icon-theme-40.1.1-3.el9.noarch.rpm: Curl error (28): Timeout was reached for https://mirror.alpha-labs.net/almalinux/9.4/AppStream/x86_64/os/Packages/adwaita-icon-theme-40.1.1-3.el9.noarch.rpm [Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds]
(38/856): brltty-6.3-4.el9.x86_64.rpm            21 kB/s | 1.5 MB     01:12
(39/856): cairo-1.17.4-7.el9.x86_64.rpm         180 kB/s | 659 kB     00:03
(40/856): cairo-gobject-1.17.4-7.el9.x86_64.rpm 620 kB/s |  18 kB     00:00
(41/856): cairomm-1.14.2-10.el9.x86_64.rpm      906 kB/s |  62 kB     00:00
[MIRROR] almalinux-backgrounds-90.5.1-1.1.el9.noarch.rpm: Curl error (28): Timeout was reached for http://ftp.halifax.rwth-aachen.de/almalinux/9.4/AppStream/x86_64/os/Packages/almalinux-backgrounds-90.5.1-1.1.el9.noarch.rpm [Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds]
(42/856): checkpolicy-3.6-1.el9.x86_64.rpm       12 kB/s | 351 kB     00:29
(43/856): cheese-3.38.0-6.el9.x86_64.rpm        135 kB/s |  94 kB     00:00
[MIRROR] cheese-libs-3.38.0-6.el9.x86_64.rpm: Curl error (28): Timeout was reached for http://ftp.uni-bayreuth.de/linux/almalinux/9.4/AppStream/x86_64/os/Packages/cheese-libs-3.38.0-6.el9.x86_64.rpm [Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds]
[MIRROR] cheese-libs-3.38.0-6.el9.x86_64.rpm: Curl error (28): Timeout was reached for https://mirror.alpha-labs.net/almalinux/9.4/AppStream/x86_64/os/Packages/cheese-libs-3.38.0-6.el9.x86_64.rpm [Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds]
(44/856): cheese-libs-3.38.0-6.el9.x86_64.rpm    10 kB/s | 829 kB     01:22
(45/856): chrome-gnome-shell-42.1-1.el9.x86_64. 1.8 MB/s |  50 kB     00:00
[MIRROR] almalinux-backgrounds-90.5.1-1.1.el9.noarch.rpm: Curl error (28): Timeout was reached for http://ftp.uni-bayreuth.de/linux/almalinux/9.4/AppStream/x86_64/os/Packages/almalinux-backgrounds-90.5.1-1.1.el9.noarch.rpm [Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds]
[MIRROR] adwaita-icon-theme-40.1.1-3.el9.noarch.rpm: Curl error (28): Timeout was reached for http://ftp.uni-bayreuth.de/linux/almalinux/9.4/AppStream/x86_64/os/Packages/adwaita-icon-theme-40.1.1-3.el9.noarch.rpm [Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds]
[MIRROR] cldr-emoji-annotation-39-2.el9.noarch.rpm: Curl error (28): Timeout was reached for http://ftp.fau.de/almalinux/9.4/AppStream/x86_64/os/Packages/cldr-emoji-annotation-39-2.el9.noarch.rpm [Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds]

Then it ends.

Since I have installed other machines in a similar way I don't think that it is a general network problem.

Is there a way to check the hardware (e.g. network interface card) with my current installation?

Now that Alma Linux is no longer 1to1 with RHEL, I'm thinking about migrating my Alma Linux 9 sever to RHEL 9. I have a developer license with Red Hat so it would be free.

Does anyone have an opinion on if this would be a good move or not?

Hello, before me is upgrade OS. I am looking for manual or …. how to do it. Unfortunately OS is on physical HW. I am writing step by step procedure and now i have: 1/ change repo to Alma 2/ run upgrade 3/ change network script to NetworkManager 4/ reboot to new OS

On second point will be necessary, maybe, make transaction in yum/dnf shell. Do you have anybody better manual/procedure/...?

Does anyone know a wat to migrate Alma Linux 9 to RHEL?

Hello I am using the following command to update the system (almalinux kde 9.4). Recently I am getting the following and it is not updating the flatpak.

[abc@pc ~]$ sudo dnf update -y && sudo flatpak update -y
[sudo] password for abc:    
Dependencies resolved.
Nothing to do.
Complete!
Looking for updates…
Info: org.kde.Platform//6.6 is end-of-life, with reason:
  We strongly recommend moving to the latest stable version of the Platform and SDK
Applications using this runtime:
  com.github.quaternion, com.obsproject.Studio
Nothing to do.

Please advise me and thank you.