Guido, (replying to all this time)
I sent a second mail last night - I tried reinstalling gnome-settings-daemon, then doing the remove-install routine on iio-sensor-proxy and nothing happened. I just did the following on the laptop: install gnome-settings-daemon, remove iio-sensor-proxy, install iio-sensor-proxy (no logout, but it's not running), systemctl start iio-sensor-proxy. The last command produced nothing except a command prompt - no indication that it didn't start. But I just did systemctl list-units | grep "iio" systemctl list-units | grep "gnome" systemctl list-units | grep "gsd" ps -ef | grep "iio" ps -ef | grep "gnome" ps -ef | grep "gsd" In no case does grep find anything. I did systemctl enable iio-sensor-proxy and I get "The unit files have no installation config (WantedBy=, RequiredBy=, Also=, Alias= settings in the [Install] section, and DefaultInstance= for template units). This means they are not meant to be enabled using systemctl. ... etc." How can I enable the unit so I can start it? (This is on the T420 laptop. I've never used the gnome desktop, but I *think *years ago I wanted to do some desktop tweaks, and thinking that Mate was Gnome 2-based, I installed gnome-settings-daemon - then realized Mate has its own configuration editor and installed that. So that explains why gnome-settings-daemon was on the T420.) But I reinstalled the OS on the desktop one month ago when I got a new drive, and *didn't *install gnome-settings-daemon there - but I noticed the logout problem on the desktop once. gsd was *not *installed on the desktop when I checked last night. I've never been able to reproduce it a second time on the desktop. Re the time on the log - I wrote the second-to-the-last mail I sent last night at Thu, Feb 04, 2021 at 09:18:06PM -0500 (according to the header), and I sent it right after the last forced logout I noted in the mail. I attached the journal created after logging back in (the small journal file) - then I sent a final mail with the earlier (large) journal file. So the last forced logout would have occurred around 8:30 - 9:15 PM EST. One other thing in case it's relevant - I'm on debian testing, and I habitually do a dist-upgrade on my machines nearly daily. But I don't have needrestart or checkrestart installed, so I rely on the upgrade process to restart anything it thinks need restarting. Bruce I. On Fri, Feb 5, 2021 at 8:26 AM Guido Günther <[email protected]> wrote: > ... > Thanks for providing those details! > > The final check would be to reinstall gnome-settings-daemon and see if > you can trigger the problem again. I don't spot anything related to > either g-s-d or iio-sensor-proxy in the logs so this is really odd. > > > > > One final note: When I can successfully install the package, apt tells > me: > > "iio-sensor-proxy.service is a disabled or a static unit not running, not > > starting it." As I said, I probably have no devices that might use > > it. > > It's DBus activated so shouldn't be even started when unused - that's > what puzzles me. If you have gnome-settings-daemon installed, do you > have any running processes starting with ` /usr/libexec/gsd-` in your > mate session? Once thing i could imagine is that they're conflicting > with mate's setting daemon and mate's setting daemon giving up closes > your session (in that case iio-sensor-proxy would just be the trigger). > > I wonder if that would DBus activate iio-sensor-proxy - I still wouldn't > know how that would log . Also can you > check if iio-sensor-proxy is actually running as a process with > gnome-settings-daemon installed? > > You have several logins/logouts in your log. Can you pinpoint at what > time the logout happened so i can check the specific spot in the log? > > Cheers, > -- Guido > > -- ----- [email protected]
