Desktop Environment is slow after reboot

dragomir · 2026-03-12 10:31:23

I have updated my system yesterday and after update and login entire desktop environment became slow (keys are registered late, cursor lags behind the input and just teleports around).

After first login I have to lock the desktop (not log out) and log back in, and after that everything works normally.

I am using Lenovo yoga pro 7 14imh9, with gnome desktop environment on wayland with Intel cpu and ARC graphics.

After the update I started receiving errors while booting up (dmesg output, only errors):

[    0.463642] ACPI Error: Needed [Integer/String/Buffer], found [Package] 00000000bc5f9978 (20250807/exresop-469)
[    0.463649] fbcon: Taking over console
[    0.463658] ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [ToHexString] (20250807/dswexec-433)
[    0.463663] ACPI Error: Aborting method \_SB.VFAN._DSM due to previous error (AE_AML_OPERAND_TYPE) (20250807/psparse-529)
[    0.463669] ACPI: \_SB_.VFAN: failed to evaluate _DSM 401861a7-fe99-ae41-a488-35c75926c8eb rev:0 func:2 (0x3003)
[    0.463699] ACPI Error: Needed [Integer/String/Buffer], found [Package] 000000001e6296d8 (20250807/exresop-469)
[    0.463702] ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [ToHexString] (20250807/dswexec-433)
[    0.463705] ACPI Error: Aborting method \_SB.VFAN._DSM due to previous error (AE_AML_OPERAND_TYPE) (20250807/psparse-529)
[    0.463710] ACPI: \_SB_.VFAN: failed to evaluate _DSM 401861a7-fe99-ae41-a488-35c75926c8eb rev:0 func:2 (0x3003)
[    0.464190] Freeing initrd memory: 18516K

[    0.558355] integrity: Problem loading X.509 certificate -74


[    3.729907] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.HEC.DPTF.FCHG], AE_NOT_FOUND (20250807/psargs-332)
[    3.729911] ACPI Error: Aborting method \_SB.IETM.CHRG.PPSS due to previous error (AE_NOT_FOUND) (20250807/psparse-529)

[    4.291191] i801_smbus 0000:00:1f.4: SMBus is busy, can't use it!
[    4.291199] i801_smbus 0000:00:1f.4: SMBus is busy, can't use it!
[    4.291205] i801_smbus 0000:00:1f.4: SMBus is busy, can't use it!
[    4.291211] i801_smbus 0000:00:1f.4: SMBus is busy, can't use it!
[    4.291216] i801_smbus 0000:00:1f.4: SMBus is busy, can't use it!
[    4.291222] i801_smbus 0000:00:1f.4: SMBus is busy, can't use it!
[    4.291228] i801_smbus 0000:00:1f.4: SMBus is busy, can't use it!

[    4.312796] lenovo_wmi_gamezone 887B54E3-DDDC-4B2C-8B88-68A26A8835D0-6: platform_profile probe failed

I am not sure what is causing the issue and would greatly appreciate the answer

Last edited by dragomir (2026-03-12 17:03:33)

seth · 2026-03-12 15:40:51

After first login I have to lock the desktop (not log out) and log back in, and after that everything works normally.

Race condition?
Compare

glxinfo -B

for the slow and fast situation.

Also please use [code][/code] tags, the bbs predates markdown by approximately your age.

dragomir · 2026-03-12 17:23:34

I am sorry for the code block, Markdown became my second nature.

I have ran

glxinfo -B

It at first complained about using xe drivers, but I ran it with both xe and i915 drivers and saved the outputs

# While the system is slow (Using Xe driver)

name of display: :0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Intel (0x8086)
    Device: Mesa Intel(R) Arc(tm) Graphics (MTL) (0x7d55)
    Version: 26.0.1
    Accelerated: yes
    Video memory: 31690MB
    Unified memory: yes
    Preferred profile: core (0x1)
    Max core profile version: 4.6
    Max compat profile version: 4.6
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2
OpenGL vendor string: Intel
OpenGL renderer string: Mesa Intel(R) Arc(tm) Graphics (MTL)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 26.0.1-arch1.1
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6 (Compatibility Profile) Mesa 26.0.1-arch1.1
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile

OpenGL ES profile version string: OpenGL ES 3.2 Mesa 26.0.1-arch1.1
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20


# After lock/unlock(Using Xe driver)

