KDE Plasma Workspaces for RLRC

Hi,

I tried installing the “KDE Plasma Workspaces” after installing “epel-release” with my Rocky Linux Release Candidate 8.3 setup and running into below pasted errors:

yum groupinstall "KDE Plasma Workspaces"

Last metadata expiration check: 0:01:09 ago on Sun 02 May 2021 02:25:44 AM IST.
Error:
Problem 1: conflicting requests

  • nothing provides xmessage needed by plasma-workspace-5.18.4.1-2.el8.x86_64
    Problem 2: package sddm-breeze-5.18.4.1-2.el8.noarch requires plasma-workspace = 5.18.4.1-2.el8, but none of the providers can be installed
  • conflicting requests
  • nothing provides xmessage needed by plasma-workspace-5.18.4.1-2.el8.x86_64
    Problem 3: package plasma-desktop-5.18.4.1-2.el8.1.x86_64 requires plasma-workspace >= 5.18, but none of the providers can be installed
  • conflicting requests
  • nothing provides xmessage needed by plasma-workspace-5.18.4.1-2.el8.x86_64
    Problem 4: package kde-print-manager-19.12.3-2.el8.x86_64 requires plasma-workspace, but none of the providers can be installed
  • conflicting requests
  • nothing provides xmessage needed by plasma-workspace-5.18.4.1-2.el8.x86_64
    (try to add ‘–skip-broken’ to skip uninstallable packages or ‘–nobest’ to use not only best candidate packages)

Also, when tried installing xmessage package, it gave below errors:

yum install xmessage

Last metadata expiration check: 0:12:06 ago on Sun 02 May 2021 02:25:44 AM IST.
No match for argument: xmessage
Error: Unable to find a match: xmessage

Any suggestions to fix this will be very much appreciated.

Thanks,
Bhavik

Platform:

  • Rocky Linux release 8.3

  • Linux localhost.localdomain 4.18.0-240.22.1.el8.x86_64 #1 SMP Mon Apr 12 04:29:16 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

1 Like

[moving to development/testing]

Hello and welcome! If you’re familiar with filing bugs, please do so on our Bugzilla server.

Thanks

Hi,
It’s not a bug, you have to enable the powertools repo and the dependencies will be met.
xmessage is not in a package called xmessage.
Regards,
GZU

Hi @bhavik-fractal , i partialy succeeded.
Yet i dont have KDE display … yet !
I keep on trying.
Best & nice day
Fred

sudo dnf install epel-release
sudo dnf config-manager --set-enabled powertools
sudo dnf --enablerepo=epel,powertools group -y install “KDE Plasma Workspaces” “base-x”
startx

Seemed to work for me.

I’m on Rocky 8.4 and followed the instructions at

with the exception of editing bash_profile at the end.
which got me most of the way…
wks ago now and I didn’t write it all down but…
to default system Login I changed what turns out to be “Display Manager” from Gnome GDM to KDE SDDM though took a while to discover SDDM was KDE (no longer a kdm). Also various older posts refer to config files … none of which are present because its now done via systemctl with: sudo systemctl enable sddm.service -f

oh yeah, and use X11 not Wayland if you want to be able to set a “primary” monitor and place 2nd monitor on left of main. ( applies to Gnome too )

1 Like

I have been trying out Rocky using Oracle Virtual Box and VMware Workstation Pro running on Win 10 and so far I haven’t managed to get KDE working at all while running under VMware. I tried installed KDE from a fresh install of with a base “Server with GUI” and the “Workstation” option and both times when I change the GUI to Plasma at the login screen I get sent to a blank screen with an error message box for “ksplashqml” crashing. I also tried installing Rocky with the latest Beta, 16, and 15 “hardware” versions and I still get the same issue. On a fresh install of CentOS 8, I can perform the same installation steps for KDE and not run into any issues running the virt on VMware Workstation. I suspect the ksplashqml crash is more of just a symptom than a root cause but, it doesn’t generate a good crash dump either way.

