Jammy Jellyfish XFCE Lock Screen not displaying correctly

[Alex Powell]

Jammy Jellyfish LightDM is frozen after long period of inactivity
Latest updates installed, has been happening since first install 2 weeks ago.

Upon using the laptop after over night or coming back from work, the screen is frozen. I can move the mouse around but click is unresponsive.

To resolve the issue, I ctrl+alt+f2 in order to log into a shell then restart the LightDM services.

I am using an XFCE environment.

Description: Ubuntu Jammy Jellyfish (development branch)
Release: 22.04

xfce4-screensaver:
  Installed: 4.16.0-1
  Candidate: 4.16.0-1
  Version table:
 *** 4.16.0-1 500
        500 http://au.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
        100 /var/lib/dpkg/status

lightdm:
  Installed: 1.30.0-0ubuntu5
  Candidate: 1.30.0-0ubuntu5
  Version table:
 *** 1.30.0-0ubuntu5 500
        500 http://au.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
        100 /var/lib/dpkg/status
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu78
Architecture: amd64
CasperMD5CheckResult: unknown
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2022-01-16 (45 days ago)
InstallationMedia: Xubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1)
Package: lightdm 1.30.0-0ubuntu5
PackageArchitecture: amd64
ProcEnviron:
 LANGUAGE=en_AU:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
Tags: jammy
Uname: Linux 5.15.0-18-generic x86_64
UpgradeStatus: Upgraded to jammy on 2022-02-18 (13 days ago)
UserGroups: N/A
_MarkForUpload: True
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu78
Architecture: amd64
CasperMD5CheckResult: unknown
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2022-01-16 (46 days ago)
InstallationMedia: Xubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1)
Package: xfce4-screensaver 4.16.0-1
PackageArchitecture: amd64
ProcEnviron:
 LANGUAGE=en_AU:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
Tags: jammy
Uname: Linux 5.15.0-18-generic x86_64
UpgradeStatus: Upgraded to jammy on 2022-02-18 (13 days ago)
UserGroups: N/A
_MarkForUpload: True

[Erich Eickmeyer (eeickmeyer)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:
apport-collect 1962818

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

[Alex Powell (alexj.powell)]

apport information

[Alex Powell (alexj.powell)]

apport information

[Alex Powell (alexj.powell)]

apport information

[Alex Powell (alexj.powell)]

Changing package to xfce-screensaver after additional troubleshooting:
-apt remove xfce4-screensaver resolves the issue

Appears that the frozen screen is a result of xfce4-screensaver not operating as expected and is not a LightDM issue

[Alex Powell (alexj.powell)]

xfce4-screensaver:
  Installed: 4.16.0-1
  Candidate: 4.16.0-1
  Version table:
 *** 4.16.0-1 500
        500 http://au.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
        100 /var/lib/dpkg/status

[Alex Powell (alexj.powell)]

apport information

[Alex Powell (alexj.powell)]

apport information

[Alex Powell (alexj.powell)]

Switching the display compositor over to Compton also resolves the issue while xfce4-screensaver is still installed.

Problem may exist in xfwm4?

xfwm4:
  Installed: 4.16.1-1
  Candidate: 4.16.1-1
  Version table:
 *** 4.16.1-1 500
        500 http://au.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
        100 /var/lib/dpkg/status

[Alex Powell (alexj.powell)]

Simply entering my password and pressing return also resolves the issue
Seems that the lock screen is present, but is not visible for some reason.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.