No login screen on wake from sleep after recent updates

Issues & Assistance GNOME
21

Thanks @petsam for you kind pointers, below is the output of those statements. I don't know if the shadow service should always be active and running? my guess it should be but not sure.

 5:35PM  ➤ systemctl status shadow                                                                                                                                            git:resident
○ shadow.service - Verify integrity of password and group files
     Loaded: loaded (/usr/lib/systemd/system/shadow.service; static)
     Active: inactive (dead)
TriggeredBy: ● shadow.timer
 5:45PM  ➤ sudo pacman -S shadow                                                                                                                                              git:resident
[sudo] password for daya:            
warning: shadow-4.11.1-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (1) shadow-4.11.1-1

Total Installed Size:  3.60 MiB
Net Upgrade Size:      0.00 MiB

:: Proceed with installation? [Y/n] y
:: Retrieving packages...
 shadow-4.11.1-1-x86_64 is up to date
(1/1) checking keys in keyring                                                                                                 [-----------------------------------------------------------------------------] 100%
(1/1) checking package integrity                                                                                               [-----------------------------------------------------------------------------] 100%
(1/1) loading package files                                                                                                    [-----------------------------------------------------------------------------] 100%
(1/1) checking for file conflicts                                                                                              [-----------------------------------------------------------------------------] 100%
(1/1) checking available disk space                                                                                            [-----------------------------------------------------------------------------] 100%
:: Running pre-transaction hooks...
(1/1) Creating Timeshift snapshot before upgrade...
Using system disk as snapshot device for creating snapshots in BTRFS mode

/dev/dm-0 is mounted at: /run/timeshift/backup, options: rw,relatime,compress=zstd:3,ssd,space_cache,subvolid=5,subvol=/

Creating new backup...(BTRFS)
Saving to device: /dev/dm-0, mounted at path: /run/timeshift/backup
Created directory: /run/timeshift/backup/timeshift-btrfs/snapshots/2022-05-05_17-46-05
Created subvolume snapshot: /run/timeshift/backup/timeshift-btrfs/snapshots/2022-05-05_17-46-05/@
Created control file: /run/timeshift/backup/timeshift-btrfs/snapshots/2022-05-05_17-46-05/info.json
BTRFS Snapshot saved successfully (0s)
Tagged snapshot '2022-05-05_17-46-05': ondemand
------------------------------------------------------------------------------
Maximum backups exceeded for backup level 'daily'

/dev/dm-0 is mounted at: /run/timeshift/backup, options: rw,relatime,compress=zstd:3,ssd,space_cache,subvolid=5,subvol=/

------------------------------------------------------------------------------
Removing snapshot: 2022-05-04_15-20-48
Deleting subvolume: @ (Id:2493)
Deleted subvolume: @ (Id:2493)

Destroying qgroup: 0/2493
Destroyed qgroup: 0/2493

