[Bug]: External monitor connected cause black wallpaper + no waybar

[Karanxidhu]

Bug Report

Description

I am using a external monitor with my laptop. For that i have to use multi-gpu env to enable gpu for external monitor for high refresh rate.
Multi-GPU

It was working fine before the latest nvidia graphics driver update ig, but now when i enable the external monitor only as my laptop dont support hybrid gpu. Only cursor and rofi is visible, disabling / disappearing waybar + wallpaper etc.

Steps to Reproduce

1. fresh install HyDE
2. add the dedicated card from Multi-GPU
3. reboot

Expected Behavior

my laptop screen should be blank, and external monitor should work normally on high refreshrate.

Actual Behavior

my laptop screen is blank, external monitor showing cursor, wallpaper black + no waybar + frequent crashes like cant open firefox but chrome is launching.

Screenshots

Environment

• Linux Distro: ArchLinux
• Linux Version, output of uname -a: Linux archlinux 6.13.2-arch1-1 v0.1.0 #1 SMP PREEMPT_DYNAMIC Sat, 08 Feb 2025 18:54:55 +0000 x86_64 GNU/Linux
• Hyprland Version, output of hyprctl version: HYPRLAND_INSTANCE_SIGNATURE not set! (is hyprland running?)
• Installation Environment: On The Main Hardware
• Other info: resolution 2560x1440@120

[kRHYME7]

what happens when you select a theme?

[kRHYME7]

can you open a terminal in there?

[kRHYME7]

@Karanxidhu This might be a compositor issue, Try to use hyprland-git first. If it was not fixed already open an issue in the Hyprland GitHub.

[Karanxidhu]

so nothing happens when i change theme and yes terminal opens.
Okay i will try that can you just give me the steps for the same.
Edit: but it was working smoothly with the versions before jan this year.

[kRHYME7]

There's nothing changed in the configs regarding rendering. And I can't find any breaking changes. This might be a regression in Hyprland.

[Olaipai]

How are you logging in?
If using SDDM - Double check that you are using Hyprland and not Hyprland-uwsm.

Other than that you would need to provide logs, envs and monitor config file.

I've had something similar happen when having a monitor with a position way off what is expected. This can also happen when logging in with UWSM without the bare minimum required causing issues.

I have also had this happened on dGPU after messing with the boilerplate config and or blanking out env.vars from the sourced file in conf_home.