Plasma-wayland freezing problem with 2nd monitor

[ypihoh]

plasma-wayland session (complete computer) freezing problem here.

• Occurs when I plug in a new hdmi screen.

• No other tty is working. I have to do a hard shutdown and reboot.

• I’ve tried to spot errors on next startup and found some powerdevil errors but they are here when it’s working.

• Works fine when the hdmi screen is plugged in on startup. But if it is shutdown, it goes to sleep or it is disconnected for some reason, I can’t plug it in back without freezing.

• X11 session works fine.

• Same behavior with 6.12 and 6.6 kernels.

• I’ve tried the last live cd (25.0.10) and got the same problem .. versus an old one (25.0.4) that is working without the issue.

System:
  Kernel: 6.12.48-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
  Desktop: KDE Plasma v: 6.3.6 tk: Qt v: N/A wm: kwin_wayland dm: SDDM
    Distro: Manjaro base: Arch Linux
Machine:
  Type: Laptop System: LENOVO product: 20Y4S2U000 v: ThinkPad P1 Gen 4i
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
CPU:
  Info: 8-core model: 11th Gen Intel Core i7-11850H bits: 64 type: MT MCP
    arch: Tiger Lake rev: 1 cache: L1: 640 KiB L2: 10 MiB L3: 24 MiB
Graphics:
  Device-1: Intel TigerLake-H GT1 [UHD Graphics] vendor: Lenovo driver: i915
    v: kernel arch: Xe ports: active: eDP-1 empty: DP-1, DP-2, DP-3, DP-4,
    HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:9a60
  Device-2: NVIDIA GA104M [GeForce RTX 3070 Mobile / Max-Q] vendor: Lenovo
    driver: nouveau v: kernel arch: Ampere pcie: speed: 2.5 GT/s lanes: 16
    ports: active: HDMI-A-2 empty: DP-5,DP-6 bus-ID: 01:00.0
    chip-ID: 10de:249d
  Display: wayland server: X.org v: 1.21.1.18 with: Xwayland v: 24.1.8
    compositor: kwin_wayland driver: X: loaded: modesetting
    alternate: fbdev,vesa dri: iris,zink gpu: i915,nouveau d-rect: 3840x4560
    display-ID: 0
  Monitor-1: HDMI-A-2 pos: primary,top model: Sony TV 00 res: 3840x2160
    hz: 60 dpi: 92 diag: 1220mm
  Monitor-2: eDP-1 pos: bottom model: LG Display 0x06aa res: 3840x2400
    hz: 60 dpi: 284 diag: 406mm
  API: EGL v: 1.5 platforms: device: 0 drv: zink device: 1 drv: iris
    device: 2 drv: swrast gbm: drv: zink surfaceless: drv: zink wayland:
    drv: iris x11: drv: iris
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 25.2.3-arch1.2
    glx-v: 1.4 direct-render: yes renderer: Mesa Intel UHD Graphics (TGL GT1)
    device-ID: 8086:9a60 display-ID: :1.0
  API: Vulkan v: 1.4.321 surfaces: N/A device: 0 type: integrated-gpu
    driver: mesa intel device-ID: 8086:9a60 device: 1 type: discrete-gpu
    driver: mesa nvk device-ID: 10de:249d
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor wl: wayland-info x11: xdpyinfo,xprop

Any help would be apreciated

[soundofthunder]

Your post has been moved to a dedicated topic.

Please provide your full inxi output as described (below) – edit your first post and replace the text there rather than creating another post for it.

@ypihoh

Occurs when I plug in a new hdmi screen.

You haven’t mentioned how this monitor is connected – via a direct HDMI <=> HDMI cable or an adapter cable of some kind. Have you tried other ports that might be available?

@ypihoh

I have to do a hard shutdown and reboot.

[HowTo] reboot / turn off your frozen computer: REISUB/REISUO

Difficulty: ★★☆☆☆ This tutorial was created because people are using a hard power off during freezes, so this will teach you how to turn off your computer when everything is frozen using softer means. So whenever you see someone saying they had to “Power Off” or “Hard Reset” their system without doing a REISUB, please send them here! If you’re reading this in response to a question, please click the green link above this text to bring you to the full unabridged text of the tutorial…

@ypihoh

I’ve tried to spot errors on next startup and found some powerdevil errors but they are here when it’s working.

Please provide logs rather than relying on what you might or might not see during boot. If you are unfamiliar with how to generate appropriate logs, manjaro-log-helper might be … helpful.