I can get to a CLI prompt using CTRL + ALT + F2 and when I check the status of display-manager.service it shows that gdm.service is running. If I force it to use sddm instead, then the system hangs on boot. With Oracle VirtualBox, when using the KDE GUI, the display-manager is also using gdm too but, the KDE GUI does load successfully.

This is from gnome “Problem Reporting” app

Nov 04 08:28:42 Rocky-KDE.localdomain plasmashell[25454]: org.kde.plasmaquick: Applet preload policy set to 1
Nov 04 08:28:42 Rocky-KDE.localdomain plasmashell[25454]: kf5.kpackage: No metadata file in the package, expected it at: "/usr/share/wallpapers/Next/contents/images/"
Nov 04 08:28:42 Rocky-KDE.localdomain plasmashell[25454]: kf5.kpackage: No metadata file in the package, expected it at: "/usr/share/wallpapers/Next/contents/images/"
Nov 04 08:28:42 Rocky-KDE.localdomain plasmashell[25454]: kf5.kpackage: No metadata file in the package, expected it at: "/usr/share/wallpapers/Next/contents/images/"
Nov 04 08:28:42 Rocky-KDE.localdomain plasmashell[25454]: file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:76:9: Unable to assign [undefined] to QStringList
Nov 04 08:28:42 Rocky-KDE.localdomain plasmashell[25454]: file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:75:9: Unable to assign [undefined] to int
Nov 04 08:28:42 Rocky-KDE.localdomain plasmashell[25454]: file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:75:9: Unable to assign [undefined] to int
Nov 04 08:28:42 Rocky-KDE.localdomain plasmashell[25454]: file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:76:9: Unable to assign [undefined] to QStringList
Nov 04 08:28:43 Rocky-KDE.localdomain plasmashell[25454]: trying to show an empty dialog
Nov 04 08:28:43 Rocky-KDE.localdomain plasmashell[25454]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:146:19: QML Loader: Binding loop detected for property "height"
Nov 04 08:28:43 Rocky-KDE.localdomain plasmashell[25454]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:146:19: QML Loader: Binding loop detected for property "height"
Nov 04 08:28:44 Rocky-KDE.localdomain plasmashell[25724]: org.kde.plasmaquick: Applet preload policy set to 1
Nov 04 08:28:44 Rocky-KDE.localdomain plasmashell[25724]: kf5.kpackage: No metadata file in the package, expected it at: "/usr/share/wallpapers/Next/contents/images/"
Nov 04 08:28:44 Rocky-KDE.localdomain plasmashell[25724]: kf5.kpackage: No metadata file in the package, expected it at: "/usr/share/wallpapers/Next/contents/images/"
Nov 04 08:28:44 Rocky-KDE.localdomain plasmashell[25724]: kf5.kpackage: No metadata file in the package, expected it at: "/usr/share/wallpapers/Next/contents/images/"
Nov 04 08:28:44 Rocky-KDE.localdomain plasmashell[25724]: file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:76:9: Unable to assign [undefined] to QStringList
Nov 04 08:28:44 Rocky-KDE.localdomain plasmashell[25724]: file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:75:9: Unable to assign [undefined] to int
Nov 04 08:28:44 Rocky-KDE.localdomain plasmashell[25724]: file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:75:9: Unable to assign [undefined] to int
Nov 04 08:28:44 Rocky-KDE.localdomain plasmashell[25724]: file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:76:9: Unable to assign [undefined] to QStringList
Nov 04 08:28:44 Rocky-KDE.localdomain plasmashell[25724]: trying to show an empty dialog
Nov 04 08:28:44 Rocky-KDE.localdomain plasmashell[25724]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:146:19: QML Loader: Binding loop detected for property "height"
Nov 04 08:28:44 Rocky-KDE.localdomain plasmashell[25724]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:146:19: QML Loader: Binding loop detected for property "height"

This is from /var/log/messages for the same time period.

