[SOLVED] DWM windows "randomly" freeze and become unusable

leakciM · 2022-02-04 15:22:23

Hello Folks,

I have a weird issue and I am not sure about what is causing it, which brings me to my first post on this forum. Horray!!

Here is a quick description of my issue:

I log into my system on TTY 1 which then fires my window manager (dwm). Then I start using my laptop. 99% of the time I am using a terminal (kitty) or a browser (qutebrowser/brave) or both. Then after a "random" amount of time, suddenly all of the open windows freeze. I can still spawn new windows or open a new browser window. But the windows that were open, and all the work happening in those windows is stuck. I can't close them, can't save or click on them. I have to logout and log back in again and use a recovery system of the programs I was running (vim swap files most of the time) to get my work back... I don't know what is triggering this. It happened with different terminals and browsers. It also happened when I was only using a terminal or only a browser. This should be an X server problem but I am unable to find the problems in the logs...

Here is a overview of my config:

OS: Arch Linux
Kernel: x86_64 Linux 5.16.4-arch1-1
Packages: 717
Shell: bash 5.1.16
Resolution: 2560x1440
WM: dwm
GTK Theme: Adwaita [GTK3]
Disk: 450G / 938G (51%)
CPU: Intel Core i7-8650U @ 8x 4.2GHz
GPU: Intel Corporation UHD Graphics 620 (rev 07)

Here as some logs shortly after this happened:

cat ~/.local/share/xorg/Xorg.0.log

