#StackBounty: #networking #wireless #suspend How to prevent wifi sleep after suspend

Bounty: 50

Every time I open my notebook lid I have to wait a few seconds for wifi to reconnect. I remember that in Windows it was already connected. I need a way to prevent wifi from disconneting on suspend.

The closest answer I found was https://askubuntu.com/a/961460/613425 but it didn’t work. I also tried the iwconfig wlan0 poweroff in the answer but it didn’t work even before reboot.


Get this bounty!!!

#StackBounty: #debian #power-management #suspend #crash #intel-graphics Sony docking station crashes GUI on unsuspend

Bounty: 100

I have a Sony Vaio (2012) SVS13a with a full docking station which the notebook clips into. I run Debian Testing and have the latest updates installed as of writing this question.

When I have the notebook in the docking station and I suspend, most of the time when I un-suspend my windows manager crashes and I’m faced with the login screen (lightdm) again. I’ve tried different windows managers (XFCE4 & EXWM) and the same thing happens in both.

When the issue happens the Windows Manager doesn’t crash straight away, I’m presented with a black screen then when I change over to VT1 and back to VT7, then it crashes and I’m redirected to the lightdm screen.

I find this in my dmesg after;

[180410.346999] [drm:intel_display_resume [i915]] *ERROR* Restoring old state failed with -22

It didn’t used to happen, although I’ve always had some issues in the docking station. Sometimes the external screen wouldn’t come on, but it would never crash. It’s only been like this in the last few months.

If I run the external screen, keyboard & mouse directly not using the docking station then I can suspend and un-suspend without a problem. I did this for two weeks over the summer break. So the problem is definitely to do with the docking station.


Get this bounty!!!

#StackBounty: #suspend #power-management #laptop Ubuntu 17.10 laptop doesn't suspend on lid close

Bounty: 100

Thinkpad T450 running Ubuntu 17.10 which was clean-installed (not upgraded) some weeks back. I frequently moved from room to room and like the laptop to go to sleep when I close the lid. It seems to never do this, staying awake all the time. I have to hold down the power button in the indicator and choose the pause icon to suspend it. Previous releases of Ubuntu used to “Just Work”.

I have tried toggling the option in Tweaks to ensure it is set to suspend on lid close, but this makes no difference. Is this a bug or expected behaviour?


Get this bounty!!!

#StackBounty: #suspend #power-management #laptop Ubuntu 17.10 laptop doesn't suspend on lid close

Bounty: 100

Thinkpad T450 running Ubuntu 17.10 which was clean-installed (not upgraded) some weeks back. I frequently moved from room to room and like the laptop to go to sleep when I close the lid. It seems to never do this, staying awake all the time. I have to hold down the power button in the indicator and choose the pause icon to suspend it. Previous releases of Ubuntu used to “Just Work”.

I have tried toggling the option in Tweaks to ensure it is set to suspend on lid close, but this makes no difference. Is this a bug or expected behaviour?


Get this bounty!!!

#StackBounty: #suspend #power-management #laptop Ubuntu 17.10 laptop doesn't suspend on lid close

Bounty: 100

Thinkpad T450 running Ubuntu 17.10 which was clean-installed (not upgraded) some weeks back. I frequently moved from room to room and like the laptop to go to sleep when I close the lid. It seems to never do this, staying awake all the time. I have to hold down the power button in the indicator and choose the pause icon to suspend it. Previous releases of Ubuntu used to “Just Work”.

I have tried toggling the option in Tweaks to ensure it is set to suspend on lid close, but this makes no difference. Is this a bug or expected behaviour?


Get this bounty!!!

#StackBounty: #suspend #shutdown #17.10 Not able to suspend or shutdown properly on ubuntu 17.10

Bounty: 50

I renctly updated to Ubuntu 17.10 and I’m not able to suspend my desktop. My screen are powered off but the fan still run and I’m not able to press the power button of my computer to resume.

I have this in /var/log/syslog :

