[CLOSED] Screen turns back on after screensavor activates

[SunriseYawning]

Please post the output from:

Code: Select all

xrandr --listactivemonitors

Code: Select all

$ xrandr --listactivemonitors
Monitors: 2
 0: +*HDMI-0 1920/527x1080/296+0+0  HDMI-0
 1: +DP-4 1920/527x1080/296+1920+0  DP-4

I'll leave the thread open until Monday. Thank you all for your assistance.

[sebastjava]

Preamble: Please don't feel offended when I explain basic safety procedures. I know you are an IT expert, but I need to make sure you don't get into trouble, and, most of all, there are all sorts of people reading here and some of them will try this too...

First of all, save and close all your open files.

In the worst case, you may need to force power-off, i.e. press the power button continuously for a few seconds. Doing a full restart would then reset everything back to normal. I experienced this before and my computer did not suffer.

Now, create those two keyboard shortcuts:

ScreenON

Code: Select all

bash -c "xrandr --output HDMI-0 --auto --output DP-4 --auto;"

NOTE: This will only work with your current installation: HDMI-0 and DP-4.

ScreenLOCK

Code: Select all

bash -c "cinnamon-screensaver-command -l; sleep 3; xrandr --output HDMI-0 --off --output DP-4 --off;"

NOTE: This will only work with your current installation: HDMI-0 and DP-4.

There is a 3 seconds delay between the screen lock and the screen off. Please leave this sleep 3 there, it might be really needed. Same thing for this bash -c and everything else here...

It works! And that's a bit confusing and scary... I was forgetting something... You can't use your keyboard shortcuts when the screen is locked, of course! So, here, you end up having to type your password while the screen is off! Well, it doesn't make a big difference. Usually, you get to see how many characters you typed, and you get a warning message when the cap locks is on. Now you must type your password while facing a blank screen! It is only when you successfully unlocked your screen that you can press your ScreenON keyboard shortcut!

Maybe we could build something smarter, later on. Something that would turn on your screen as soon as you unlock it, for example. But let's start with these 2 little tests here, please.

[SunriseYawning]

I will give this a try....after I figure out why Linux Mint isn't booting again. I think this is a ZFS issue. I'll post another thread...

I really hope I don't have to reinstall LM again...this will be the third install in as many weeks.

[SunriseYawning]

I had a chance to try the commands that @sebastjava recommended. The screen turns off for a few seconds and turns right back on.

I think this is actually related to power management.

When I set the screen timeout (in Power Management) to 5 minutes and the screensaver timeout to 15, Power Management turns off the screen and locks it as expected. However, after a few seconds, they turn back on.

It almost seems like the two might be in conflict, but that might be worth investigating.

[sebastjava]

(...) Power Management turns off the screen and locks it as expected. (...)

Ah, okay, I learned something. Both the power management and the screensaver can lock the screen. Tested and confirmed.

You tried my special CLI, I tried both your GUI settings and your special CLI. Whatever you do, you always get that same problem. On the opposite, I never had this problem. My screen never turns back on after a few seconds. Or minutes. It only turns back on when I touch the mouse or the keyboard, as expected.

And we are both on the same LM Cinnamon 21.3 ? The difference therefore lies in the hardware or the drivers. Again, have you tried unplugging your laptop from the monitors, having only your desktop, with LM Cinnamon 21.3, plugged onto the monitors? Just for a 5 minutes test... Apart from that, I have no idea...

My current settings are these:

Again, I never had any trouble with these. And I tested all your GUI settings and CLI, and never had any trouble here. Here is my system:

Code: Select all

System:
  Kernel: 5.15.0-100-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: HP product: HP EliteDesk 800 G2 SFF v: N/A serial: <superuser required>
    Chassis: type: 4 serial: <superuser required>
  Mobo: HP model: 8054 v: KBC Version 05.39 serial: <superuser required> UEFI: HP
    v: N01 Ver. 02.59 date: 09/13/2022
Battery:
  Device-1: hidpp_battery_0 model: Logitech Wireless Mouse serial: <filter>
    charge: 55% (should be ignored) rechargeable: yes status: Discharging
CPU:
  Info: quad core model: Intel Core i5-6500 bits: 64 type: MCP smt: <unsupported> arch: Skylake-S
    rev: 3 cache: L1: 256 KiB L2: 1024 KiB L3: 6 MiB
  Speed (MHz): avg: 2600 min/max: 800/3600 cores: 1: 2600 2: 2600 3: 2600 4: 2600
    bogomips: 25599
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel HD Graphics 530 vendor: Hewlett-Packard driver: i915 v: kernel ports:
    active: HDMI-A-2 empty: DP-1, DP-2, DP-3, HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:1912
    class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: modesetting unloaded: fbdev,vesa
    gpu: i915 display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2") s-diag: 582mm (22.9")
  Monitor-1: HDMI-2 mapped: HDMI-A-2 model: VZ249 serial: <filter> res: 1920x1080 hz: 60 dpi: 93
    size: 527x296mm (20.7x11.7") diag: 604mm (23.8") modes: max: 1920x1080 min: 720x400
  OpenGL: renderer: Mesa Intel HD Graphics 530 (SKL GT2) v: 4.6 Mesa 23.2.1-1ubuntu3.1~22.04.2
    direct render: Yes
