Build a Fresh Arch ISO to test archinstall 3.0.0 on KVM Guest

 Following   https://xerolinux.xyz/posts/build-archiso/

Issue commands: 

$ sudo pacman -S archiso
$ mkdir ~/ArchWork && mkdir ~/ArchOut
$ sudo mkarchiso -v -w ~/ArchWork -o ~/ArchOut /usr/share/archiso/configs/releng

 

Next Step is obvious 

❯ pwd

/home/boris/ArchOut
❯ cp archlinux-2024.11.19-x86_64.iso ~/Downloads/

 

You are ready for straight forward deploying Arch Linux via Virt-manager in standard way and watch new interface provided by current status of Arch with no failure in pipewire section

When done reboot the instance as usual

Make sure that deployment has been performed via Virt-Manager connected to libvirtd daemon

~/Downloads
❯ ls -l *.iso
.rw-r--r-- 1.2G libvirt-qemu 10 Nov 16:17  archlinux-2024.11.01-x86_64.iso
.rw-r--r-- 1.2G libvirt-qemu 19 Nov 09:10  archlinux-2024.11.19-x86_64.iso

Getting Spice console to work for Arch Plasma 6.2.3 Guest at ArchLinux Plasma 6.2.3 KVM Virtualiztion Host (bare metal)

UPDATE as of 11/16/24 See https://gitlab.com/qemu-project/qemu/-/issues/2639#note_2199435292 

Just downgrade QEMU to the previous version - QEMU 9.1.0-2 will solve the problem    $ sudo pacman -U  /var/cache/pacman/pkg/qemu-*9.1.0-2-x86_64.pkg.tar.zst  until 9.1.2 would be done by maintainers .

========================================

Switch from from ICH9 to AC97 (sound)  via Virt-Manager Guest features  resolves the issue in meantime. Sound from youtube's video running inside VM starts to go via external speakers. Tested for F41 KDE Spin Guest at ArchLinux Plasma 6.2.3 KVM Virtualiztion Host as well. Also notice that Fedora 41 KVM Virtualization Server works with any deployed guest and Arch Linux Plasma in particular via Spice Console with default option ICH9 without any problems.

The most recent openSUSE-Krypton as KVM guest at  ArchLinux Plasma 6.2.3 KVM Virtualiztion Host behaves exactly the same way as was described above - switching Virt-Manager setting sound ICH9 => AC97. Afterwards everything works fine .

Setup Dual DE Arch KDE Plasma 6.2.3 and Hyprland ML4W 2.9.6.5 on bare metal

 First DE supposed to be installed is KDE Plasma 6.2.3, installation follows instructions proposed in thread  https://github.com/archlinux/archinstall/issues/2764  due to known issue with pipewire-pulse.service in arch ISO version as of 11/01/2024

# pacman -Sy git

# git clone https://github.com/archlinux/archinstall

# cd archinstall 

# python -m archinstall

Managing this way you come through Piperwire section of archinstall without any trouble.

After reboot we may install Stephan's Raabe Hyprland ML4W 2.9.6.5 Dotfiles straight away via commands

 $ sudo pacman -S --needed base-devel git

 $ git clone https://aur.archlinux.org/yay.git

 $ cd yay 

 $ makepkg -si

 $ yay -S ml4w-hyprland

 $ ml4w-hyprland-setup 

Original video may be seen here https://www.youtube.com/watch?v=JT_YHknWfKs

Switching to Plasma DE may be performed via really nice prompt screen which can inherit wallpaper has been setup for Hyprland session

Login prompt screen was done in VENV

Activation Desktops Effects => Windows Management => Cube feature on F41 KDE Spin in VENV

 I was forced to enable 3D accelearation && OpenGL and bring up just once KVM instance of F41 KDE Spin  to obtain option Desktops Effects => Windows Management => Cube visible for activation. Six virtual desktops had been already activated. Afterwards Super+"C" started to work.  Then I shutdown F41 KDE instance and disabled  3D accelearation && OpenGL. Following runtime sessions of F41 KDE KVM Guest would have Cube Desktop feature enabled and Super+"C" functional even in normal UEFI mode with disabled options 3D accelearation && OpenGL of Virtual-manager.

So in normal UEFI mode session of Virt-manager F41 still keeps required for Cube Desktop options enabled and Cube Desktop feature functional

Same way behaves Arch Linux Plasma 6.2.2 KVM Guest regarding Cube Desktop feature activation

