Display freezes when using second monitor after upgrade to Kubuntu 23.10

I know this is question is more suited to a forum like Ubuntu stack exchange. But this form is so much easier to read and deal with…

After upgrading to 23.10 the display will freeze randomly.

I can get the display to come back, by disconnecting my second screen.

The system as a whole is unresponsive when it happens. But any video I was playing will continue to play and the sound will come through (can’t turn down the sound though). Also if I use the keyboard shortcut to open a terminal (ctrl + F6… I think). The terminal will not display for a few seconds. And I’m unable to go back to the gui (F7).

This last time it happened, I decided to wait it out. I unplugged all peripherals (including my second display). And this is what I got:

It took a bit for the device to refresh and come back alive. For example, this screenshot was taken using spectacle. It took 5 seconds after pressing the hotkey to bring up spectacle for the gui to respond.

Here is the Journalctl of the last time the freeze happend: log

I found this bit interesting:

Nov 15 12:17:27 laptop-txtechnician kernel: i915 0000:00:02.0: [drm] *ERROR* flip_done timed out
Nov 15 12:17:27 laptop-txtechnician kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:131:pipe B] commit wait timed out
Nov 15 12:17:37 laptop-txtechnician kernel: i915 0000:00:02.0: [drm] *ERROR* flip_done timed out
Nov 15 12:17:37 laptop-txtechnician kernel: i915 0000:00:02.0: [drm] *ERROR* [PLANE:82:plane 1B] commit wait timed out
Nov 15 12:17:38 laptop-txtechnician kernel: ------------[ cut here ]------------
Nov 15 12:17:38 laptop-txtechnician kernel: i915 0000:00:02.0: vblank wait timed out on crtc 1
Nov 15 12:17:38 laptop-txtechnician kernel: WARNING: CPU: 9 PID: 1353 at drivers/gpu/drm/drm_vblank.c:1310 drm_wait_one_vblank+0x1f1/0x210 [drm]

Any help would be appreciated.

That part from the journal is indeed interesting; it’s an Intel driver bug where updating the screen (or rather a related event) times out. You can report the issue here: Issues · drm / intel · GitLab

1 Like

I reported it. thanks.

I also switched over to wayland and haven’t had the error again.

Have you tried this