name of display: :0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Intel (0x8086)
    Device: Mesa Intel(R) Arc(tm) Graphics (MTL) (0x7d55)
    Version: 26.0.1
    Accelerated: yes
    Video memory: 31690MB
    Unified memory: yes
    Preferred profile: core (0x1)
    Max core profile version: 4.6
    Max compat profile version: 4.6
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2
OpenGL vendor string: Intel
OpenGL renderer string: Mesa Intel(R) Arc(tm) Graphics (MTL)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 26.0.1-arch1.1
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6 (Compatibility Profile) Mesa 26.0.1-arch1.1
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile

OpenGL ES profile version string: OpenGL ES 3.2 Mesa 26.0.1-arch1.1
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

# While system is slow (Using i915 driver)

name of display: :0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Intel (0x8086)
    Device: Mesa Intel(R) Arc(tm) Graphics (MTL) (0x7d55)
    Version: 26.0.1
    Accelerated: yes
    Video memory: 31690MB
    Unified memory: yes
    Preferred profile: core (0x1)
    Max core profile version: 4.6
    Max compat profile version: 4.6
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2
OpenGL vendor string: Intel
OpenGL renderer string: Mesa Intel(R) Arc(tm) Graphics (MTL)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 26.0.1-arch1.1
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6 (Compatibility Profile) Mesa 26.0.1-arch1.1
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile

OpenGL ES profile version string: OpenGL ES 3.2 Mesa 26.0.1-arch1.1
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

# After lock/unlock(Using i915 driver)

name of display: :0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Intel (0x8086)
    Device: Mesa Intel(R) Arc(tm) Graphics (MTL) (0x7d55)
    Version: 26.0.1
    Accelerated: yes
    Video memory: 31690MB
    Unified memory: yes
    Preferred profile: core (0x1)
    Max core profile version: 4.6
    Max compat profile version: 4.6
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2
OpenGL vendor string: Intel
OpenGL renderer string: Mesa Intel(R) Arc(tm) Graphics (MTL)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 26.0.1-arch1.1
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6 (Compatibility Profile) Mesa 26.0.1-arch1.1
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile

OpenGL ES profile version string: OpenGL ES 3.2 Mesa 26.0.1-arch1.1
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

The same issue appears using both drivers and the fix is the same. I think the problem is a race condition as well, but I do not know where to find it.

I have also ran

diff

on all outputs and nothing is different (I included everything for the sake of completeness).

The CPU model is Intel Core Ultra 7 first gen if it helps.

seth · 2026-03-13 14:08:21

on all outputs and nothing is different

Nor any suspicious.

entire desktop environment became slow (keys are registered late, cursor lags behind the input and just teleports around)

Assuming only the input is affected

[    4.291228] i801_smbus 0000:00:1f.4: SMBus is busy, can't use it!
[    4.312796] lenovo_wmi_gamezone 887B54E3-DDDC-4B2C-8B88-68A26A8835D0-6: platform_profile probe failed

actually becomes suspicious here.
Please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

You're probably not getting this w/ the LTS kernel?

dragomir · 2026-03-13 17:21:42

I am using 6.19.6 kernel, and on my other computer, also running Arch with the same kernel, I have no issues, the issue only started after updating from 6.16 (I am not completely sure, but not older than that).

The issue is not only with inputs, everything becomes slow, but trackpad and keyboards become almost unusable.

I am not using LTS kernel, and my other computer runs fine, even with nvidia graphics.

The entire boot log is here.

seth · 2026-03-13 21:24:32

I am not using LTS kernel

The idea was to test that to verify it's a kernel regression.
There's a single warning

Mar 13 17:59:06 hostname kernel: WARNING: drivers/gpu/drm/i915/display/intel_bios.c:2732 at intel_bios_init+0x13a4/0x1840 [i915], CPU#0: (udev-worker)/299

If it's not the kernel, do you face the same w/ not-gnome (even more fancy DEs like hyprland or enlightnement)?

dragomir · 2026-03-14 09:25:31

I have just tried running XFCE4 and it started working immediately. I wish I could try gnome on X, but I can only choose between Gnome and Gnome Classic

seth · 2026-03-14 13:13:23

