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]

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

Setup Dual DE KDE Plasma 6.2 Beta && Cosmic on F41 Server and KDE Spin Nightly builds

Looks like presence on Fedora 41 Server preinstalled KDE Plasma 6.2 Beta allows to setup Cosmic DE as second DE following  https://copr.fedorainfracloud.org/coprs/ryanabx/cosmic-epoch/  . The most recent Fedora 41 KDE Spin behaves the same way as F41 Server. 

The Fedora Project does not exercise any power over the contents of this repository beyond the rules outlined in the Copr FAQ at 

<https://docs.pagure.org/copr.copr/user_documentation.html#what-i-can-build-in-copr>,

and packages are not held to any quality or security level.

$ sudo dnf copr enable ryanabx/cosmic-epoch

$ sudo dnf install cosmic-desktop

REFERENCES

https://lxer.com/module/newswire/view/346022/index.html

Setup KDE Plasma 6.2 Beta on Fedora 41 Servers and WKS Nightly builds

 Commands below

$ sudo dnf5 install @kde-desktop-environment

$ sudo systemctl enable sddm   # server's setup

$ sudo systemctl set-default graphical.target  # server's setup

work at least in meantime for both F41 Server (no GUI installed by default ) and F41 WKS with Gnome 47 installed by default. Syntax above is mentioned due to command $ dnf5 group list doesn't help at the moment .

Install COSMIC as second DE on the most recent version of ArcoLinuxPlasma6 KVM Guest

This post has been done in respond to Youtube Video 

"Arco : 4262 Installing Cosmic desktop on ArcoLinux and failing - same happened on real metal"

 https://www.youtube.com/watch?v=xojSPVxj3DU&lc=UgxmCcMeOGbav5Zg7hd4AaABAg

 First tune Virt-manager as follows

Log into KDE Plasma6 DE and issue

$ sudo pacman -S cosmic

$ sudo reboot

Dual DE Setup Hyprland (ML4W 2.9.6) && Cosmic on Arch Linux (minimal) via Paru

There was typo in the header, the correct version is ML4W 2.9.6.1-1  Dotfiles

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

 Setup  Arch Linux (minimal)  using archinstall and the most recent ISO as of 09/01/24 along with base-devel git openssh sddm vim nano . We intend to perform both DEs installation using Paru as AUR Helper . Start with paru build 

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

$ cd paru 

$ makepkg -si 

Now we need access to AUR via Paru AUR Helper :

$ paru -S cosmic

$ sudo reboot

$ sudo pacman -S packagekit

$ sudo pacman -S power-profiles-daemon

$ sudo systemctl enable sddm

$ sudo reboot

Verify Cosmic DE functionality

Continue with  Hyprland (ML4W 2.9.6.1-1) installation as second DE been inside Arch Cosmic Instance

$ paru -S ml4w-hyprland

$ ml4w-hyprland-setup

When done reboot and log into Hyprland (ML4W 2.9.6.1) 

Now verify some features of  Hyprland DE functionality

The last snapshot verifies installation on Mission-Center on Hyperland with ML4W 2.9.6.1-1 Dotfiles (Stephan Raabe)

Options provided at SDDM login prompt

REFERENCES

https://www.debugpoint.com/install-cosmic-arch-linux/