Audio:
  Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: Hewlett-Packard
    driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:a170 class-ID: 0403
  Sound Server-1: ALSA v: k5.15.0-100-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 Ethernet I219-LM vendor: Hewlett-Packard driver: e1000e v: kernel port: N/A
    bus-ID: 00:1f.6 chip-ID: 8086:15b7 class-ID: 0200
  IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 1.15 TiB used: 77.88 GiB (6.6%)
  ID-1: /dev/sda vendor: Samsung model: SSD 840 EVO 250GB size: 232.89 GiB speed: 6.0 Gb/s
    type: SSD serial: <filter> rev: CB6Q scheme: MBR
  ID-2: /dev/sdb vendor: Western Digital model: WD5000AAKX-60U6AA0 size: 465.76 GiB
    speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter> rev: 1H18 scheme: GPT
  ID-3: /dev/sdc vendor: SanDisk model: SDSSDH3 512G size: 476.94 GiB speed: 6.0 Gb/s type: SSD
    serial: <filter> rev: 1000 scheme: GPT
Partition:
  ID-1: / size: 123.46 GiB used: 19.23 GiB (15.6%) fs: ext4 dev: /dev/sdc1
  ID-2: /boot/efi size: 3.99 GiB used: 6.1 MiB (0.1%) fs: vfat dev: /dev/sdc3
  ID-3: /home size: 250.92 GiB used: 23.62 GiB (9.4%) fs: ext4 dev: /dev/sdc2
Swap:
  ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile
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
  Device-1: 1-3:2 info: Logitech Unifying Receiver type: Mouse,HID
    driver: logitech-djreceiver,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s power: 98mA
    chip-ID: 046d:c52f class-ID: 0300
  Device-2: 1-6:3 info: Elan Micro ActiveJet K-2024 Multimedia Keyboard type: Keyboard,HID
    driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 1.5 Mb/s power: 100mA
    chip-ID: 04f3:0103 class-ID: 0300
  Hub-2: 2-0:1 info: Super-speed hub ports: 10 rev: 3.0 speed: 5 Gb/s chip-ID: 1d6b:0003
    class-ID: 0900
Sensors:
  System Temperatures: cpu: 30.0 C pch: 43.5 C mobo: N/A
  Fan Speeds (RPM): N/A
Repos:
  Packages: 2286 apt: 2265 flatpak: 21
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/google-chrome.list
    1: deb [arch=amd64] https: //dl.google.com/linux/chrome/deb/ stable main
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
    1: deb http: //packages.linuxmint.com virginia main upstream import backport
    2: deb http: //ubuntu.mirror.iweb.ca jammy main restricted universe multiverse
    3: deb http: //ubuntu.mirror.iweb.ca jammy-updates main restricted universe multiverse
    4: deb http: //ubuntu.mirror.iweb.ca jammy-backports main restricted universe multiverse
    5: deb http: //security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse
Info:
  Processes: 243 Uptime: 5d 24m wakeups: 45 Memory: 15.38 GiB used: 2.33 GiB (15.2%) Init: systemd
  v: 249 runlevel: 5 Compilers: gcc: 11.4.0 alt: 11/12 Client: Unknown python3.10 client
  inxi: 3.3.13

[SunriseYawning]

I appreciate you trying it out on your end. I am running Cinnamon 21.3.

I unplugged the other cables from the monitor so that only the connections to the LM remained and I observed the same behavior.

What is the software that runs power management? When I have some time next weekend, I'm going to pour into it to see if I can find the cause of the issue. I suspect that there is some sort of conflict that's causing it to "wake up".

[SunriseYawning]

FWIW, I ended up installing Ubuntu 22.04 and the screen still does not turn off properly. I'm thinking this is a video card/driver issue.

[sebastjava]

Good to know. Thanks for the follow up. I didn't want to look stupid, I was already dealing with a mess somewhere else in these forums, but, believe it or not, this is exactly what I was thinking.

FWIW, I ended up installing Ubuntu 22.04 and the screen still does not turn off properly. I'm thinking this is a video card/driver issue.

I haven't done any research, but AFAIK, you tried both your CLI DPMS and my CLI xrandr. Both of these were bypassing the GUI applications, to talk directly to your driver and graphics card. That's how I see it. So, it seems pointless to loose your time in trying to search for problems in the GUI. I'm thinking this is a video card/driver issue, me too.

Additionally, as already said, I have the same software as you, I mean, before you switch back Ubuntu, and I did the same things as you did, and I never saw this issue here. So, the difference must be with the driver or hardware...