You are not logged in.
greenjeans, as I understand it, that mess in the .desktop file only runs the first time you boot. After that, the correct background is set. Of course, that only counts if you install it. With the live iso, every time you boot it is the first boot.
Offline
FTR, every time I've booted, including the time with Xfce before I added Mate, I get a blue Devuan wallpaper.
Offline
Posting from live-session now, a few things I noticed:
1. the Mate .desktop for the polkit is still in /etc/xdg/autostart, so it still tries to start it up. need to chunk that now that you're using xfce-polkit, yes?
2. The file chooser dialog when opened was too long for my 1366x768 laptop screen, the bottom extended down past the screen so the cancel and open buttons are hidden from view, I grabbed a drag-handle and re-sized it and after that it respected my setting. Maybe set it's initial size a little smaller?
3. Potential issue with ~/.xsession-errors. Previously the file re-cycled itself each session, deleting old backup and making a new backup and new current. In this system instead of re-cycling it just appends the current session to the file, so nothing ever gets deleted. This could make for a very large file for a user that re-boots everyday and sometimes several times in a day. It's especially bad with the current theme as it generates around 270 lines of gtk theme parsing errors on every new session (just deprecation warnings, everything works okay). So i'm up to about 2000 lines in that file with 5 logins. Maybe need to go back to re-cycling? Or even just delete the current one when you shut down maybe?
Yeah the boot into live-session worked fine with the wallpaper, just slow to load that first time. And it did run just the first login, after that no more and I even trashed those two autostart files after a couple of logouts and and it didn't need them anymore, wallpaper showed up every time.
Seems like some issue with the live-session, something either missing or shouldn't be there, maybe in the config file and needing to be re-genned with a new detection which seems like that's what the special autostart does one time. Solved my issue a while back pretty much the same way. I'd just leave it, it's doing a good job. Seems like a good way to make a first-run script too, offering to set some things up for the user might be nice.
EDIT: It's also giving me an error on boot-up about colord, and errors in the session log when I try to use the "Color Profiles" menu entry:
(xfce4-color-settings:25106): xfce4-color-settings-WARNING **: 00:05:17.017: failed to connect to colord: Error calling StartServiceByName for org.freedesktop.ColorManager: Failed to setup environment correctlyLast edited by greenjeans (Today 00:11:58)
https://sourceforge.net/projects/vuu-do/ Vuu-do GNU/Linux, Devuan-based Openbox systems.
Devuan 6 mate-mini iso, pure Devuan, 100% no-vuu-do. Now with Xlibre as well.
Please donate to support Devuan and init freedom! https://devuan.org/os/donate
https://devuanusers.com/ Apps source : https://git.devuan.org/greenjeans
Online
Hello:
... instead of re-cycling it just appends the current session ...
... nothing ever gets deleted. This could make for a very large file ...
Indeed ...
I have seen huge GB sized [.xsession-errors] files.
But recycling the file means that you will not have access to the error log from the last session.
I see log files as the bread and butter of a Linux installation.
To me, the best solution is the one posted here. ### not that I'd have a clue as to what the file says, but someone else might ...
TL;DR: add a task to your crontab to periodically check the size of [.xsession-errors file].
If it grows past an arbitrary size, you truncate it to an also arbitrary amount of lines.
You set the size and the amount of lines.
eg: size=5GB lines=10000
*/15 * * * * [ $(du -k .xsession-errors | awk '{ print $1 }') -gt 5000000 ] && tail -10000 /home/$(whoami)/.xsession-errors > /home/$(whoami)/.xsession-errorsBest,
A.
Last edited by Altoid (Today 01:57:11)
Offline
Cycling through init 1 does result in gparted not starting. I think it's related to the elogind problem described here - https://dev1galaxy.org/viewtopic.php?id=8273 Same thing happens after switching to xfce-polkit.
Relevant auth.log is pasted below.
mate-polkit: It gets installed automatically. I removed it in the build but should have purged it instead. I'll probably revert to using mate-polkit and let that get changed in whichever task-* package is pulling it in.
(Edit: damn, it's xfce4 that pulls in mate-polkit, and that's not one of our forked packages.)
greenjeans, which file-chooser are you talking about? Where am I going to set its size?
Here is /var/log/auth.log from freia desktop-live with mate-polkit after cycling through init 1 then starting gparted.
2026-11-03T10:13:58.418179+00:00 localhost elogind[2057]: New seat seat0.
2026-11-03T10:13:58.437089+00:00 localhost elogind[2057]: Watching system buttons on /dev/input/event3 (Power Button)
2026-11-03T10:13:58.437120+00:00 localhost elogind[2057]: Watching system buttons on /dev/input/event1 (Lid Switch)
2026-11-03T10:13:58.437147+00:00 localhost elogind[2057]: Watching system buttons on /dev/input/event2 (Sleep Button)
2026-11-03T10:13:58.437173+00:00 localhost elogind[2057]: Watching system buttons on /dev/input/event0 (AT Translated Set 2 keyboard)
2026-11-03T10:13:58.437198+00:00 localhost elogind[2057]: Watching system buttons on /dev/input/event10 (ThinkPad Extra Buttons)
2026-11-03T10:13:58.437226+00:00 localhost elogind[2057]: Watching system buttons on /dev/input/event17 (ACPI Virtual Keyboard Device)
2026-11-03T10:14:11.434094+00:00 localhost slim: pam_unix(slim:session): session opened for user devuan(uid=1000) by devuan(uid=0)
2026-11-03T10:14:11.434131+00:00 localhost slim: gkr-pam: unable to locate daemon control file
2026-11-03T10:14:11.540531+00:00 localhost slim: gkr-pam: gnome-keyring-daemon started properly
2026-11-03T10:14:11.557212+00:00 localhost elogind[2057]: New session 1 of user devuan.
2026-11-03T10:14:11.562484+00:00 localhost slim: gkr-pam: couldn't unlock the login keyring.
2026-11-03T10:14:17.496317+00:00 localhost pkexec: PAM (polkit-1) /usr/lib/pam.d is not supported on this system; see /usr/share/doc/libpam0g/Debian-PAM-MiniPolicy.gz
2026-11-03T10:14:17.510825+00:00 localhost pkexec: pam_unix(polkit-1:session): session opened for user root(uid=0) by devuan(uid=1000)
2026-11-03T10:14:17.512281+00:00 localhost pkexec[2851]: devuan: Executing command [USER=root] [TTY=unknown] [CWD=/home/devuan] [COMMAND=/usr/sbin/xfpm-power-backlight-helper --set-brightness-switch 0]
2026-11-03T10:15:41.966908+00:00 localhost su: The gnome keyring socket is not owned with the same credentials as the user login: /home/devuan/.cache/keyring-Y0ZVX3/control
2026-11-03T10:15:41.966917+00:00 localhost su: gkr-pam: couldn't unlock the login keyring.
2026-11-03T10:15:41.968758+00:00 localhost su[3419]: (to root) devuan on pts/0
2026-11-03T10:15:41.969364+00:00 localhost su[3419]: pam_unix(su-l:session): session opened for user root(uid=0) by devuan(uid=1000)
2026-11-03T10:15:41.969412+00:00 localhost su[3419]: The gnome keyring socket is not owned with the same credentials as the user login: /home/devuan/.cache/keyring-Y0ZVX3/control
2026-11-03T10:15:41.969420+00:00 localhost su[3419]: gkr-pam: couldn't unlock the login keyring.
2026-11-03T10:15:56.961252+00:00 localhost elogind[3895]: New seat seat0.
2026-11-03T10:15:56.975024+00:00 localhost elogind[3895]: Watching system buttons on /dev/input/event3 (Power Button)
2026-11-03T10:15:56.975157+00:00 localhost elogind[3895]: Watching system buttons on /dev/input/event1 (Lid Switch)
2026-11-03T10:15:56.975230+00:00 localhost elogind[3895]: Watching system buttons on /dev/input/event2 (Sleep Button)
2026-11-03T10:15:56.975301+00:00 localhost elogind[3895]: Watching system buttons on /dev/input/event0 (AT Translated Set 2 keyboard)
2026-11-03T10:15:56.975369+00:00 localhost elogind[3895]: Watching system buttons on /dev/input/event10 (ThinkPad Extra Buttons)
2026-11-03T10:15:56.975440+00:00 localhost elogind[3895]: Watching system buttons on /dev/input/event17 (ACPI Virtual Keyboard Device)
2026-11-03T10:15:57.965924+00:00 localhost slim: pam_unix(slim:session): session opened for user devuan(uid=1000) by devuan(uid=0)
2026-11-03T10:15:57.965963+00:00 localhost slim: gkr-pam: unable to locate daemon control file
2026-11-03T10:15:57.973551+00:00 localhost slim: gkr-pam: gnome-keyring-daemon started properly
2026-11-03T10:15:57.985212+00:00 localhost elogind[3895]: New session 2 of user devuan.
2026-11-03T10:15:57.990813+00:00 localhost slim: gkr-pam: couldn't unlock the login keyring.
2026-11-03T10:16:00.144224+00:00 localhost pkexec: PAM (polkit-1) /usr/lib/pam.d is not supported on this system; see /usr/share/doc/libpam0g/Debian-PAM-MiniPolicy.gz
2026-11-03T10:16:00.147273+00:00 localhost pkexec: pam_unix(polkit-1:session): session opened for user root(uid=0) by devuan(uid=1000)
2026-11-03T10:16:00.148941+00:00 localhost pkexec[4792]: devuan: Executing command [USER=root] [TTY=unknown] [CWD=/home/devuan] [COMMAND=/usr/sbin/xfpm-power-backlight-helper --set-brightness-switch 0]
2026-11-03T10:16:15.793469+00:00 localhost polkit-agent-helper-1[5051]: PAM (polkit-1) /usr/lib/pam.d is not supported on this system; see /usr/share/doc/libpam0g/Debian-PAM-MiniPolicy.gz
2026-11-03T10:16:21.869917+00:00 localhost polkit-agent-helper-1[5051]: gkr-pam: unable to locate daemon control file
2026-11-03T10:16:21.869924+00:00 localhost polkit-agent-helper-1[5051]: gkr-pam: stashed password to try later in open session
2026-11-03T10:16:21.876807+00:00 localhost pkexec: PAM (polkit-1) /usr/lib/pam.d is not supported on this system; see /usr/share/doc/libpam0g/Debian-PAM-MiniPolicy.gz
2026-11-03T10:16:21.878425+00:00 localhost pkexec: pam_unix(polkit-1:session): session opened for user root(uid=0) by devuan(uid=1000)
2026-11-03T10:16:21.879121+00:00 localhost pkexec[5012]: devuan: Executing command [USER=root] [TTY=unknown] [CWD=/home/devuan] [COMMAND=/usr/sbin/gparted]
2026-11-03T10:16:48.092548+00:00 localhost su: The gnome keyring socket is not owned with the same credentials as the user login: /home/devuan/.cache/keyring-4FE4X3/control
2026-11-03T10:16:48.092556+00:00 localhost su: gkr-pam: couldn't unlock the login keyring.
2026-11-03T10:16:48.094372+00:00 localhost su[5201]: (to root) devuan on pts/0
2026-11-03T10:16:48.094925+00:00 localhost su[5201]: pam_unix(su-l:session): session opened for user root(uid=0) by devuan(uid=1000)
2026-11-03T10:16:48.094968+00:00 localhost su[5201]: The gnome keyring socket is not owned with the same credentials as the user login: /home/devuan/.cache/keyring-4FE4X3/control
2026-11-03T10:16:48.094976+00:00 localhost su[5201]: gkr-pam: couldn't unlock the login keyring.
2026-11-03T10:17:01.934906+00:00 localhost CRON[5217]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
2026-11-03T10:17:01.938067+00:00 localhost CRON[5217]: pam_unix(cron:session): session closed for user rootLast edited by fsmithred (Today 15:43:07)
Offline
I tried running the script in that elgoind thread and it gets rid of the extra cgroups stuff that accumulate on repeated logins, but it doesn't fix the problem with gparted not starting after the first login. I also couldn't start it from terminal after the first login.
Offline
su: The gnome keyring socket is not owned with the same credentials as the user login: /home/devuan/.cache/keyring-4FE4X3/controlEven if this is not the problem here, it's still a problem, gnome-keyring is a pain. It gets off-sync with the user (and their credentials) over the course of builds/installs. Username/password changes on install but nothing corrects the info in gnome-keyring. This is what causes a browser error that is legend now for all it's years of being a bug.
Last edited by greenjeans (Today 17:00:38)
https://sourceforge.net/projects/vuu-do/ Vuu-do GNU/Linux, Devuan-based Openbox systems.
Devuan 6 mate-mini iso, pure Devuan, 100% no-vuu-do. Now with Xlibre as well.
Please donate to support Devuan and init freedom! https://devuan.org/os/donate
https://devuanusers.com/ Apps source : https://git.devuan.org/greenjeans
Online
@fsmithred - Re: file chooser default size - You should be able to just initiate the file-chooser for something, use the corner grab-handle to re-size, and it will remember your setting after that. And that preference will still be in the config in a snapshotted system.
Oh and forgot to mention, the screensaver gui does the same thing, too long for screen.
https://sourceforge.net/projects/vuu-do/ Vuu-do GNU/Linux, Devuan-based Openbox systems.
Devuan 6 mate-mini iso, pure Devuan, 100% no-vuu-do. Now with Xlibre as well.
Please donate to support Devuan and init freedom! https://devuan.org/os/donate
https://devuanusers.com/ Apps source : https://git.devuan.org/greenjeans
Online