Screen tearing and cursor corruption with different per-monitor scaling factors (Intel Meteor Lake, X11)

オープン
#14,126 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 8 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
42/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
活発
技術スタック
javascript, linux

調査の方向性

Start by reproducing the issue in Cinnamon 6.4.14 on X11 with the reported Intel graphics setup, enabling scale-monitor-framebuffer and x11-randr-fractional-scaling; compare mixed scaling with both monitors at the same scale. The report points to Cinnamon display configuration and Muffin composition but names no source files or tests, so locating the responsible code will require reading around those areas. Done means mixed per-monitor scaling no longer causes tearing or cursor corruption.

索引モデルが issue の本文から書いたものです。

説明

ChatGPT helped me to create this report, so sorry if there is something a little off (I'm a begginer)

Environment

  • Laptop: ASUS Zenbook 14 UX3405MA
  • Operating System: Linux Mint 22.1
  • Desktop Environment: Cinnamon 6.4.14
  • Window Manager / Compositor: Muffin 6.4.1
  • Display Server: X11
  • Kernel: 7.0.0-42-generic
  • GPU: Intel Meteor Lake-P / Intel Arc Graphics
  • GPU PCI ID: 8086:7d55
  • Kernel graphics driver: i915
  • Xorg driver: modesetting
  • OpenGL renderer: Mesa Intel Arc Graphics (MTL)
  • OpenGL driver: iris
  • Mesa version: 25.2.8-0ubuntu0.24.04.4
  • X.Org: 21.1.11
  • Base distribution: Ubuntu 24.04 (Noble)

No proprietary NVIDIA or AMD drivers are installed.

Display configuration

Internal laptop display
  • Panel: Samsung 0x419d
  • Connector: eDP-1
  • Native resolution: 2880 × 1800
  • Available refresh rates: 60 Hz and 120 Hz
  • Required scaling: 200%
External monitor
  • Manufacturer: LG
  • Model: LG QHD, 31.5 inches
  • Connector: HDMI-1 (HDMI-A-1)
  • Native resolution: 2560 × 1440
  • Working refresh rate: approximately 59.95/60 Hz
  • Required scaling: 100%

Both displays are correctly detected by Cinnamon and X11.

Problem description

When both monitors are configured with the same scaling factor, everything works correctly.

However, when using different scaling factors on the two displays, screen tearing appears on both monitors and the mouse cursor starts flickering, displaying visual corruption or becoming distorted.

The issue occurs regardless of which monitor uses the higher scaling factor.

This is reproducible with both configurations:

  • Internal display: 200%, external display: 100%.
  • Internal display: 100%, external display: 200%.

The problem disappears when both monitors use the same scaling factor.

This strongly suggests an issue related to multi-monitor composition and per-monitor scaling under Cinnamon/Muffin on X11.

Steps to reproduce

  1. Connect an external LG QHD monitor through HDMI.
  2. Enable Cinnamon's experimental fractional scaling controls.
  3. Ensure the following experimental features are enabled:

    scale-monitor-framebuffer

    x11-randr-fractional-scaling

  4. Open System Settings → Display.
  5. Configure the internal display to 200% scaling.
  6. Configure the external display to 100% scaling.
  7. Apply the configuration and move windows around, move the mouse cursor and play a video.

Observe the screen tearing and cursor corruption.

Repeat the test with both displays configured at 100%, and then with both configured at 200%.

Test results

Internal display External display Result
100% 100% No tearing or cursor issues
200% 200% No tearing or cursor issues
200% 100% Tearing and cursor corruption
100% 200% Tearing and cursor corruption

Additional observations:

  • Tearing occurs during video playback.
  • Tearing also occurs when moving application windows around the desktop.
  • The problem is not limited to a particular media player.
  • Cursor flickering and visual corruption can affect the internal display as well as the external display.
  • Disconnecting the external monitor and using the internal display alone at 200% works correctly.
  • Changing the internal display to 120 Hz while keeping the external display at approximately 60 Hz does not solve the issue.
  • The problem is not apparently caused by the refresh-rate difference.

The most important finding is that the problem is consistently triggered by different scaling factors across the two displays, regardless of which display is configured at 200%.

Fractional scaling configuration

The following experimental features are enabled:

gsettings get org.cinnamon.muffin experimental-features

Result:

['scale-monitor-framebuffer', 'x11-randr-fractional-scaling']

Current fractional scaling mode:

gsettings get org.cinnamon.muffin.x11 fractional-scale-mode

Result:

'scale-ui-down'

We also tested the alternative scale-up mode.

This did not resolve screen tearing and made the external mouse cursor rendering significantly worse.

The system was subsequently restored to scale-ui-down.

Other troubleshooting performed

The following aspects have already been investigated:

  • Confirmed that the session is running under X11.
  • Confirmed that the Intel i915 kernel driver and modesetting Xorg driver are active.
  • Confirmed that direct rendering is enabled.
  • Checked Cinnamon/Muffin compositing and fullscreen unredirect settings.
  • Tested different display refresh rates.
  • Tested both monitors at identical scaling factors.
  • Tested both possible combinations of different scaling factors.
  • Confirmed that HDMI detection and monitor configuration persistence are working correctly.

The HDMI connection previously had signal detection problems and occasional system freezes with older kernels.

Using kernel 7.0.0-42-generic has significantly improved HDMI detection and stability.

The external monitor now works correctly at 2560 × 1440 and approximately 60 Hz.

We would prefer not to modify the working kernel, Mesa installation or Intel graphics driver configuration without a specific technical reason.

Related issue

https://github.com/linuxmint/cinnamon/issues/13808

The hardware is exactly the same ASUS Zenbook 14 UX3405MA, with the same Intel Meteor Lake-P / Intel Arc Graphics GPU.

However, there are important differences:

  • The related issue uses scale-up, whereas this report uses scale-ui-down.
  • The related issue describes intermittent cursor disappearance and flickering in specific overlapping display regions.
  • In our case, both screen tearing and cursor corruption occur on both displays whenever different scaling factors are used.
  • Our external monitor is an LG QHD display connected through HDMI, rather than the DisplayPort-connected iiyama monitor described in the related issue.

We believe these two reports may involve related problems in Cinnamon/Muffin's handling of hardware cursor rendering and multi-monitor composition with different scaling factors.

Expected behaviour

Both monitors should work correctly with independent scaling:

  • Internal Samsung display: 2880 × 1800, 200%, 60 Hz.
  • External LG display: 2560 × 1440, 100%, approximately 60 Hz.

Expected results:

  • No screen tearing on either display.
  • No cursor flickering, disappearance or visual corruption.
  • Smooth window movement and video playback.
  • Correct hardware-accelerated Intel graphics rendering.
  • Independent scaling without loss of image sharpness.

Actual behaviour

Different scaling factors consistently trigger screen tearing and mouse cursor rendering problems.

Using identical scaling factors on both displays eliminates these problems, but this is not a practical solution because the laptop display requires 200% scaling while the external monitor requires 100%.

Questions for the developers

  1. Is this a known limitation or bug in Muffin's X11 multi-monitor composition when different scaling factors are used?
  2. Could the problem be related to hardware cursor plane handling across different CRTCs?
  3. Is there a known issue with x11-randr-fractional-scaling and the Intel i915/modesetting graphics stack?
  4. Is there a fix or a recommended configuration that would allow independent monitor scaling without screen tearing or cursor corruption?
  5. Could this issue be related to #13808, despite the different symptoms and fractional scaling modes?

We would appreciate any guidance on further diagnostic information that could help identify the responsible component.

Thank you for your work on Cinnamon and Linux Mint.

主要言語
JavaScript
スター
5.7k
フォーク
941
平均マージ
6日 18時間
マージ済み PR(30日)
12

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

linuxmint/cinnamon のほかの issue

linuxmint/cinnamon の issue をすべて見る

似ている issue

JavaScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。