[ 27059.911] (II) XINPUT: Adding extended input device "TPPS/2 Elan TrackPoint" (type: MOUSE, id 11)
[ 27059.911] (**) Option "AccelerationScheme" "none"
[ 27059.911] (**) TPPS/2 Elan TrackPoint: (accel) selected scheme none/0
[ 27059.911] (**) TPPS/2 Elan TrackPoint: (accel) acceleration factor: 2.000
[ 27059.911] (**) TPPS/2 Elan TrackPoint: (accel) acceleration threshold: 4
[ 27059.913] (II) event15 - TPPS/2 Elan TrackPoint: is tagged by udev as: Mouse Pointingstick
[ 27059.913] (II) event15 - TPPS/2 Elan TrackPoint: trackpoint multiplier is 0.40
[ 27059.914] (II) event15 - TPPS/2 Elan TrackPoint: device is a pointer
[ 27059.916] (II) config/udev: Adding input device TPPS/2 Elan TrackPoint (/dev/input/mouse1)
[ 27059.916] (II) No input driver specified, ignoring this device.
[ 27059.916] (II) This device may have been added with another device file.
[ 27059.916] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event4)
[ 27059.916] (**) AT Translated Set 2 keyboard: Applying InputClass "libinput keyboard catchall"
[ 27059.916] (**) AT Translated Set 2 keyboard: Applying InputClass "system-keyboard"
[ 27059.916] (II) Using input driver 'libinput' for 'AT Translated Set 2 keyboard'
[ 27059.917] (II) systemd-logind: got fd for /dev/input/event4 13:68 fd 30 paused 0
[ 27059.917] (**) AT Translated Set 2 keyboard: always reports core events
[ 27059.917] (**) Option "Device" "/dev/input/event4"
[ 27059.917] (**) Option "_source" "server/udev"
[ 27059.918] (II) event4  - AT Translated Set 2 keyboard: is tagged by udev as: Keyboard
[ 27059.918] (II) event4  - AT Translated Set 2 keyboard: device is a keyboard
[ 27059.919] (II) event4  - AT Translated Set 2 keyboard: device removed
[ 27059.919] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input4/event4"
[ 27059.919] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 12)
[ 27059.919] (**) Option "xkb_model" "pc105"
[ 27059.919] (**) Option "xkb_layout" "us"
[ 27059.919] (**) Option "xkb_options" "ctrl:nocaps,compose:ralt"
[ 27059.921] (II) event4  - AT Translated Set 2 keyboard: is tagged by udev as: Keyboard
[ 27059.921] (II) event4  - AT Translated Set 2 keyboard: device is a keyboard
[ 27059.922] (II) config/udev: Adding input device PC Speaker (/dev/input/event6)
[ 27059.922] (II) No input driver specified, ignoring this device.
[ 27059.922] (II) This device may have been added with another device file.
[ 27059.926] (II) config/udev: Adding input device ThinkPad Extra Buttons (/dev/input/event5)
[ 27059.926] (**) ThinkPad Extra Buttons: Applying InputClass "libinput keyboard catchall"
[ 27059.926] (**) ThinkPad Extra Buttons: Applying InputClass "system-keyboard"
[ 27059.926] (II) Using input driver 'libinput' for 'ThinkPad Extra Buttons'
[ 27059.927] (II) systemd-logind: got fd for /dev/input/event5 13:69 fd 31 paused 0
[ 27059.927] (**) ThinkPad Extra Buttons: always reports core events
[ 27059.927] (**) Option "Device" "/dev/input/event5"
[ 27059.927] (**) Option "_source" "server/udev"
[ 27059.928] (II) event5  - ThinkPad Extra Buttons: is tagged by udev as: Keyboard Switch
[ 27059.928] (II) event5  - ThinkPad Extra Buttons: device is a keyboard
[ 27059.928] (II) event5  - ThinkPad Extra Buttons: device removed
[ 27059.929] (**) Option "config_info" "udev:/sys/devices/platform/thinkpad_acpi/input/input6/event5"
[ 27059.929] (II) XINPUT: Adding extended input device "ThinkPad Extra Buttons" (type: KEYBOARD, id 13)
[ 27059.929] (**) Option "xkb_model" "pc105"
[ 27059.929] (**) Option "xkb_layout" "us"
[ 27059.929] (**) Option "xkb_options" "ctrl:nocaps,compose:ralt"
[ 27059.930] (II) event5  - ThinkPad Extra Buttons: is tagged by udev as: Keyboard Switch
[ 27059.930] (II) event5  - ThinkPad Extra Buttons: device is a keyboard
[ 27061.680] (II) intel(0): EDID vendor "AUO", prod id 8246
[ 27061.681] (II) intel(0): Printing DDC gathered Modelines:
[ 27061.681] (II) intel(0): Modeline "2560x1440"x0.0  245.50  2560 2608 2640 2720  1440 1443 1448 1504 -hsync -vsync (90.3 kHz eP)
[ 27384.813] (EE) event14 - Synaptics TM3289-021: kernel bug: Touch jump detected and discarded.
See https://wayland.freedesktop.org/libinput/doc/1.19.3/touchpad-jumping-cursors.html for details
[ 27426.127] (EE) event14 - Synaptics TM3289-021: kernel bug: Touch jump detected and discarded.
See https://wayland.freedesktop.org/libinput/doc/1.19.3/touchpad-jumping-cursors.html for details
[ 29412.156] (EE) intel(0): Failed to set backlight intel_backlight for output eDP1, disabling

journalctl -b

