Ika is LineageOS 23.2 (Android 16) rebuilt as a desktop operating system running in a VM on Linux. The virtual machine manager is based on Google's Cuttlefish virtual Android device with CrosVM, as opposed to the more widely known QEMU. It began as a way to run Android on Apple Silicon hosts and support for x86-64 arrived later in development.

As of release 260930 there are prebuilt Arch Linux packages for x86_64, alongside Fedora 44 and Debian 13 / Ubuntu 26.04.

Features:

• A resizable window that maintains DPI settings and stays pixel-perfect at any size
• GPU acceleration with OpenGL ES and Vulkan
• Windowed Apps: Run an Android app in its own standalone window on your desktop. Android apps show up in your desktop's app menu, grouped under "Android Apps (Ika)", and the list stays in sync as you install or remove apps.
• Games start fullscreen with gamepad, keyboard and mouse passthrough as HID devices. For games that ignore the mouse, right-click the game's launcher icon and choose "Play with Touch Input" to simulate touch/tap events.

Install on Arch (x86_64)

The download is about 1.8 GB (201 MB app plus a 1.57 GB disk image). Reboot after installing: The packages add you to new groups and install udev rules and limits, so logging out isn't enough.

Build from source:

./ika-buildcreates Arch packages from source. 16 GB RAM minimum is required for a successful Android build. When building from source, you choose MindTheGapps, microG, or a fully de-Googled ROM. Plan on 300 GB of disk and 3 to 6+ hours for the initial Android build.

GitHub: https://github.com/DesktopECHO/ika

Ika is still a young project, so expect some rough edges, and game compatibility varies from title to title. Bug reports and feedback are welcome, especially from users on Arch-based distros.

Hi!

solved: https://www.reddit.com/r/archlinux/comments/1wvzk1j/comment/pdgwnik/

I'm here to report a packaging issue, and ask about potential fixes to it. Some time ago I've noticed that Blender from the main repos was failing to start on my system due to an mismatched abseil-cpp version. I've shrugged it off as a problem related to *-testing repos I was using at the time and switched to AUR's blender-bin for the time being, which uses its own packaged dependencies. However, now that I needed the version that uses the same Python that's installed on the system, I decided to disable testing repos and try using the official package. However, it still doesn't work: the log below shows the error, the package versions, and the fact that I do, indeed, have testing disabled and all packages synced to their official stable versions. Username/hostname are changed just in case

Is the blender package just simply broken for now? Do I have any other options aside from manually compiling it if I want a version that uses Python 3.14 instead of 3.13?