Nov  4 08:28:40 Rocky-KDE /usr/libexec/gdm-x-session[25256]: org.kde.plasma.session: Starting autostart service  "/etc/xdg/autostart/org.kde.plasmashell.desktop" ("/usr/bin/plasmashell")
Nov  4 08:28:40 Rocky-KDE /usr/libexec/gdm-x-session[25256]: org.kde.plasma.session: Starting autostart service  "/etc/xdg/autostart/pam_kwallet_init.desktop" ("/usr/libexec/pam_kwallet_init")
Nov  4 08:28:40 Rocky-KDE /usr/libexec/gdm-x-session[25256]: org.kde.plasma.session: Starting autostart service  "/etc/xdg/autostart/polkit-kde-authentication-agent-1.desktop" ("/usr/libexec/kf5/polkit-kde-authentication-agent-1")
Nov  4 08:28:40 Rocky-KDE /usr/libexec/gdm-x-session[25256]: org.kde.plasma.session: Starting autostart service  "/etc/xdg/autostart/baloo_file.desktop" ("/usr/bin/baloo_file")
Nov  4 08:28:40 Rocky-KDE /usr/libexec/gdm-x-session[25256]: org.kde.plasma.session: Starting autostart service  "/etc/xdg/autostart/xembedsniproxy.desktop" ("/usr/bin/xembedsniproxy")
Nov  4 08:28:41 Rocky-KDE /usr/libexec/gdm-x-session[25256]: org.kde.plasma.session: Starting autostart service  "/etc/xdg/autostart/gmenudbusmenuproxy.desktop" ("/usr/bin/gmenudbusmenuproxy")
Nov  4 08:28:41 Rocky-KDE dbus-daemon[25253]: [session uid=1000 pid=25253] Activating service name='org.kde.ActivityManager' requested by ':1.21' (uid=1000 pid=25454 comm="/usr/bin/plasmashell " label="unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023")
Nov  4 08:28:41 Rocky-KDE /usr/libexec/gdm-x-session[25256]: org.kde.plasma.session: Starting autostart service  "/etc/xdg/autostart/xdg-user-dirs.desktop" ("/usr/bin/xdg-user-dirs-update")
Nov  4 08:28:41 Rocky-KDE /usr/libexec/gdm-x-session[25256]: org.kde.plasma.session: Starting autostart service  "/etc/xdg/autostart/vmware-user.desktop" ("/usr/bin/vmware-user-suid-wrapper")
Nov  4 08:28:41 Rocky-KDE /usr/libexec/gdm-x-session[25256]: org.kde.plasma.session: Starting autostart service  "/etc/xdg/autostart/pulseaudio.desktop" ("/usr/bin/start-pulseaudio-x11")
Nov  4 08:28:41 Rocky-KDE /usr/libexec/gdm-x-session[25256]: org.kde.plasma.session: Starting autostart service  "/etc/xdg/autostart/abrt-applet.desktop" ("/usr/bin/abrt-applet")
Nov  4 08:28:41 Rocky-KDE /usr/libexec/gdm-x-session[25256]: org.kde.plasma.session: Starting autostart service  "/etc/xdg/autostart/gnome-shell-overrides-migration.desktop" ("/usr/libexec/gnome-shell-overrides-migration.sh")
Nov  4 08:28:41 Rocky-KDE /usr/libexec/gdm-x-session[25256]: org.kde.plasma.session: Starting autostart service  "/etc/xdg/autostart/spice-vdagent.desktop" ("/usr/bin/spice-vdagent")
Nov  4 08:28:41 Rocky-KDE /usr/libexec/gdm-x-session[25256]: org.kde.plasma.session: Starting autostart service  "/etc/xdg/autostart/geoclue-demo-agent.desktop" ("/usr/libexec/geoclue-2.0/demos/agent")
Nov  4 08:28:41 Rocky-KDE /usr/libexec/gdm-x-session[25256]: org.kde.plasma.session: Starting autostart service  "/etc/xdg/autostart/powerdevil.desktop" ("/usr/libexec/org_kde_powerdevil")
Nov  4 08:28:41 Rocky-KDE /usr/libexec/gdm-x-session[25256]: org.kde.plasma.session: Starting autostart service  "/etc/xdg/autostart/tracker-store.desktop" ("/usr/bin/gdbus", "call", "-e", "-d", "org.freedesktop.DBus", "-o", "/org/freedesktop/DBus", "-m", "org.freedesktop.DBus.StartServiceByName", "org.freedesktop.Tracker1", "0")
Nov  4 08:28:41 Rocky-KDE /usr/libexec/gdm-x-session[25256]: org.kde.plasma.session: Starting autostart service  "/etc/xdg/autostart/tracker-extract.desktop" ("/usr/libexec/tracker-extract")
Nov  4 08:28:41 Rocky-KDE /usr/libexec/gdm-x-session[25256]: org.kde.plasma.session: Starting autostart service  "/etc/xdg/autostart/tracker-miner-apps.desktop" ("/usr/libexec/tracker-miner-apps")
Nov  4 08:28:41 Rocky-KDE /usr/libexec/gdm-x-session[25256]: org.kde.plasma.session: Starting autostart service  "/etc/xdg/autostart/tracker-miner-fs.desktop" ("/usr/libexec/tracker-miner-fs")
Nov  4 08:28:41 Rocky-KDE /usr/libexec/gdm-x-session[25256]: org.kde.plasma.session: Starting autostart service  "/etc/xdg/autostart/sealertauto.desktop" ("/usr/bin/seapplet")
Nov  4 08:28:42 Rocky-KDE plasmashell[25454]: org.kde.plasmaquick: Applet preload policy set to 1
Nov  4 08:28:42 Rocky-KDE plasmashell[25454]: kf5.kpackage: No metadata file in the package, expected it at: "/usr/share/wallpapers/Next/contents/images/"
Nov  4 08:28:42 Rocky-KDE plasmashell[25454]: kf5.kpackage: No metadata file in the package, expected it at: "/usr/share/wallpapers/Next/contents/images/"
Nov  4 08:28:42 Rocky-KDE plasmashell[25454]: kf5.kpackage: No metadata file in the package, expected it at: "/usr/share/wallpapers/Next/contents/images/"
Nov  4 08:28:42 Rocky-KDE plasmashell[25454]: file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:76:9: Unable to assign [undefined] to QStringList
Nov  4 08:28:42 Rocky-KDE plasmashell[25454]: file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:75:9: Unable to assign [undefined] to int
Nov  4 08:28:42 Rocky-KDE plasmashell[25454]: file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:75:9: Unable to assign [undefined] to int
Nov  4 08:28:42 Rocky-KDE plasmashell[25454]: file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:76:9: Unable to assign [undefined] to QStringList
Nov  4 08:28:43 Rocky-KDE plasmashell[25454]: trying to show an empty dialog
Nov  4 08:28:43 Rocky-KDE plasmashell[25454]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:146:19: QML Loader: Binding loop detected for property "height"
Nov  4 08:28:43 Rocky-KDE plasmashell[25454]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:146:19: QML Loader: Binding loop detected for property "height"
Nov  4 08:28:44 Rocky-KDE /usr/libexec/gdm-x-session[25256]: KCrash: Attempting to start /usr/bin/plasmashell from kdeinit
Nov  4 08:28:44 Rocky-KDE /usr/libexec/gdm-x-session[25256]: KCrash: Application 'plasmashell' crashing...
Nov  4 08:28:44 Rocky-KDE plasmashell[25724]: org.kde.plasmaquick: Applet preload policy set to 1
Nov  4 08:28:44 Rocky-KDE plasmashell[25724]: kf5.kpackage: No metadata file in the package, expected it at: "/usr/share/wallpapers/Next/contents/images/"
Nov  4 08:28:44 Rocky-KDE plasmashell[25724]: kf5.kpackage: No metadata file in the package, expected it at: "/usr/share/wallpapers/Next/contents/images/"
Nov  4 08:28:44 Rocky-KDE plasmashell[25724]: kf5.kpackage: No metadata file in the package, expected it at: "/usr/share/wallpapers/Next/contents/images/"
Nov  4 08:28:44 Rocky-KDE plasmashell[25724]: file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:76:9: Unable to assign [undefined] to QStringList
Nov  4 08:28:44 Rocky-KDE plasmashell[25724]: file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:75:9: Unable to assign [undefined] to int
Nov  4 08:28:44 Rocky-KDE plasmashell[25724]: file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:75:9: Unable to assign [undefined] to int
Nov  4 08:28:44 Rocky-KDE plasmashell[25724]: file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:76:9: Unable to assign [undefined] to QStringList
Nov  4 08:28:44 Rocky-KDE plasmashell[25724]: trying to show an empty dialog
Nov  4 08:28:44 Rocky-KDE plasmashell[25724]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:146:19: QML Loader: Binding loop detected for property "height"
Nov  4 08:28:44 Rocky-KDE plasmashell[25724]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:146:19: QML Loader: Binding loop detected for property "height"
Nov  4 08:28:44 Rocky-KDE kernel: QSGRenderThread[25731]: segfault at 0 ip 0000000000000000 sp 00007f21d1bf38a8 error 14 in plasmashell[561ad5ea4000+9b000]
Nov  4 08:28:44 Rocky-KDE abrt-hook-ccpp[25732]: Process 25724 (plasmashell) of user 1000 killed by SIGSEGV - dumping core
Nov  4 08:29:45 Rocky-KDE abrt-hook-ccpp[25976]: Process 25454 (plasmashell) of user 1000 killed by SIGSEGV - dumping core
Nov  4 08:29:48 Rocky-KDE plasma_waitforname[25788]: org.kde.knotifications: WaitForName: Service was not registered within timeout
Nov  4 08:30:48 Rocky-KDE plasma_waitforname[26020]: org.kde.knotifications: WaitForName: Service was not registered within timeout

