Dear Maintainer,

Running a dist-upgrade on Debian Testing (on two different machines - Lenovo
T420 laptop and old i7-990x desktop) I noticed that upgrading to 3.0.2 causes
my user to be logged out immediately. I can log back in normally, but I have to
restart NetworkManager by hand. Then  dpkg --configure -a followed by another
dist-upgrade  and everything seems okay.

I just tried  apt-get --reinstall install iio-sensor-proxy  to force a
reinstall of the package by itself and got logged out again as it reinstalled.
So I think it narrows it down to this package.

Hi,

There may be more to it. With no logs, I'm afraid that may not be the
right conclusion. Also, note that iio-sensor-proxy gets pulled in into
the generic GNOME desktop.

Would it be possible for you to extract more details from your system
logs ?

And while my primary machine no more has orientation sensors but the
package is still installed/upgraded and I don't recollect running into
the symptom you describe.

iio-sensor-proxy:amd64 (3.0-1, 3.0-2)

Control: tag -1 +moreinfo

rrs@priyasi:~$ sudo apt purge iio-sensor-proxy
[sudo] password for rrs:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
  iio-sensor-proxy*
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 183 kB disk space will be freed.
Do you want to continue? [Y/n]
(Reading database ... 417802 files and directories currently
installed.)
Removing iio-sensor-proxy (3.0-2) ...
(Reading database ... 417776 files and directories currently
installed.)
Purging configuration files for iio-sensor-proxy (3.0-2) ...
Processing triggers for dbus (1.12.20-1) ...
21:02 ♒ ॐ ♅ ♄ ⛢     ☺ 😄

rrs@priyasi:~$ no-proxy-apt install iio-sensor-proxy
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
  iio-sensor-proxy
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 39.6 kB of archives.
After this operation, 183 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian testing/main amd64 iio-sensor-proxy
amd64 3.0-2 [39.6 kB]
Fetched 39.6 kB in 1s (68.8 kB/s)
Retrieving bug reports... 0% Fail
Error retrieving bug reports from the server with the following error
message:
E: getaddrinfo: Name or service not known (aptproxy:3142)
It appears that your network connection is down. Check network
configuration and try again
Retry downloading bug information? [Y/n] n
Continue the installation anyway? [y/N] y
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
Selecting previously unselected package iio-sensor-proxy.
(Reading database ... 417776 files and directories currently
installed.)
Preparing to unpack .../iio-sensor-proxy_3.0-2_amd64.deb ...
Unpacking iio-sensor-proxy (3.0-2) ...
Setting up iio-sensor-proxy (3.0-2) ...
iio-sensor-proxy.service is a disabled or a static unit, not starting
it.
Processing triggers for dbus (1.12.20-1) ...
Scanning processes...
Scanning candidates...
Scanning processor microcode...
Scanning linux images...

Running kernel seems to be up-to-date.

The processor microcode seems to be up-to-date.

No services need to be restarted.

No containers need to be restarted.

No user sessions are running outdated binaries.
21:03 ♒ ॐ ♅ ♄ ⛢     ☺ 😄

Hi,

You're saying it does *not* happen with 3.0-1 but happens with 3.0-1? I
would have not idea how the changes between the version can trigger
this. Also there's no relation to network-manager here. Look at the dpkg
logs and journal please.
Cheers,
 -- Guido

Hi Bruce,

Adding the bug back to cc: so Ritesh and others can follow along.

This sounds a lot as if your desktop environment wouldn't cope with
iio-sensor-proxy being restarted - so likely not a bug in this package.

- Which desktop are you running?
- Please provide the `sudo journalctl -b0` (please check for sensitive
  data before sending it out)
- does the same problem also happen when you do

   `sudo systemctl restart iio-sensor-proxy`

  in a terminal?

Cheers,
 -- Guido

Hi Bruce,

(adding the bug back in cc: - please hit reply-all so others can follow
a long too).

I've got some further questions below:

[..snip..]

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.

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

Cheers,
 -- Guido

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.

Hi,

It's DBus activated so it'll start when a service requests it. For
debugging you can run /usr/sbin/iio-sensor-proxy by hand (as root).

I do believe this is a problem in mate - not iio-sensor-proxy since a
restart of the daemon itself basically can't log you out - as far as i
can tell.
Cheers,
 -- Guido