I am posting this using my TW machine. After my rather amateur efforts to install Leap 16.0 on my newly upgraded hardware, only completed with the kind help from Malcolm, Hui and others I had stopped using that machine and paused before completing my personal customisation until now.
Meanwhile and over the holiday period I tried to catch up on what is going on with openSUSE and its many variants/cousins. I read with interest the changes which are taking place and understand the trends which will leave the OS a more secure foundation for various applications and packages used in an increasingly vulnerable work environment. Having read about the options I had more or less satisfied myself that Leap 16.0, which I saw as a logical upgrade from Leap 15.6, was still the way to go for my “work” machine.
I started my upgraded machine yesterday with the intention of continuing to customize my OS and add the various standard apps which I use. I assumed, since I had not turned it on for a month, that I should check for updates and ran zypper up.
This promptly put me back to asking for help because the machine is no longer useable. After a couple more reboots I am now able to work on the machine but only by using X11.
Malcolm’s comments and trends in OS design with some options now being RO and suited to sandboxed apps gave me pause but, based on my excellent experience with Leap 15.6 and predecessors I embraced Leap 16.0 with enthusiasm.
To find that Wayland and Plasma as downloaded by me have been something of a disaster is a great surprise and disappointment.
Please can somebody tell me what I should do, as soon as possible, to get a clean and stable Leap 16.0 OS working on Wayland!
Alastair, I’m currently running KDE Gear version 25.12.1, KDE Plasma version 6.5.90 (version 6.6 Beta 1) and KDE Frameworks version 6.22.0 with Wayland “pure” on this Leap 16.0 machine:
The only small inconvenience is, that the KDE repositories in the Open Build Service have to be updated by means of “zypper dup” – with at least the “–allow-vendor-change” option.
I’m currently also using the “–allow-name-change” option.
AFAIK, deano_ferrari is also running Leap 16.0 with KDE Plasma with this configuration.
Hi and very many thanks. I am sure this is what I need but being a simple soul what exactly do I have to install and configure. With all the comments here I am pleased to learn that I should be able to get my system to work but I fell at the first fence with your “KDE Gear version 25.12.1” I see that my present version is a bit behind
think I am OK for now and many thanks to all for the help, somewhat cryptic for this simple soul but thanks anyhow.
My original post is still I feel accurate. Leap 16.0 should not have been released as the newest version of the Leap series until these issues has been fixed and incorporated in the main installation stream.
Just for the future should I now run updates with zypper up or zypper dup?
You should only need zypper up in general. The zypper -v dup --allow-vendor-change was specifically to upgrade the desktop environment packages via the KDE repos you added.
I put up a question in the KDE Discuss Forum around the issue of KDE Gear versions – subsequent to that discussion I raised a KDE Bug Report requesting the wish that, the “Gear” version be included in the KDE Information system – the wish was knocked out of the Arena faster than anything you’ve ever seen …
Dean, I see the current state of the KDE Plasma packages in the openSUSE KDE-Frameworks repository – the KDE Plasma version 6.6 Beta status (version 6.5.90) – as being a potential hazard with a simple “zypper update”.
Once KDE Plasma reaches version 6.6 in Calender Week 8 – Tuesday the 17th of February – and, those packages become available in the openSUSE repository – I will also resume simply “zypper update” but, until then …
After a few days and having had significant help form this forum and, I confess AI (ChatGPT) my Leap 16.0 is still working well. I remain in awe of all the dedicated contributors who make this possible but there was no and still is not, that I can find, an easy route to getting Leap 16.0 installed and running and none of the contributors gave me an idiots guide but more a pathway with required reading which takes valuable time.
Having achieved the basics I needed I have looked at installing additional apps. Have tried a retrograde attempt to re-instate Yast2 I gave up on this as a mistake but really, where is the replacement. I now have to read up about Marylyn and Cockpit, both new to me and am also told that Agama is the Yast replacement.
openSUSE project has unveiled the release of Agama 17, the installer that replaces the classic SUSE and openSUSE installation interface. This new system makes a fundamental difference by separating the user interface from YaST’s internal components, allowing the installation to be managed even from a web interface.
Strange then that there is no mention of Agama that I can find anywhere in my Leap 16.0 installation.
What has prompted me to continue this thread is that on my TW system I use a Gnome app Disk Usage Analyser (baobab) which is very convenient when sorting out drives and remaining capacities. In the past I would have entered baobab into the search box in Yast, accepted the app and the installation and yast would have sorted out all the dependencies etc.
I can of course run
sudo zypper install baobab
but if Agama is the replacement for Yast2, where is it and why can I not use it?
Agama is the Installer, as you discovered, Myrlyn for packagae Management, Cockpit for the rest (based on installed plugins) and the evil command line for the rest…
It’s Myrlyn (although Marylyn would have been a nice choice too ) and it works much like YaST2-Software. There are a few subtle differences here and there, but basically if you used YaST2-Software you are already good-to-go with Myrlyn.
) and it works much like YaST2-Software. There are a few subtle differences here and there, but basically if you used YaST2-Software you are already good-to-go with Myrlyn.