On Sun, Oct 31, 2021 at 09:48:53PM +0100, Landry Breuil wrote: > Le Sun, Oct 31, 2021 at 09:39:35PM +0100, Matthieu Herrb a écrit : > > On Fri, Oct 29, 2021 at 10:33:04AM +0200, Peter N. M. Hansteen wrote: > > > On Fri, Oct 29, 2021 at 10:05:34AM +0200, Landry Breuil wrote: > > > > > > > i can confirm i've seen this when upgrading my machines, and most of > > > > them were previously running various snapshots from beginning of > > > > september/end of september, so likely a regression from "something" in X > > > > or drm ? > > > > > > I think we can narrow it down to some time this week. If I remember > > > correctly, > > > I did not see this after upgrading to whatever was the latest snap late > > > last Sunday afternoon CEST, but I noticed this first yesterday morning > > > after my late Wednesday evening CEST upgrade. > > > > > > The problem persists after upgrading to this morning's snap, ie > > > > > > index.txt 29-Oct-2021 02:19 1690 > > > > > > > Ktracing the screensaver process shows it execs > > /usr/local/libexec/xfce4-screensaver-dialog > > which fails with the following error: > > > > ** (xfce4-screensaver-dialog:72106): ERROR **: 21:36:25.353: Failed to > > connect to xfconf daemon: Cannot spawn a message bus when setuid. > > > > I don't know much about xfconf / dbus / setuid applications > > interactions, but this doesn't look like something related to changes > > in base. > > Well... iirc, nothing changed between xfconf and xfce4-screensaver since > months ... ? changes in credentials passing over sockets ?
The error messages comes from libgio-2.0.so.4200.14 part of glib2. -- Matthieu Herrb
