A little OT follow-up : Gnome is now working properly for me.

This is hove I did it. :-)

Had the old not so good working Gnome installation (that this thread is based upon) on a partition that I cloned to another partition the other day. (Must clone to have the old version left, because that's where Calibre's Annotations plugin works (for my Kobo tablet) not on my now so fancy up to mode Ceres installation) When I tried to update it, Gnome/Ceres, on the new partition with aptitude, apt-get upgrade or apt-get dist-upgrade, it took many minutes without coming up with a solution.

Then I used my favorite, and usually only package management method/application, Aptitude. I took and marked one application packet for update. Now when Aptitude shows a red B, for broken, I double click or press the return key, on the package name to see more about the package. Then I see which dependencies are not resolved.
Now I do the same process for the broken dependency, as for the original package. Highlighting it by clicking on it or moving down the current highlight with the keyboard buttons.

Once there, I check if it is possible to install the package. Press the + key. If it turns green at the left in Aptitude - green i or iM -, everything is fine. If it turns red B, I repeat the process until all it's dependencies are met.

When all needed programs are marked with a green i or green iM, it can be good to make sure that all packages, if they can, are marked with green iM instead of just i. iM means that that package is only installed if it is needed by another program/program package. (It is because many programs can be marked i, instead of iM, that aptitude and apt-get can have problems solving dependencies. Some programs - iM marked programs - must not be removed.) To do this, select one package at a time and press the Ctrl and M keys simultaneously. Now i has become iM. If it becomes nothing, I press the + key, so that it becomes i again. Without any highlighting at all, the package/program would be deleted, as no other program depends on it. Therefore, iM does not work on these high hierarchy program packages.

Now I press g, on the keyboard. If all went well, and I didn't miss any dependency, in the usually long dependency tree, a number of packages are now ready for installation. If not: do it again, do it right - If it went wrong: reverse Aptitude with the q key. If it was right: press g again, to perform the actual installation/upgrade.

After that package installation, with all dependencies, I take and select the next one. I prefer to select at the top of the program hierarchy, then I get many dependencies that other programs also need. When all programs are upgraded, I'm done, my computer has the latest programs. Now I test apt-get upgrade or apt-get dist-upgrade and see if any small package is forgotten.

And after rebooting it turns out that the problem I had earlier - in February - is now fixed, so now I'm running Gnome instead of KDE as my DE. Let's see how long it lasts. Longing in some ways to go back to KDE but will now give Gnome a chance. Most of my favorite programs are built with GTK. It's only Typora and Calibre that are done on QT. So in that way it feels better with Gnome. But we'll see...

Thank you for your response. I was using KDE in Wayland on Devuan Ceres for three years before I wanted to test the evolution of Gnome a couple of weeks ago. Now I like Gnome.
In the KDE environment in Wayland, there were no problems with the applications that now fail in Gnome. So it should be something Gnome related that makes it not work.
The big problem for me is that I can't troubleshoot because the terminal shows nothing when I start applications from it. So I don't have a clue where the error could be. And the logs don't show anything either.

Thank you very much hunter0one.
I found your post after almost two weeks of troubleshooting. During that time I have had to use a backup since March as all my attempts to solve the problem have failed.
Following your information I was able to upgrade my regular, but unusable system, downgrade libgudev. After that everything works as perfectly as it did before I upgraded libgudev on 22 July.

Some day even you will be able to handle the pieces. It's all about experience.

I thought we had a forum like this to, among other things, develop and learn new things, not to be negative about new ideas and progress. But I'm so incredibly blown away and stupid so I do things that I feel like to test and learn, not that other say I should do.

Why go so far? The most suitable repos to supplement Devuan's own with is Debian. This is because Devuan downloads most of it's aplications directly from Debian repos.
If you want a different version of firefox or firefox-esr, you first look at a fresher Devuan repro, like Ceres, otherwise you look at Debian Experimental. Then they can look further afield.

Here are my suggestions, to add in the sources.list:

deb http://deb.devuan.org/merged ceres main non-free contrib
deb http://http.debian.net/debian experimental main non-free contrib

Firefox 93.0-1 is in Devuan Ceres (I use that one) & Debian Sid
Firefox 92.0-2 is in Debian Experimental

Firefox-ESR 92.2.0-esr1 is in Devuan Ceres & Debian Sid
Firefox-ESR 92.1.0-esr1 is in Debian Experimental