Jan 24 21:18:18 x1 kernel: smpboot: Booting Node 0 Processor 7 APIC 0x7
Jan 24 21:18:18 x1 kernel: CPU7 is up
Jan 24 21:18:18 x1 kernel: ACPI: PM: Waking up from system sleep state S3
Jan 24 21:18:18 x1 kernel: ACPI: EC: interrupt unblocked
Jan 24 21:18:18 x1 kernel: ACPI: EC: event unblocked
Jan 24 21:18:18 x1 kernel: nvme nvme0: Shutdown timeout set to 8 seconds
Jan 24 21:18:18 x1 kernel: nvme nvme0: 8/0/0 default/read/poll queues
Jan 24 21:18:18 x1 kernel: usb 2-3: Disable of device-initiated U1 failed.
Jan 24 21:18:18 x1 kernel: i915 0000:00:02.0: [drm] GuC firmware i915/kbl_guc_62.0.0.bin version 62.0 submission:disabled
Jan 24 21:18:18 x1 kernel: i915 0000:00:02.0: [drm] GuC SLPC: disabled
Jan 24 21:18:18 x1 kernel: i915 0000:00:02.0: [drm] HuC firmware i915/kbl_huc_4.0.0.bin version 4.0 authenticated:yes
Jan 24 21:18:18 x1 kernel: i915 0000:00:02.0: [drm] [ENCODER:94:DDI A/PHY A] is disabled/in DSI mode with an ungated DDI clock, gate it
Jan 24 21:18:18 x1 kernel: i915 0000:00:02.0: [drm] [ENCODER:102:DDI B/PHY B] is disabled/in DSI mode with an ungated DDI clock, gate it
Jan 24 21:18:18 x1 kernel: i915 0000:00:02.0: [drm] [ENCODER:118:DDI C/PHY C] is disabled/in DSI mode with an ungated DDI clock, gate it
Jan 24 21:18:18 x1 kernel: usb 2-3: Disable of device-initiated U2 failed.
Jan 24 21:18:18 x1 kernel: usb 2-3: reset SuperSpeed USB device number 2 using xhci_hcd
Jan 24 21:18:18 x1 kernel: usb 1-8: reset high-speed USB device number 3 using xhci_hcd
Jan 24 21:18:18 x1 kernel: OOM killer enabled.
Jan 24 21:18:18 x1 kernel: Restarting tasks ... done.
Jan 24 21:18:18 x1 kernel: usb 1-9: USB disconnect, device number 17
Jan 24 21:18:18 x1 iwd[3862]: Received Deauthentication event, reason: 3, from_ap: false
Jan 24 21:18:18 x1 iwd[3862]: netconfig: Failed to delete IP address. Error -99: Cannot assign requested address
Jan 24 21:18:18 x1 iwd[3862]: resolve-systemd: Failed to modify the DNS entries. org.freedesktop.resolve1.LinkBusy: Link wlan0 is managed.
Jan 24 21:18:18 x1 systemd-logind[3863]: Lid opened.
Jan 24 21:18:18 x1 systemd-resolved[3859]: Clock change detected. Flushing caches.
Jan 24 21:18:18 x1 systemd-networkd[455]: wlan0: Lost carrier
Jan 24 21:18:18 x1 systemd-networkd[455]: wlan0: DHCP lease lost
Jan 24 21:18:18 x1 systemd-networkd[455]: wlan0: DHCPv6 lease lost
Jan 24 21:18:18 x1 systemd-resolved[3859]: Switching to fallback DNS server 1.1.1.1#cloudflare-dns.com.
Jan 24 21:18:18 x1 systemd-sleep[81609]: System returned from sleep state.
Jan 24 21:18:18 x1 kernel: PM: suspend exit
Jan 24 21:18:18 x1 kernel: usb 1-9: new full-speed USB device number 18 using xhci_hcd
Jan 24 21:18:18 x1 kernel: usb 1-9: New USB device found, idVendor=06cb, idProduct=009a, bcdDevice= 1.64
Jan 24 21:18:18 x1 kernel: usb 1-9: New USB device strings: Mfr=0, Product=0, SerialNumber=1
Jan 24 21:18:18 x1 kernel: usb 1-9: SerialNumber
Jan 24 21:18:19 x1 kernel: wlan0: authenticate with dc
Jan 24 21:18:19 x1 kernel: wlan0: send auth to dc (try 1/3)
Jan 24 21:18:19 x1 kernel: wlan0: authenticated
Jan 24 21:18:19 x1 kernel: wlan0: associate with dc (try 1/3)
Jan 24 21:18:19 x1 kernel: wlan0: RX AssocResp from dc (capab=0x1011 status=0 aid=6)
Jan 24 21:18:19 x1 systemd-networkd[455]: wlan0: Connected WiFi access point: Freebox-6AB4DC (dc:00:b0:f3:31:e4)
Jan 24 21:18:19 x1 kernel: wlan0: associated
Jan 24 21:18:19 x1 kernel: wlan0: Limiting TX power to 23 (23 - 0) dBm as advertised by dc:00:b0:f3:31:e4
Jan 24 21:18:19 x1 systemd-networkd[455]: wlan0: Gained carrier
Jan 24 21:18:19 x1 systemd[1]: systemd-suspend.service: Deactivated successfully.
Jan 24 21:18:19 x1 systemd[1]: Finished System Suspend.
Jan 24 21:18:19 x1 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 24 21:18:19 x1 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 24 21:18:19 x1 systemd[1]: Stopped target Sleep.
Jan 24 21:18:19 x1 systemd[1]: Reached target Suspend.
Jan 24 21:18:19 x1 systemd-logind[3863]: Operation 'sleep' finished.
Jan 24 21:18:19 x1 systemd[1]: Stopped target Suspend.
Jan 24 21:18:19 x1 kernel: audit: type=1130 audit(1643055499.379:178): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? termina>
Jan 24 21:18:19 x1 kernel: audit: type=1131 audit(1643055499.379:179): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? termina>
Jan 24 21:18:19 x1 systemd-networkd[455]: wlan0: DHCPv6 lease lost
Jan 24 21:18:20 x1 kernel: mei_hdcp 0000:00:16.0-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915])
Jan 24 21:18:21 x1 systemd-networkd[455]: wlan0: DHCPv4 address 192.168.1.66/24, gateway 192.168.1.254 acquired from 192.168.1.254
Jan 24 21:18:23 x1 iwd[3862]: resolve-systemd: Failed to modify the DNS entries. org.freedesktop.resolve1.LinkBusy: Link wlan0 is managed.
Jan 24 21:18:23 x1 iwd[3862]: resolve-systemd: Failed to modify the domains entries. org.freedesktop.resolve1.LinkBusy: Link wlan0 is managed.

