I am not prompted for my password when booting after running out of power (e.g. empty battery)

Bug #1890261 reported by De Baron
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
New
Low
Unassigned

Bug Description

Ubuntu 18.04.4 LTS

When the system shuts down because of lack of power supply, the next time, I am not prompted for my password; I go directly to the desktop.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-screensaver (not installed)
ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18
Uname: Linux 4.15.0-112-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.15
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Aug 4 11:06:26 2020
InstallationDate: Installed on 2018-10-04 (669 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: gnome-screensaver
Symptom: security
Title: Screen locking issue
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
De Baron (baronline) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report. Could you add your 'journalctl -b 0' after the system start? When the battery gets empty the system does try to suspend or hibernate depending of your configuration so the next boot is not a standard one but a resume which could explain you don't get prompted to log in

affects: gnome-screensaver (Ubuntu) → gnome-shell (Ubuntu)
Changed in gnome-shell (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
De Baron (baronline) wrote : Re: [Bug 1890261] Re: I am not prompted for my password when booting after running out of power (e.g. empty battery)

 I am sorry Sebastien, these are far too much lines to copy and paste (I'm not an expert on this).
Besides, the journal starts only today, I don't know whether I can go back in time.
Bart
    Op woensdag 5 augustus 2020 12:41:24 CEST schreef Sebastien Bacher <email address hidden>:

 Thank you for your bug report. Could you add your 'journalctl -b 0'
after the system start? When the battery gets empty the system does try
to suspend or hibernate depending of your configuration so the next boot
is not a standard one but a resume which could explain you don't get
prompted to log in

** Package changed: gnome-screensaver (Ubuntu) => gnome-shell (Ubuntu)

** Changed in: gnome-shell (Ubuntu)
  Importance: Undecided => Low

** Changed in: gnome-shell (Ubuntu)
      Status: New => Incomplete

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1890261

Title:
  I am not prompted for my password when booting after running out of
  power (e.g. empty battery)

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 18.04.4 LTS

  When the system shuts down because of lack of power supply, the next
  time, I am not prompted for my password; I go directly to the desktop.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-screensaver (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18
  Uname: Linux 4.15.0-112-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug  4 11:06:26 2020
  InstallationDate: Installed on 2018-10-04 (669 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
  SourcePackage: gnome-screensaver
  Symptom: security
  Title: Screen locking issue
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1890261/+subscriptions

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

You can go back in time. For example to collect the previous boot (the one before the current one) you can run:

  journalctl -b-1 > prevboot.txt

and the one before that:

  journalctl -b-2 > prevprevboot.txt

Revision history for this message
De Baron (baronline) wrote :
Download full text (368.8 KiB)

 The requested log:

b$$$$$$$$@**********:~$ journalctl -b 0
-- Logs begin at Thu 2020-06-25 16:50:08 CEST, end at Mon 2020-08-24 15:01:37 CE
aug 24 14:56:47 ********** kernel: microcode: microcode updated early to revision
aug 24 14:56:47 ********** kernel: Linux version 4.15.0-112-generic (buildd@lcy01
aug 24 14:56:47 ********** kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-
aug 24 14:56:47 ********** kernel: KERNEL supported cpus:
aug 24 14:56:47 ********** kernel: Intel GenuineIntel
aug 24 14:56:47 ********** kernel: AMD AuthenticAMD
aug 24 14:56:47 ********** kernel: Centaur CentaurHauls
aug 24 14:56:47 ********** kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87
aug 24 14:56:47 ********** kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE
aug 24 14:56:47 ********** kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX
aug 24 14:56:47 ********** kernel: x86/fpu: Supporting XSAVE feature 0x008: 'MPX
aug 24 14:56:47 ********** kernel: x86/fpu: Supporting XSAVE feature 0x010: 'MPX
aug 24 14:56:47 ********** kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[
aug 24 14:56:47 ********** kernel: x86/fpu: xstate_offset[3]: 832, xstate_sizes[
aug 24 14:56:47 ********** kernel: x86/fpu: xstate_offset[4]: 896, xstate_sizes[
aug 24 14:56:47 ********** kernel: x86/fpu: Enabled xstate features 0x1f, context
aug 24 14:56:47 ********** kernel: e820: BIOS-provided physical RAM map:
aug 24 14:56:47 ********** kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000
aug 24 14:56:47 ********** kernel: BIOS-e820: [mem 0x0000000000058000-0x000000000
aug 24 14:56:47 ********** kernel: BIOS-e820: [mem 0x0000000000059000-0x000000000
aug 24 14:56:47 ********** kernel: BIOS-e820: [mem 0x000000000009e000-0x000000000
aug 24 14:56:47 ********** kernel: BIOS-e820: [mem 0x0000000000100000-0x000000006
lines 1-23...skipping...
-- Logs begin at Thu 2020-06-25 16:50:08 CEST, end at Mon 2020-08-24 15:01:37 CEST. --
aug 24 14:56:47 ********** kernel: microcode: microcode updated early to revision 0xd6, date = 2020-04-23
aug 24 14:56:47 ********** kernel: Linux version 4.15.0-112-generic (buildd@lcy01-amd64-027) (gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)) #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 (Ubuntu 4.15.0-112.113-ge
aug 24 14:56:47 ********** kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic root=UUID=9d9ee766-7e97-44c0-acad-3482fdf034e9 ro quiet splash vt.handoff=1
aug 24 14:56:47 ********** kernel: KERNEL supported cpus:
aug 24 14:56:47 ********** kernel: Intel GenuineIntel
aug 24 14:56:47 ********** kernel: AMD AuthenticAMD
aug 24 14:56:47 ********** kernel: Centaur CentaurHauls
aug 24 14:56:47 ********** kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
aug 24 14:56:47 ********** kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
aug 24 14:56:47 ********** kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
aug 24 14:56:47 ********** kernel: x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
aug 24 14:56:47 ********** kernel: x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
aug 24 14:56:47 ********** kernel: x86/fpu: xstate_offset[2]: 576, xstate_size...

Changed in gnome-shell (Ubuntu):
status: Incomplete → New
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.