problem with the setting 'turn off the screen when inactive for ... minutes'

[mikeymike]

OS: Mint 21 Cinnamon
Screen: Iiyama XU2292HS
Graphics: AMD R9 380X

When the setting (in the thread title) is enabled/triggered, the screen goes off for a moment then comes back on again.

What's really strange is that if I leave Mint at the login screen, after a while it manages to put the screen into standby just fine.

[Pjotr]

Please generate an overview of your system like this:

- Launch a terminal window (this is how to launch a terminal window);

- Make the terminal window full screen, to avoid chopped lines;

- Copy/paste this command into the terminal:

Code: Select all

inxi -Fxpmrz

(if you type: the letter F is a capital letter, and don't omit the space after inxi!)

Press Enter.

Copy/paste the output in your next message.

[exploder]

I have the exact same problem. Running these two commands as user in the terminal will put the display to sleep.

First run:

Code: Select all

xset +dpms

Then run:

Code: Select all

bash -c 'sleep 0.1 && xset dpms force off'

This was from a discussion about this issue on the Ubuntu Forum.

Edit: Here is a link to the discussion.

https://ubuntuforums.org/showthread.php?t=2483409

[exploder]

Back to square one. The display is still coming back on....

[mikeymike]

Code: Select all

inxi -Fxpmrz

Code: Select all

System:
  Kernel: 5.15.0-58-generic x86_64 bits: 64 compiler: gcc v: 11.3.0
    Desktop: Cinnamon 5.4.12 Distro: Linux Mint 21 Vanessa
    base: Ubuntu 22.04 jammy
Machine:
  Type: Desktop System: ASUS product: All Series v: N/A
    serial: <superuser required>
  Mobo: ASUSTeK model: Z97-PRO GAMER v: Rev X.0x
    serial: <superuser required> UEFI: American Megatrends v: 2203
    date: 02/26/2016
Memory:
  RAM: total: 11.63 GiB used: 2.86 GiB (24.6%)
  RAM Report:
    permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: quad core model: Intel Core i5-4690K bits: 64 type: MCP arch: Haswell
    rev: 3 cache: L1: 256 KiB L2: 1024 KiB L3: 6 MiB
  Speed (MHz): avg: 3472 high: 3501 min/max: 800/3900 cores: 1: 3501
    2: 3500 3: 3388 4: 3500 bogomips: 27999
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: AMD Tonga XT / Amethyst [Radeon R9 380X M295X] vendor: PC Partner
    driver: amdgpu v: kernel bus-ID: 01:00.0
  Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: amdgpu,ati
    unloaded: fbdev,modesetting,vesa gpu: amdgpu resolution: 1920x1080~60Hz
  OpenGL: renderer: AMD Radeon R9 380 Series (tonga LLVM 13.0.1 DRM 3.42
  5.15.0-58-generic)
    v: 4.6 Mesa 22.0.5 direct render: Yes
Audio:
  Device-1: Intel 9 Series Family HD Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel bus-ID: 00:1b.0
  Device-2: AMD Tonga HDMI Audio [Radeon R9 285/380] vendor: PC Partner
    driver: snd_hda_intel v: kernel bus-ID: 01:00.1
  Sound Server-1: ALSA v: k5.15.0-58-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 I218-V vendor: ASUSTeK driver: e1000e v: kernel
    port: f040 bus-ID: 00:19.0
  IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 4.78 TiB used: 2.05 TiB (43.0%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: 980 PRO with Heatsink 1TB
    size: 931.51 GiB temp: 50.9 C
  ID-2: /dev/sda vendor: Samsung model: SSD 840 PRO Series size: 238.47 GiB
  ID-3: /dev/sdb vendor: Seagate model: ST4000VN008-2DR166 size: 3.64 TiB
Partition:
  ID-1: / size: 232.24 GiB used: 99.64 GiB (42.9%) fs: ext4 dev: /dev/sda2
  ID-2: /boot/efi size: 95 MiB used: 30.3 MiB (31.9%) fs: vfat
    dev: /dev/nvme0n1p2
  ID-3: /mnt/data size: 3.64 TiB used: 1.96 TiB (53.8%) fs: ntfs
    dev: /dev/sdb2
Swap:
  ID-1: swap-1 type: partition size: 977 MiB used: 524 KiB (0.1%)
    dev: /dev/sda3
Sensors:
  System Temperatures: cpu: 29.8 C mobo: 27.8 C gpu: amdgpu temp: 51.0 C
  Fan Speeds (RPM): N/A gpu: amdgpu fan: 232
Repos:
  Packages: 2853
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
    1: deb https://mirror.cov.ukservers.com/linuxmint vanessa main upstream import backport
    2: deb http://archive.ubuntu.com/ubuntu jammy main restricted universe multiverse
    3: deb http://archive.ubuntu.com/ubuntu jammy-updates main restricted universe multiverse
    4: deb http://archive.ubuntu.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/teamviewer.list
    1: deb [signed-by=/usr/share/keyrings/teamviewer-keyring.gpg] https://linux.teamviewer.com/deb stable main
  Active apt repos in: /etc/apt/sources.list.d/unit193-encryption-jammy.list
    1: deb http://ppa.launchpad.net/unit193/encryption/ubuntu jammy main
Info:
  Processes: 261 Uptime: 10h 49m Init: systemd runlevel: 5 Compilers:
  gcc: 11.3.0 Shell: Bash v: 5.1.16 inxi: 3.3.13

[mikeymike]

https://ubuntuforums.org/showthread.php?t=2483409

Thanks for this, I have an Iiyama monitor too and I gave the suggestion a try of manually setting the monitor's input source. It worked in a test, I'll try leaving that setting in place for now.

Admittedly I don't much like having to remember that setting in case I ever switch to DisplayPort, and I'm puzzled as to why it'll happily suspend the monitor at the login screen without this extra setting, but hey ho.

I might try un-setting this setting and running the test again in case some recent Linux update has done the trick, admittedly it's been a while since I last tested it and I've been meaning to get around to posting this thread for a while.

[exploder]

For now I will just press the button on my monitor if I really want it shut off. Still like to figure out the cause of the issue.

[linuxovios]

There is a possibility (has happened to me in the past) a USB device is waking up the monitor. Through trial and error try to figure out if one of your usb devices (i.e. mouse) is causing the problem.

Also, try updating to 5.19 kernel or newer and see if the problem remains.