Unable to turn on second monitor

[benwu25]

Wayfire version

0.11.0-ad2c781a (Feb 21 2026) branch HEAD wlroots-0.19.2

GPU / Driver

Please provide your GPU model and driver version. This information can be found in:

• glxinfo -B
• vulkaninfo --summary

==========
VULKANINFO
==========

Vulkan Instance Version: 1.4.328


Instance Extensions: count = 25
-------------------------------
VK_EXT_acquire_drm_display             : extension revision 1
VK_EXT_acquire_xlib_display            : extension revision 1
VK_EXT_debug_report                    : extension revision 10
VK_EXT_debug_utils                     : extension revision 2
VK_EXT_direct_mode_display             : extension revision 1
VK_EXT_display_surface_counter         : extension revision 1
VK_EXT_headless_surface                : extension revision 1
VK_EXT_surface_maintenance1            : extension revision 1
VK_EXT_swapchain_colorspace            : extension revision 5
VK_KHR_device_group_creation           : extension revision 1
VK_KHR_display                         : extension revision 23
VK_KHR_external_fence_capabilities     : extension revision 1
VK_KHR_external_memory_capabilities    : extension revision 1
VK_KHR_external_semaphore_capabilities : extension revision 1
VK_KHR_get_display_properties2         : extension revision 1
VK_KHR_get_physical_device_properties2 : extension revision 2
VK_KHR_get_surface_capabilities2       : extension revision 1
VK_KHR_portability_enumeration         : extension revision 1
VK_KHR_surface                         : extension revision 25
VK_KHR_surface_protected_capabilities  : extension revision 1
VK_KHR_wayland_surface                 : extension revision 6
VK_KHR_xcb_surface                     : extension revision 6
VK_KHR_xlib_surface                    : extension revision 6
VK_LUNARG_direct_driver_loading        : extension revision 1
VK_NV_display_stereo                   : extension revision 1

Instance Layers: count = 5
--------------------------
VK_LAYER_MESA_anti_lag      Open-source implementation of the VK_AMD_anti_lag extension. 1.4.303  version 1
VK_LAYER_MESA_device_select Linux device selection layer                                 1.4.303  version 1
VK_LAYER_MESA_overlay       Mesa Overlay layer                                           1.4.303  version 1
VK_LAYER_NV_optimus         NVIDIA Optimus layer                                         1.4.312  version 1
VK_LAYER_NV_present         NVIDIA GR2608 layer                                          1.4.312  version 1

Devices:
========
GPU0:
	apiVersion         = 1.4.312
	driverVersion      = 580.126.9.0
	vendorID           = 0x10de
	deviceID           = 0x1c03
	deviceType         = PHYSICAL_DEVICE_TYPE_DISCRETE_GPU
	deviceName         = NVIDIA GeForce GTX 1060 6GB
	driverID           = DRIVER_ID_NVIDIA_PROPRIETARY
	driverName         = NVIDIA
	driverInfo         = 580.126.09
	conformanceVersion = 1.4.1.3
	deviceUUID         = f7f6167a-387c-4c67-585f-a48905382a47
	driverUUID         = 9756eed7-117e-56eb-8928-8e249b39bb59
GPU1:
	apiVersion         = 1.4.328
	driverVersion      = 25.3.3
	vendorID           = 0x8086
	deviceID           = 0x5912
	deviceType         = PHYSICAL_DEVICE_TYPE_INTEGRATED_GPU
	deviceName         = Intel(R) HD Graphics 630 (KBL GT2)
	driverID           = DRIVER_ID_INTEL_OPEN_SOURCE_MESA
	driverName         = Intel open-source Mesa driver
	driverInfo         = Mesa 25.3.3
	conformanceVersion = 1.4.0.0
	deviceUUID         = 86801259-0400-0000-0002-000000000000
	driverUUID         = 5c10bf6e-db0c-8eff-68fa-3dc1cfcf1172

Describe the bug

Hi, I set up my monitors in wayfire.ini like this:

[output:HDMI-A-3]
mode = 1920x1080
position = 0,0
transform = normal
scale = 1.000000

[output:HDMI-A-2]
mode = 1920x1080
mode = off
position = 0,1080
transform = normal
scale = 1.000000

and upon logging in, wlr-randr output is

