Internal display freezes after login

Framework Laptop 13
1

Hello!

Since a few weeks I’m experiencing the issue, that the internal display freezes after a few seconds after resuming/logging in with Gnome. The keyboard still responds, I can change the screen brightness and make screen shots from the contents of the screen. I can unfreeze it with running printf freeze > /sys/power/state (I set a hotkey for that) loginctl suspend does not help. My feeling is, that something in the handover between the lock/login screen and the gnome session goes wrong.

The system I’m running on: Debian 13 running linux-6.16 running Gnome-48.0. But the issue persists across different Distributions and kernel versions.

The issue does not happen with sway. It correlates with the BIOS upgrade to 3.04, but I’m not sure if that is the issue.

Does anyone have similiar problems?

–Enno

Framework 16 internal display freezing
2

I assume the AI 300 boards? Yep! On Bluefin, I get the same sort of freeze maybe one time in six after logging in. Closing the lid, waiting for a couple seconds, and re-opening it always fixes it.

If you’re talking about the 7040 series, then no. Those things were stone cold reliable for me (after three months of pain when they shipped).

3

Are you using Xorg?

4

Have you filed a ticket? Would recommend reaching out to support just in case! http://frame.work/support

5

No, wayland.

6

Already opened a ticket. Lets’s see what happens :slight_smile:

7

Hi, do you have any updates? I previously would experience this issue when using an external monitor, but now it’s happening even when unconnected

8

Update: The root cause was a gnome extension: GitHub - daitj/gnome-display-brightness-ddcutil: Display brightness slider for gnome shell using ddcutil backend

apparently, since the BIOS update, the interaction between this extension and the monitors i2c leads to the screen freezing.

9

Excellent, thank you! I also have that installed, and disabling it ( Brightness control using ddcutil - GNOME Shell Extensions ) then rebooting solved my issue as well.