Display Issue @ Manjaro-Gnome after Stable-Update-2025-06-23

Support Graphics & Display
, ,
1

When I had installed above update more cleanly with @linux-aarhus’ and @anon33601770’s help, it looked at first glance as if …

had been reduced to a bearable extent. (Not only) because I want to get this installation into a state that can serve as a template for my other machine (productive but having other issues with ugly workarounds), I really want to get rid of it.
Since it appeared only after the update, I suspect an incompatibility of the (same version of the) driver with other (updated) display elements, but I have no clue how to resolve that (e.g. by specific downgrades).
And: it doesn’t affect KDE (which is why I added the gnome tag to the topic).
The display related inxi output for Gnome:

Graphics:
  Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] vendor: Fujitsu
    driver: i915 v: kernel arch: Gen-9.5 process: Intel 14nm built: 2016-20
    ports: active: eDP-1 empty: none bus-ID: 00:02.0 chip-ID: 8086:3e9b
    class-ID: 0300
  Device-2: NVIDIA GP107GLM [Quadro P600 Mobile] vendor: Fujitsu
    driver: nouveau v: kernel non-free: 550-570.xx+ status: current (as of
    2025-04; EOL~2026-12-xx) arch: Pascal code: GP10x process: TSMC 16nm
    built: 2016-2021 pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 3
    speed: 8 GT/s ports: active: none empty: DP-1, DP-2, DP-3, DP-4, DP-5
    bus-ID: 01:00.0 chip-ID: 10de:1cbc class-ID: 0300 temp: 29.0 C
  Device-3: Chicony FJ Camera driver: uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-7:4 chip-ID: 04f2:b3b4
    class-ID: 0e02 serial: <filter>
  Display: unspecified server: X.org v: 1.21.1.18 with: Xwayland v: 24.1.8
    compositor: gnome-shell driver: gpu: i915 display-ID: :0
    note: <missing: xdpyinfo/xrandr>
  Monitor-1: eDP-1 model: BOE Display 0x0630 built: 2016 res: 1920x1080
    dpi: 142 gamma: 1.2 chroma: red: x: 0.584 y: 0.365 green: x: 0.349 y: 0.580
    blue: x: 0.161 y: 0.141 white: x: 0.314 y: 0.329
    size: 344x194mm (13.54x7.64") diag: 395mm (15.5") ratio: 16:9
    modes: 1920x1080
  API: EGL v: 1.5 hw: drv: intel iris drv: nvidia nouveau platforms:
    device: 0 drv: nouveau device: 1 drv: iris device: 2 drv: swrast gbm:
    drv: nouveau surfaceless: drv: nouveau x11: drv: iris inactive: wayland
  API: OpenGL v: 4.6 compat-v: 4.3 vendor: intel mesa v: 25.1.4-arch1.1
    glx-v: 1.4 direct-render: yes renderer: Mesa Intel UHD Graphics 630 (CFL
    GT2) device-ID: 8086:3e9b memory: 30.27 GiB unified: yes
  Info: Tools: api: eglinfo,glxinfo x11: xprop

.
… and for KDE:

Graphics:
  Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] vendor: Fujitsu
    driver: i915 v: kernel arch: Gen-9.5 process: Intel 14nm built: 2016-20
    ports: active: eDP-1 empty: none bus-ID: 00:02.0 chip-ID: 8086:3e9b
    class-ID: 0300
  Device-2: NVIDIA GP107GLM [Quadro P600 Mobile] vendor: Fujitsu
    driver: nouveau v: kernel non-free: 550-570.xx+ status: current (as of
    2025-04; EOL~2026-12-xx) arch: Pascal code: GP10x process: TSMC 16nm
    built: 2016-2021 pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 3
    speed: 8 GT/s ports: active: none empty: DP-1, DP-2, DP-3, DP-4, DP-5
    bus-ID: 01:00.0 chip-ID: 10de:1cbc class-ID: 0300 temp: 37.0 C
  Device-3: Chicony FJ Camera driver: uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-7:4 chip-ID: 04f2:b3b4
    class-ID: 0e02 serial: <filter>
  Display: unspecified server: X.Org v: 21.1.18 with: Xwayland v: 24.1.8
    compositor: kwin_x11 driver: X: loaded: modesetting alternate: fbdev,vesa
    dri: iris,nouveau gpu: i915 display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
    s-diag: 582mm (22.93") monitors: <missing: xrandr>
  Monitor-1: eDP-1 model: BOE Display 0x0630 built: 2016 res: 1920x1080
    dpi: 142 gamma: 1.2 chroma: red: x: 0.584 y: 0.365 green: x: 0.349 y: 0.580
    blue: x: 0.161 y: 0.141 white: x: 0.314 y: 0.329
    size: 344x194mm (13.54x7.64") diag: 395mm (15.5") ratio: 16:9
    modes: 1920x1080
  API: EGL v: 1.5 hw: drv: intel iris drv: nvidia nouveau platforms:
    device: 0 drv: nouveau device: 1 drv: iris device: 2 drv: swrast gbm:
    drv: nouveau surfaceless: drv: nouveau x11: drv: iris inactive: wayland
  API: OpenGL v: 4.6 compat-v: 4.3 vendor: intel mesa v: 25.1.4-arch1.1
    glx-v: 1.4 direct-render: yes renderer: Mesa Intel UHD Graphics 630 (CFL
    GT2) device-ID: 8086:3e9b memory: 30.27 GiB unified: yes
  API: Vulkan v: 1.4.313 layers: N/A device: 0 type: discrete-gpu
    name: Quadro P600 (NVK GP107) driver: mesa nvk v: 25.1.4-arch1.1
    device-ID: 10de:1cbc surfaces: N/A device: 1 type: integrated-gpu
    name: Intel UHD Graphics 630 (CFL GT2) driver: mesa intel
    v: 25.1.4-arch1.1 device-ID: 8086:3e9b surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor wl: wayland-info x11: xdpyinfo,xprop

If downgrading wouldn’t be a clean solution, disabling the NVIDIA might be an alternative. I’m not going to play any real time game or do demanding video editing - the most demanding apps might be FreeCAD and the like.

2

I have no experience with CAD applications - but Intel HD 630 can handle a lot - it may not be optimal for CAD but it will go some of the way, I am sure.

When you are confident the system work with the Intel iGPU and you have become confident in the administration of a rolling release Linux - you can begin to experiment with the dGPU.

3

Might need some patience, but that’s it. Its performance is sufficient on my other machine without a dGPU.

Well, I had been - until a hard memory reset ~ 3 years ago. And regaining it seems a very slow process.

Aside from that: I’d like to understand the different handling by the (affected) Gnome and the (not-affected) KDE.

4

I know that feeling - I have a huge gap in my memory… my reset was 13 years ago - it is a long hard pull.

5

Since I haven’t found a solution, I’ve at least tested above alternative. At the time of first mentioning it, I had no idea how and I’ve no idea (or, indeed I know - cp. directly above) why that didn’t come to me earlier (hoping someone might mention it): It’s nothing to do in Manjaro, it’s of course to be done in the machine’s bios.
While it doesn’t solve the issue, it conceals its effect, puts the laptop into a usable state.
(Which has become more urgent, because the workaround for the sound/video issue of the desktop stopped working after using bluetooth, which is another topic.)

Meanwhile, new topics re. choosing other (recommended) drivers for the dGPU have popped up here.
I’m going to try that, as soon as the desktop’s new issue and the pending update, which refuses to install, is sorted out.