[user@computer ~]$ blender
blender: error while loading shared libraries: libabsl_log_internal_check_op.so.2508.0.0: cannot open shared object file: No such file or directory
[user@computer ~]$ yay -Q abseil-cpp
abseil-cpp 20260817.0-2
[user@computer ~]$ yay -Q blender
blender 17:5.2.2-2
[user@computer ~]$ yay -Ql abseil-cpp | rg 2508
[user@computer ~]$ rg testing /etc/pacman.conf
68:# The testing repositories are disabled by default. To enable, uncomment the
72:#[core-testing]
78:#[extra-testing]
87:#[multilib-testing]
[user@computer ~]$ sudo pacman -Syyuu
[sudo] password for user:
:: Synchronizing package databases...
 core                                                                                                                                         126.3 KiB   590 KiB/s 00:00 [#########################################################################################################] 100%
 extra                                                                                                                                          8.5 MiB  5.41 MiB/s 00:02 [#########################################################################################################] 100%
 multilib                                                                                                                                      82.2 KiB   473 KiB/s 00:00 [#########################################################################################################] 100%
:: Starting full system upgrade...
 there is nothing to do

I remember editing udev rules to do this with a different controller, and had no issues, but this lebron james edition controller will not listen and im not entirely sure why, ive tried creating another udev rules file and im not entirely sure what to call it but something that has to do with the product and vendor id, below is the 2 files i created for this, along with its lsusb entry and evtest touchpad entry

the vendor id thing: 
KERNEL=="uinput", MODE="0666"
KERNEL=="hidraw*", SUBSYSTEM=="hidraw", ATTRS{idVendor}=="054c", ATTRS{idProduct}=="0ce6", MODE="0666"
KERNEL=="hidraw*", SUBSYSTEM=="hidraw", KERNELS=="0003:054C:0CE6.*", MODE="0666"

touchpad rules:
# Disable DS4 touchpad acting as mouse
# USB
ATTRS{name}=="Sony Corp. DualSense wireless controller (PS5)", ENV{LIBINPUT_IGNORE_DEVICE}="1"
# Bluetooth
ATTRS{name}=="DualSense Wireless Controller Touchpad", ENV{LIBINPUT_IGNORE_DEVICE}="1"


evtest:
Input driver version is 1.0.1
Input device ID: bus 0x3 vendor 0x54c product 0xce6 version 0x8111
Input device name: "Sony Interactive Entertainment Wireless Controller Touchpad"


lsusb:
Bus 001 Device 010: ID 054c:0ce6 Sony Corp. DualSense wireless controller (PS5)

not sure what else to put, let me know and ill happily provide any more information needed, the vendor id thing was basically copy and pasted aside from some small changes to the vendor id product id and bus number, from a file called "50-ds4drv.rules" which i faintly rememebr being related to my controller rules on the controller that worked with the rules, (from like november of 2025 so thats why my memory on this is a little foggy) that i searched up and saw results about it being related to that, aside from the glaring obvious sony vendor id and ds4 mention lol

Hi folks, desperately need some help here...

I followed this guide to install Virt-Manager: https://tanis.codes/posts/virt-manager-qemu-arch-linux/

Which caused this issue with Steam failing to launch: https://help.steampowered.com/en/faqs/view/2112-4548-B98B-3A06

How can I either fix this or undo what broke it?

I am seriously getting fed up with different VM solutions breaking things when I try to use them.

Output when launching Steam from the console: https://pastebin.com/Dfe499vh

Recently I have been interested in the Wubi input method, and I have found out that the input method has 3 different versions, Wubi86, Wubi98, and New Century Wubi. I also have installed Fcitx5 on my computer and I wonder, what version of Wubi is used by Fcitx5?

So it turns out the timing was pure coincidence. I changed my search terms to be specifically about KDE Plasma, and found some results that said the splashscreen is what actually causes the delay... I disabled that, and the login time is just a couple of seconds...I expect the entries in my pastebin are normal, I just hadn't looked before.

I will leave my original blurb in case it amuses any veterans.

-------------

Hi folks,

I tried to get winapps working so I could use Adobe CS programs, but I kept running into issues so I abandoned it and removed Docker.

I had Windows installed in the docker container and had placed and edited the config files, but I ran into an issue with xfreerdp3 where it could no longer connect to the VM even though I could still connect via the browser or with Remmina, after a reboot... I wasn't sure what I had done, so I attempted to remove everything to give myself a fighting chance if I wanted to try the process again from scratch.

Ever since then I have a 20+ second wait from the login screen to the desktop being displayed (KDE Plasma) whereas before it was only a second or two.

If I do systemd-analyze blame, I have between 100 and 150 entries which are some variation of "dev-disk-by\x2d ..."

seen here; https://pastebin.com/rcCtwAWq

I do have quite a few drives in this system, my WIndows install has four SSDs, two NVME and two SATA, and then I added a fifth SSD to try different LInux variants. But the other drives aren't mounted at login, I have to click on them to mount them.

Any ideas please?

Bear in mind when wording your replies that I am on day 2 of "Try Linux for a month" with a view to abandoning WIndows. I have plenty of professional experience with computers, but this is my first time touching LInux.... We always had "a guy" for that. 😂

This might not have been a day 2 activity, with hindsight...

I have been running into weird issues right after I installed a new 500gb hdd that I share between Linux and windows .

It varies from weird freezes where I can use mouse or keyboard and even the clock stops and I just have to reboot (but I think I solved that one ) to blue screens this is the second time here it is if that helps

Panic Report

Arch: x86_64

Version: 7.2.8-arch1-2

[ 932.307323] CPU: 3 UID: 0 PID: 11870 Comm: rm Tainted: G D OE 7.2.8-arch1-2 #1 PREEMPT(full) 186163caea6eb5dc4b2a0252463c7ce1c6927294 [ 932.307329] Tainted: [D]=DIE, [O]=OOT_MODULE, [E]=UNSIGNED_MODULE [ 932.307331] Hardware name: Micro-Star International Co., Ltd. MS-7C96/A520M-A PRO (MS-7C96), BIOS 1.G0 10/16/2023 [ 932.307334] RIP: 0010:__list_del_entry_valid_or_report+0xe3/0xf6 [ 932.307338] Code: 48 0f b9 3a e9 60 ff ff ff b0 01 48 39 7d 08 74 23 48 89 ef e8 6e 7f 46 00 48 8d 3d 67 86 8d 02 48 8b 55 08 48 89 e9 48 89 de <67> 48 0f b9 3a e9 35 ff ff ff 5b 5d 41 5c e9 7a f4 35 01 48 89 df [ 932.307341] RSP: 0018:ffffceca85d57c98 EFLAGS: 00010202 [ 932.307345] RAX: 0000000000000001 RBX: ffff8d94131c78c8 RCX: ffff8d94131c7ec8 [ 932.307348] RDX: ffff8d94131c78c0 RSI: ffff8d94131c78c8 RDI: ffffffff885226f0 [ 932.307350] RBP: ffff8d94131c7ec8 R08: 0000000000000000 R09: ffffffff8825e540 [ 932.307353] R10: ffffceca85d579e0 R11: ffffceca85d579d8 R12: ffff8d94131c7748 [ 932.307355] R13: 0000000000000000 R14: ffff8d954400fae8 R15: ffff8d954400fad0 [ 932.307358] FS: 00007f747166d740(0000) GS:ffff8d9806fea000(0000) knlGS:0000000000000000 [ 932.307360] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 932.307363] CR2: 00007fc9a4c3b8e0 CR3: 00000001bd8cf000 CR4: 0000000000350ef0 [ 932.307366] Call Trace: [ 932.307369] <TASK> [ 932.307374] list_lru_del.cold+0x8/0xd [ 932.307379] ? __pfx_select_collect+0x10/0x10 [ 932.307384] list_lru_del_obj+0x80/0xa0 [ 932.307390] d_lru_del+0x53/0x90 [ 932.307395] ? srso_return_thunk+0x5/0x5f [ 932.307399] __move_to_shrink_list+0x99/0xd0 [ 932.307404] select_collect+0x6a/0x90 [ 932.307407] d_walk+0xd5/0x2d0 [ 932.307412] ? __pfx_select_collect+0x10/0x10 [ 932.307415] shrink_dcache_tree+0x91/0x1a0 [ 932.307422] vfs_rmdir+0x12c/0x270 [ 932.307427] filename_rmdir+0x1a3/0x260 [ 932.307434] __x64_sys_unlinkat+0x74/0x80 [ 932.307438] do_syscall_64+0xaa/0x660 [ 932.307442] ? srso_return_thunk+0x5/0x5f [ 932.307446] ? srso_return_thunk+0x5/0x5f [ 932.307449] ? do_syscall_64+0x5f/0x660 [ 932.307453] ? srso_return_thunk+0x5/0x5f [ 932.307457] entry_SYSCALL_64_after_hwframe+0x76/0x7e [ 932.307461] RIP: 0033:0x7f747151252b [ 932.307472] Code: 77 05 c3 0f 1f 40 00 48 8b 15 e1 67 10 00 f7 d8 64 89 02 b8 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 07 01 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d b5 67 10 00 f7 d8 64 89 01 48 [ 932.307475] RSP: 002b:00007ffda3dbb948 EFLAGS: 00000216 ORIG_RAX: 0000000000000107 [ 932.307478] RAX: ffffffffffffffda RBX: 000055f8a4d26290 RCX: 00007f747151252b [ 932.307481] RDX: 0000000000000200 RSI: 000055f8a4d26390 RDI: 0000000000000006 [ 932.307483] RBP: 00007ffda3dbba10 R08: 0000000000000003 R09: 00007ffda3dbba3c [ 932.307486] R10: 0000000000000000 R11: 0000000000000216 R12: 000055f8a47dc060 [ 932.307488] R13: 0000000000000001 R14: 00007ffda3dbbb20 R15: 000055f8a47dc001 [ 932.307496] </TASK> [ 932.307498] ---[ end trace 0000000000000000 ]--- [ 932.322157] Oops: invalid opcode: 0000 [#2] SMP NOPTI [ 932.322166] CPU: 3 UID: 0 PID: 39 Comm: ksoftirqd/3 Tainted: G D W OE 7.2.8-arch1-2 #1 PREEMPT(full) 186163caea6eb5dc4b2a0252463c7ce1c6927294 [ 932.322173] Tainted: [D]=DIE, [W]=WARN, [O]=OOT_MODULE, [E]=UNSIGNED_MODULE [ 932.322175] Hardware name: Micro-Star International Co., Ltd. MS-7C96/A520M-A PRO (MS-7C96), BIOS 1.G0 10/16/2023 [ 932.322178] RIP: 0010:__d_free+0xd/0x30 [ 932.322185] Code: ff 90 66 66 2e 0f 1f 84 00 00 00 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3 0f 1e fa 0f 1f 44 00 00 48 8d b7 50 <ff> ff ff 48 b8 00 05 2e 00 95 8d ff ff 48 89 c7 e9 fe e2 f2 ff 0f [ 932.322188] RSP: 0018:ffffceca80283da0 EFLAGS: 00010246 [ 932.322192] RAX: ffff8d94131cfef0 RBX: 0000000000005009 RCX: ffff8d9500372c00 [ 932.322195] RDX: ffffffff86201be8 RSI: 0000000000000002 RDI: ffff8d94131cfef0 [ 932.322197] RBP: ffff8d978fef42c0 R08: ffff8d94131cf3c0 R09: ffffffff85e64970 [ 932.322200] R10: fffff3dbc04c73c0 R11: ffff8d95002e0500 R12: ffff8d9500c49bc0 [ 932.322202] R13: ffffceca80283df0 R14: 0000000000000008 R15: 000000d912e8c8ed [ 932.322205] FS: 0000000000000000(0000) GS:ffff8d9806fea000(0000) knlGS:0000000000000000 [ 932.322208] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 932.322210] CR2: 00007fc9a4c3b8e0 CR3: 00000001bd8cf000 CR4: 0000000000350ef0 [ 932.322213] Call Trace: [ 932.322216] <TASK> [ 932.322219] rcu_do_batch+0x360/0x630 [ 932.322226] ? srso_return_thunk+0x5/0x5f [ 932.322234] rcu_core+0x141/0x2e0 [ 932.322240] handle_softirqs+0xe8/0x2a0 [ 932.322246] ? __pfx_smpboot_thread_fn+0x10/0x10 [ 932.322251] run_ksoftirqd+0x2f/0x40 [ 932.322255] smpboot_thread_fn+0xf3/0x220 [ 932.322260] kthread+0xe4/0x120 [ 932.322264] ? __pfx_kthread+0x10/0x10 [ 932.322269] ret_from_fork+0x2a7/0x330 [ 932.322274] ? __pfx_kthread+0x10/0x10 [ 932.322278] ret_from_fork_asm+0x1a/0x30 [ 932.322287] </TASK> [ 932.322289] Modules linked in: rfcomm snd_seq_dummy snd_hrtimer snd_seq uhid algif_hash algif_skcipher af_alg snd_ctl_led bnep vfat exfat fat btusb btmtk btrtl btbcm snd_hda_codec_alc662 btintel intel_rapl_msr snd_hda_codec_realtek_lib snd_hda_codec_atihdmi snd_hda_codec_generic snd_hda_codec_hdmi intel_rapl_common bluetooth snd_hda_intel rfkill snd_usb_audio ee1004 snd_hda_codec snd_usbmidi_lib aesni_intel snd_hda_core snd_ump r8169 gf128mul snd_intel_dspcfg snd_rawmidi aead snd_intel_sdw_acpi realtek snd_seq_device snd_hwdep rapl phy_package wmi_bmof pcspkr snd_pcm sp5100_tco mdio_devres joydev mousedev snd_timer libphy k10temp mc snd i2c_piix4 mdio_bus soundcore i2c_smbus gpio_amdpt vboxnetadp(OE) vboxnetflt(OE) gpio_generic mac_hid vboxdrv(OE) kvm_amd ccp kvm irqbypass pkcs8_key_parser crypto_user uinput i2c_dev zram 842_decompress 842_compress lz4hc_compress amdgpu drm_buddy amdxcp i2c_algo_bit drm_ttm_helper ttm drm_exec drm_panel_backlight_quirks nvme gpu_sched drm_suballoc_helper nvme_core nvme_keyring [ 932.322400] hid_playstation drm_display_helper nvme_auth led_class_multicolor video cec ff_memless wmi [ 932.322415] ---[ end trace 0000000000000000 ]--- [ 932.322418] RIP: 0010:__d_lookup_rcu+0x61/0x120 [ 932.322422] Code: 00 48 8b 04 c2 48 83 f8 01 0f 86 cd 00 00 00 4c 89 64 24 10 48 83 e0 fe 4c 8b 66 08 eb 0c 48 8b 00 48 85 c0 0f 84 86 00 00 00 <44> 8b 58 fc 4c 39 50 10 75 ea 48 39 58 18 75 e4 49 89 d9 48 8b 70 [ 932.322425] RSP: 0018:ffffceca80257a08 EFLAGS: 00010206 [ 932.322429] RAX: 0000000200240000 RBX: 0000000577045c71 RCX: 0000000077045c71 [ 932.322431] RDX: ffff8d978ee00000 RSI: ffffceca80257aa0 RDI: ffff8d95794b1240 [ 932.322434] RBP: ffffceca80257ad4 R08: 0000000000000000 R09: 00000000000000a8 [ 932.322436] R10: ffff8d95794b1240 R11: 00000000ffff8d96 R12: ffff8d950a628a98 [ 932.322438] R13: ffff8d9536630000 R14: ffffceca80257bd0 R15: ffff8d950a628a80 [ 932.322441] FS: 0000000000000000(0000) GS:ffff8d9806fea000(0000) knlGS:0000000000000000 [ 932.322443] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 932.322446] CR2: 00007fc9a4c3b8e0 CR3: 00000001bd8cf000 CR4: 0000000000350ef0 [ 932.322449] Kernel panic - not syncing: Fatal exception in interrupt [ 932.322546] Kernel Offset: 0x4a00000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)

Edit : Solved the problem was caused by resizing my Linux partition which caused some broken some time shift hardlinks to break which caused a kernel panic every time any service tried to access them . I booted into a live usb an mounted my Linux partition and ran e2fsck and deleted time shift snapshots and that fixed it

I'm trying to find the root cause of a problem with the keyboard backlight on my laptop.

I've already created several posts about this issue on different forums and groups, but unfortunately I haven't been able to find a solution. I've tried various approaches, including linux-ogc (recommended for asus gaming laptop owners) and other suggested solutions, but nothing helped.

I eventually decided to completely reinstall the system and try the same procedure that helped me the previous time.

First, I installed Windows, performed all available updates, and installed Armoury Crate. The keyboard backlight was not working correctly even in Windows using the default settings, so I used Armoury Crate to configure the keyboard lighting.

After that, I reinstalled Arch Linux.

And surprisingly, the keyboard backlight is now working in Arch Linux.

This is why I'm making this post now, while everything is still working. I would like to find out what exactly is different this time compared to my previous installation.

Is there a way to check and document the current state of the system, for example:

• which kernel modules are currently loaded,
• which drivers are responsible for the keyboard and its backlight,
• which devices/interfaces related to the keyboard are detected,
• whether any kernel or bootloader parameters affect the backlight,
• which ACPI interfaces or settings are currently being used,
• whether Armoury Crate could have changed some hardware or firmware state,
• whether there is a specific module, parameter, firmware setting, or configuration that is responsible for the backlight working now.

My main goal is to collect as much information as possible while the backlight is working, so that I can later compare it with the system state if the backlight stops working again.

I'm worried that at some point a package update, kernel update, or some other change could cause the keyboard backlight to stop working again. If that happens, I want to be able to identify the actual cause and restore the backlight without having to reinstall Windows every time.

Could someone please suggest which commands or diagnostic information I should collect right now, while the backlight is working, so that I can compare it later if the problem returns?

If there is a way to create some kind of "snapshot" of the current configuration related to ACPI, HID, ASUS/ROG hardware, keyboard drivers, kernel modules, etc., I would be happy to do that as well.

I'm hoping someone here can help me track down the actual cause of this problem. I've already gone through hundreds of posts and tried many different solutions, but so far nothing has worked.

This time, I'd really like to take advantage of the fact that the backlight is currently working and collect the necessary information before the problem happens again.

specs:

asus tuf gaming a16

AMD Ryzen™ 7 260 w/ Radeon™ 780M Graphics × 16

gpu: nvidia 5060 laptop

DISCLAIMER: a LLM helped me write this because I'm no expert and couldn't possibly provide all these info on my own

I'm trying to set up oo7 as my Secret Service implementation on Arch Linux with COSMIC.

My environment:

• COSMIC Wayland
• greetd + cosmic-greeter
• oo7 0.6.0-3 from the official Arch repositories
• libsecret installed
• PAM authentication through login

I followed the ArchWiki oo7 instructions and initially put the PAM entries in /etc/pam.d/greetd, but eventually discovered that my COSMIC Greeter configuration contains:

[general]
service = "login"

So I moved the PAM configuration to /etc/pam.d/login:

auth       required     pam_securetty.so
auth       requisite    pam_nologin.so
auth       include      system-local-login
auth       optional     pam_oo7.so
account    include      system-local-login
session    include      system-local-login
session    optional     pam_oo7.so
password   include      system-local-login

After rebooting, pam_oo7 is definitely being invoked during login. The journal shows:

greetd[1368]: Connecting to daemon socket at: /run/user/1000/oo7-pam.sock
greetd[1286]: Failed to send secret to oo7 daemon: Failed to connect to daemon socket: Child process failed with exit code 1

The interesting part is that the PAM module appears to try to start the daemon when the socket doesn't exist.

I inspected the installed pam_oo7.so and found these strings:

Socket not found, attempting to start daemon
Attempting to start oo7-daemon directly
/usr/bin/oo7-daemon
Started oo7-daemon with PID
Child process terminated abnormally

However, the installed package does not provide /usr/bin/oo7-daemon.

For example:

$ ls -l /usr/bin/oo7-daemon
ls: cannot access '/usr/bin/oo7-daemon': No such file or directory

But the package does provide:

/usr/lib/oo7-daemon
/usr/lib/security/pam_oo7.so

The systemd user service also points to the /usr/lib location:

ExecStart=/usr/lib/oo7-daemon

The service itself is currently disabled, as recommended for the PAM setup.

So as far as I can tell, the situation is:

pam_oo7
  ↓
/run/user/1000/oo7-pam.sock doesn't exist
  ↓
tries to start /usr/bin/oo7-daemon
  ↓
/usr/bin/oo7-daemon doesn't exist
  ↓
child exits with code 1
  ↓
PAM can't connect to the socket

I'm not going to create a symlink or otherwise modify the installation yet, because I don't know whether this is:

1. a packaging bug in oo7 0.6.0-3,
2. an intentional difference between the PAM module and the packaged daemon location,
3. something specific to how pam_oo7 is expected to be configured with greetd/COSMIC, or
4. something I'm misunderstanding about the intended daemon startup mechanism.

What is the correct way to handle this? Should pam_oo7 be starting /usr/lib/oo7-daemon somehow, should the daemon be started separately, or is the /usr/bin/oo7-daemon path in pam_oo7.so indicative of a package/version bug?

I'd appreciate guidance before I make any workaround changes.

Is there any issue with arch aur rpc i am facing problems installing packages from aur even tried the manual way build but cloned from aur any solutions

I would like to know how to make the scrollock keyboard key turn on the keyboard backlight?
I didn’t found a solution in the Arch Wikis. Also I want to find solution that makes caps lock and num lock turn off the backlight.

I’m using KDE plasma Wayland. Everything is updated in latest version in Extra.

What would yall recommend

My dell precison running arch linux... From this mouth it's laging, and even sometimes when I'm launching 2 programs at the same time it can go to the kernel panic... My hardware checked and this okay it's arch linux problem... And it's laging everyvere!

Sometimes I need an old version of a package, I thought it would be great if I could create a virtual environment where I can use an older version of a package similar to python environments.

I was thinking of making one, so I was wondering if there is some glaring reason why nobody has created one yet.

Hello friends, here is the question: How is it furned to be that Linux cannot boot without a Microsoft FAT32 partition? How do you solve this problem? Can a serious server-grade system like Linux really not boot without a Microsoft FAT32 partition? Even if I move `/boot` to Ext4 or Btrfs, I still have to keep `/boot/efi` as FAT32, because otherwise the system won't boot. wtf?