Yes, wicd did/does provide a good and fairly distinct GUI for configuring the network devices and before it was abandoned due to the python2 -> python3 change it was still only in the beginning of its path to enshittification, so quite a good option if one feels a need for a GUI.

The best however is to not use any of those configuration scramblers, but to settle for the original ifupdown system together with wpagui. With those you are seated with maximal flexibility, simple configuration basis by editing text file(s) and a fantastic opportunity catering for any custom networking landscaping.

All it takes is a bit of knowledge which is acquired by means of reading -- reading man pages, starting with man interfaces. Knowledge is power. When you give knowledge away for an idea of convenience, then you lose.

When/if interesting discussions emerge I would be keen to assist with improved platform software.

The programs egrep and fgrep belong to the grep package.
Possibly you have them as /bin/grep and /bin/egrep where they have been residing since yonks. Now everything is supposed to reside in /usr/bin due to a reconfiguration of the root filesystem where all pathnames /bin, /sbin and /lib* are replaced with links to same-named directories under usr.

You may have heard about it as "usrmerge".

Most likely you have updated checking tools that expects/requires those silly-links.

Note that UEFI bios is 32-bit software so booting may have difficulties with an EFI partition beyond 4G byte address. The general advice is always to have that partition first on the disk (i.e. starting at a 1M = 2048 sectors offset).

Don't use connman

Good.

Development like that would happen in git.devuan.org/devuan/documentation with normal fork+change+merge activity.

Thus, 1) register there; 2) fork the project, 3) start a branch.. perhaps named wip/excalibur (but naming could well be discussed); 4) edit; 5) make merge requests to the source project.

dd

Does the user that starts Xorg have due access to /dev/dri/card0 ?

A next option if indeed the "59" package does provide the required ABI could be to use equivs and set up a dummy "58" package so as to make apt happy (believing the "58" package is installed).

Your equivs package, which takes a small amount of effort, would be void of content and only have the meta information declaring it to provide libavformat58 and depend on libavformat59.

In that way you would implement that claim that your "59" package provides whatever is required from the "58" package.

Thanks for your concern. Let us now and henceforth round up the nonsense and only post things likely to be of more general interest.

Possibly i you get the initial grub splash screen, you might try using E, C or ESC to enter grub command line and ther type "exit" and ENTER.