Display doesnt come back after turning monitors off and back on

Support Graphics & Display
1

EDIT::
System:
Kernel: 6.6.47-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/boot/vmlinuz-6.6-x86_64
root=UUID=ca7fd84c-5967-473c-a2d8-bb37fb208f2e rw quiet
udev.log_priority=3
Desktop: KDE Plasma v: 6.0.5 tk: Qt v: N/A info: frameworks v: 6.5.0
wm: kwin_x11 with: krunner tools: xscreensaver,xscreensaver-systemd vt: 2
dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
Type: Desktop Mobo: ASRock model: B450M Pro4 serial:
uuid: UEFI: American Megatrends v: P5.00
date: 03/08/2021
Battery:
Device-1: hidpp_battery_0 model: Logitech Wireless Touch Keyboard K400
serial: charge: 55% (should be ignored) rechargeable: yes
status: discharging
Memory:
System RAM: total: 32 GiB available: 30.74 GiB used: 12.1 GiB (39.4%)
Message: For most reliable report, use superuser + dmidecode.
Array-1: capacity: 128 GiB slots: 4 modules: 4 EC: None
max-module-size: 32 GiB note: est.
Device-1: Channel-A DIMM 0 type: DDR4 detail: synchronous unbuffered
(unregistered) size: 8 GiB speed: 2667 MT/s volts: note: check curr: 1
min: 1 max: 1 width (bits): data: 64 total: 64 manufacturer: Corsair
part-no: CMK32GX4M4Z2933C16 serial: N/A
Device-2: Channel-A DIMM 1 type: DDR4 detail: synchronous unbuffered
(unregistered) size: 8 GiB speed: 2667 MT/s volts: note: check curr: 1
min: 1 max: 1 width (bits): data: 64 total: 64 manufacturer: Corsair
part-no: CMK16GX4M2Z2933C16 serial: N/A
Device-3: Channel-B DIMM 0 type: DDR4 detail: synchronous unbuffered
(unregistered) size: 8 GiB speed: 2667 MT/s volts: note: check curr: 1
min: 1 max: 1 width (bits): data: 64 total: 64 manufacturer: Corsair
part-no: CMK32GX4M4Z2933C16 serial: N/A
Device-4: Channel-B DIMM 1 type: DDR4 detail: synchronous unbuffered
(unregistered) size: 8 GiB speed: 2667 MT/s volts: note: check curr: 1
min: 1 max: 1 width (bits): data: 64 total: 64 manufacturer: Corsair
part-no: CMK16GX4M2Z2933C16 serial: N/A
CPU:
Info: model: AMD Ryzen 5 5600G with Radeon Graphics bits: 64 type: MT MCP
arch: Zen 3 gen: 3 level: v3 note: check built: 2021-22
process: TSMC n7 (7nm) family: 0x19 (25) model-id: 0x50 (80) stepping: 0
microcode: 0xA50000B
Topology: cpus: 1x dies: 1 clusters: 1 cores: 6 threads: 12 tpc: 2
smt: enabled cache: L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB
desc: 6x512 KiB L3: 16 MiB desc: 1x16 MiB
Speed (MHz): avg: 3570 min/max: 1400/3900 boost: enabled scaling:
driver: acpi-cpufreq governor: schedutil cores: 1: 3570 2: 3570 3: 3570
4: 3570 5: 3570 6: 3570 7: 3570 8: 3570 9: 3570 10: 3570 11: 3570 12: 3570
bogomips: 93633
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities:
Type: gather_data_sampling status: Not affected
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data status: Not affected
Type: reg_file_data_sampling status: Not affected
Type: retbleed status: Not affected
Type: spec_rstack_overflow status: Vulnerable: Safe RET, no microcode
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
sanitization
Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; IBRS_FW;
STIBP: always-on; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not
affected
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Navi 23 [Radeon RX 6600/6600
XT/6600M] vendor: Micro-Star MSI driver: amdgpu v: kernel arch: RDNA-2
code: Navi-2x process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4
speed: 16 GT/s lanes: 16 ports: active: DP-1,HDMI-A-1 empty: DP-2,DP-3
bus-ID: 03:00.0 chip-ID: 1002:73ff class-ID: 0300
Device-2: Advanced Micro Devices [AMD/ATI] Cezanne [Radeon Vega Series /
Radeon Mobile Series] driver: N/A alternate: amdgpu arch: GCN-5 code: Vega
process: GF 14nm built: 2017-20 pcie: gen: 3 speed: 8 GT/s lanes: 16
link-max: gen: 4 speed: 16 GT/s bus-ID: 0a:00.0 chip-ID: 1002:1638
class-ID: 0300
Display: x11 server: X.Org v: 21.1.13 with: Xwayland v: 24.1.2
compositor: kwin_x11 driver: X: loaded: amdgpu unloaded: modesetting,radeon
alternate: fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
Screen-1: 0 s-res: 4480x1440 s-dpi: 96 s-size: 1185x381mm (46.65x15.00")
s-diag: 1245mm (49.01")
Monitor-1: DP-1 mapped: DisplayPort-0 pos: primary,top-right
model: LG (GoldStar) ULTRAGEAR serial: built: 2022 res: 2560x1440
hz: 120 dpi: 93 gamma: 1.2 size: 697x392mm (27.44x15.43")
diag: 800mm (31.5") ratio: 16:9 modes: max: 2560x1440 min: 640x350
Monitor-2: HDMI-A-1 mapped: HDMI-A-0 pos: bottom-l model: BenQ GL2480
serial: built: 2020 res: 1920x1080 dpi: 92 gamma: 1.2
size: 531x298mm (20.91x11.73") diag: 609mm (24") ratio: 16:9 modes:
max: 1920x1080 min: 720x400
API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
device: 1 drv: swrast gbm: drv: kms_swrast surfaceless: drv: radeonsi x11:
drv: radeonsi inactive: wayland
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.1.6-arch1.1
glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 6600 (radeonsi navi23
LLVM 18.1.8 DRM 3.54 6.6.47-1-MANJARO) device-ID: 1002:73ff
memory: 7.81 GiB unified: no
API: Vulkan v: 1.3.279 layers: 8 device: 0 type: discrete-gpu name: AMD
Radeon RX 6600 (RADV NAVI23) driver: mesa radv v: 24.1.6-arch1.1
device-ID: 1002:73ff surfaces: xcb,xlib
Audio:
Device-1: Advanced Micro Devices [AMD/ATI] Navi 21/23 HDMI/DP Audio
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 03:00.1 chip-ID: 1002:ab28 class-ID: 0403
Device-2: Advanced Micro Devices [AMD/ATI] Renoir Radeon High Definition
Audio driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
link-max: gen: 4 speed: 16 GT/s bus-ID: 0a:00.1 chip-ID: 1002:1637
class-ID: 0403
Device-3: Advanced Micro Devices [AMD] Family 17h/19h HD Audio
vendor: ASRock driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s
lanes: 16 link-max: gen: 4 speed: 16 GT/s bus-ID: 0a:00.6
chip-ID: 1022:15e3 class-ID: 0403
API: ALSA v: k6.6.47-1-MANJARO status: kernel-api with: aoss
type: oss-emulator tools: alsactl,alsamixer,amixer
Server-1: JACK v: 1.9.22 status: off tools: N/A
Server-2: PipeWire v: 1.2.3 status: active with: 1: pipewire-pulse
status: active 2: pipewire-media-session status: active 3: pipewire-alsa
type: plugin tools: pactl,pw-cat,pw-cli
Network:
Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
vendor: ASRock driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1
port: e000 bus-ID: 07:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp7s0 state: up speed: 1000 Mbps duplex: full mac:
Info: services: NetworkManager,systemd-timesyncd
Bluetooth:
Device-1: ASUSTek Broadcom BCM20702A0 Bluetooth driver: btusb v: 0.8
type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-2:2
chip-ID: 0b05:17cb class-ID: fe01 serial:
Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
Drives:
Local Storage: total: 3.18 TiB used: 1.87 TiB (58.6%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 970 EVO 500GB
size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
lanes: 4 tech: SSD serial: fw-rev: 2B2QEXE7 temp: 32.9 C
scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Smart Modular Tech.
model: SHGS31-1000GS-2 size: 931.51 GiB block-size: physical: 4096 B
logical: 512 B speed: 6.0 Gb/s tech: SSD serial: fw-rev: 0Q00
scheme: GPT
ID-3: /dev/sdb maj-min: 8:16 vendor: Smart Modular Tech.
model: SHGS31-1000GS-2 size: 931.51 GiB block-size: physical: 4096 B
logical: 512 B speed: 6.0 Gb/s tech: SSD serial: fw-rev: 0Q00
scheme: GPT
ID-4: /dev/sdc maj-min: 8:32 vendor: Crucial model: CT1000MX500SSD4
size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: fw-rev: 023 scheme: GPT
Message: No optical or floppy data found.
Partition:
ID-1: / raw-size: 465.46 GiB size: 457.09 GiB (98.20%)
used: 253.82 GiB (55.5%) fs: ext4 dev: /dev/nvme0n1p2 maj-min: 259:2
label: N/A uuid: ca7fd84c-5967-473c-a2d8-bb37fb208f2e
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 312 KiB (0.1%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
label: NO_LABEL uuid: 4D0D-8D3C
Swap:
Alert: No swap data was found.
Sensors:
System Temperatures: cpu: 40.8 C mobo: N/A gpu: amdgpu temp: 53.0 C
mem: 64.0 C
Fan Speeds (rpm): N/A gpu: amdgpu fan: 0
Info:
Processes: 366 Power: uptime: 1d 4h 42m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 12.28 GiB services: org_kde_powerdevil,upowerd
Init: systemd v: 256 default: graphical tool: systemctl
Packages: 1834 pm: pacman pkgs: 1799 libs: 494 tools: pamac pm: flatpak
pkgs: 35 Compilers: clang: 18.1.8 gcc: 14.2.1 Shell: Zsh v: 5.9 default: Bash
v: 5.2.32 running-in: yakuake inxi: 3.3.36

END OF EDIT::
I dont even know where to begin with solving this.

When I turn my monitors off before going to bed, but leave the computer on for music or w/e reason, they turn on again in the morning, obviously. But they get no signal from the computer and go into power saving mode. No mouse or keyboard action wakes it up. I have to do a hard power down (99% sure I cant avoid hard reset when input devices dont work and there is no display)

Everything works correctly with respect to screensaver. I have it set to 1min and it works flawlessly. I can also turn the monitors off for multiple hours during the day when I leave home and experience no issues when I arrive back home and turn the monitors back on.

I let the monitors stay on overnight a few times, with screensaver active, and everything was fine in the morning. I also tried changing my display settings to only use the main monitor before going to sleep but that did not change anything.

So its ONLY when the monitors are powered off for more than 4 hours (or something) that I experience this issue.

It started randomly. Not associated with updates or other system changes.

I have not yet logged in as a different user to let things sit overnight to see if its a profile issue due to the inconvenience of having to remember to do that. Ill make a noted/reminder to increase the chance I successfully do this tonight.

Whether or not the issue replicates what would be my next step? If it does not replicate on a 2nd user profile, id like to move forward with modifying my profile to correct the issue versus clean slate. If it does replicate, well…ill still be looking for assistance in what to check next.

Thanks for any assistance.
I didnt add any logs or what not only due to not knowing what to include for this weird issue but ill add logs if directed!

2

Check your BIOS. Make sure any related settings are configured properly; for example, look for something like wake on mouse, wake on keyboard, etc.

Every mainboard is different, so all I can do is wish you luck.

Cheers.

3

How about with posting your system settings?

inxi --admin --verbosity=5 --filter --no-host --width

Are you sure your input device (keyboard) dont work? Press numlock key on your Keyboard and look if the LED is Power On/Off.

Or Capslock LED.

If you see feedback, you can revive your PC with Reisub.
If you have a PC or Laptop idk (most Laptops dont have this LEDs as far as i know), since you not posted your system yet.

You can also try different Kernels and report back what Kernels did you used already.

4

Got it. I would not have thought to check BIOS. Nothing there has been changed recently at all but ill look thru it all next time I reboot. Thanks for the suggestion.

1 Like
5

Thanks for the suggestions.
I posted the output of the command you gave. Its at the top of my OG post.

Yes, I am sure my keyboard and mouse are not functioning when I encounter this issue. I got the secondary monitor to display one of these mornings (never replicated) and the clock was also frozen. Further confirming some type of full system freeze or possibly a freeze of only the plasmashell GUI?? Would that be possible and if yes, are there ways to reboot just the shell … :neutral_face :w/o keyboard or mouse :melting_face:

Ill go thru and try the different kernels. I still do need to try letting it sit overnight on a different profile but if it doesnt replicate under new user, that could mean anything. It could be any of the programs running that causes it. Its not necessarily an issue with the manjaro operating system? Or would you argue this and lean towards an issue with manjaro itself with barely any chance that it could be other software?

6

I recall with one of my older systems, the gremlins were suddenly causing mayhem (I didn’t feed them, I swear).

As it happens, BIOS settings were reverting to the defaults because the BIOS battery (a typical Lithium battery, $2-to-$5 from just about anywhere) was not keeping a charge.

An easy fix, when I realised what the issue was; and those gremlins? Well, I guess they moved on to greener pastures.

Cheers.

7

A frozen GUI doesn’t prove your keyboard input isn’t being received.

Try rebooting with REISUB instead of the power button. If the Caps Lock light isn’t flashing then it should work (assuming you’ve set it up).

Have you tried switching to a tty? If so you may be able to restart plasma or the display server. There’s a keyboard option to restart the display server using Ctrl+Alt+Backspace, you have to enable it in your keyboard settings.

8

Please post Terminal Code as Preformatted Text, so mark the output and press crtl+e

If your Keyboard isn’t working it could be mean that you face a probably much bigger issue, than just a desktop freeze.

Your input may be not shown, but the Keyboard input should be still recognised.

But since you are using a Wireless Keyboard, im not sure if the connection to a wireless keyboard shows the same reliability as a Wired Keyboard.

Specially when it comes to a Frozen System.

For Plasma i used crlt+shift+f12

9

That doesn’t do anything by default, I checked last time you mentioned it and again just now. It doesn’t seem to be in the keyboard options.

So it seems you set this up yourself. :man_shrugging:

1 Like
10

You are right, i tried my shortcut but its no longer working.

But i write it down 4 year’s ago, maybe there was some changes around Plasma… otherwise i have no clue why its no longer working. :man_shrugging:

I just try crlt+alt+backspace but this shortcut behaves like a normal logout,
where you forced to Login with a password prompt.

Switching between TTY and Desktop shows for me a Desktop Reset Popup… but what ever helps here, should be the goal.

11

It’s not a normal logout, though it may look like it.

It kills the X server (and everything running in it), which is then automatically restarted and you’re left at the login screen. AFAIK a logout wouldn’t kill the X server, and would probably close things more gracefully.

1 Like
12

In case it’s useful for anyone following the flow:

Note that these shortcuts listed are obviously for KDE; there may be subtle variations accoring to the DE used.

Cheers.

3 Likes
13

Likewise:

Referred (not very clearly) to the options provided by xkeyboard-config, which for plasma 6 can be found in System Settings → Keyboard → Keyboard → Key Bindings (used to be called something else, probably Keyboard Options, either way it’s the third tab).

The Ctrl + Alt + Backspace option is under “Key sequence to kill the X server”, or as “terminate(ctrl_alt_bksp)” in the list provided by localectl

localectl list-x11-keymap-options

Not to be confused with the DE dependant shortcuts which can be found in System Settings → Keyboard → Shortcuts.

The first part:

Covered both.

Though I suppose they’re all keyboard options, but hopefully it helps people decipher my ramblings.

2 Likes
14

@Kobold @dmt @soundofthunder
Thanks fir the replies. I wasnt in a position to trouble shoot and attempt any of the ideas laid out due to schedule and have been just turning it off overnight. But now its refusing to update so I gotta do a wipe & fresh install. It gives me some theme not found error and I cant login after update. … The issues have been increasing in severity and frequency this past year-ish so it is well time enough to just do a fresh install versus trying to fix. Im 3 “serious” issues deep, still all ongoing and “serious” but not debilitating. Not worth it. Fresh is best!