HDMI-A-3 "HP Inc. HP VH240a 6CM9240214 (HDMI-A-3)"
  Make: HP Inc.
  Model: HP VH240a
  Serial: 6CM9240214
  Physical size: 530x300 mm
  Enabled: yes
  Modes:
    1920x1080 px, 60.000000 Hz (preferred, current)
    1920x1080 px, 59.938999 Hz
    1920x1080 px, 50.000000 Hz
    1680x1050 px, 59.953999 Hz
    1600x900 px, 60.000000 Hz
    1280x1024 px, 60.020000 Hz
    1440x900 px, 59.887001 Hz
    1280x800 px, 59.810001 Hz
    1280x720 px, 60.000000 Hz
    1280x720 px, 59.943001 Hz
    1280x720 px, 50.000000 Hz
    1024x768 px, 60.004002 Hz
    800x600 px, 60.317001 Hz
    720x576 px, 50.000000 Hz
    720x480 px, 59.939999 Hz
    640x480 px, 59.939999 Hz
    640x480 px, 59.929001 Hz
  Position: 0,0
  Transform: normal
  Scale: 1.000000
  Adaptive Sync: disabled
HDMI-A-2 "Dell Inc. DELL S2715H V14F367MA7ML (HDMI-A-2)"
  Make: Dell Inc.
  Model: DELL S2715H
  Serial: V14F367MA7ML
  Physical size: 600x340 mm
  Enabled: no
  Modes:
    1920x1080 px, 60.000000 Hz (preferred)
    1920x1080 px, 60.000000 Hz
    1920x1080 px, 59.939999 Hz
    1920x1080 px, 50.000000 Hz
    1600x900 px, 60.000000 Hz
    1280x1024 px, 75.025002 Hz
    1280x1024 px, 60.020000 Hz
    1152x864 px, 75.000000 Hz
    1280x720 px, 60.000000 Hz
    1280x720 px, 60.000000 Hz
    1280x720 px, 59.939999 Hz
    1280x720 px, 50.000000 Hz
    1024x768 px, 75.028999 Hz
    1024x768 px, 60.004002 Hz
    800x600 px, 75.000000 Hz
    800x600 px, 60.317001 Hz
    720x576 px, 50.000000 Hz
    720x576 px, 50.000000 Hz
    720x480 px, 60.000000 Hz
    720x480 px, 60.000000 Hz
    720x480 px, 59.939999 Hz
    720x480 px, 59.939999 Hz
    720x480 px, 59.939999 Hz
    640x480 px, 75.000000 Hz
    640x480 px, 60.000000 Hz
    640x480 px, 59.939999 Hz
    640x480 px, 59.939999 Hz
    720x400 px, 70.082001 Hz

Then, running wlr-randr --output HDMI-A-2 --on does nothing. It exists successfully but the monitor stays black, and the output of wlr-randr is the same as it was.

Additional context

Also, I used to have sddm configured to show the greeter on both menus, via xrandr. When this was enabled, I would log into wayfire and the greeter would stay on HDMI-A-2. Then, upon trying to move the first window that is opened, the entire UI freezes and I have to shut down my computer.

Also, both monitors work on Hyprland, and wlr-randr can toggle them successfully. So I doubt it's a kernel or driver issue.

Expected behavior

Wayfire enables both monitors and runs with both monitors with no freezing.

[soreau]

Wayfire version

0.11.0-ad2c781a (Feb 21 2026) branch HEAD wlroots-0.19.2

Hi, I set up my monitors in wayfire.ini like this:

[output:HDMI-A-3]
mode = 1920x1080
position = 0,0
transform = normal
scale = 1.000000

[output:HDMI-A-2]
mode = 1920x1080
mode = off
position = 0,1080
transform = normal
scale = 1.000000

If I understand correctly, you are overriding your apparent intended mode with mode = off for HDMI-A-2. Does it help if you remove this line from your config?

[benwu25]

Sorry, that was there while debugging but removing it doesn't affect anything. Even if HDMI-A-2 was off initially because of this config, wouldn't wlr-randr be able to turn the monitor on after starting up?

[soreau]

Are you able to test with another wlroots compositor such as sway or labwc, using the same version of wlroots 0.19.2? If it also does not work under other wlroots compositors, the problem is not with wayfire, but more likely a wlroots or general driver issue.

[benwu25]

I installed sway and logged in, and I was met with a black screen and a cursor only, though the cursor was able to move between both monitors. Terminal wouldn't open, also couldn't exit. So I assume it's not a wayfire problem then?

[soreau]

Well it might be the case that no clients were started, but this seems strange. If you know the WAYLAND_DISPLAY name, you can set it to start a client from another shell like ssh or another tty by running e.g. WAYLAND_DISPLAY=wayland-1 terminal. But if you have a mouse on both outputs and no errors in the logs, this is a good indication it enabled the output successfully. Check the output with something like sway -d &> ~/sway.log.

[benwu25]

The last lines of sway.log warn

00:00:00.002 [ERROR] [sway/server.c:163] !!! Proprietary Nvidia drivers are in use !!!
93 00:00:00.002 [ERROR] [sway/server.c:165] Use Nouveau instead
94 00:00:00.002 [ERROR] [sway/server.c:175] Proprietary drivers are NOT supported. To launch sway anyway, launch with --unsupporte   d-gpu and DO NOT report issues.

