Live system cannot leave 'Lock Screen' when selected from menu

Bug #2000787 reported by sudodus
28
This bug affects 5 people
Affects Status Importance Assigned to Milestone
casper (Ubuntu)
Fix Released
Medium
Simon Quigley

Bug Description

I thought this was bug 1989163 but it remains when that bug is squashed.

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: lubuntu-desktop 23.04.3
ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
Uname: Linux 5.19.0-21-generic x86_64
ApportVersion: 2.24.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.477
CurrentDesktop: LXQt
Date: Fri Dec 30 14:30:38 2022
LiveMediaBuild: Lubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221229)
SourcePackage: lubuntu-meta
UpgradeStatus: No upgrade log present (probably fresh install)

This fails for me (reported in comments #5, #13, #14 of bug 1989163):

Selecting 'Lock Screen' works in my Dell Precision M4800, when running Lubuntu Kinetic Live. The screensaver starts and runs (a bit stuttering, different from earlier). The problem is to get rid of it. I get a pop-up window 'XscreenSaver 2021, v6.02' and it should be happy when pressing Enter or OK (with a blank password) but nothing happens and I have to stop the graphical desktop environment via ctrl+alt+F2.

This seems to be different from your descriptions, but I guess it is related.

Edit: I created a second user (in the live system at the virtual text screen tty2) and logged into it. Then tried 'Lock Screen' and then it worked to get back into the desktop environment. So in my case it seems that the pop-up window 'XscreenSaver 2021, v6.02' wants a non-blank password :-/

It fails not only in a Dell with nvidia but also in a Toshiba with Intel graphics. I think you can reproduce the bug in most live Lubuntu Lunar systems.

I don't know the name of the package containing the 'Lock Screen' tool called by the menu, so please modify the target package to the correct one.

Related branches

Revision history for this message
sudodus (nio-wiklund) wrote :
sudodus (nio-wiklund)
description: updated
description: updated
description: updated
Revision history for this message
sudodus (nio-wiklund) wrote :
Revision history for this message
sudodus (nio-wiklund) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in lubuntu-meta (Ubuntu):
status: New → Confirmed
Revision history for this message
Leó Kolbeinsson (leok) wrote :

Tested Lubuntu Lunar daily ISO dated 30-12-22 Live session and this was present as in original report.

Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/2000787

tags: added: iso-testing
Revision history for this message
Aaron Rainbolt (arraybolt3) wrote :

Successfully reproduced this bug in the latest Lunar ISO.

Revision history for this message
KGIII (uninvolved) wrote :

Confirmed in today's like .iso test.

The password doesn't appear to work, but that's above my pay grade.

Revision history for this message
sudodus (nio-wiklund) wrote :

@ KGIII (uninvolved),

If you create a second user (not 'lubuntu') and a password for it (in the live system), it works. I tried to set a password for the default user 'lubuntu' but it did not help/work, which I think matches your experience.

Revision history for this message
Aaron Rainbolt (arraybolt3) wrote :

I wonder if maybe this is related to the UID of the default lubuntu user?

Revision history for this message
sudodus (nio-wiklund) wrote (last edit ):

We should also consider what is the best action here:

1. Workaround: Turn off Lock Screen for the live user 'lubuntu'. But it would be nice to keep it for other user IDs which could be useful in persistent live systems.

2. Solution: Make unlocking work with blank password for the live user 'lubuntu'. But it provides no real security.

Revision history for this message
sudodus (nio-wiklund) wrote (last edit ):

I noticed that the live Lunar Ubuntu Desktop (standard Ubuntu) arrives at a page that prompts to enter user name and password, in other words, there is not longer a standard user with a blank password.

This should be considered when we decide how to deal with this bug and/or in general how to deal with assigning a user ID for the live session of Lubuntu and/or other community flavours.

Revision history for this message
sudodus (nio-wiklund) wrote :

This bug is still alive at Lubuntu Lunar Beta in March 30 (2023).

Revision history for this message
Thomas Piekarski (t-piekarski) wrote :

The bug is present on Kubuntu Lunar Final Milestone, 20230414.1 as well. While ISO Testing I can not unlock the system and I presume on Kubuntu there is also no default password.

Revision history for this message
Aaron Rainbolt (arraybolt3) wrote :

@t-piekarski: Could you file the Kubuntu problem as a separate bug? Lubuntu and Kubuntu use entirely different lock screen mechanisms and so these are very likely unrelated although they seem the same on the surface. The Kubuntu people probably should know about this. (I would file this against plasma-desktop.)

Revision history for this message
Aaron Rainbolt (arraybolt3) wrote :

Pretty sure this is related to the default password on the live ISO being literally blank. As it turns out, XScreenSaver locks you out if your user password is blank (as confirmed when triaging https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/2016436).

Not sure if there's much we can do about that on the live ISO or not.

Revision history for this message
sudodus (nio-wiklund) wrote :

@Aaron Rainbolt,

Well, maybe a workaround is the best we can do now: remove XScreensaver from the live menu (but not from the installed menu).

Paul White (paulw2u)
tags: added: mantic
Simon Quigley (tsimonq2)
Changed in lubuntu-meta (Ubuntu):
importance: Undecided → Medium
status: Confirmed → In Progress
assignee: nobody → Simon Quigley (tsimonq2)
affects: lubuntu-meta (Ubuntu) → casper (Ubuntu)
Changed in casper (Ubuntu):
assignee: Simon Quigley (tsimonq2) → nobody
assignee: nobody → Simon Quigley (tsimonq2)
Revision history for this message
Erich Eickmeyer (eeickmeyer) wrote :

Ubuntu Studio is also affected, but the mechanism is different and just needs some code added. Adding here for posterity.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package casper - 1.484

---------------
casper (1.484) mantic; urgency=medium

  [ Erich Eickmeyer ]
  * scripts/34disable_kde_services: Add ubuntustudio (LP: #2000787)

  [ Steve Langasek ]
  * scripts/34disable_kde_services: refactor to reduce code duplication.

 -- Steve Langasek <email address hidden> Fri, 29 Sep 2023 17:34:55 -0700

Changed in casper (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.