Do you see anything unusual in the logs above? Please let me know if you need any further information or if this message is missing any important information.

Thanks a lot for any help you can provide!!!!!
Cheers

Last edited by leakciM (2022-02-11 11:00:16)

Trilby · 2022-02-04 15:27:13

Have you ever had some dynamic display in the "frozen" windows? Either a video playing, or an updating display like top/htop? I'm curious whether the content of the windows is frozen or if they just no longer receive input focus (so you can't use the mouse / keyboard in them).

Also, if you open new windows, do the "frozen" windows get retiled? If they get retiled and change size, does the content update properly for the new size?

leakciM · 2022-02-04 15:43:56

Trilby wrote:

Have you ever had some dynamic display in the "frozen" windows? Either a video playing, or an updating display like top/htop? I'm curious whether the content of the windows is frozen or if they just no longer receive input focus (so you can't use the mouse / keyboard in them).
Also, if you open new windows, do the "frozen" windows get retiled? If they get retiled and change size, does the content update properly for the new size?

Hi Trilby,

Yesterday this happened while I had a teams meeting with video on in one of the tabs open and it just happened atm with HTOP open.
I am able to focus on the "frozen" windows and move them to other screens or main/secondary positions but when I use the close window shortcut nothing happens. So they seem to net receive any mouse or keybord input anymore.

When I open new windows, the "frozen" windows get retiled but they will only display the contents of any active window a move in front of them (if this makes any sense?).

Thanks again!!

Last edited by leakciM (2022-02-04 15:47:21)

leakciM · 2022-02-04 15:48:02

Or maybe I am missing some important drivers/firmwares? I reinstalled this laptop fairly recently and I am trying to keep a very minimal config.

Last edited by leakciM (2022-02-04 15:48:13)

Trilby · 2022-02-04 16:23:44