Deleted directory: /run/timeshift/backup/timeshift-btrfs/snapshots/2022-05-04_15-20-48
Removed snapshot: 2022-05-04_15-20-48
------------------------------------------------------------------------------
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/garuda/theme.txt
Found linux image: /boot/vmlinuz-linux
Found initrd image: /boot/amd-ucode.img /boot/initramfs-linux.img
Found fallback initrd image(s) in /boot:  amd-ucode.img initramfs-linux-fallback.img
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Found Garuda Linux on /dev/mapper/luks-ec233d36-2eb5-4b54-a5f8-8db36ac50d51
Found Ubuntu 16.04.6 LTS on /dev/mapper/luks-ec233d36-2eb5-4b54-a5f8-8db36ac50d51
Found Debian GNU/Linux 10 (buster) on /dev/mapper/luks-ec233d36-2eb5-4b54-a5f8-8db36ac50d51
Found Debian GNU/Linux 9 (stretch) on /dev/mapper/luks-ec233d36-2eb5-4b54-a5f8-8db36ac50d51
Adding boot menu entry for UEFI Firmware Settings ...
Detecting snapshots ...
Found snapshot: 2022-05-05 17:46:05 | timeshift-btrfs/snapshots/2022-05-05_17-46-05/@ | ondemand | {timeshift-autosnap} {created before upgrade} |
Found snapshot: 2022-05-05 17:19:27 | timeshift-btrfs/snapshots/2022-05-05_17-19-27/@ | ondemand | {timeshift-autosnap} {created before upgrade} |
Found snapshot: 2022-05-05 17:18:30 | timeshift-btrfs/snapshots/2022-05-05_17-18-30/@ | ondemand | {timeshift-autosnap} {created before upgrade} |
Found snapshot: 2022-05-05 14:00:01 | timeshift-btrfs/snapshots/2022-05-05_14-00-01/@ | daily    | N/A                                           |
Found snapshot: 2022-05-05 12:42:28 | timeshift-btrfs/snapshots/2022-05-05_12-42-27/@ | ondemand | {timeshift-autosnap} {created before upgrade} |
Found snapshot: 2022-05-05 11:29:06 | timeshift-btrfs/snapshots/2022-05-05_11-29-06/@ | ondemand | {timeshift-autosnap} {created before upgrade} |
Found snapshot: 2022-05-04 13:00:01 | timeshift-btrfs/snapshots/2022-05-04_13-00-01/@ | daily    | N/A                                           |
Found snapshot: 2022-05-03 13:00:01 | timeshift-btrfs/snapshots/2022-05-03_13-00-01/@ | daily    | N/A                                           |
Found 8 snapshot(s)
Unmount /tmp/grub-btrfs.azCqXYaxC3 .. Success
Found memtest86+ image: /boot/memtest86+/memtest.bin
done
:: Processing package changes...
(1/1) reinstalling shadow                                                                                                      [-----------------------------------------------------------------------------] 100%
:: Running post-transaction hooks...
(1/8) Reloading system manager configuration...
(2/8) Arming ConditionNeedsUpdate...
(3/8) Refreshing PackageKit...
(4/8) Foreign/AUR package notification
audio-recorder 3.3.4-1
awslogs 0.14.0-3
brother-hl-l2370dw 4.0.0-0
brother-hl2270dw 2.1.0_2-5
calls 42.0-1
condution-bin 1.1.1-0
cronopete 4.14-1
espeak 1:1.48.04-4
figlet-fonts 1.0-3
figlet-fonts-extra 1.0-1
gtd-free 0.6beta-3
java-service-wrapper 3.5.49-1
javafx-scenebuilder 18.0.0-1
jumpapp 1.2-1
libgnomecanvas 2.30.3-4
magnifiqus 0.2.1-1
memtest86-efi 1:9.4build1000-4
nautilus-admin 1.1.9-1
nemo-compare 5.2.0-1
nemo-dropbox 5.2.0-1
nodejs-localtunnel 2.0.2-1
pcmemtest 1.5-1
pdfstudio-bin 2021.1.4-1
pika-backup 0.4.0.beta.5-1
polar-bookshelf-bin 2.0.103-1
silver-searcher-git 2.2.0.60.ga61f178.r2057.a61f178-1
sofia-sip 1.13.6-1
superproductivity-bin 7.11.5-1
tunnelto 0.1.18-1
vgrive 1.6.1-6
vscodium-bin 1.66.2-1
vscodium-bin-marketplace 1.56.0-7
xcursor-sweet 20200612-1
xzoom 0.3-6
zoom-firefox 0.0.3-0
zoom-firejail 0.1.6-1
zoomx 0.0.1-1
(5/8) Orphaned package notification...
ant 1.10.12-1
appstream-qt 0.15.3-1
celt 0.11.3-4
cheese 41.1-2
cppunit 1.15.1-2
elfutils 0.187-1
extra-cmake-modules 5.93.0-1
fuse-overlayfs 1.8.2-1
gendesk 1.0.9-3
gnome-bluetooth 3.34.5-3
go 2:1.18.1-1
gobject-introspection 1.72.0-1
imake 1.0.8-3
intltool 0.51.0-6
itstool 1:2.0.7-1
java-service-wrapper 3.5.49-1
kactivities-stats 5.93.0-1
kvantum-theme-sweet-git r256.866a934-1
libcroco 0.6.13-2
libdazzle 3.44.0-1
libgnomecanvas 2.30.3-4
libgweather 40.0+r87+g80e5a652-2
libkleo 22.04.0-1
libmms 0.6.4-3
libofa 0.9.3-9
libpipewire02 0.2.7-2
libvterm 0.2-1
lua52 5.2.4-5
memavaild 0.6-1
meson 0.62.1-1
neard 0.18-1
networkmanager-qt 5.93.0-1
nm-connection-editor 1.26.0-1
nohang 0.2.0-1
packagekit-qt5 1.0.2-1
pahole 1.23-1
plasma-framework 5.93.0-4
prelockd 0.9-1
python-peewee 3.14.10-1
python-plumbum 1.7.2-1
python-pycryptodome 3.14.1-1
python-pypdf2 1.26.0-2
python-secretstorage 3.3.1-3
python-sh 1.14.2-3
quazip-qt5 1.3-1
rebuild-detector 4.4.1-2
rust 1:1.60.0-1
samurai 1.2-2
sccache 0.2.15-2
scim 1.4.18-3
sweet-gtk-theme-dark 3.0-1
tepl 6.0.1-1
uresourced 0.5.2-1
vala 0.56.1-1
wayland-protocols 1.25-1
xcursor-sweet 20200612-1
xournalpp 1.1.1-1
yubikey-personalization 1.20.0-3
zita-alsa-pcmi 0.4.0-1
zita-resampler 1.8.0-1
(6/8) Checking for .pacnew and .pacsave files...
.pac* files found:
/etc/nsswitch.conf.pacnew
/etc/locale.gen.pacnew
/etc/default/grub.pacnew
/etc/default/grub-btrfs/config.pacnew
/etc/pacman.d/mirrorlist.pacnew
/etc/paru.conf.pacnew
/etc/sudoers.pacnew
/etc/systemd/system.conf.pacnew
Please check and merge
(7/8) Checking which packages need to be rebuilt
unknown command: gem. Perhaps you have to reshim?
foreign	audio-recorder
foreign	awslogs
foreign	brother-hl2270dw
foreign	brother-hl-l2370dw
foreign	calls
foreign	condution-bin
foreign	cronopete
foreign	espeak
foreign	figlet-fonts
foreign	figlet-fonts-extra
foreign	gtd-free
foreign	javafx-scenebuilder
foreign	java-service-wrapper
foreign	jumpapp
foreign	libgnomecanvas
foreign	magnifiqus
foreign	memtest86-efi
foreign	nautilus-admin
foreign	nemo-compare
foreign	nemo-dropbox
foreign	nodejs-localtunnel
foreign	pcmemtest
foreign	pdfstudio-bin
foreign	pika-backup
foreign	polar-bookshelf-bin
foreign	silver-searcher-git
foreign	sofia-sip
foreign	superproductivity-bin
foreign	tunnelto
foreign	vgrive
foreign	vscodium-bin
foreign	vscodium-bin-marketplace
foreign	xcursor-sweet
foreign	xzoom
foreign	zoom-firefox
foreign	zoom-firejail
foreign	zoomx
(8/8) Syncing all file systems...
 5:46PM  ➤