"This [repo mix ]is a very risky thing to attempt, and is generally regarded as a bad idea for all but the most advanced Debian users."

I'm an advanced user that have used Linux as my only OS since 2003. I'm convinced that everybody can learn by trying, and therefore recommend to mix repos if they need, or want, it. But have a backup of the system if something get messier than you can handle. I have an extra partition on the disk for the backup copy of my system, with that I can dual boot in emergency, while I solve the problems on my primary system.

Not sudo -i, sudo -l (sudo --login).

Copy your old system with "cp -a" to a new partition on a disk or usb memory that is partitioned with GPT. Do not forget to create a / boot / EFI partition and enter this partition in / etc / fstab, if you want to be able to install grub and boot from the new system. Also change other things in / etc / fstab based on the newly created partitions. Then you must install a kernel that is signed. Then also change in /etc/initramfs-tools/conf.d/resume so that you have the correct swap partition, else the system will hang for a wile at boot but sooner or later boot completely.
If you have a necessary custom built kernel module that is not signed, that module will not work with secure boot.

That's the way to do it if you need something that is not in the distro you are running.

Personally, I want the latest KDE, the one in Debian Experimental, so I added Debian Experimental to my sources.list and ran "aptitude upgrade -t experimental". Then I also got some other new candy. I have now been doing this every day for several weeks and have only had one problem, that VirtualBox-DKMS did not want to be compiled with Experimental's kernel 5.13.0 trunk. So I have to settle for 5.10.
In addition, I use libc6 2.33 from the latest Ubuntu release Hirsute Hippo, to be able to use the Firefox plugin ScrapBee. But now I saw that 2.32 came in Debian Experimental so I take and test it instead.
And then I run LibreOffice nightly builds 7.3_alpha because I'm love and need the new outline function which is next as good as Emacs Org Mod's outline mode. https://dev-builds.libreoffice.org/dail … F/current/
I almost forgot to tell you that I use DisplayCal and for this I need some python 2 packages from Debian Buster. (I like to download my packages from Debian because I think it is easiest (I'm used to) to search for packages there.)
Must recommend snapshot.debian.org It's a real goldmine with all the packages and versions since the beginning of time. http://snapshot.debian.org/

This is one way to have fun, develop yourself and learn more about Linux. Should something go wrong I learn even more.

Since GNU-Linux/Debian/Devuan is mostly done by volunteers on a non-profit basis, you can not require them to do anything other than what they are interested in. This means that they skip things they think are unnecessary, such as user-friendliness. Therefore, the use of GNU-Linux/Debian/Devuan requires a great willingness to acquire their own knowledge. This must be respected. If not, then there is Windows. And if you want other solutions than those offered, you have to make them yourself. That's how it works.

You will need at least three packages newer than Beowold to use the 11th generation of Intel processors. In any case, this applies to i7, and I think it also applies to i5.
The packages are:
intel-media-va-driver-non-free for graphics
https://pkginfo.devuan.org/cgi-bin/pack … .1.1+ds1-1
firmware-sof-signed for audio
https://pkginfo.devuan.org/cgi-bin/pack … gned=1.7-1
firmware iwlwifi for wifi
https://pkginfo.devuan.org/cgi-bin/pack … -2~bpo10+1

The easiest way is to add Debian's Experimental to your source list and just run 'aptitude upgrade -t experimental'. That's what I've been running for a few weeks to get the latest KDE and the latest of it all. ;-)

There is so much you "should not do" with Linux but that I do successfully and without problems. Instead of using virtual environments, I run different environments - XFCE 4, Gnome and KDE - on different partitions with but the same / home where the different configuration files coexist. That's not the way to do it, is it? You should not even test if it works, because it is better to believe than to know.

And plugging in individual program files from Arch solved my problem that some programs could not start with Nvidia, Gnome and Wayland. But it did not cause any problems.
Installing libc from Ubuntu solved my problem with a Firefox plugin. But it did not cause any problems.

As for Trinity, I only used it for a few days. It was when I was using Konqueror to surf that I discovered that Konqueror does not support modern web technologies. Also, I had some general issues with making things work.

Right now I'm trying KDE 5 and am very impressed. Now finally all programs look the same whether it is GTK and QT. But I have not managed to get KDE to run on Wayland, yet. But I'm testing and learning... just for fun...