I’ve only managed to get a partial crash dumps for ksplashqml so far.

# file coredump
coredump: ELF 64-bit LSB core file, x86-64, version 1 (SYSV), SVR4-style, from '/usr/bin/plasmashell', real uid: 1000, effective uid: 1000, real gid: 1000, effective gid: 1000, execfn: '/usr/bin/plasmashell', platform: 'x86_64'
# cat core_backtrace
{   "signal": 11
,   "executable": "/usr/bin/plasmashell"
,   "only_crash_thread": true
,   "stacktrace":
      [ {   "crash_thread": true
        ,   "frames":
              [ {   "address": 140299137094543
                ,   "build_id": "296658ed4f68231cb3ef55ded9b584404deed520"
                ,   "build_id_offset": 226191
                ,   "function_name": "raise"
                ,   "file_name": "/usr/lib64/libc-2.28.so"
                }
              , {   "address": 140299199130076
                ,   "build_id": "c5fc5715bad7a9a8b0aa0c1f063f15e22e218554"
                ,   "build_id_offset": 23004
                ,   "function_name": "KCrash::defaultCrashHandler(int)"
                ,   "file_name": "/usr/lib64/libKF5Crash.so.5.68.0"
                }
              , {   "address": 140299137094672
                ,   "build_id": "296658ed4f68231cb3ef55ded9b584404deed520"
                ,   "build_id_offset": 226320
                ,   "function_name": "__restore_rt"
                ,   "file_name": "/usr/lib64/libc-2.28.so"
                } ]
        } ]
}
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/bin/plasmashell'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x0000000000000000 in ?? ()
[Current thread is 1 (Thread 0x7f8c5290c700 (LWP 3054))]