22

@tbg the mobo has not changed and this wake from sleep issue started just 2-3 days ago, before that everything was working fine since ~1 year. So I am not sure if I still need to search mobo specific kernel parameters

23

@petsman related to shadow.service following is the status output after reinstalling it

 6:13PM ~ ➤ sudo systemctl start shadow.service && sudo systemctl status shadow.service                                                                                                                           
○ shadow.service - Verify integrity of password and group files
     Loaded: loaded (/usr/lib/systemd/system/shadow.service; static)
     Active: inactive (dead) since Thu 2022-05-05 18:13:35 CDT; 6ms ago
TriggeredBy: ● shadow.timer
    Process: 711554 ExecStart=/bin/sh -c /usr/bin/pwck -r || r=1; /usr/bin/grpck -r && exit $r (code=exited, status=0/SUCCESS)
   Main PID: 711554 (code=exited, status=0/SUCCESS)
        CPU: 5ms

May 05 18:13:35 big-machine systemd[1]: Started Verify integrity of password and group files.
May 05 18:13:35 big-machine systemd[1]: shadow.service: Deactivated successfully.
1 Like
24

@tbg how do I know if and what compositor I am using ? from pacman logs grep I don’t see any compositor

 6:21PM ~ ➤ cat /var/log/pacman.log | ag -i compositor                                                                                                                                                            
[2021-11-04T16:00:08-0500] [ALPM] warning: directory permissions differ on /opt/zoom/QtWayland/Compositor/
 6:21PM ~ ➤
25

Sorry, you're on Gnome, I don't think the compositor can be shut down with Gnome.

1 Like
26

Apparently it cannot.

1 Like
27

I just stumbled upon the open source video driver which was already installed with Garuda

extra/xf86-video-nouveau 1.0.17-2 (90.8 KiB 222.9 KiB) [xorg-drivers] (Installed)

so my question is if I were to uninstall the nvidia driver completely (for troubleshooting this issue) then would the system automagically resue nouveau driver or will I have to handhold it ? If handholding is needed then what are the steps ?

28

Yes.
The nvidia driver blacklists nouveau in order to be loaded and take control of the card.
When nvidia related packages are removed (including the blacklisting file, which belongs to them), then nouveau will control nvidia card, whether nouveau package is installed, or not, since it is included in the linux kernels (modesetting).

4 Likes
29

@petsam thanks for your quick reply.

So I can plan things ahead, say if the GUI does not render for some reason, can I boot into plain text mode ?? and reinstall Nvidia if I have to in case nouveau doesn't work. If that's possible then how do I boot into text mode

30
  • Edit grub menu entry (press E while at grub menu).
  • Go to the line that starts with linux . Delete splash and quiet and add (number) 3 at the end of the line.
  • Press F10 to boot.
3 Likes
31

