[Bug 1759950] Re: Lid-close suspend: blank screen when switching to user session

[Bug Watch Updater]

Launchpad has imported 2 comments from the remote bug at
https://bugzilla.xfce.org/show_bug.cgi?id=15151.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2019-02-20T17:25:46+00:00 Carlos Pita wrote:

No matter how I configure xfce4 power manager lid close on battery/ac
events, the ones configured in logind.conf win.

If I set logind to ignore all lid events, nothing really happens, so
that logind again wins (the ignore settings take precedence over xfce4
power manager).

This is the ignore logind config:

HandleLidSwitch=ignore
HandleLidSwitchExternalPower=ignore
LidSwitchIgnoreInhibited=no

The LidSwitchIgnoreInhibited flag seems to be irrelevant, since both
values result in the same behavior.

This is my power manager config:

~:: xfconf-query -c xfce4-power-manager -vl
/xfce4-power-manager/blank-on-battery                   3
/xfce4-power-manager/brightness-on-battery              9
/xfce4-power-manager/brightness-switch                  1
/xfce4-power-manager/brightness-switch-restore-on-exit  0
/xfce4-power-manager/critical-power-action              2
/xfce4-power-manager/critical-power-level               5
/xfce4-power-manager/dpms-on-battery-off                9
/xfce4-power-manager/dpms-on-battery-sleep              6
/xfce4-power-manager/general-notification               true
/xfce4-power-manager/handle-brightness-keys             false
/xfce4-power-manager/inactivity-on-ac                   15
/xfce4-power-manager/inactivity-on-battery              15
/xfce4-power-manager/lid-action-on-ac                   3
/xfce4-power-manager/lid-action-on-battery              1
/xfce4-power-manager/logind-handle-lid-switch           true
/xfce4-power-manager/power-button-action                2

Reply at: https://bugs.launchpad.net/ubuntu/+source/light-
locker/+bug/1759950/comments/3

------------------------------------------------------------------------
On 2019-02-20T18:06:48+00:00 Carlos Pita wrote:

Btw, I tested this with mate-power-manager and it works straight out of
the box, without even changing the default logind settings.

Reply at: https://bugs.launchpad.net/ubuntu/+source/light-
locker/+bug/1759950/comments/4


** Changed in: xfce4-power-manager
       Status: Unknown => Confirmed

** Changed in: xfce4-power-manager
   Importance: Unknown => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1759950

Title:
  Lid-close suspend: blank screen when switching to user session

Status in Light-Locker:
  New
Status in Xfce4 Power Manager:
  Confirmed
Status in light-locker package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New
Status in xfce4-power-manager package in Ubuntu:
  Confirmed
Status in xubuntu-default-settings package in Ubuntu:
  New

Bug description:
  I'm currently testing Xubuntu 18.04 after a do-release-upgrade from
  16.04.

  I discovered a very weird issue. When doing S3 sleep via closing the
  lid, on resume the lock screen appears, I authenticate, but as soon as
  it switches to the user session the screen goes blank - not even a
  backlight.

  Switching to other ttys works and they display correctly but the GUI
  user session remains blank.

  If the system is manually suspended (not using the lid), then resumed
  either by opening the lid or pressing the power button, the GUI user
  session is fine.

  I narrowed it down to xfce4-power-manager and discovered disabling the
  lock-screen cured the issue.

  I cloned the repository and reviewed commits between 1.7 and 1.8.
  Fortunately there aren't many. Looking at 6365683 "Proper exit status
  for light-locker-command" I suspected the change in the SetActive
  return value, and reverted it.

  After a build/install cycle I've found the system now behaves
  correctly so I think the change should be reverted.

  I've created an issue upstream for this at

  https://github.com/the-cavalry/light-locker/issues/108

To manage notifications about this bug go to:
https://bugs.launchpad.net/light-locker/+bug/1759950/+subscriptions