Setting up Gnome and KDE Plasma on the same instance of Manjaro 23.1.1

There are several desktop environments and window managers available for Manjaro, each with their own unique style, interface, and features. Furthermore, it is possible to install multiple environments if desired, which can be selected at the login screen at any time. Users are not restricted to whatever comes pre-installed with a particular flavour of Manjaro.

Enable Wayland support in KDE Plasma session 

Just issue following command and re-login

Now issue the command

$ sudo pacman -S gnome

and logout from KDE Plasma session . 

You are supposed to view updated logging screen

For now select from drop up menu in left down corner Gnome(Wayland) and log into Gnome session

Re-login via new logging screen to Plasma(Wayland)

It seems that installing Manjaro KDE Plasma as the first graphical environment followed by installing GNOME 45.2 DE optimally combines this two DEs on the latest build of Manjaro

Setting up Wayland on openSUSE Tumbleweed

UPDATE as of 12/27/23

Same setup as below succeeded on openSUSE Leap 15.5. But in this case it requires significantly more testing then for Tumbleweed

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

By default during install  openSUSE Tumbleweed with KDE  Desktop installer selects X11 as windowing system. After logging into KDE ( on openSUSE ) load Yast Control Center and proceed as shown on snapshots below

Software->View->Pattern

Next step is  "select && highlight" Gnome (Wayland)

On screen up here select "Continue"

Now all packages required for Wayland support on Gnome 45.2 and KDE 5.27.10 are supposed to be installed on the system. 

You are all set . After log out right click in left down corner of original logging screen to select desired option. It may be Gnome 45.2 either KDE 5.27.10 with Wayland support

Option with the most recent version of Gnome

Option with KDE 5.27.10

OpenSUSE Tumbleweed Installer vs Anaconda (Blivet-GUI)

 OpenSUSE Tumbleweed Installer  in expert mode creates disk layout with volumes group VG_SUSE. At first glance, it has practically the same possibilities as demonstrates Anaconda (Blivet-GUI) and more over creates subfolders under "/" root as BTRFS subvolumes

A BTRFS subvolume is a part of filesystem with its own independent file/directory hierarchy and inode number namespace. Subvolumes can share file extents. A snapshot is also subvolume, but with a given initial content of the original subvolume. A subvolume has always inode number 256. A subvolume looks like a normal directory, with some additional operations described below. Subvolumes can be renamed or moved, nesting subvolumes is not restricted but has some implications regarding snapshotting. The numeric id (called subvolid or rootid) of the subvolume is persistent and cannot be changed.

Installer creates PV on /dev/vda3 and then associates LVM group VG_SUSE with PV just created.  Afterwards three LVMs are been crteated and "/" root FS (BTRFS) , /home FS (XFS), swap area get mounted on corresponding LVMs  - LV1_SUSE,LV2_SUSE,LV3_SUSE 

KVM Hypervisor installed essentially automatically

Another disk layout snapshot via Yast Control Center

Install Deepin Desktop Environment on Ubuntu Server 23.04

UPDATE as of 12/07/23

Original post has been written with intend to make gdm3 default display manager and it works with no issues at all. However it appears that Lightdm could replace gdm3 as Default DM, following below is a brief description of sequence of steps to achieve this goal. First of all

$ sudo dpkg-reconfigure gdm3  and choose default DM to be Lightdm

Next step is an update  of lightdm.service  -   /usr/lib/systemd/system/lightdm.service

adding at the bottom of file two lines :

[Install]

WantedBy=graphical.target

Now enable lightdm.service $ sudo systemctl enable lightdm .

# Just in case "enabling shared memory" via virt-manager has 

# been done for Ubuntu Servers guests .

and  issue `shutdown -r now` via deepin-terminal

Actions been done are supposed to bring you to text login prompt.  Then go ahead and login to text mode console. Right after this action Deepin Graphical console will be brought up and allow you to get into DDE which seems to behave stable.

Immediately one more question raises up - how much we actually need ubuntu-gnome-desktop to be installed if Lightdm may be Default DM.

UPDATE as of 12/08/23 So far instances been built without ubuntu-gnome-desktop behave same way as described above

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

In particular case we do have to install ubuntu-gnome-desktop before ubuntudde-dde, presuming that gdm3 will become the  Default Desktop manager

$ sudo apt install ubuntu-gnome-desktop

$ sudo systemctl set-default graphical.target

$ sudo reboot

$ sudo add-apt-repository ppa:ubuntudde-dev/stable

$ sudo apt update

$ sudo apt install ubuntudde-dde

$ sudo reboot

$ sudo apt update

Configure Linux bridge br0

boris@ubuntusrv:~$ cat  /etc/netplan/01-netcfg.yaml

network:

 ethernets:

   enp1s0:

     dhcp4: false

     dhcp6: false

 # add configuration for bridge interface

 bridges:

   br0:

     interfaces: [enp1s0]

     dhcp4: false

     addresses: [192.168.0.73/24]

     macaddress: 52:54:00:da:0b:72

     routes:

       - to: default

         via: 192.168.0.1

         metric: 100

     nameservers:

       addresses: [8.8.8.8]

     parameters:

       stp: false

     dhcp6: false

 version: 2

boris@ubuntusrv:~$ sudo netplan apply

Calamares Installer 3.2.6(X) vs Debian Network Installer (Anaconda Blivet-GUI)

 Configutation below might be created with some previous manual intervention causes Calamares to crash

Same configuration may be created via Debian Network Installer either Anaconda Advanced Installer (Blivet-GUI) . Both mentionded installers pass through runtime phase and successfully create Debian 12.2 or Fedora 39 Server (WKS) instances .