UPDATE as of 10/26/24. Cockpit Web Console supports Fedora's 41 Server's KDE RC 1.4 Cube Desktop Feature described above  

Start Pycharm-community-2024.2.3 on Suse Tumbleweed

 Straight forward install Pycharm-community-2024.2.3 via extracting tar ball either snap will fail showing up following error

boris@localhost:~/Downloads/pycharm-community-2024.2.3/bin> ./pycharm.sh
**Start Failed**
Internal error
java.lang.InternalError: Unable to load native GTK libraries

To avoid this failure libgthread-2_0-0 is supposed to be preinstalled :

 boris@localhost:~> sudo zypper install libgthread-2_0-0

[sudo] password for root:  
Loading repository data...
Reading installed packages...
Resolving package dependencies...

The following NEW package is going to be installed:
 libgthread-2_0-0

1 new package to install.

Package download size:    78.9 KiB

Package install size change:
             |      39.2 KiB  required by packages that will be installed
   39.2 KiB  |  -      0 B    released by packages that will be removed

Backend:  classic_rpmtrans
Continue? [y/n/v/...? shows all options] (y): y
Retrieving: libgthread-2_0-0-2.82.1-1.1.x86_64 (Main Repository (OSS))              (1/1),  78.9 KiB     
Retrieving: libgthread-2_0-0-2.82.1-1.1.x86_64.rpm ..................................[done (43.2 KiB/s)]

Checking for file conflicts: .....................................................................[done]
(1/1) Installing: libgthread-2_0-0-2.82.1-1.1.x86_64 .............................................[done]
Running post-transaction scripts .................................................................[done]

$ sudo zypper install glib2-devel would work as well

Same step should be undertaken for openSUSE_Krypton.x86_64-16.0-Build13.241.iso

Plasma version is 6.2.80 for Krypton has  been assembled on 10/14/24

References

https://dbaxps.blogspot.com/2024/02/install-python-311-pycharm-on-opensuse.html

Setup Python 3.13 via pyenv along with system-wide 3.12.7 on ArchLinux KDE Plasma 6.2

 Pyenv is a tool for managing multiple Python versions. Once pyenv is installed you can easily switch between one project that uses Python 3.13.0 and a system-wide default Python 3.12.7.

$ git clone https://github.com/pyenv/pyenv.git ~/.pyenv

The following two installs are required to perform successful build Python 3.13.0 for particular user via pyenv. This build won't affect system-wide Python 3.12.7

$ sudo pacman -S base-devel

$ sudo pacman -S tk

Now we update ~/.bashrc as follows :

$ echo 'export PYENV_ROOT="$HOME/.pyenv"' >> ~/.bashrc

$ echo 'export PATH="$PYENV_ROOT/bin:$PATH"' >>  ~/.bashrc

$ echo 'eval "$(pyenv init --path)"' >> ~/.bashrc

$ source  ~/.bashrc

$ pyenv install 3.13.0

Downloading Python-3.13.0.tar.xz...

-> https://www.python.org/ftp/python/3.13.0/Python-3.13.0.tar.xz

Installing Python-3.13.0...

Installed Python-3.13.0 to /home/boris/.pyenv/versions/3.13.0

$ pyenv global 3.13.0

Notice that Pycharm projects running 3D plots requires PyQt6 to be

installed in particular virtual environment of this project

REFERENCES

https://snapcraft.io/install/pycharm-community/arch

Setup DUAL DE KDE Plasma 6.2 Beta && Hyprland (ML4W 2.9.6.1) on Arch Linux

 Perform standard install KDE Plasma 6.1.5  on Arch Linux as KVM instance. Then add following lines right above  core-testing entry :-

[kde-unstable]
Include = /etc/pacman.d/mirrorlist

into /etc/pacman.conf 

When /etc/pacman.conf would be updated  issue 

 $ sudo pacman -Syu ; $ sudo reboot

Next step would be install Hyprland (ML4W 2.9.6.1)  via Paru as suggested below

$ git clone https://aur.archlinux.org/paru-git.git 

$ cd paru-git 

$ makepkg -si 

$ paru -S ml4w-hyprland

$ sudo reboot

$ ml4w-hyprland-setup

$ sudo reboot

Log into Hyprland via updated SDDM promt

Then you may run neofetch for instance inside Hyprland (ML4W 2.9.6.1) DE