Nov  3 04:35:57 oscar gnome-shell[3537]: JS WARNING: [/home/dougui/.local/share/gnome-shell/extensions/suspend-button@laserb/extension.js 202]: assignment to undeclared variable gnomeShellVersion
Nov  3 04:35:57 oscar NetworkManager[1050]: <info>  [1509698157.6376] manager: sleep requested (sleeping: no  enabled: yes)
Nov  3 04:35:57 oscar NetworkManager[1050]: <info>  [1509698157.6376] manager: sleeping...
Nov  3 04:35:57 oscar systemd[1]: Reached target Sleep.
Nov  3 04:35:57 oscar org.gnome.Shell.desktop[2428]: Window manager warning: Failed to set power save mode for output DVI-I-1: Not permitted
Nov  3 04:35:57 oscar org.gnome.Shell.desktop[2428]: Window manager warning: Failed to set power save mode for output HDMI-1: Not permitted
Nov  3 04:35:57 oscar gnome-shell[2428]: Screen lock is locked down, not locking
Nov  3 04:35:57 oscar systemd[1]: Starting Suspend...
Nov  3 04:35:57 oscar systemd-sleep[5572]: Selected interface 'enp4s0'
Nov  3 04:35:57 oscar systemd-sleep[5572]: OK
Nov  3 04:35:57 oscar systemd-sleep[5572]: Suspending system...

I have errors but nothing special.

Here is information about my system :

Linux oscar 4.13.0-16-lowlatency #19-Ubuntu SMP PREEMPT Wed Oct 11 19:51:52 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

EDIT

It happens when I shutdown also.


Get this bounty!!!

#StackBounty: #suspend #screen #xserver Variant on the NotWakingUpAfterSuspend problem

Bounty: 50

I looked at may posts about this problem, but I could not find one to my problem.

After suspend or sleep my computer does wake up. I know, because Ctrl-Alt-F1 shows me a console. But my desktop screen remains black and is unresponsive.

How can I wake up my desktop from a working console on the same computer?

what I tried

  • run ‘set -display $DISPLAY dpms force on’. Did not work bu gave me ‘unable to open display “”‘. Same when I tried to set ‘DISPLAY=:0’ manually.
  • ‘sudo sysctrl unlock-session’ got no reaction
  • I can not reproduce yet, but twice I go a graphical message like ‘your screen is locked. You will be forwarded to the unlock dialog’ (can’t recall exact wording). But screen got black again.
  • startx on the F1 console started and empty desktop fine. So in principle graphics capabilities are there.
  • ‘sudo system lightdm restart’ wakes that screen with a login dialog. Since it kills all running applications its not really a help.
  • found some other bounty question with references to light-locker and xscreensaver. Never heard of both before, but followed what I could read there. So I purged light-locker and installed xscreensaver with -data and -gl extensions. Somehow seemed to work since desktop asked me to disable lightlocker deamon which I did. But problem remained. Maybe I did not correctly do that swap.


Get this bounty!!!

#StackBounty: #suspend #evolution #ms-exchange Evolution-ews: Ticket Expired. How to renew ticket after suspend?

Bounty: 50

I connect Evolution to an MS Exchange Server. That works just fine. But when waking up from suspend, Evolution cannot connect anymore with Error Message “Ticket Expired”.

Ticket Expired

That happens regardless if Evolution was closed or not during suspend, it does still occur after closing and reopening Evolution.

After a reboot the connection works again.

How can I either fix this issue OR just do a full restart of evolution (including the eventual backend services) without having to reboot ?

Update:

I tried evolution -q and evolution --force-shutdown, but it didn’t help.

Running with --gtk-debug=error:

$ evolution --gtk-debug=error
(evolution:28353): Gtk-DEBUG: Connecting to session manager
(evolution:28353): Gtk-DEBUG: Registering client 'evolution' ''
(evolution:28353): Gtk-DEBUG: Registered client at '/org/gnome/SessionManager/Client25'

(evolution:28353): camel-WARNING **: Failed to initialize NSS SQL database in sql:/etc/pki/nssdb: NSS error -8126

The Failed to initialize – Warning is always there, also when everything works.


Get this bounty!!!

#StackBounty: #suspend #evolution #ms-exchange Restart Evolution

Bounty: 50

I connect Evolution to an MS Exchange Server. That works just fine. But when waking up from suspend, Evolution cannot connect anymore with Error Message “Ticket Expired”.

Ticket Expired

That happens regardless if Evolution was closed or not during suspend, it does still occur after closing and reopening Evolution.

After a reboot the connection works again.

How can I either fix this issue OR just do a full restart of evolution (including the eventual backend services) without having to reboot ?


Get this bounty!!!