Thanks - it sounds like the frozen windows are indeed loosing their connection to the X server. One way this might be able to happen is if the hostname changes while running. Please post the output of the following and describe which networking tools you use (networkmanager by any chance?) (edit: I see iwd entries in the journal, so I gather that's used, but confirmation would still be good)

hostname

cat /etc/hostname

hostnamectl

Even better would be if you can get the output of `hostname` from before and right after such a freeze.

Last edited by Trilby (2022-02-04 16:31:19)

leakciM · 2022-02-04 16:30:47

Thank you for your help.

Here is the output of cat /etc/hostname:

[mt@x1 iwd]$ cat /etc/hostname 
x1

I am using iwd as a networking tool and I had to create a conf file for it to work properly.

[mt@x1 iwd]$ cat /etc/iwd/main.conf 
[General]
EnableNetworkConfiguration=true
[Network]
NameResolvingService=systemd
RoutePriorityOffset=300

I am not sure I understand how the hostname or the network manager could be the cause?

Last edited by leakciM (2022-02-04 16:31:07)

Trilby · 2022-02-04 16:34:24

leakciM wrote:

I am not sure I understand how the hostname or the network manager could be the cause?

I'm not sure that's what it is, but it's worth testing. X11 is a network protocol, and clients (programs with windows open) connect to the Xorg server via the local/internal network. Problems with hostname settings will cause a failure of clients to connect to the server. What I don't know is whether a client with an active connection can be dropped due to a hostname change - but it seems a fair hypothesis to test.

I only mentioned network manager as NM itself seems prone to messing with the hostname settings if / when it is not configured properly.

leakciM · 2022-02-04 16:44:14

Thanks that makes sense.

Is there anything I could try with the hostnames?

leakciM · 2022-02-04 16:47:15

If it can help it seems that the DNS part in those logs and DHCP seem to be something recurring when this hapens.

I will try to disable the iwd service and see if it stops happening when I'm offline.

leakciM · 2022-02-09 18:11:03

So this problem still persists.

I found that when I use the Brave browser the window can still receive some input (eg. I am able to switch tabs as I can see the title of the window changing) and after a while the window works normal again but the other frozen windows (qutebrowser or terminal-kitty) remain frozen). I am not able to provide input for kitty or qutebrowser.

Any other suggestions on things to try or what might be the cause of this weird freeze?

I did not have time to try with the iwd servide disabled as I had to work and needed internet...

Last edited by leakciM (2022-02-09 18:37:39)

V1del · 2022-02-09 18:34:49

Try removing xf86-video-intel. Make sure you don't have xorg confs referencing the "intel" driver lying around.

Last edited by V1del (2022-02-09 18:36:22)

jprestwo · 2022-02-09 21:03:34

leakciM wrote:

Thank you for your help.
Here is the output of cat /etc/hostname:
[mt@x1 iwd]$ cat /etc/hostname 
x1
I am using iwd as a networking tool and I had to create a conf file for it to work properly.
[mt@x1 iwd]$ cat /etc/iwd/main.conf 
[General]
EnableNetworkConfiguration=true
[Network]
NameResolvingService=systemd
RoutePriorityOffset=300
I am not sure I understand how the hostname or the network manager could be the cause?

One thing I notice is your using EnableNetworkConfiguration, but also have systemd-networkd running. Either disable EnableNetworkConfiguration or set systemd-networkd to ignore IWD's interface. No idea if this is causing a problem, but its a start towards correctness

leakciM · 2022-02-10 08:36:04

V1del wrote:

Try removing xf86-video-intel. Make sure you don't have xorg confs referencing the "intel" driver lying around.

Thanks! I removed the xf86-video-intel and until know it seems to be working fine, no frozen windows yet! The computer seems to be running more smoothly as well.
I will keep using it for another couple of days and see if this is it. If it's working I will change the topic to solved.