Update: I uninstalled Nvidia drivers but the suspend issue still is not resolved. I even tried shutting off WiFi (I have no RJ45 connection) and BlueTooth completely before attempting Sleep ... but machine never wakes up.

I don't have snapshots from 3-4 days ago to restore to since I have update the system one too many times since and only so many snapshots are stored and older ones are deleted.

Please help.

32

If using nvidia, there is a fair chance there is some helping kernel parameter, but noone can know for sure.

Read your Mobo user manual for anything about Sleep modes (S3, S2 or similar) and alter them, if any. It’s one possible solution to try.

Another thing is, after all this weird behavior and after your troubleshooting, it could be a HW issue. It happens several times that BIOS/firmware either reset, or clog. This is often solved clearing buffers, or updating firmware, or resetting BIOS.
You might want to try to remove power from your desktop for several minutes (hours?), or/and resetting BIOS battery.

Get whatever available info from the vendor’s support and manuals.

Good luck!

3 Likes
33

Latest update: I switched to Garuda Dragonize kde on X11 and even though I am not getting consistent boot to GUI I was able to partially wake from sleep. The reason I say partially is the keyboard and mouse didn't work only the monitor showed the desktop background. Pleaee note at this time auto login is disabled.

Could someone pleaee nudge to further alleviate this problem?

Thanks in advance for your help

34

Check Archwiki on DPMS / suspend troubleshooting and test few of the service files examples. With KDE, you usually restart kwin or plasma.
No one solution fits all issues.

2 Likes
35

latest update: Just for the heck of it and to rule out any hardware issues. I installed latest Garuda KDE edition on a separate disk and the sleep wake works perfectly. So obviously it was some update that caused the issue.

I guess this is the bane of using rolling releases, you just don't know when you will get burned badly.

36

This is not the only possibility, I guess.
Other changes might have happened on the system by any package, application, utility or manually by the admin to break this feature.
Not that it is not by an updated package, but I added for clarity.

If you really want to pinpoint the issue, you may install Garuda (on a new spare drive?) on the same computer, check that sleep is working OOTB, reboot and upgrade your system.
After next reboot, you should have your answer… :person_shrugging:

I still suggest trying Arcwiki for solutions.

2 Likes
37

That’s one reason why Snapshots are very very useful (as well as backups on another drive).
Please setup your snapshots management so next time this can be avoided and you can either test your changes within a snapshot prior to apply them on your main subvolumes or use a snapshot to rollback the changes.

Now the damage was done, but for next time…

3 Likes
38

Thanks for the wonderful tip. I knew snapshots were being created automatically on each update but I didn't know that they could experimented with like the way you describe.

Would you please share some documentation on that manual management of snapshot specifically the part of applying to subvolume before applying to main volume?

FYI I only have one ssd and separate backups of home folder not system folders.

39

Well I would go off topic if I start on Snapshots. lol However I believe you need a bit of guidance to avoid repeating a non-restore situation and I want to help.

I will respond to your question, but for any further information the answers will be found elsewhere in a few days or weeks.

That being said, you would have had less problems if you had enough snapshots to restore from, so it's a bit related.

It's not the 1st time I would like to refer someone to some sort of tutorial/explanation on snapshots and how to use them to prevent system breakage and rollback.
I will search the Forum and see if this exists already, if not I am very tempted to create one myself and use it for future references. Snapshots can save your system so they are important.

In the meantime, my suggestion is you at least increase the number of snapshots Snapper automatically takes. Hourly, Daily, Weekly, Monthly, use how you feel comfortable but make sure the number of PACMAN snapshots should be sufficient for your usage (default is 10 now, when activated). I would recommend to use 10 if you have disk space for it.
Then if something breaks, you restore a previous snapshot of root (@) and you are back on a clean system, giving you time to discuss here with people and search the web about your problem, rather than try to fix it in a hurry and make things worse.

As for applying the changes within a Snapshot before you apply on your main subvolumes, I have to understand better how Garuda uses Snapper by default, my test bench on a fresh Garuda install does not return good results at the moment (weird). This would be part of my potential tutorial if I can't find one. I don't use Snapper myself so I have to learn.

Again, plz increase your number of Snapshots, especially Pacman (assuming you have enough disk space to handle) and try to have at least 1 Snapshot taken per day, if you use your machine every day. This way when you need to restore you can chose any day and you don't need to think much about "what am I going to lose if I restore an old backup from 2 weeks ago?". :slight_smile:

Don't worry, I learned the hard way many times too! Snapshots and external SSD backups helped me learn a lot and also saved my life countless number of times (much less now cuz I better master my system after learning the hard way lol).

Now back on TOPIC, have you fixed your issue?
You installed on a 2nd SSD and it's fine. Do you consider this topic solved, then?

4 Likes
40
4 Likes