Maybe the firmware depends on SystemD    ( For those with no sense of humor it was a joke )

I also suspect the laptop's firmware. I wonder if an update is available. On the other hand we can not ignore that the Debian flash drive did work while the Devuan drive did not. Maybe Debian has worked some magic to get around the issue.  Seems to be a cat and mouse game.

A personal testimony:  I've had nothing but success with Lenovo laptops . . .but then again the first thing I do is change settings in the bios, which OP is unable to do in this situation.  That does make a big difference.

A stab in the dark here. I see you are using connman.  If connman is allowed to change the host name it can cause problems with X authority as it expects a different name. Maybe try adding AllowHostnameUpdates=false to /etc/connman/main.conf

Like I said, "a stab in the dark". If it works good. Sorry, if I'm wrong just put it back how it was

EDIT : I see you had it fixed before I pressed post. I guess I was barking up the wrong tree and your hostname wasn't even set to begin with.

Just my thoughts on distrowatch, and some of it kind of parrots what has already been said. Don't mean for it to be a rants, just how I see it.

If you watch Distrowatch closely you will notice all distros  have an increase in popularity after a new release. So, a newly announce release could temporarily pass a more popular distro that hasn't had a new release in over a year or more. Also people go to distrowatch to learn about distros, not for the newest scoop on high ranking distros like Ubuntu, Arch, Manjaro, Mint, and so on.  People interested in those distros use a search, engine or have the sites bookmarked, or follow a links from popular tech sites. This plays in favor for the small distros as Distrowatch's counters see less activity for the top distros which results in a lower ranks.

Now with that said there are also the "fanboy and girls" who flood distrowatch generate activity for their pet distro in order to increase the ranking.

And don't get me started about how they divide Ubuntu's ranking by all it's available flavors, but do not do this with other distros like Manjaro, Mint, and Puppy that offer various editions. Some of these editions are not even based on the same core. Apparently this is justified because each Ubuntu flavor his a different website, but I see it as nothing more then bias.  I'm not a fan of Ubuntu, but I want fair and honest numbers were ever distro is ranked by the same rules.

With that out of the way. I will say that distrowatch is a useful site, and I even find it's faulty ranking system useful as long as you understand it has faults.

Sorry, I did not specify a release date. I prefer quality and flexibility over deadlines. As you stated in the Issue you submitted,  " its ready, when its ready. " . But that's a hard line answer, and I understand it is not helpful. So allow me to answer you in an informative way that does not obligate me.

Progress is directly linked to my availability (free time).  I'll try my best to have it ready before the end of the month, hopefully sooner depending on time, energy and coffee.  The largest number of issues are with the Time & Date tool.  If it is the cause of much delay.  I will either leave it out of the build or just set NoDisplay=true in it's .desktop file.

I do feel the Time & Date tool is important because it allows control of the date/time/timezone without having to add even more dependencies to  the system. Also it seems many of the newer Graphical time set tools are simply a front end for timedatectl (systemd)

Zapper, I'm glad  you found something that works and hope it's a good solution for you.   I may of been wrong in my previous post about needing to change the .desktop for JWMKit Logout as your links to this app are probably in the static part of the menu and the tray. In this case you need to make the changes to it with both the Tray and Menu tools.  Sorry about that, but I assume you figured this out already.

I'll also make the assumption that since my app does not support doas (which I've been hearing a lot about lately) that you are just calling jwmkit_logout with doas instead of using a feature built into the logout app. Which I guess would work just as well.

Now I need to add doas support to jwmkit_logout. . . I think I may take another approach and just allow the user specify the specific logout commands they want.

Zapper, Thanks for trying out this new build and sharing your experience.

As for the keybinding, I'm not sure if you mean the actual keybindings I have set or the JWM Kit tool for assigning keybindings. To be honest they both need some work and I am aware of that. A complete rewrite of JWM Kit Keys is on the agenda.

Once again thanks for your input.

Sorry for the delay in answering. I've be out of town.  The bad news is JWM Kit Live has no wifi tools installed. Not even command line. The good news is this give you the freedom to choose your own wifi solution by simply using the package manager and a wired connection.  I recommend using ConnMan, but you can use whatever suits you.  Just use  Synaptic package manager to find an install it.

You may (or may not) need to install the firmware for your wifi card. Which is also not to complicated.  Just type lspci in the terminal and find the model of your wifi card and a simple search on duckduckgo should help you find what firmware package to install. Once again you can install it with Synaptic.

Hint: There is plenty of discussion on the web regarding wifi tools and firmware for Debian based Distros.

Sorry for taking so long to reply WoodLark. Not only have I been busy I also wanted to take the time to provide as informative of an answer as possible.  Which involved me taking a look at Puppy. I am pleased to inform you that JWM KIt works quite well in FOSSAPUP not problem. I did have to make changes to the default JWM config as it caused some conflict. For example: It would automatically re-generated the menu and overwrite any changes made by JWM Kit.

To All interested in JWM Kit on Puppy.

I can't ignore the fact that their is definitely an interest to seeing JWM Kit work in Puppy Linux, so I will be taking the time to not only get it working in puppy, but to share the process.  I guess you could call it a guide, but it's mostly just notes of me getting JWM KIt running in Puppy. I'm using FOSSAPUP.  But let me know what puppy core y'all are interested in so I can provide more helpful documentation.

Everything you need is here:
https://codeberg.org/JWMKit/JWM_Kit

I'll post back when I've finished my documentation.  You should be able to find it at the codeberg.org page listed above.  I'll create a folder called puppy with the info, and it will also contain any config files I create in the process.

UPDATE: Finished my Puppy documentation. You can find it on my codeberg site listed above in a folder called puppy. The file NOTES is the documentation, and the other files are examples you can use to reproduce the process.

The Add button just creates the item and adds it to the list  You need to use the up and down arrow buttons to place the item where you want it.  Sorry if this is not obvious. 

As I said there will be lots of changes coming in the future. In the future versions the menu editor will not be a global view, but will be divided by menus (and the root menu). I also plan to have newly added items place next to the current selected item instead of at the bottom.

@darry1966 I'm glad it worked well for you.  I have to give Devuan the credit due.  To be honest most of the work in creating this spin has been towards JWM, and JWM Kit as my focus was to demonstrate JWM Kit. So if you hardware works well that's just the power of Devuan since I've not done anything special for hardware support.  If anything I've chosen user freedom over ease of use.  For example I could make JWM Kit more useful/powerful by automatically creating trays and menus on a system, but I decided It was more important to allow the user to keep or create their own,

@Ozi I know where you are coming from. I've given Star a spin and it tells me a lot about your preferences which I can best describe as simple and just works.  No need for fancy makeup . . . or even icons.  I used to maintain a similar system based on Debian for myself, but abandoned it about 2008 when I finally got some new hardware and wanted to play with all the fancy new distros at the time.

@Ozi I understand where you are coming from. If you are familiar with JWM and have experience editing the XML yourself.  No graphical app will ever offer the flexibility of editing the config in a text editor.  I myself am the type person who would rather use a command over a graphical app. I still prefer the JWM Kit Wallpaper over manually editing just to set a wallpaper. I can view the images and set it all in one app. This single example is why I made JWM Kit separate apps instead of one big one.  So people can use just the parts they want. I  know I have packaged them all in one .deb but there is no reason they can not be packaged/installed separately.

Thanks for your feedback