sudo pacman -S manjaro-log-helper

There is also this tutorial:

[HowTo] Find error logs

Difficulty: ★☆☆☆☆ The first step for troubleshooting an issue is to find an error log: a trace produced by an application when failing/crashing, and providing the first trail a user/developer can follow to fix it. 1. Reach a usable system Obviously, it will be impossible to acquire those logs if you can’t have access to a usable system. See: [HowTo] Reach a minimal system 2. Find the faulty application If you don’t know which application failed – this is usually the case on a system or gra…

Please provide as much detail as you can to help others help you. I’m sure someone will assist when they are able.

Regards.

---

Welcome to the Manjaro community

As a new or infrequent forum user, please take some time to familiarise yourself with Forum requirements, and the many ways to use the forum to your benefit.

To that end, links are provided (below) - Please use them.

---

Be prepared to provide outputs from various commands when asked. It’s equally important to provide as much actionable information as possible in your first post, rather than simply indicating there is a problem.

Waiting for others to blindly ask questions can be counter-productive – typically, nobody has a at their disposal – Instead, please help others to make informed suggestions, based on information you provide.

---

Update Announcements

The Update Announcements contain important information and a Known Issues and Solutions section that should generally be checked before posting a request for support.

System Information

While information from *-fetch type apps might be fine for someone wishing to buy your computer, for Support purposes it’s better to ask your system directly;

Output of the inxi command (with appropriate parameters, and formatted according to forum guidelines) will generate information useful for those wishing to help:

inxi --filter --verbosity=8

or the short form (preferred):

inxi -zv8

• inxi man pages (Arch Manual)

@Running `inxi` in `chroot`

If you need to run inxi from within a chroot environment, and find the output is laced with unexpected 12’s, please try again with:

• Add to the long form command: --color=0
• or, change the short form to: inxi -zv8c0

@Your privacy is respected

When inxi is run using the --filter or -z parameters, any personally identifiable information is filtered from the resulting output.

Highly Recommended

• How to Post
• How to Request Support
• How to Post Command Output as Preformatted Text

Technical Resources

• Manjaro Update Announcements
• Manjaro Wiki
• Arch Wiki
• Tutorials

Required Reading

• Forum Rules
• Strict Forum Rules and Guidelines

---

@Notice

The above content is partially pre-prepared as an introduction for new or returning forum Users. Please take the time to follow any links given and discover how to use the Manjaro forum features effectively.

[linux-aarhus]

Since you are using stable branch it is likely the issue has been solved with the next plasma release.

 $ mbn info plasma-desktop -q
Branch         : archlinux
Name           : plasma-desktop
Version        : 6.4.5-4
Repository     : extra
Build Date     : Fri 10 Oct 2025 15:37:03 
Packager       : Antonio Rojas <arojas@archlinux.org>
Branch         : unstable
Name           : plasma-desktop
Version        : 6.4.5-4
Repository     : extra
Build Date     : Fri 10 Oct 2025 15:37:03 
Packager       : Antonio Rojas <arojas@archlinux.org>
Branch         : testing
Name           : plasma-desktop
Version        : 6.4.5-4
Repository     : extra
Build Date     : Fri 10 Oct 2025 15:37:03 
Packager       : Antonio Rojas <arojas@archlinux.org>
Branch         : stable
Name           : plasma-desktop
Version        : 6.3.6-1
Repository     : extra
Build Date     : Tue 08 Jul 2025 18:10:33 
Packager       : Manjaro Build Server <build@manjaro.org>

[ypihoh]

Thanks for the REISUB tip! It helped me retrieve control of my screen and it could help me get more info on that hdmi-wayland problem…. but I have little time to follow all the troubleshooting process and report as I am indeed an infrequent forum user.

I’ll probably roll back and wait for the next update to see if the problem is still there. Hoping it’s not… or try other things in between. I’ll keep you posted if somethings comes up.

Thank you very much for the answers!

[soundofthunder]

@ypihoh

I have little time to follow all the troubleshooting process and report as I am indeed an infrequent forum user.

Unfortunately, it’s part of the process; it’s normally suggested to make time, especially given that minimal information can often point in many directions.

@ypihoh

I’ll probably roll back and wait for the next update … I’ll keep you posted if somethings comes up.

The topic has been closed without a solution.

If you discover the issue persists beyond the next influx of updates, ask a Moderation staff member to re-open this topic, if you like.

Make sure to add a full description of additional details you might have found in the meantime.

Regards.