Hmmm...strange. Then again, I'm a window manager user without much experience at all with MATE.

Perhaps a....

apt install --reinstall cmus

?

I don't know. Sorry.

...or...open lxappearance as root...

sudo lxappearance

...or use su if you prefer, then enter...

lxappearance

When lxappearance opens, you can choose the theme and icons that you want to use for the root apps.

Hahaha! That's pretty good.

As always though, there are exceptions to the rule...

My Credit Union is 30 miles away from me. My work schedule doesn't allow me the ability to visit the CU in person.

Could I use a local bank? Sure! I've used several in the past, and I will never use one again. (Imagine a lot of Yosemite Sam grumbling here)...Brick'a, brack'a, brickin, no-good-for-nothin', frick'a, frackin', low-down-'n-dirty, slop'n-doppin-stinkin' banks...

I also pay all of our monthly bills (other than my city utility bill) through my Credit Union's online bill pay.

However, I have a certain Devuan derivative ( ) installed onto a USB, and all that it's used for Is to do my online banking. Not much trouble to boot the USB when I need to do online banking.

Thanks HoaS. I wasn't aware of that.

rayburn,

Came back from vacation a day early...

I just ran updates, and had no issues. The menu still works perfectly.

So...

I reinstalled the entire system. Ran updates. The menu is still working perfectly.

I did notice there was an update for libgtk3-perl, so perhaps that will fix the issue for you if you run updates again.

Also, there is an alternative menu that I provided in ~/.config/openbox/Other-Menu

It uses openbox-menu to provide the applications menu.

Directions are in the Release Notes (if you still have them).

If you don't have them and want to try the other menu, just copy the menu.xml file from the Other-Menu folder into the openbox folder, and overwrite the existing one.

EDITED TO ADD...

Then, open the terminal or Run Command, and enter...

openbox --reconfigure

I may hang myself here, but I've built some Debian respins with live-build by request. I read in the Arch wiki that systemd doesn't play nicely with slim, so I used Lightdm in those builds.

In each one, I replaced lightdm with slim while testing them (for myself) for several weeks. I never had any issues with it on Debian/systemd.

Not sure what the issue is or could be...but then again...it didn't matter to me.

LOLOL!

Devuan Ceres...

The Gentoo Jinxer...
The Arch Annihilator...
The Solus Stopper...
The Tumbleweed Terminator...
The Manjaro Maligner...

...n'stuff.

Thanks HD! The wmderland release is also based on ceres, but it's a tiling window manager. So...I wanted to give users an option for a floating window manager too.

Yes, thanks for the help HoaS, and thank you rayburn for using MiyoLinux and hanging in there to get this sorted out. The su -l command was instituted by Debian and went into effect with Buster...and therefore...Devuan beowulf. That was my fault for not realizing the situation earlier. So, you'll need to use it periodically when doing things like update-grub.

I hope you enjoy wmderland! Have fun!

Hmmm...strange. I'll try it when as soon as I'm able, but it might be awhile. In the meantime, you can see if this command works...instead of...

su

...use...

su -l

...at the beginning. That's a lower-case l (as in letter).

Hi rayburn. When dual-booting or multi-booting, I have my main system that controls grub, and I install grub for the other systems on the actual partition that I'm putting that system on...if that makes sense.

Do you know the disk letter and partition number that you put wmderland on? Such as, most disk letters will be designated as sda for a hard drive. The partition number will depend on how many partitions you have.

If you still have wmderland on a USB, boot it up. When you reach the desktop, you can open gparted to find out for sure what the disk letter and partition number is for wmderland.

Your's may differ, but in this example, I will use sda as the disk...and 3 as the partition number. So, wmderland is assumed to be on sda3 in the example below. Make sure to use your correct ones.

Open the terminal, and enter the following commands one at a time...the su password is miyo

su
mount /dev/sda3 /mnt
mount --bind /dev /mnt/dev 
mount --bind /dev/pts /mnt/dev/pts 
mount --bind /proc /mnt/proc 
mount --bind /sys /mnt/sys
chroot /mnt
grub-install /dev/sda3
update-grub
exit && umount /mnt

Now reboot into your main system, and run update-grub on it.

If all went well, the wmderland system should show on your grub screen the next time you reboot.

When I saw your post, I looked to see what other posts you had made (because I'm sneaky that way ), and I saw you had an issue with obmenu-generator. I'm sorry that I missed it before. If that ever happens again, just open the terminal, and enter the following command...

sudo cpanm Linux::DesktopFiles

Then run the following for no icons...

obmenu-generator -p 

...or this for icons...

obmenu-generator -p -i

Don't forget...

The derivatives that Stanz releases already have i2p installed!

http://dev1galaxy.org/viewtopic.php?id=3382