Gnome no longer supports X11 - have you tried gnome on a fresh user account (in case it's some gnome setting)?
Can you try some other wayland compositor (in doubt just weston)?

dragomir · 2026-03-14 17:00:59

I have played around with many configs and tried to break everything to see what is the underlying cause.

I have tried both weston and hyprland. The issue is definitely with Gnome, even though I got fixated on boot errors so I tried to fix that side, but it turns out I have two different issues.

The first issue is still something with drivers - I am getting ACPI erorrs and smbus errors. The second one is with Gnome. The Gnome issue works as following.

1. Boot to gdm -> everything seems fine
2. Log in to hyprland/weston -> everything is fine
3. Log out -> still, everything is fine
4. Log in to Gnome/Gnome Classic -> entire system is slow
5. Lock screen in Gnome -> Now everything is also fine
6. Unlock -> Still fine

After locking the screen gnome survives even a full log out - it is just the first login to gnome that causes issues. Log out/Log in cycle does not resolve the issues but Lock/Unlock does.

seth · 2026-03-14 21:22:41

seth wrote:

have you tried gnome on a fresh user account

The behavior is somewhat bizarre because GDM is a gnome-shell itself so it seems to hinge on your session.
Does merely switching the VT (ctrl+alt+F3 and back) impact the situation?

dragomir · 2026-03-15 16:30:46

Switching VT does not help. However, I have encountered some new bizarre behaviors.

I have created a new user account and only created a home directory and a password for it.

Switching accounts does not make the issue go away - on both accounts there must be a lock/unlock to make the DE usable.

Also, the new account cannot run the display at full resolution at 120Hz, I get either artifacts all across the screen, or the entire screen turns black for a few seconds.
The new account can do 120Hz at 3/4 of the full resolution or 60Hz at full resolution (does not matter if the variable refresh rate is turned on or off).

However, after setting either account to 60Hz the issue with slowness does not happen. GDM also runs at 60Hz which I have not noticed until now.
Still, hyprland and weston run at 120Hz by default and do not exhibit the same issues.

Last edited by dragomir (2026-03-15 16:43:06)

seth · 2026-03-15 16:55:46

Is the monitor https://wiki.archlinux.org/title/Variable_refresh_rate capable?

for OUT in /sys/class/drm/card*; do echo $OUT; edid-decode $OUT/edid; echo "================="; done

You'll need https://archlinux.org/packages/extra/x86_64/v4l-utils/

dragomir · Yesterday 10:56:39

I do not know what to look for, so here is the output of your command. I have tried using vrrtest and the actual fps always matches target fps, and I can enable vsync.

Block 0, Base EDID:
  EDID Structure Version & Revision: 1.4
  Vendor & Product Identification:
    Manufacturer: LEN
    Model: 35505
    Made in: week 30 of 2022
  Basic Display Parameters & Features:
    Digital display
    Bits per primary color channel: 10
    DisplayPort interface
    Maximum image size: 31 cm x 20 cm
    Gamma: 2.20
    Supported color formats: RGB 4:4:4
    First detailed timing includes the native pixel format and preferred refresh rate
    Display supports continuous frequencies
  Color Characteristics:
    Red  : 0.6777, 0.3193
    Green: 0.2646, 0.6894
    Blue : 0.1494, 0.0595
    White: 0.3125, 0.3281
  Established Timings I & II: none
  Standard Timings: none
  Detailed Timing Descriptors:
    DTD 1:  3072x1920   60.000000 Hz  16:10   120.000 kHz    387.840000 MHz (312 mm x 195 mm)
                 Hfront   48 Hsync  32 Hback   80 Hpol N
                 Vfront    3 Vsync   6 Vback   71 Vpol N
    Display Range Limits:
      Monitor ranges (Range Limits Only): 30-120 Hz V, 240-240 kHz H, max dotclock 780 MHz
    Alphanumeric Data String: 'LENOVO'
    Alphanumeric Data String: 'LEN145-3K'
  Extension blocks: 2
Checksum: 0x4a

----------------

Block 1, CTA-861 Extension Block:
  Revision: 3
  Native detailed modes: 0
  HDR Static Metadata Data Block:
    Electro optical transfer functions:
      Traditional gamma - SDR luminance range
    Supported static metadata descriptors:
      Static metadata type 1
    Desired content max luminance: 96 (400.000 cd/m^2)
    Desired content max frame-average luminance: 96 (400.000 cd/m^2)
    Desired content min luminance: 35 (0.075 cd/m^2)
  Unknown CTA-861 Data Block (tag 0x00, length 0):
  Unknown CTA-861 Data Block (tag 0x00, length 0):
  Unknown CTA-861 Data Block (tag 0x00, length 0):
  Unknown CTA-861 Data Block (tag 0x00, length 0):
Checksum: 0xfe  Unused space in Extension Block: 112 bytes

----------------

Block 2, DisplayID Extension Block:
  Version: 1.2
  Extension Count: 0
  Display Product Type: Extension Section
  Video Timing Modes Type 1 - Detailed Timings Data Block:
    DTD:  3072x1920  120.001547 Hz  16:10   240.003 kHz    775.690000 MHz (aspect 16:10, no 3D stereo)
               Hfront   48 Hsync  32 Hback   80 Hpol N
               Vfront    3 Vsync   6 Vback   71 Vpol N
  Checksum: 0x55
Checksum: 0x90

I can also enable VRR in hyprland with no issues.

Also I have just updated my system - kernel, gnome, mesa and vulkan received updates. All of the updates are here

Last edited by dragomir (Yesterday 11:10:31)

seth · Yesterday 14:15:26

I do not know what to look for

Display supports continuous frequencies

https://wiki.archlinux.org/title/Variab … rate#GNOME

gsettings get org.gnome.mutter experimental-features

dragomir · Yesterday 15:18:57

So, the display supports VRR. This is the output of the gsettings command

> gsettings get org.gnome.mutter experimental-features

['scale-monitor-framebuffer', 'variable-refresh-rate', 'xwayland-native-scaling']

VRR is already on, but as I have said in

dragomir wrote:

Switching VT does not help. However, I have encountered some new bizarre behaviors.
I have created a new user account and only created a home directory and a password for it.
Switching accounts does not make the issue go away - on both accounts there must be a lock/unlock to make the DE usable.
Also, the new account cannot run the display at full resolution at 120Hz, I get either artifacts all across the screen, or the entire screen turns black for a few seconds.
The new account can do 120Hz at 3/4 of the full resolution or 60Hz at full resolution (does not matter if the variable refresh rate is turned on or off).
However, after setting either account to 60Hz the issue with slowness does not happen. GDM also runs at 60Hz which I have not noticed until now.
Still, hyprland and weston run at 120Hz by default and do not exhibit the same issues.

it does not change anything. I suspect that running at 120Hz is somehow responsible for the issues, but I cannot pinpoint what is the exact root cause of the issue.

seth · Yesterday 15:30:39

VRR is already on, but as I have said in

The plan was to turn it *off* - notably because of the "experimental" part - to see whether it's the cause.
You can likely also disable it in the monitor OSD

dragomir · Yesterday 17:29:56

I have disabled all experimental features and it did not resolve the issue, but the issue manifests differently.

The screen turns black until I move the cursor, at which point it correctly displays everything for a second and turns black. During the entire process
there is some tearing on the display. The issue is once again resolved by a single lock/unlock cycle.

The issue does not happen when the display is set to 60Hz by default, but as soon as I turn on 120Hz mode, it starts to do what I described above.
A lock/unlock cycle once again makes the issue go away.

seth · Yesterday 21:09:34

I have disabled [VRR] … screen turns black until I move the cursor, at which point it correctly displays everything for a second and turns black … does not happen when the display is set to 60Hz

Sounds like a signal issue, could be power saving and the IGP only clocks up (w/ gnome) for the lockscreen??
"i915.enable_psr=0 intel_idle.max_cstate=1 i915.enable_dc=0 ahci.mobile_lpm_policy=1", https://wiki.archlinux.org/title/Kernel_parameters
If this helps you want to figure which parameter is critical - "intel_idle.max_cstate=1" is the worst one, so rule that out first.

Arch Linux

#1 2026-03-12 10:31:23

Desktop Environment is slow after reboot

#2 2026-03-12 15:40:51

Re: Desktop Environment is slow after reboot

#3 2026-03-12 17:23:34

Re: Desktop Environment is slow after reboot

#4 2026-03-13 14:08:21

Re: Desktop Environment is slow after reboot

#5 2026-03-13 17:21:42

Re: Desktop Environment is slow after reboot

#6 2026-03-13 21:24:32

Re: Desktop Environment is slow after reboot

#7 2026-03-14 09:25:31

Re: Desktop Environment is slow after reboot

#8 2026-03-14 13:13:23

Re: Desktop Environment is slow after reboot

#9 2026-03-14 17:00:59

Re: Desktop Environment is slow after reboot

#10 2026-03-14 21:22:41

Re: Desktop Environment is slow after reboot

#11 2026-03-15 16:30:46

Re: Desktop Environment is slow after reboot

#12 2026-03-15 16:55:46

Re: Desktop Environment is slow after reboot

#13 Yesterday 10:56:39

Re: Desktop Environment is slow after reboot

#14 Yesterday 14:15:26

Re: Desktop Environment is slow after reboot

#15 Yesterday 15:18:57

Re: Desktop Environment is slow after reboot

#16 Yesterday 15:30:39

Re: Desktop Environment is slow after reboot

#17 Yesterday 17:29:56

Re: Desktop Environment is slow after reboot

#18 Yesterday 21:09:34

Re: Desktop Environment is slow after reboot

Board footer