You are not logged in.
So I got a nice e-mail from Dan the other day,
I hope he's doing well. He's the reason why I'm around here.
Why not just copy the image you want over to /usr/share/slim/themes/<theme_name>/? Then just delete the current image (or rename it to something else) and change the name of the new image to background.png/jpg.
Did you also know you can put multiple folders in /usr/share/slim/themes/ and make an edit to /etc/slim.conf so that you can have multiple images it randomly chooses from? That's what I do.
The obvious solution is to remove them both in one command.
Another obvious solution is to put them on hold.
Thanks for the answer and instructions.
Okay, so I deleted it in /usr/lib/udev/rules.d where I accidentally put it, and then put it in /etc/udev/rules.d where it should be. Rebooted and works (again). Remarked as "SOLVED." Thanks again rolfie.
[Maybe I don't have as much of a clue as I thought I did to put it in the wrong place.
]
Well, its a LO document in German, and it contains one or the other more or less private comment I don't want to share.
I understand.
By the way, did you see what I did in my post directly above your post? I put the fix in the wrong place. Should I correct that or just leave it alone?
I don't know what's going on, but now when I browse to /etc/udev/rules.d it shows the folder as completely empty. However, the fix still works. Any clue what's going on? (In the meantime I unmarked it as "SOLVED" even though it still is working.)
EDIT
I see what I did. I put the fix in /usr/lib/udev/rules.d and not /etc/udev/rules.d. But it's working. Should I leave well enough alone? Or will an update erase the file in /usr/lib/udev/rules.d?
I have a long document describing all these tweaks.
I might be interested in that.
So I went ahead and just did it, and it works. Thanks rolfie. Now I have something new to add to my list of things to do after a reinstall. I really hate these things that "corporate actors" (to use your phrase) do trying to protect the user from himself. It sucks for those of us who have a clue of what we're doing.
I don't have a /etc/udev/rules.d/65-ext4.rules file. Do I just create it?
I'm assuming a reboot will be necessary?
So when I was running Devuan 5 all of my devices (usb stick + external hard drive) would mount automatically when I plugged them in. Now with version 6 my external hard drive does not (usb stick still does though). It does show up in Mate's side pane, and when I click on it there, it gets mounted. So this is not too big of a deal, but I would still like it to mount when plugged in. I did a search and found this on the itsfoss website >Link Here< "Method 2: Automount Using Udev Rules and autofs" but it seems that there should be an easier simpler way to do this. Is there? Or should I just try the info from itsfoss?
It worked for me when I update to Excalibur. Not sure why it's not working for you. Did you try any DVDs yet?
Hi greenjeans, I installed today your Devuan-Mate-Mini-6-20250901_1322.iso. Thanks for making this available. After a minor hiccup I got things running smoothly. (I was having an extended boot time, way beyond normal. After some poking around the answer was to add the word "noresume" on a line in fstab.)
Thanks again. 👍
So while running a live session of Excalibur I attemted to remove pulseaudio. But it would not let me do it without installing pipewire-pulse. So I allowed it, and then tried to remove pipewire-pulse, but it wouldn't let me do it without installing pulseaudio. So there must be a way to do it (i.e., have neither installed) because my current bare-metal install of Crowz/Devuan 5 has neither installed. How is it done?
Do you plan on releasing a version based on Excalibur?
I wrote:
I'll probably do the install later next week when I have more free time.
I was, until I realized that straight Devuan has pulseaudio instead of alsa. I think I know the answer to this, but do you remove pulseaudio for alsa in Vuu-do?
greenjeans wrote:
Yeah it might take a re-boot, but you can try logging out and back in on a live session after removing just the gnome-keyring package.
That worked! Thanks. I'll probably do the install later next week when I have more free time. Again, thanks! ![]()
Thank you for your help so far greenjeans. So I just tried this again and I'm stumped. I've removed gnome-keyring, gnome-keyring-pkcs11, and libpam-gnome-keyring (while leaving alone Debian and Devuan keyrings), but I'm still getting the keyring not unlocked message when launching Chromium. Maybe it requires a reboot? But that wouldn't work on a live session, so I'll never know. Any ideas now? If not, I guess I'll just wait for a Vuu-do or Crowz release of version 6.
BTW, when I try to unlock the keyring neither the passwords "devuan" or "root" work, nor "live" either.
Okay, let me try this again . . . .
So I ran a live session again and tried to delete the keyrings. At some point I noticed there are 3, gnome, debian, and devuan. When I try to delete them all it breaks apt, and it can't be fixed. I'm not a computer guru so I don't understand why trying to delete the keyrings keeps breaking apt. I would like to install this version on bare metal but I'm concerned that if installed this same problem will appear. Any ideas or suggestions?
Ah, okay, I see. Thanks for your patience. ![]()
Are you planning to release a Vuu-do based on Excalibur?
greenjeans wrote:
It's not installed in the Vuu-do iso's
I'm confused. Then what caused the keyring not unlocked message?
greenjeans wrote:
Problem is the gnome-keyring package here, I solved it in Vuu-do by uninstalling it
So if this problem pops up in a fresh install, all I need to do is delete gnome-keyring package? (I don't store passwords anywhere except on a piece of paper.)
greenjeans wrote:
11-06-2025 New versions uploaded.
Hi greenjeans. Thanks for these builds. Today I downloaded the Devuan-Mate-Mini-6-20250901_1322.iso version and ran it in a live session. I added the Chromium browser to the live session and when I went to open it, I got a message that the keyring was not unlocked. I dismissed the message, and Chromium worked as it should. To see if I would get the keyring message again, I closed Chromium and then reopened it. I got the keyring message again, but again after dismissing it everything continued to work.
My question is, if I install your spin, will I continue to get this keyring message?
Okay, thanks. And thanks for the heads up on yt-dlp.