[CLOSED] Screen turns back on after screensavor activates

[SunriseYawning]

I'm not new to Linux, but new to Linux Mint. I have been running Ubuntu for almost 12 years now and decided to give Linux Mint a try after a recent hard drive failure.

So far, it's very slick and very happy with the change. However, there is a small little annoyance I'm hoping to get some help on. When I lock the screen, the monitors do not switch off.

After finding this post and this post, it looks like screensaver doesn't activate dpms settings.

Even after binding Super + L to

Code: Select all

bash -c "cinnamon-screensaver-command -l; xset dpms force off;"

, after a few minutes, the screen turns back on.

I've checked my power settings and my screensaver settings and don't see anything obvious that I've missed. Is there a way to keep the screen off until interaction from the user?

Thanks!

[SMG]

When I lock the screen, the monitors do not switch off.

Welcome to the forum, SunriseYawning.

That can often be a problem related to the graphics drivers. Please open the System Reports app and click the System Information tab on the left. Your computer's information should come up in the right pane. Then click the Copy button in the lower right and paste the results into a reply window here so we can see how Linux Mint views your hardware.

[SunriseYawning]

Thanks for replying SMG! Here is the output from System Reports:

Code: Select all

System:
  Kernel: 5.15.0-97-generic x86_64 bits: 64 compiler: gcc v: 11.4.0 Desktop: Cinnamon 6.0.4
    tk: GTK 3.24.33 wm: muffin vt: 7 dm: LightDM 1.30.0 Distro: Linux Mint 21.3 Virginia
    base: Ubuntu 22.04 jammy
Machine:
  Type: Desktop System: Micro-Star product: US Desktop Aegis RS v: 2.0
    serial: <superuser required>
  Mobo: Micro-Star model: PRO B760-VC WIFI (MS-7D98) v: 2.0 serial: <superuser required>
    UEFI: American Megatrends LLC. v: B.D3 date: 03/24/2023
Battery:
  Device-1: hidpp_battery_0 model: Logitech M720 Triathlon Multi-Device Mouse serial: <filter>
    charge: 100% (should be ignored) rechargeable: yes status: Discharging