The virts are spun up to meet minimum spec with the exception of RAM, I have that set to 8 GB.

In case anyone lands here / is still having issues with installing KDE, I just installed it again and made some notes:

Installed on a fresh kvm/qemu RL 8.5 VM ( 4 threads, 4G RAM , virtIO qcow2 live file with a backing file ).
Host is RL 8.4 on a Dell Precision 32G Ram, 12 threads.

  1. Installed RL 8.5 from dvd iso img
  2. Rebooted VM
  3. Launch terminal and su to root
  4. dnf config-manager --set-enabled powertools ( important to do this BEFORE KDE install later. )
  5. dnf -y install epel-release
  6. dnf -y update
  7. dnf groupinstall -y “KDE Plasma Workspaces”
  8. systemctl enable sddm.service -f
  9. reboot
  10. At the login, select “Plasma (X11)” for desktop session at the bottom of the screen, enter password, hit return and WAIT.

  1. It did appear to hang a bit ( a min or 2 most ) here but came through in the end…

And all seems reasonably responsive/OK.

Hello @bobar et al,

Thank you so much for your responses here on this topic and yes this definitely helped get the KDE Plasma Workspaces working now with Rocky Linux 8.5 (4.18.0-348.20.1.el8_5.x86_64) :slight_smile: sorry it took me a while to catch up this.