@V1del, do you mind sharing how the xf86-video-intel might be the cause of this? I'm curious, as from those logs I was completely lost...

jprestwo wrote:

leakciM wrote:
Thank you for your help.
Here is the output of cat /etc/hostname:
[mt@x1 iwd]$ cat /etc/hostname 
x1
I am using iwd as a networking tool and I had to create a conf file for it to work properly.
[mt@x1 iwd]$ cat /etc/iwd/main.conf 
[General]
EnableNetworkConfiguration=true
[Network]
NameResolvingService=systemd
RoutePriorityOffset=300
I am not sure I understand how the hostname or the network manager could be the cause?
One thing I notice is your using EnableNetworkConfiguration, but also have systemd-networkd running. Either disable EnableNetworkConfiguration or set systemd-networkd to ignore IWD's interface. No idea if this is causing a problem, but its a start towards correctness

@jprestwo, thanks I will also change this in 2-3 days (to see if the xf86 has solved it). I thought I needed to have both in my iwd/main.conf! I am not sure yet what exactly these two lines do...

Last edited by leakciM (2022-02-10 08:36:27)

leakciM · 2022-02-11 12:41:18

@V1del, it seems to be solved! Many many many thanks!

If you don't mind, what made you think it was xf86-video-intel by looking at these logs?

Last edited by leakciM (2022-02-11 12:41:34)

V1del · 2022-02-11 13:13:52

You aren't going to see much in the logs, because it doesn't run into anything that's explicitly logged. It's pretty much a "default" suspicion for any kind of graphical weirdness whenever I see it used, because it had these kinds of issues for years and has not seen much active development. It's not installed anymore for newer (~2010+) intel chips on the more automated distributions like Ubuntu and Fedora. It certainly still has it's uses if you happen to have a card that does not support the OpenGL 2 requirement of the modesetting driver you are using now, but these are very old GPUs that don't provide this and I suspect x86-video-intel being actually well tested on those. There's also the note with some further links under: https://wiki.archlinux.org/title/Intel_ … stallation

leakciM · 2022-02-12 15:51:00

Fantastic thank you soo much!

Arch Linux

#1 2022-02-04 15:22:23

[SOLVED] DWM windows "randomly" freeze and become unusable

#2 2022-02-04 15:27:13

Re: [SOLVED] DWM windows "randomly" freeze and become unusable

#3 2022-02-04 15:43:56

Re: [SOLVED] DWM windows "randomly" freeze and become unusable

#4 2022-02-04 15:48:02

Re: [SOLVED] DWM windows "randomly" freeze and become unusable

#5 2022-02-04 16:23:44

Re: [SOLVED] DWM windows "randomly" freeze and become unusable

#6 2022-02-04 16:30:47

Re: [SOLVED] DWM windows "randomly" freeze and become unusable

#7 2022-02-04 16:34:24

Re: [SOLVED] DWM windows "randomly" freeze and become unusable

#8 2022-02-04 16:44:14

Re: [SOLVED] DWM windows "randomly" freeze and become unusable

#9 2022-02-04 16:47:15

Re: [SOLVED] DWM windows "randomly" freeze and become unusable

#10 2022-02-09 18:11:03

Re: [SOLVED] DWM windows "randomly" freeze and become unusable

#11 2022-02-09 18:34:49

Re: [SOLVED] DWM windows "randomly" freeze and become unusable

#12 2022-02-09 21:03:34

Re: [SOLVED] DWM windows "randomly" freeze and become unusable

#13 2022-02-10 08:36:04

Re: [SOLVED] DWM windows "randomly" freeze and become unusable

#14 2022-02-11 12:41:18

Re: [SOLVED] DWM windows "randomly" freeze and become unusable

#15 2022-02-11 13:13:52

Re: [SOLVED] DWM windows "randomly" freeze and become unusable

#16 2022-02-12 15:51:00

Re: [SOLVED] DWM windows "randomly" freeze and become unusable

Board footer