I package LibreWolf in a debianized fashion: build.opensuse.org. Here is  the nice download page which includes instructions for installing the apt repo: software.opensuse.org

I collaborate with the upstream LibreWolf team, whenever I actually get around to building each new version. I actually then repackage LibreWolf dpkg with my own customizations on top of this debianized LW, so I am dogfooding this.

Ah, you wanted help changing the hostname that appears in the $PS1 prompt of your shell. I'm glad you found the answer, and that you shared it here. Yes, some installers can zip past some things (or not even provide an option to change them).

Well, a window manager primarily does one thing, which is manage the windows that are displayed or can be made available for display! Fluxbox actually includes a few extra features like its own integrated "toolbar" which is what a lot of DEs call a "panel." You can choose which of multiple items can be displayed on the toolbar, such as the list of running windows (the "iconbar" in Fluxbox parlance), and a "system tray" and a clock and a virtual desktop switcher.
Fluxbox as a window manager does also provide menu functionality on the desktop itself, so that you can add launcher entries so you can get to programs. I use a tool I found that generates XDG-compliant menus for Fluxbox: https://github.com/gapan/xdgmenumaker. That means, it reads /usr/share/applications like almost every other menuing program (from XFCE, Gnome, KDE, etc.) out there!

Perhaps you could write a wrapper script that transforms "system:///media/sdb1" to "file:///media/sdb1" and which then calls mpv.
Now, it if involves access files on a partition (i.e., a disk partition such as /dev/sdb1) maybe your script could choose to mkdir /tmp/dev-sdb1 ; mount /dev/sdb1 /tmp/dev-sdb1 ; gimp ${newfilename}.

Somebody had mentioned a sysvinit orphaned scripts package that might be in Debian? Maybe this script can go in there.

I'm not discouraging its use! I think it's kind of scary-- to use web-related technologies on the login page, but I used it briefly when the project I was working with used it. But I think Antergos let it slip into the Aethernet, and I am unaware of any SuSE management of it.
Lightdm-webkit2-greeter also went by web-greeter or lightdm-web-greeter. I think it was renamed upstream briefly before stopping development: https://github.com/Antergos/web-greeter.

Live long and prosper.

I would hope that if Spock from Star Trek were to live today, he would use Devuan GNU+Linux because it is the logical choice.

So you're a Linux sysadmin contracting firm, eh? That sounds really cool, and probably is my "dream job."

Alas, we have no magic for you. Can you inspect /var/log/syslog and /var/log/Xorg.0.log for messages at the time you tried to enable the second monitor?

You didn't specify which file manager you are using, so I will assume this is with Thunar, the default file manager in Xfce, which I think is the default desktop environment for Beowulf. Thunar follows multiple XDG specifications, including the desktop file spec.

If you would like Thunar (and other Xfce applications in general) to easily recognize Irfanview as an application that handles various mimetypes, you can set up a file at /usr/share/applications/irfanview.desktop (all users) or ~/.local/share/applications/irfanview.desktop. Make the contents resemble (source):

[Desktop Entry]
Categories=Graphics;Viewer;
Comment=View graphics
Exec=/usr/bin/irfanview %F
GenericName=Graphics Viewer
Icon=irfanview
Keywords=irfan;graphics;image;viewer;batch;
MimeType=x-content/image-dcf;image/png;image/gif;image/jpeg;image/jpg;image/bmp;image/tiff;image/ico;image/vnd.adobe.photoshop;
Name=Irfanview
StartupNotify=true
Terminal=false
Type=Application
Version=1.0

Adjust the binary name in the Exec line to point to your script that invokes Irfanview, or perhaps the whole wine invocation, although files with spaces in their names could get messy. For example, it could be

Exec=/usr/bin/wine "C:\Program Files\Irfanview\iview64.exe" %F

The %F in the Exec line is important, because that will tell XDG-compliant applications that it can pass multiple files to the program at the same time. Irfanview, when given multiple files, will let you scroll between just those multiple files.

The MimeType line is also very important, because it tells $SOMETHING (I am not entirely certain) what filetypes should list this application in the "Open with..." pre-filled list. But the "Other application..." dialog will show all /usr/share/application/*.desktop files that have a %F or %f in the Exec.

I forget what command you need to run to update the caches or menus so everything initially becomes aware of the changed .desktop file. A logout usually does it too. Maybe somebody can rescue me from my strange gap in knowledge.

NOTE:
I disavow responsibility for troubleshooting spaces and quotes in the Exec line of a .desktop file!

I can see how Debian might choose some level of sanity by providing support for sysvinit again, but the heavy lifting of making that possible would have been done in a separate environment (i.e., Devuan). It's clear that such maintenance and support wouldn't happen within the Debian world directly.

Wow, you find it easier to help Debian? I have not even collected the courage to try to go offer help on any packages in Debian. The amount of red tape I infer from all their vast documentation makes me unwilling to go offer my limited services in packaging up software that I want to package. I realize they have concerns about orphaned packages at some point in the future should I become unavailable.

I just started showing up to Devuan meetings and said I had some modifications to packages, and boom, they shoved some stuff at me and now I'm responsible for a few things!

If you think wicd itself is the cause of the problem, perhaps you could try another lightweight network manager (not to be confused with Network Manager). When Devuan Ceres dropped wicd because it is written in python2, I switched to connman. It has been about as good as wicd.

I had a flaky wireless network card that thankfully also got added to mainline kernel tree around the time I had to drop wicd, so I was never sure if it was the flaky driver or wicd.