I was searching online earlier about this sway issue and one Arch linux forum thread suggested someone did fix it by disabling nvidia in some way, so this coheres with that thread. I don't remember seeing anywhere that proprietary drivers were incompatible with wayfire? Would it be worth trying open source drivers?

[soreau]

What I am thinking, is that since you have a setup with multiple GPUs, it could be that one monitor is connected to one GPU CRTC and the other is connecting to the other GPU CRTC, which might make things confusing for the compositor. I would recommend trying to start wayfire with different render nodes by setting WLR_RENDER_DRM_DEVICE to one of the nodes in /dev/dri/renderD12*. You can also try disabling EGL and DRM modifiers and even WLR_DRM_DEVICES set to target /dev/dri/card*. Hopefully you can figure out how to get wayfire working. See the wlroots docs for reference.

[soreau]

I don't remember seeing anywhere that proprietary drivers were incompatible with wayfire? Would it be worth trying open source drivers?

Many users use nvidia proprietary drivers with wayfire with varying degrees of success, so it can work.

[benwu25]

You wouldn't believe it, but both monitors end up working if nvidia drivers aren't loaded! So at least there's that temporary solution, and the output quality is just fine, no flickering like on Hyprland. I just did sudo mv /etc/modprobe.d/nvidia.conf ~/ and restarted and both monitors worked on entering wayfire. I'm not too sure what I would do next to try to debug the driver issue, but either way I'm happier. Actually, I'm not even sure if I prevented nvidia drivers from loading, since glxinfo indicates that direct rendering is enabled.

[benwu25]

Output of vulkaninfo --summary after the above change. I guess wayfire is using direct rendering on the integrated GPU?

==========
VULKANINFO
==========

Vulkan Instance Version: 1.4.328


Instance Extensions: count = 25
-------------------------------
VK_EXT_acquire_drm_display             : extension revision 1
VK_EXT_acquire_xlib_display            : extension revision 1
VK_EXT_debug_report                    : extension revision 10
VK_EXT_debug_utils                     : extension revision 2
VK_EXT_direct_mode_display             : extension revision 1
VK_EXT_display_surface_counter         : extension revision 1
VK_EXT_headless_surface                : extension revision 1
VK_EXT_surface_maintenance1            : extension revision 1
VK_EXT_swapchain_colorspace            : extension revision 5
VK_KHR_device_group_creation           : extension revision 1
VK_KHR_display                         : extension revision 23
VK_KHR_external_fence_capabilities     : extension revision 1
VK_KHR_external_memory_capabilities    : extension revision 1
VK_KHR_external_semaphore_capabilities : extension revision 1
VK_KHR_get_display_properties2         : extension revision 1
VK_KHR_get_physical_device_properties2 : extension revision 2
VK_KHR_get_surface_capabilities2       : extension revision 1
VK_KHR_portability_enumeration         : extension revision 1
VK_KHR_surface                         : extension revision 25
VK_KHR_surface_protected_capabilities  : extension revision 1
VK_KHR_wayland_surface                 : extension revision 6
VK_KHR_xcb_surface                     : extension revision 6
VK_KHR_xlib_surface                    : extension revision 6
VK_LUNARG_direct_driver_loading        : extension revision 1
VK_NV_display_stereo                   : extension revision 1

Instance Layers: count = 5
--------------------------
VK_LAYER_MESA_anti_lag      Open-source implementation of the VK_AMD_anti_lag extension. 1.4.303  version 1
VK_LAYER_MESA_device_select Linux device selection layer                                 1.4.303  version 1
VK_LAYER_MESA_overlay       Mesa Overlay layer                                           1.4.303  version 1
VK_LAYER_NV_optimus         NVIDIA Optimus layer                                         1.4.312  version 1
VK_LAYER_NV_present         NVIDIA GR2608 layer                                          1.4.312  version 1

Devices:
========
GPU0:
	apiVersion         = 1.4.328
	driverVersion      = 25.3.3
	vendorID           = 0x8086
	deviceID           = 0x5912
	deviceType         = PHYSICAL_DEVICE_TYPE_INTEGRATED_GPU
	deviceName         = Intel(R) HD Graphics 630 (KBL GT2)
	driverID           = DRIVER_ID_INTEL_OPEN_SOURCE_MESA
	driverName         = Intel open-source Mesa driver
	driverInfo         = Mesa 25.3.3
	conformanceVersion = 1.4.0.0
	deviceUUID         = 86801259-0400-0000-0002-000000000000
	driverUUID         = 5c10bf6e-db0c-8eff-68fa-3dc1cfcf1172

[soreau]

Check the output of wayfire to know for sure. You can use something like wayfire -d wlroots &> ~/wayfire.log.