CPU:
  Info: 16-core (8-mt/8-st) model: 13th Gen Intel Core i7-13700F bits: 64 type: MST AMCP
    smt: enabled arch: N/A rev: 1 cache: L1: 1.4 MiB L2: 24 MiB L3: 30 MiB
  Speed (MHz): avg: 4642 high: 5179 min/max: 800/5100:5200:4100 cores: 1: 5100 2: 5101 3: 5092
    4: 5100 5: 5100 6: 5100 7: 5100 8: 5100 9: 5179 10: 5175 11: 5155 12: 5100 13: 5100 14: 5100
    15: 5108 16: 5100 17: 3692 18: 3716 19: 3702 20: 3701 21: 3689 22: 3694 23: 3703 24: 3705
    bogomips: 101376
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: NVIDIA vendor: Micro-Star MSI driver: nvidia v: 535.161.07 pcie: speed: 2.5 GT/s
    lanes: 8 ports: active: none off: DP-3,HDMI-A-1 empty: DP-1,DP-2 bus-ID: 01:00.0
    chip-ID: 10de:2805 class-ID: 0300
  Device-2: Logitech BRIO Ultra HD Webcam type: USB driver: snd-usb-audio,uvcvideo
    bus-ID: 1-5.1.3:23 chip-ID: 046d:085e class-ID: 0102 serial: <filter>
  Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: nvidia
    unloaded: fbdev,modesetting,nouveau,vesa gpu: nvidia display-ID: :0 screens: 1
  Screen-1: 0 s-res: 3840x1080 s-dpi: 96 s-size: 1016x286mm (40.0x11.3") s-diag: 1055mm (41.6")
  Monitor-1: DP-4 pos: right res: 1920x1080 hz: 60 dpi: 93 size: 527x296mm (20.7x11.7")
    diag: 604mm (23.8")
  Monitor-2: HDMI-0 pos: primary,left res: 1920x1080 hz: 60 dpi: 93 size: 527x296mm (20.7x11.7")
    diag: 604mm (23.8")
  OpenGL: renderer: NVIDIA GeForce RTX 4060 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 535.161.07
    direct render: Yes
Audio:
  Device-1: Intel vendor: Micro-Star MSI driver: snd_hda_intel v: kernel bus-ID: 00:1f.3
    chip-ID: 8086:7a50 class-ID: 0403
  Device-2: NVIDIA vendor: Micro-Star MSI driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s
    lanes: 8 bus-ID: 01:00.1 chip-ID: 10de:22bd class-ID: 0403
  Device-3: Logitech BRIO Ultra HD Webcam type: USB driver: snd-usb-audio,uvcvideo
    bus-ID: 1-5.1.3:23 chip-ID: 046d:085e class-ID: 0102 serial: <filter>
  Sound Server-1: ALSA v: k5.15.0-97-generic running: yes
  Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
  Device-1: Intel driver: iwlwifi v: kernel port: N/A bus-ID: 00:14.3 chip-ID: 8086:7a70
    class-ID: 0280
  IF: wlo1 state: down mac: <filter>
  Device-2: Realtek RTL8125 2.5GbE vendor: Micro-Star MSI driver: r8169 v: kernel pcie:
    speed: 5 GT/s lanes: 1 port: 3000 bus-ID: 04:00.0 chip-ID: 10ec:8125 class-ID: 0200
  IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IF-ID-1: docker0 state: down mac: <filter>
Bluetooth:
  Device-1: Intel type: USB driver: btusb v: 0.8 bus-ID: 1-14:8 chip-ID: 8087:0033 class-ID: e001
  Report: hciconfig ID: hci0 rfk-id: 0 state: up address: <filter>
RAID:
  Device-1: bpool type: zfs status: DEGRADED level: mirror-0 raw: size: 1.88 GiB free: 1.44 GiB
    allocated: 447 MiB zfs-fs: size: 1.75 GiB free: 1.31 GiB
  Components: Online: 1: 9143651052787727312 2: nvme1n1p3
  Device-2: rpool type: zfs status: ONLINE level: mirror-0 raw: size: 920 GiB free: 908 GiB
    allocated: 11.8 GiB zfs-fs: size: 891.5 GiB free: 879.69 GiB
  Components: Online: 1: nvme0n1p4 2: nvme1n1p4
  Device-3: viper type: zfs status: ONLINE level: linear raw: size: 1.81 TiB free: 1.79 TiB
    allocated: 20.3 GiB zfs-fs: size: 1.76 TiB free: 1.74 TiB
  Components: Online: 1:
Drives:
  Local Storage: total: raw: 7.3 TiB usable: 9.93 TiB used: 29.56 GiB (0.3%)
  ID-1: /dev/nvme0n1 vendor: MSI model: M450 1TB size: 931.51 GiB speed: 63.2 Gb/s lanes: 4
    type: SSD serial: <filter> rev: EJFMC0.0 temp: 37.9 C scheme: GPT
  ID-2: /dev/nvme1n1 vendor: Toshiba model: N/A size: 953.87 GiB speed: 31.6 Gb/s lanes: 4
    type: SSD serial: <filter> rev: AAHA4102 temp: 35.9 C scheme: GPT
  ID-3: /dev/sda vendor: Western Digital model: WD20EZBX-00AYRA0 size: 1.82 TiB speed: 6.0 Gb/s
    type: HDD rpm: 7200 serial: <filter> rev: 1A01 scheme: GPT
  ID-4: /dev/sdb vendor: Western Digital model: WD40EZAX-00C8UB0 size: 3.64 TiB speed: 6.0 Gb/s
    type: HDD rpm: 5400 serial: <filter> rev: 1A01 scheme: GPT
Partition:
  ID-1: / size: 886.91 GiB used: 7.22 GiB (0.8%) fs: zfs logical: rpool/ROOT/ubuntu_ze334f
  ID-2: /boot size: 1.74 GiB used: 439.9 MiB (24.6%) fs: zfs logical: bpool/BOOT/ubuntu_ze334f
  ID-3: /boot/efi size: 511 MiB used: 14.2 MiB (2.8%) fs: vfat dev: /dev/nvme0n1p1
  ID-4: /var/log size: 879.69 GiB used: 7.4 MiB (0.0%) fs: zfs
    logical: rpool/ROOT/ubuntu_ze334f/var/log
Swap:
  ID-1: swap-1 type: partition size: 2 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/nvme0n1p2
USB:
  Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 16 rev: 2.0 speed: 480 Mb/s
    chip-ID: 1d6b:0002 class-ID: 0900
  Hub-2: 1-5:2 info: Genesys Logic Hub ports: 4 rev: 2.0 speed: 480 Mb/s power: 100mA
    chip-ID: 05e3:0608 class-ID: 0900
  Hub-3: 1-5.1:20 info: Realtek RTS5411 Hub ports: 4 rev: 2.1 speed: 480 Mb/s chip-ID: 0bda:5411
    class-ID: 0900
  Hub-4: 1-5.1.1:28 info: VIA Labs Hub ports: 4 rev: 2.1 speed: 480 Mb/s chip-ID: 2109:2811
    class-ID: 0900
  Device-1: 1-5.1.1.2:29 info: SHARKOON GmbH Keyboard type: Keyboard,HID driver: semitek,usbhid
    interfaces: 3 rev: 1.1 speed: 12 Mb/s power: 100mA chip-ID: 1ea7:0907 class-ID: 0300
    serial: <filter>
  Hub-5: 1-5.1.2:30 info: VIA Labs Hub ports: 4 rev: 2.1 speed: 480 Mb/s chip-ID: 2109:2811
    class-ID: 0900
  Device-1: 1-5.1.2.2:31 info: Yubicom Yubikey 4/5 OTP+U2F+CCID type: Keyboard,HID,Smart Card
    driver: hid-generic,usbhid interfaces: 3 rev: 2.0 speed: 12 Mb/s power: 30mA chip-ID: 1050:0407
    class-ID: 0b00
  Device-2: 1-5.1.3:23 info: Logitech BRIO Ultra HD Webcam type: Video,Audio
    driver: snd-usb-audio,uvcvideo interfaces: 5 rev: 2.1 speed: 480 Mb/s power: 500mA
    chip-ID: 046d:085e class-ID: 0102 serial: <filter>
  Hub-6: 1-5.1.4:26 info: Realtek RTS5411 Hub ports: 4 rev: 2.1 speed: 480 Mb/s
    chip-ID: 0bda:5411 class-ID: 0900
  Device-1: 1-5.2:6 info: Logitech Unifying Receiver type: Keyboard,Mouse,HID
    driver: logitech-djreceiver,usbhid interfaces: 3 rev: 2.0 speed: 12 Mb/s power: 98mA
    chip-ID: 046d:c52b class-ID: 0300
  Hub-7: 1-6:3 info: Genesys Logic Hub ports: 4 rev: 2.0 speed: 480 Mb/s power: 100mA
    chip-ID: 05e3:0608 class-ID: 0900
  Device-1: 1-11:5 info: Micro Star MYSTIC LIGHT type: HID driver: hid-generic,usbhid
    interfaces: 1 rev: 1.1 speed: 12 Mb/s power: 500mA chip-ID: 1462:7d98 class-ID: 0300
    serial: <filter>
  Device-2: 1-14:8 info: Intel type: Bluetooth driver: btusb interfaces: 2 rev: 2.0
    speed: 12 Mb/s power: 100mA chip-ID: 8087:0033 class-ID: e001
  Hub-8: 2-0:1 info: Super-speed hub ports: 10 rev: 3.1 speed: 20 Gb/s chip-ID: 1d6b:0003
    class-ID: 0900
Sensors:
  System Temperatures: cpu: 27.8 C mobo: N/A gpu: nvidia temp: 35 C
  Fan Speeds (RPM): N/A gpu: nvidia fan: 0%
Repos:
  Packages: 2310 apt: 2304 flatpak: 6
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/docker.list
    1: deb [arch=amd64 signed-by=/usr/share/keyrings/docker.gpg] https: //download.docker.com/linux/ubuntu jammy stable
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
    1: deb https: //mirrors.advancedhosters.com/linuxmint/packages virginia main upstream import backport
    2: deb http: //mirrors.advancedhosters.com/ubuntu jammy main restricted universe multiverse
    3: deb http: //mirrors.advancedhosters.com/ubuntu jammy-updates main restricted universe multiverse
    4: deb http: //mirrors.advancedhosters.com/ubuntu jammy-backports main restricted universe multiverse
    5: deb http: //security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse
  Active apt repos in: /etc/apt/sources.list.d/virtualbox.list
    1: deb [arch=amd64 signed-by=/etc/apt/trusted.gpg.d/vbox.gpg] http: //download.virtualbox.org/virtualbox/debian jammy contrib
  Active apt repos in: /etc/apt/sources.list.d/vscode.list
    1: deb [arch=amd64,arm64,armhf] http: //packages.microsoft.com/repos/code stable main
Info:
  Processes: 734 Uptime: 2d 15h 20m wakeups: 26 Memory: 31.17 GiB used: 13.85 GiB (44.4%)
  Init: systemd v: 249 runlevel: 5 Compilers: gcc: 11.4.0 alt: 11/12
  Client: Unknown python3.10 client inxi: 3.3.13

I found this forum post that seemed related: I'm using DisplayPort and HDMI for two screens. But the problem occurs even when I use one display.

[SMG]

Thanks for replying SMG! Here is the output from System Reports:

13th-gen Intel CPU needs to be using a 6 series kernel. Please upgrade using Update Manager.

Instructions for upgrading to the 6.5 kernel:

• Open Update Manager.
• Select View > Linux Kernels and click Continue.
• Make sure 6.5 is selected on the left panel and then click the top-most option on the right panel. An "Install" button will appear.
• Install the kernel and then reboot for it to become active.

I also suggest checking to see if this is the most recent BIOS/UEFI for your computer. Newer computers often get more updates as issues are found and fixed.

Machine:
Type: Desktop System: Micro-Star product: US Desktop Aegis RS v: 2.0
serial: <superuser required>
Mobo: Micro-Star model: PRO B760-VC WIFI (MS-7D98) v: 2.0 serial: <superuser required>
UEFI: American Megatrends LLC. v: B.D3 date: 03/24/2023

[SunriseYawning]

I updated to kernel 6.5 but had the same issues. I checked my mobo's website and saw a date discrepancy between the latest version and the version I had, but the version number was the same. I decided to update anyway, but then I could not boot.

I dropped into the grub menu and found that trying to do an ls of the main hard drive said something to the effect of "Secured Boot preventing the listing of this file".

I realized that doing the mobo firmware "upgrade" may have deleted the keys. I was able to reboot to an older kernel and deleted the new kernel with the hope of reinstalling it along with the EFI key. However, now when I reboot, I get an error:

Code: Select all

error: file `/BOOT/ubuntu_ze334f@/vmlinuz5.15.0-91-generic' not found.
error: you need to load the kernel first

This was the kernel that was working before. I tried disabling Secure Boot and still not able to boot. I'll admit I'm a bit out of my element here. Is there any way to install EFI keys from a Live USB?

[SMG]

I updated to kernel 6.5 but had the same issues. I checked my mobo's website and saw a date discrepancy between the latest version and the version I had, but the version number was the same. I decided to update anyway, but then I could not boot.

Sometimes updating the BIOS/UEFI reverts the settings to their defaults. Do you recall if you had changed any of the settings in the past?

I dropped into the grub menu and found that trying to do an ls of the main hard drive said something to the effect of "Secured Boot preventing the listing of this file".

That message is not ringing a bell for me so I'm not sure what message you saw.

I realized that doing the mobo firmware "upgrade" may have deleted the keys.

It might have changed settings, but I have never heard of a BIOS/UEFI doing anything with keys.

I was able to reboot to an older kernel and deleted the new kernel with the hope of reinstalling it along with the EFI key.

The kernels with Linux Mint are already signed and do not need you to install keys.

However, now when I reboot, I get an error:

Code: Select all

error: file `/BOOT/ubuntu_ze334f@/vmlinuz5.15.0-91-generic' not found.
error: you need to load the kernel first

This was the kernel that was working before. I tried disabling Secure Boot and still not able to boot. I'll admit I'm a bit out of my element here. Is there any way to install EFI keys from a Live USB?

See if this helps grub error: you need to load kernel first.

[SunriseYawning]

While I was searching, I came across this article. When I was on Ubuntu 20, there was a command to create Machine Owner Keys and load them into the BIOS. I couldn't remember what it was but the article showed that the live USB includes "Boot Repair" which should fix this for you.

I just ran Boot Repair off of the Linux Mint USB and I got the MOK prompt to enter my password. Upon reboot, I got the MOK menu! Key was installed successfully but back at the "Secure Boot" problem. The full text of the error:

Code: Select all

grub> ls (hd0)
error: Secure Boot forbids loading module from (hd3,gpt1)/grub/x86_64-efi/ufs2.mod.

I'm going to attempt the solution you linked tomorrow. It's getting late here. I'll report back once I do.

Thank you again for taking the time to help. It's very much appreciated.

[SunriseYawning]

Sorry I realized I didn't answer your questions.

Sometimes updating the BIOS/UEFI reverts the settings to their defaults. Do you recall if you had changed any of the settings in the past?

Outside of boot order, no.

The kernels with Linux Mint are already signed and do not need you to install keys.

When I installed Linux Mint, I enabled third-party software. This installed MOK keys in my bios.

See if this helps grub error: you need to load kernel first.

It doesn't seem to apply in my case. It might be a mixture of running zfs and signatures but I can't get grub to load the zfs drivers to load bpool to get the kernel.

[SMG]

See if this helps grub error: you need to load kernel first.

It doesn't seem to apply in my case. It might be a mixture of running zfs and signatures but I can't get grub to load the zfs drivers to load bpool to get the kernel.

I didn't catch that you were running zfs when I went through your inxi.

Code: Select all

  ID-1: / size: 886.91 GiB used: 7.22 GiB (0.8%) fs: zfs logical: rpool/ROOT/ubuntu_ze334f
  ID-2: /boot size: 1.74 GiB used: 439.9 MiB (24.6%) fs: zfs logical: bpool/BOOT/ubuntu_ze334f
  ID-3: /boot/efi size: 511 MiB used: 14.2 MiB (2.8%) fs: vfat dev: /dev/nvme0n1p1
  ID-4: /var/log size: 879.69 GiB used: 7.4 MiB (0.0%) fs: zfs
    logical: rpool/ROOT/ubuntu_ze334f/var/log

I do not know the differences between using zfs and ext4 with regards to secure boot, but apparently additional work is needed.

[SunriseYawning]

I do not know the differences between using zfs and ext4 with regards to secure boot, but apparently additional work is needed.

Thanks again SMG for your help. I've decided to reinstall. While I'm reinstalling, I'm going to confirm that a Mobo firmware update will kill the keys, which will be good to know down the line. I really hope that isn't the case since this would mean that I won't be able to install updates, at least not without a full re-install, which would be very very annoying.

That said, it still doesn't resolve my monitor issues! I'm going to try installing the open-source video drivers to see if that fixes things.

[SMG]

That said, it still doesn't resolve my monitor issues! I'm going to try installing the open-source video drivers to see if that fixes things.

We never really got to try too much for your original problem. It is unusual for Nvidia drivers to have the problem you described. We would want to check logs when your system is back up running again.

[sebastjava]

When I lock the screen, the monitors do not switch off.

The screen lock, i.e. the screensaver does not turn off the screen. At least not on LM Cinnamon 21.3. The screensaver only makes a dimmed desktop background picture, and displays a bright, white digital clock on top. That's fine with me. That's normal. It is the Power Management which is responsible for turning off the screen. When you set it to do so. And, of course, as soon as your cat touches the mouse or the keyboard, the screen is back on. That's normal. Not even a mouse click, just move the mouse and the screen is back on. That's normal.

I set my things this way:

Screensaver > Delay before starting: 15 minutes
Power Management > Turn off the screen when inactive for 30 minutes
Power Management > Suspend when inactive for 1 hour

Else, if you really want to make things more complicated and mess up with your system, then follow my nice little tutorial here: viewtopic.php?p=2437772#p2437772

This should really turn off the screen, seriously, without going back on when you just accidentally tip the mouse. But BEWARE..! I don't think that's a good idea..! Your computer would still be working, your desktop would not be locked, your screen would be totally off and you could make a bad mistake like deleting of moving files while you can't see what is going on..! Of course, it just takes a little tricky command line to turn your screen back on, but how the hell are you supposed to do that when you can't see anything!?


Please excuse me for any dumb comments or conclusions. I didn't have the time to read all previous posts and think much... Just putting a quick easy reply here...

[SunriseYawning]

I set my things this way:

Screensaver > Delay before starting: 15 minutes
Power Management > Turn off the screen when inactive for 30 minutes
Power Management > Suspend when inactive for 1 hour

I had the screensaver and power management both set to 15 minutes. That said, even when left overnight, the monitor stayed on.

[SunriseYawning]

We never really got to try too much for your original problem. It is unusual for Nvidia drivers to have the problem you described. We would want to check logs when your system is back up running again.

After I've banged my head against the wall a few times, I finally got Linux Mint installed again.

Open-source drivers still produce the same issue.

And I was not able to reproduce the issue I had with updating the BIOS. I flashed it twice just to be sure and I was able to boot. So, not sure what happened.

There was a bug during the install, however. I set up a mirrored ZFS pool, with the hope that I would be able to restore rpool after bpool was restored. However, the install failed to complete and stopped at Step Two: creating the partitions. It definitely didn't like the fact that there was second drive.

I formatted both drives and that seems to have solved the problem. But now unfortunately, I have to reinstall software again.

[SMG]

Open-source drivers still produce the same issue.

What are the make and model of the monitors?

[sebastjava]

Code: Select all

bash -c "cinnamon-screensaver-command -l; xset dpms force off;"

I would add a 3 seconds sleep before:

Code: Select all

sleep 3; bash -c "cinnamon-screensaver-command -l; xset dpms force off;"

I remember playing with this dpms a long time ago. At first, it didn't work well without this sleep 3, because ANY kind of activity, including a little accidental mouse or touch-pad move, would wake up the screen again... So, you copy/paste this command, press enter, and... don't touch anything!

This reminds me, once again, of a simple fact: if there is a cat around, look no further. He/she is the culprit.

[SunriseYawning]

What are the make and model of the monitors?

ViewSonic VG2453

I had these monitors on my old install of Ubuntu 22 and the screensaver/power settings worked completely as expected.

This reminds me, once again, of a simple fact: if there is a cat around, look no further. He/she is the culprit.

Don't have a cat. Even hours of no activity, the screen will remain on. If needed I can test this by turning off my mouse and unplugging the keyboard.

[SMG]

I had these monitors on my old install of Ubuntu 22 and the screensaver/power settings worked completely as expected.

Have you tried the Nvidia 525 driver? (Is it available for you in Driver Manager?)

A number of people with Nvidia GPUs and HDMI connections started running into issues with the Nvidia-530 and newer drivers.

[SunriseYawning]

Have you tried the Nvidia 525 driver? (Is it available for you in Driver Manager?)

A number of people with Nvidia GPUs and HDMI connections started running into issues with the Nvidia-530 and newer drivers.

Installed 525 drivers and the monitors are still not staying off.

[sebastjava]

Even after binding Super + L to:

Code: Select all

bash -c "cinnamon-screensaver-command -l; xset dpms force off;"

...after a few minutes, the screen turns back on.

I would simply like to make things clear, if you don't mind. Worst, I don't have answers, I just have questions:

• The Power Manager sends some DPMS command, right? After counting 5 or 15 minutes or more, it sends a xset dpms force off or "standby" or "suspend", I don't know what exactly...
• You also tried with that CLI and it works, at first, but the screen wakes up after a few minutes. Did I understand your OP correctly?
• Does it also works with the GUI, when you set the power manager to turn off the screen when inactive for 5 minutes? Yes, the screen is back on after a few minutes, but did it work, at least for a few seconds?