External monitor does not turn on after DPMS #63

New Issue

Open

opened 2022-05-13 12:19:44 +02:00 by simon · 2 comments

simon commented

2022-05-13 12:19:44 +02:00

Owner

Extract from the logs:

May 13 11:55:33 mayushii sway[639162]: > Warning:          Could not resolve keysym XF86KbdLcdMenu3
May 13 11:55:33 mayushii sway[639162]: > Warning:          Could not resolve keysym XF86KbdLcdMenu4
May 13 11:55:33 mayushii sway[639162]: > Warning:          Could not resolve keysym XF86KbdLcdMenu5
May 13 11:55:33 mayushii sway[639162]: Errors from xkbcomp are not fatal to the X server
May 13 11:55:53 mayushii pipewire[3316]: spa.alsa: front:3: snd_pcm_drop No such device
May 13 11:55:53 mayushii pipewire[3316]: spa.alsa: front:3: close failed: No such device
May 13 11:55:53 mayushii sway[3262]: 2022-05-13 11:55:53 - [main.c:373] Destroying output DP-6 (Acer Technologies Acer B277K 0x0000F36C)
May 13 11:55:53 mayushii kanshi[43633]: applying profile 'standalone'
May 13 11:55:53 mayushii kanshi[43633]: applying profile output 'eDP-1' on connected head 'eDP-1'
May 13 11:55:53 mayushii sway[3184]: 27:57:33.435 [ERROR] [wlr] [libseat] [libseat/backend/logind.c:193] Could not close device: Device not taken
May 13 11:55:53 mayushii sway[3184]: 27:57:33.435 [ERROR] [wlr] [backend/session/session.c:326] Failed to close device 117: Resource temporarily unavailable
May 13 11:55:53 mayushii sway[638563]: 11:55:53 INFO: Creating a fake screen in order for Qt not to crash
May 13 11:55:53 mayushii sway[639235]: The XKEYBOARD keymap compiler (xkbcomp) reports:
May 13 11:55:53 mayushii sway[639235]: > Warning:          Unsupported maximum keycode 708, clipping.
May 13 11:55:53 mayushii sway[639235]: >                   X11 cannot support keycodes above 255.
May 13 11:55:53 mayushii sway[639235]: > Warning:          Could not resolve keysym XF86BrightnessAuto

Possibly related upstream issues:

Sway: https://github.com/swaywm/sway/issues/5759 (One monitor won't wake up after swayidle)
Linux/DRM: https://gitlab.freedesktop.org/drm/amd/-/issues/1376 (Screen keeps being dark after reactivating from screensaver / powersaving)

This happens since I have the Acer B277K configured in clamshell mode (laptop closed and its screen disabled). This happens often when the screen goes to dpms (swayidle) or when sway/kanshi is restarted. Sometimes I can just re-plug the DP cable on my dock (which is not very easy, since it is a locking connector in a tight space), but sometimes the only option is to re-dock my laptop (which obviously also means losing power/network/audio for a short period). Extract from the logs: ``` May 13 11:55:33 mayushii sway[639162]: > Warning: Could not resolve keysym XF86KbdLcdMenu3 May 13 11:55:33 mayushii sway[639162]: > Warning: Could not resolve keysym XF86KbdLcdMenu4 May 13 11:55:33 mayushii sway[639162]: > Warning: Could not resolve keysym XF86KbdLcdMenu5 May 13 11:55:33 mayushii sway[639162]: Errors from xkbcomp are not fatal to the X server May 13 11:55:53 mayushii pipewire[3316]: spa.alsa: front:3: snd_pcm_drop No such device May 13 11:55:53 mayushii pipewire[3316]: spa.alsa: front:3: close failed: No such device May 13 11:55:53 mayushii sway[3262]: 2022-05-13 11:55:53 - [main.c:373] Destroying output DP-6 (Acer Technologies Acer B277K 0x0000F36C) May 13 11:55:53 mayushii kanshi[43633]: applying profile 'standalone' May 13 11:55:53 mayushii kanshi[43633]: applying profile output 'eDP-1' on connected head 'eDP-1' May 13 11:55:53 mayushii sway[3184]: 27:57:33.435 [ERROR] [wlr] [libseat] [libseat/backend/logind.c:193] Could not close device: Device not taken May 13 11:55:53 mayushii sway[3184]: 27:57:33.435 [ERROR] [wlr] [backend/session/session.c:326] Failed to close device 117: Resource temporarily unavailable May 13 11:55:53 mayushii sway[638563]: 11:55:53 INFO: Creating a fake screen in order for Qt not to crash May 13 11:55:53 mayushii sway[639235]: The XKEYBOARD keymap compiler (xkbcomp) reports: May 13 11:55:53 mayushii sway[639235]: > Warning: Unsupported maximum keycode 708, clipping. May 13 11:55:53 mayushii sway[639235]: > X11 cannot support keycodes above 255. May 13 11:55:53 mayushii sway[639235]: > Warning: Could not resolve keysym XF86BrightnessAuto ``` Possibly related upstream issues: * Sway: https://github.com/swaywm/sway/issues/5759 (One monitor won't wake up after swayidle) * Linux/DRM: https://gitlab.freedesktop.org/drm/amd/-/issues/1376 (Screen keeps being dark after reactivating from screensaver / powersaving)

simon added the

labels 2022-05-13 12:19:44 +02:00

simon commented

2022-06-04 11:14:41 +02:00

Poster

Owner

After the upgrade to 22.05, I often need to restart/reload sway (Mod4+Ctrl+r) to get sway to recognise the monitor with its real resolution (3840×2160@60) instead of 640×480@60 (which the monitor does not accept).