As a next step and further progression on this topic, I am looking for an option that allows the multi-user environment to “switch” the desktop session when an existing desktop (X) session is locked by another user. Generally, this option used to be available by default in the previous version of KDE Desktop Environment as well as it is also available with GNOME (GDM) but for some reason with the latest version of KDE Plasma (5.23.3-1.el8.x86_64), it seems to be missing!

Any thoughts or help on getting this option enabled/working will be greatly appreciated.

Thanks,
Bhavik

No ideas on that but you have bigger problems at the moment: KDE doesn’t work on 8.6 (covered in a few threads here last week)

@bobar would you have something similar how How To Install KDE Desktop Environment on Oracle Linux 9 ?

Sorry @Jil, I’m sticking with 8 for the next few yrs / hope not to look at 9 till a yr pre eol on 8.

Note KDE works again on 8.6 since the fixed kernel was released.

As to getting KDE on 9 I do know one thing above has changed and that is the powertools repo has been replaced in 9 with crb so enable that instead.

Appears there may be epel issues too - I’d look at this if that’s the case.

Sorry can’t help more.

EL8 will eol in 2029 and EL9 in 2032. If Red Hat continues with the three year major release cadence, then EL10 would appear in 2025 and EL11 in 2028. Therefore, you probably do not have to look at EL9 ever.

Renamed. RHEL 8 introduced CodeReady Linux Builder repository. That name being a RH trademark and hence unusable, CentOS project invented name “powertools”. Rocky 8 inherited that name for consistency. By the time RHEL 9 was released, the legal details had cleared that a name like “CRB” is ok to use and hence Rocky 9 has that.

Websearch for “How To Install KDE Desktop Environment on Oracle Linux 9” did actually include someone’s writeup for “How to KDE into Rocky 9”. Searching for “KDE into Alma 9” finds some more. The important point is to be critical about “guides”, because not all of them are accurate.

It’s okay Sir , I thought about CRB as well but seems to be failing too. I will research further about it . Thanks & Regards.

The problem is that RH lose interest in previous versions very quickly, as we saw with RHEL7. We’re already at version 8.6 and it’s nearly all patches now, as opposed to upgrades. Jumps in kernel and package versions between 8 and 9 will make it hard to stay relevant on 8.x

to what ? With security updates the vast majority of businesses would stay on Windows 7. The “upgrades” to 8,10,11 are mostly an annoyance and a hindrance to people who use computers to do work. Microsoft have demonstrated on a range of products how there is a point where changing things makes them worse not better.

RHEL 8 so far does everything I need an OS to do and having to adapt to changes is an overhead I will avoid if I can.

True, I may skip RHEL 9 when the time comes and also true there is still potential for useful improvements which I may well appreciate but I weigh that against the threat of upheaval every 6 months or even every year and the inherent risk that comes with any change - if I have a stable OS that does what I need and still gets security patches then I need a compelling reason to move to a new version. The fact that there is a new version is not a compelling reason.

It’s even possible I will avoid some particular technology completely as it moves in and out of fashion along with all the early glitches in anything new that sticks.

(And yes I still have the risk every 6 months until 8.10)

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.