Logged out of session on sleep

Software PureOS
1

In the last couple of weeks I’ve started to noticed that when I open up my librem 13 in the morning, I am often logged out of my session. I looked through syslog and found what looks to be a hint:

Mar 31 00:06:08 localhost NetworkManager[767]: <info>  [1585638368.8330] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Mar 31 00:06:08 localhost NetworkManager[767]: <info>  [1585638368.8332] manager: NetworkManager state is now ASLEEP
Mar 31 00:06:08 localhost kernel: [142358.346389] gnome-shell[53203]: segfault at 24 ip 00007f30e9ce6de1 sp 00007ffe9d5e55e0 error 4 in libwayland-server.so.0.1.0[7f30e9ce6000+7000]
Mar 31 00:06:08 localhost kernel: [142358.346406] Code: 48 8b 13 4c 8d 64 24 20 48 8d 4c 24 08 48 8d 84 24 a0 01 00 00 c7 44 24 08 10 00 00 00 48 89 44 24 10 48 8d 84 24 d0 00 00 00 <48> 8b 72 20 ba 14 00 00 00 48 89 44 24 18 89 e8 48 8d 04 40 c7 44
Mar 31 00:06:08 localhost Telegram[22124]: Error reading events from display: Broken pipe
Mar 31 00:06:08 localhost tilix[56216]: Error reading events from display: Broken pipe
```
Mar 31 00:06:08 localhost rhythmbox[37632]: Error reading events from display: Broken pipe
Mar 31 00:06:08 localhost nautilus[54255]: Error reading events from display: Broken pipe
Mar 31 00:06:08 localhost seahorse[53961]: Error reading events from display: Broken pipe
Mar 31 00:06:08 localhost gnome-session[53166]: gnome-session-binary[53166]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
Mar 31 00:06:08 localhost gnome-session-binary[53166]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
Mar 31 00:06:08 localhost gnome-session-binary[53166]: Unrecoverable failure in required component org.gnome.Shell.desktop

Is anyone else seeing this? Any recommendations for how to further debug? I’m not really sure where to go from here. It seems related to PureOS 8 beta Librem15: Randomly logged out of session, but not exactly the same.

I’m using GNOME Shell 3.30.2 on a Librem 13 v2.

lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian
Release: 9.0
Codename: amber

I’m definitely running PureOS though. Not sure why it says Debian there.

2

Hi,

I assume you updated your system? Could you try using xserver session to see if this can be reproduced?

3

I assume you updated your system?

Not sure what you’re referring to here.

Could you try using xserver session to see if this can be reproduced?

Sure! I’ll give this a shot and report back later this week.

4

Maybe he means: Are you running the latest released versions of everything, as is generally desirable?

Can you explain what you mean by this? Are you using some kind of standby / hibernate mode? Or just a normal boot?

5

The output mentions sleep, I would take that to mean that at the end of the day he closes his laptop and it then goes to sleep. In the morning he opens it back up and finds that he’s been logged out, which I would surmise means it rebooted.

To add some detail to what “updated your system” means, it means have you installed updates either via terminal (sudo apt update and sudo apt upgrade or sudo apt full-upgrade) or via the software manager?

6

I close the lid at night, open it up in the morning.

7

I kind of doubt it’s a reboot–I imagine I would need to enter my disk decryption password in that case. I think it’s just a user session crash.

8

Then you would need to verify whether

  • this is basically doing nothing to machine state
  • this is entering some kind of standby / hibernate mode

How are you determining that you have been logged out? Bear in mind that good security practice often means configuring a computer that has entered standby / hibernate to require the username and password in order to return to normal state - and coming out of a locked (but not standby / hibernate) state also requires the username and password.

It is also possible that something has ‘power saved’ and there is a bug so that it is not handled correctly on one or both of the transitions.

So you definitely need to investigate your power management settings.

Does it make any difference if you don’t close the lid? i.e. let it power save but don’t have the ‘lid close’ event?

9

Could you try using xserver session to see if this can be reproduced?

@mladen after a week or two of using xserver, I have not been able to reproduce this! So I guess it’s a wayland issue?

1 Like
10

It could be. But also could be some other software in combination with wayland.