You are not logged in.

Pages: 1

#1 2025-12-31 11:29:29

nerozero
Member
Registered: 2025-12-31
Posts: 7

[solved] Hyprpaper, Monitor eDP-1 has no target: no wp will be created

Hi there,

After updating the system hyprpaper stops displaying backgrounds.

Debug output of hyprpaper:

DEBUG ]: zwp_linux_dmabuf_v1: Got main device
DEBUG ]: zwp_linux_dmabuf_v1: Got node /dev/dri/renderD128
DEBUG ]: zwp_linux_dmabuf_v1: Got done
DEBUG ]: wayland output 63: name eDP-1
DEBUG ]: wayland output 63: description BOE 0x06EE  (eDP-1)
DEBUG ]: wayland output 63: dimensions [Vector2D: x: 1920, y: 1080]
DEBUG ]: wayland output 63: make BOE model 0x06EE
DEBUG ]: wayland output 63: done
DEBUG ]: zwp_linux_dmabuf_v1: opened node /dev/dri/renderD128 with fd 17
DEBUG ]: Supported EGL global extensions: (16) EGL_EXT_device_base EGL_EXT_device_enumeration EGL_EXT_device_query EGL_EXT_platform_base EGL_KHR_client_get_all_proc_addresses EGL_EXT_client_extensions EGL_KHR_debug EGL_EXT_platform_device EGL_EXT_explicit_device EGL_EXT_platform_wayland EGL_KHR_platform_wayland EGL_EXT_platform_x11 EGL_KHR_platform_x11 EGL_EXT_platform_xcb EGL_MESA_platform_gbm EGL_KHR_platform_gbm EGL_MESA_platform_surfaceless
DEBUG ]: eglDeviceFromDRMFD: Using device /dev/dri/card1
DEBUG ]: EGL: IMG_context_priority supported, requesting high
DEBUG ]: EGL: EXT_create_context_robustness supported, requesting lose on reset
DEBUG ]: EGL: Got a high priority context
DEBUG ]: DRM syncobj timeline support: yes
DEBUG ]: Found 1 output(s)
DEBUG ]: Monitor eDP-1 has no target: no wp will be created

Output of `hyprctl monitors`:

hyprctl monitors
Monitor eDP-1 (ID 0):
        1920x1080@60.00600 at 0x0
        description: BOE 0x06EE
        make: BOE
        model: 0x06EE
        physical size (mm): 310x170
        serial:
        active workspace: 3 (3)
        special workspace: 0 ()
        reserved: 0 37 0 0
        scale: 1.00
        transform: 0
        focused: yes
        dpmsStatus: 1
        vrr: false
        solitary: 0
        solitaryBlockedBy: windowed mode,missing candidate
        activelyTearing: false
        tearingBlockedBy: next frame is not torn,user settings,missing candidate
        directScanoutTo: 0
        directScanoutBlockedBy: user settings,missing candidate
        disabled: false
        currentFormat: XRGB8888
        mirrorOf: none
        availableModes: 1920x1080@60.01Hz 1920x1080@48.01Hz
        colorManagementPreset: srgb
        sdrBrightness: 1.00
        sdrSaturation: 1.00
        sdrMinLuminance: 0.20
        sdrMaxLuminance: 80

Thanks in advance.

Last edited by nerozero (2026-01-02 17:08:06)

Offline

#2 2025-12-31 11:35:30

Bikolyn
Member
Registered: 2025-12-31
Posts: 3

Re: [solved] Hyprpaper, Monitor eDP-1 has no target: no wp will be created

Having this issue! Dell latitude 3300

DEBUG ]: Welcome to hyprpaper!
built from commit  ()
DEBUG ]: Starting the Wayland platform
DEBUG ]: Connected to a wayland compositor: Hyprland
DEBUG ]: Got registry at 0x5bde50847e30
DEBUG ]: zwp_linux_dmabuf_v1: Got format AB4H with modifier LINEAR
DEBUG ]: zwp_linux_dmabuf_v1: Got format AB4H with modifier X_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format AB4H with modifier Y_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format AB4H with modifier Y_TILED_CCS
DEBUG ]: zwp_linux_dmabuf_v1: Got format AB4H with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format XB4H with modifier LINEAR
DEBUG ]: zwp_linux_dmabuf_v1: Got format XB4H with modifier X_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format XB4H with modifier Y_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format XB4H with modifier Y_TILED_CCS
DEBUG ]: zwp_linux_dmabuf_v1: Got format XB4H with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format AB48 with modifier LINEAR
DEBUG ]: zwp_linux_dmabuf_v1: Got format AB48 with modifier X_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format AB48 with modifier Y_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format AB48 with modifier Y_TILED_CCS
DEBUG ]: zwp_linux_dmabuf_v1: Got format AB48 with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format XB48 with modifier LINEAR
DEBUG ]: zwp_linux_dmabuf_v1: Got format XB48 with modifier X_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format XB48 with modifier Y_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format XB48 with modifier Y_TILED_CCS
DEBUG ]: zwp_linux_dmabuf_v1: Got format XB48 with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format AR30 with modifier LINEAR
DEBUG ]: zwp_linux_dmabuf_v1: Got format AR30 with modifier X_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format AR30 with modifier Y_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format AR30 with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format XR30 with modifier LINEAR
DEBUG ]: zwp_linux_dmabuf_v1: Got format XR30 with modifier X_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format XR30 with modifier Y_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format XR30 with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format AB30 with modifier LINEAR
DEBUG ]: zwp_linux_dmabuf_v1: Got format AB30 with modifier X_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format AB30 with modifier Y_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format AB30 with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format XB30 with modifier LINEAR
DEBUG ]: zwp_linux_dmabuf_v1: Got format XB30 with modifier X_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format XB30 with modifier Y_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format XB30 with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format AR24 with modifier LINEAR
DEBUG ]: zwp_linux_dmabuf_v1: Got format AR24 with modifier X_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format AR24 with modifier Y_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format AR24 with modifier Y_TILED_CCS
DEBUG ]: zwp_linux_dmabuf_v1: Got format AR24 with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format AB24 with modifier LINEAR
DEBUG ]: zwp_linux_dmabuf_v1: Got format AB24 with modifier X_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format AB24 with modifier Y_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format AB24 with modifier Y_TILED_CCS
DEBUG ]: zwp_linux_dmabuf_v1: Got format AB24 with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format XR24 with modifier LINEAR
DEBUG ]: zwp_linux_dmabuf_v1: Got format XR24 with modifier X_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format XR24 with modifier Y_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format XR24 with modifier Y_TILED_CCS
DEBUG ]: zwp_linux_dmabuf_v1: Got format XR24 with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format XB24 with modifier LINEAR
DEBUG ]: zwp_linux_dmabuf_v1: Got format XB24 with modifier X_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format XB24 with modifier Y_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format XB24 with modifier Y_TILED_CCS
DEBUG ]: zwp_linux_dmabuf_v1: Got format XB24 with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format AR15 with modifier LINEAR
DEBUG ]: zwp_linux_dmabuf_v1: Got format AR15 with modifier X_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format AR15 with modifier Y_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format AR15 with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format AR12 with modifier LINEAR
DEBUG ]: zwp_linux_dmabuf_v1: Got format AR12 with modifier X_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format AR12 with modifier Y_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format AR12 with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format RG16 with modifier LINEAR
DEBUG ]: zwp_linux_dmabuf_v1: Got format RG16 with modifier X_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format RG16 with modifier Y_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format RG16 with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format R8 with modifier LINEAR
DEBUG ]: zwp_linux_dmabuf_v1: Got format R8 with modifier X_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format R8 with modifier Y_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format R8 with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format R16 with modifier LINEAR
DEBUG ]: zwp_linux_dmabuf_v1: Got format R16 with modifier X_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format R16 with modifier Y_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format R16 with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format GR88 with modifier LINEAR
DEBUG ]: zwp_linux_dmabuf_v1: Got format GR88 with modifier X_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format GR88 with modifier Y_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format GR88 with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format GR32 with modifier LINEAR
DEBUG ]: zwp_linux_dmabuf_v1: Got format GR32 with modifier X_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format GR32 with modifier Y_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format GR32 with modifier Y_TILED_CCS
DEBUG ]: zwp_linux_dmabuf_v1: Got format GR32 with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format R  H with modifier LINEAR
DEBUG ]: zwp_linux_dmabuf_v1: Got format R  H with modifier X_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format R  H with modifier Y_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format R  H with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format R  F with modifier LINEAR
DEBUG ]: zwp_linux_dmabuf_v1: Got format R  F with modifier X_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format R  F with modifier Y_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format R  F with modifier Y_TILED_CCS
DEBUG ]: zwp_linux_dmabuf_v1: Got format R  F with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format GR H with modifier LINEAR
DEBUG ]: zwp_linux_dmabuf_v1: Got format GR H with modifier X_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format GR H with modifier Y_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format GR H with modifier Y_TILED_CCS
DEBUG ]: zwp_linux_dmabuf_v1: Got format GR H with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format GR F with modifier LINEAR
DEBUG ]: zwp_linux_dmabuf_v1: Got format GR F with modifier X_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format GR F with modifier Y_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format GR F with modifier Y_TILED_CCS
DEBUG ]: zwp_linux_dmabuf_v1: Got format GR F with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format AB8F with modifier LINEAR
DEBUG ]: zwp_linux_dmabuf_v1: Got format AB8F with modifier X_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format AB8F with modifier Y_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format AB8F with modifier Y_TILED_CCS
DEBUG ]: zwp_linux_dmabuf_v1: Got format AB8F with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format YUV9 with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format YU11 with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format YU12 with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format YU16 with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format YU24 with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format YVU9 with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format YV11 with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format YV12 with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format YV16 with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format YV24 with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format S010 with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format S210 with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format S410 with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format S012 with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format S212 with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format S412 with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format S016 with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format S216 with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format S416 with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format NV12 with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format NV21 with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format P010 with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format P012 with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format P016 with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format P030 with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format NV16 with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format NV61 with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format NV24 with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format NV42 with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format AYUV with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format XYUV with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format Y410 with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format Y412 with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format Y416 with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format YUYV with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format YVYU with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format UYVY with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format VYUY with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format Y210 with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format Y212 with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format Y216 with modifier INVALID
DEBUG ]: zwp_linux_dmabuf_v1: Got format C8 with modifier Y_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format C8 with modifier X_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format RG16 with modifier Yf_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format XR24 with modifier Yf_TILED_CCS
DEBUG ]: zwp_linux_dmabuf_v1: Got format XR24 with modifier Yf_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format XB24 with modifier Yf_TILED_CCS
DEBUG ]: zwp_linux_dmabuf_v1: Got format XB24 with modifier Yf_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format AR24 with modifier Yf_TILED_CCS
DEBUG ]: zwp_linux_dmabuf_v1: Got format AR24 with modifier Yf_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format AB24 with modifier Yf_TILED_CCS
DEBUG ]: zwp_linux_dmabuf_v1: Got format AB24 with modifier Yf_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format XR30 with modifier Yf_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format XB30 with modifier Yf_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format XR4H with modifier Y_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format XR4H with modifier X_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format YUYV with modifier Yf_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format YUYV with modifier Y_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format YUYV with modifier X_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format YVYU with modifier Yf_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format YVYU with modifier Y_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format YVYU with modifier X_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format UYVY with modifier Yf_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format UYVY with modifier Y_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format UYVY with modifier X_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format VYUY with modifier Yf_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format VYUY with modifier Y_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format VYUY with modifier X_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format NV12 with modifier Yf_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format NV12 with modifier Y_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format NV12 with modifier X_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format XYUV with modifier Yf_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format XYUV with modifier Y_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got format XYUV with modifier X_TILED
DEBUG ]: zwp_linux_dmabuf_v1: Got main device
DEBUG ]: zwp_linux_dmabuf_v1: Got node /dev/dri/renderD128
DEBUG ]: zwp_linux_dmabuf_v1: Got done
DEBUG ]: wayland output 63: name eDP-1
DEBUG ]: wayland output 63: description AU Optronics 0x202D  (eDP-1)
DEBUG ]: wayland output 63: dimensions [Vector2D: x: 1920, y: 1080]
DEBUG ]: wayland output 63: make AU Optronics model 0x202D
DEBUG ]: wayland output 63: done
DEBUG ]: zwp_linux_dmabuf_v1: opened node /dev/dri/renderD128 with fd 11
DEBUG ]: Supported EGL global extensions: (16) EGL_EXT_device_base EGL_EXT_device_enumeration EGL_EXT_device_query EGL_EXT_platform_base EGL_KHR_client_get_all_proc_addresses EGL_EXT_client_extensions EGL_KHR_debug EGL_EXT_platform_device EGL_EXT_explicit_device EGL_EXT_platform_wayland EGL_KHR_platform_wayland EGL_EXT_platform_x11 EGL_KHR_platform_x11 EGL_EXT_platform_xcb EGL_MESA_platform_gbm EGL_KHR_platform_gbm EGL_MESA_platform_surfaceless
DEBUG ]: eglDeviceFromDRMFD: Using device /dev/dri/card1
DEBUG ]: EGL: IMG_context_priority supported, requesting high
DEBUG ]: EGL: EXT_create_context_robustness supported, requesting lose on reset
DEBUG ]: EGL: Got a high priority context
DEBUG ]: DRM syncobj timeline support: yes
DEBUG ]: Found 1 output(s)
DEBUG ]: Monitor eDP-1 has no target: no wp will be created

Really weird.

Last edited by Bikolyn (2025-12-31 11:37:10)

Offline

#3 2025-12-31 11:43:34

nerozero
Member
Registered: 2025-12-31
Posts: 7

Re: [solved] Hyprpaper, Monitor eDP-1 has no target: no wp will be created

Latitude 7490:

                   -`                    nerozero@latnz
                  .o+`                   --------------
                 `ooo/                   OS: Arch Linux x86_64
                `+oooo:                  Host: Latitude 7490
               `+oooooo:                 Kernel: 6.18.2-arch2-1
               -+oooooo+:                Uptime: 59 mins
             `/:-:++oooo+:               Packages: 1443 (pacman), 9 (flatpak)
            `/++++/+++++++:              Shell: fish 4.3.2
           `/++++++++++++++:             Resolution: 1920x1080
          `/+++ooooooooooooo/`           Terminal: /dev/pts/3
         ./ooosssso++osssssso+`          CPU: Intel i5-8250U (8) @ 3.400GHz
        .oossssso-````/ossssss+`         GPU: Intel UHD Graphics 620
       -osssssso.      :ssssssso.        Memory: 1937MiB / 7812MiB
      :osssssss/        osssso+++.
     /ossssssss/        +ssssooo/-
   `/ossssso+/:-        -:/+osssso+-
  `+sso+:-`                 `.-/+oso:
 `++:.                           `-/+/
 .`                                 `/

Offline

#4 2025-12-31 11:44:30

BorisC04
Member
Registered: 2025-12-31
Posts: 3

Re: [solved] Hyprpaper, Monitor eDP-1 has no target: no wp will be created

I have the same issue after updating hyprland and hyprpaper as well.
Can't seem to find the issue.

DEBUG ]: zwp_linux_dmabuf_v1: opened node /dev/dri/renderD128 with fd 17
DEBUG ]: Supported EGL global extensions: (16) EGL_EXT_platform_base EGL_EXT_device_base EGL_EXT_device_enumeration EGL_EXT_device_query EGL_KHR_client_get_all_proc_addresses EGL_EXT_client_extensions EGL_KHR_debug EGL_KHR_platform_x11 EGL_EXT_platform_x11 EGL_EXT_platform_device EGL_MESA_platform_surfaceless EGL_EXT_explicit_device EGL_KHR_platform_wayland EGL_EXT_platform_wayland EGL_KHR_platform_gbm EGL_MESA_platform_gbm EGL_EXT_platform_xcb
DEBUG ]: eglDeviceFromDRMFD: Using device /dev/dri/card1
DEBUG ]: EGL: IMG_context_priority supported, requesting high
DEBUG ]: EGL: EXT_create_context_robustness supported, requesting lose on reset
DEBUG ]: EGL: Got a high priority context
DEBUG ]: DRM syncobj timeline support: yes
DEBUG ]: Found 1 output(s)
DEBUG ]: Monitor HDMI-A-1 has no target: no wp will be created

Offline

#5 2025-12-31 12:06:01

Bikolyn
Member
Registered: 2025-12-31
Posts: 3

Re: [solved] Hyprpaper, Monitor eDP-1 has no target: no wp will be created

For now, I switched to SwayBG and it works fine, Has to be a hyprland-update issue.
Probably something not in sync between the hyprland package and the hyprpaper one? Might need time to fix I assume

Offline

#6 2025-12-31 12:27:44

nerozero
Member
Registered: 2025-12-31
Posts: 7

Re: [solved] Hyprpaper, Monitor eDP-1 has no target: no wp will be created

The config syntax has been changed: https://wiki.hypr.land/Hypr-Ecosystem/hyprpaper/

wallpaper {
    monitor = DP-3
    path = ~/myFile.jxl
    fit_mode = cover
}

wallpaper {
    monitor = DP-2
    path = ~/myFile2.jxl
    fit_mode = cover
}

Offline

#7 2025-12-31 12:45:24

BorisC04
Member
Registered: 2025-12-31
Posts: 3

Re: [solved] Hyprpaper, Monitor eDP-1 has no target: no wp will be created

nerozero wrote:

The config syntax has been changed: https://wiki.hypr.land/Hypr-Ecosystem/hyprpaper/

wallpaper {
    monitor = DP-3
    path = ~/myFile.jxl
    fit_mode = cover
}

wallpaper {
    monitor = DP-2
    path = ~/myFile2.jxl
    fit_mode = cover
}

I am aware of that and changed my config to be in the same format as the example but the issue still persisted. Seems like something else is changed in the latest update, not just the config format.

Offline

#8 2025-12-31 12:47:18

nerozero
Member
Registered: 2025-12-31
Posts: 7

Re: [solved] Hyprpaper, Monitor eDP-1 has no target: no wp will be created

BorisC04 wrote:
nerozero wrote:

The config syntax has been changed: https://wiki.hypr.land/Hypr-Ecosystem/hyprpaper/

wallpaper {
    monitor = DP-3
    path = ~/myFile.jxl
    fit_mode = cover
}

wallpaper {
    monitor = DP-2
    path = ~/myFile2.jxl
    fit_mode = cover
}

I am aware of that and changed my config to be in the same format as the example but the issue still persisted. Seems like something else is changed in the latest update, not just the config format.

In my case changing the config fixed the issue. Try to check the monitor and image path

Offline

#9 2025-12-31 15:12:20

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 72,057

Re: [solved] Hyprpaper, Monitor eDP-1 has no target: no wp will be created

@nerozero, has your issue been resolved w/ the config syntax change?
Edit: yes. roll

Everybody else:

ls /sys/class/drm

and what do your configs look like?

Last edited by seth (2025-12-31 15:12:52)

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#10 2026-01-01 08:58:09

BorisC04
Member
Registered: 2025-12-31
Posts: 3

Re: [solved] Hyprpaper, Monitor eDP-1 has no target: no wp will be created

It turns out I forgot to change the wallpaper variable to path when I update my config, so everything works now. Thanks for your help. smile

Last edited by BorisC04 (2026-01-02 10:32:46)

Offline

#11 2026-01-01 08:59:04

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 72,057

Re: [solved] Hyprpaper, Monitor eDP-1 has no target: no wp will be created

\o/
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#12 2026-01-01 21:44:04

BrentCabbage
Member
Registered: 2026-01-01
Posts: 6

Re: [solved] Hyprpaper, Monitor eDP-1 has no target: no wp will be created

I fixed the syntax and I'm having the same issue. Here is my output from ls /sys/class/drm:
card1       card1-DP-2   card1-HDMI-A-1  version
card1-DP-1  card1-eDP-1  renderD128

Offline

#13 2026-01-01 21:47:01

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 72,057

Re: [solved] Hyprpaper, Monitor eDP-1 has no target: no wp will be created

Please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855
What does your config look like and what is the *exact* error message?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#14 2026-01-01 22:00:45

BrentCabbage
Member
Registered: 2026-01-01
Posts: 6

Re: [solved] Hyprpaper, Monitor eDP-1 has no target: no wp will be created

Bottom portion of the debug for hyprpaper:

DEBUG ]: zwp_linux_dmabuf_v1: Got format AB24 with modifier GFX9,64KB_S_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0,DCC,DCC_MAX_COMPRESSED_BLOCK=64B,DCC_INDEPENDENT_64B
DEBUG ]: zwp_linux_dmabuf_v1: Got format AB24 with modifier GFX9,64KB_S_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0,RB=1,PIPE=2,DCC,DCC_MAX_COMPRESSED_BLOCK=64B,DCC_INDEPENDENT_64B,DCC_RETILE
DEBUG ]: zwp_linux_dmabuf_v1: Got format NV12 with modifier GFX9,64KB_S_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0
DEBUG ]: zwp_linux_dmabuf_v1: Got format NV12 with modifier GFX9,64KB_S
DEBUG ]: zwp_linux_dmabuf_v1: Got format P010 with modifier GFX9,64KB_S_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0
DEBUG ]: zwp_linux_dmabuf_v1: Got format P010 with modifier GFX9,64KB_S
DEBUG ]: zwp_linux_dmabuf_v1: Got format XR4H with modifier GFX9,64KB_D_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0
DEBUG ]: zwp_linux_dmabuf_v1: Got format XR4H with modifier GFX9,64KB_S_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0
DEBUG ]: zwp_linux_dmabuf_v1: Got format XR4H with modifier GFX9,64KB_D
DEBUG ]: zwp_linux_dmabuf_v1: Got format XR4H with modifier GFX9,64KB_S
DEBUG ]: zwp_linux_dmabuf_v1: Got format AR4H with modifier GFX9,64KB_D_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0
DEBUG ]: zwp_linux_dmabuf_v1: Got format AR4H with modifier GFX9,64KB_S_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0
DEBUG ]: zwp_linux_dmabuf_v1: Got format AR4H with modifier GFX9,64KB_D
DEBUG ]: zwp_linux_dmabuf_v1: Got format AR4H with modifier GFX9,64KB_S
DEBUG ]: zwp_linux_dmabuf_v1: Got main device
DEBUG ]: zwp_linux_dmabuf_v1: Got node /dev/dri/renderD128
DEBUG ]: zwp_linux_dmabuf_v1: Got done
DEBUG ]: wayland output 63: name eDP-1
DEBUG ]: wayland output 63: description Lenovo Group Limited 0x41B5  (eDP-1)
DEBUG ]: wayland output 63: dimensions [Vector2D: x: 1920, y: 1200]
DEBUG ]: wayland output 63: make Lenovo Group Limited model 0x41B5
DEBUG ]: wayland output 63: done
DEBUG ]: zwp_linux_dmabuf_v1: opened node /dev/dri/renderD128 with fd 11
DEBUG ]: Supported EGL global extensions: (16) EGL_EXT_device_base EGL_EXT_device_enumeration EGL_EXT_device_query EGL_EXT_platform_base EGL_KHR_client_get_all_proc_addresses EGL_EXT_client_extensions EGL_KHR_debug EGL_EXT_platform_device EGL_EXT_explicit_device EGL_EXT_platform_wayland EGL_KHR_platform_wayland EGL_EXT_platform_x11 EGL_KHR_platform_x11 EGL_EXT_platform_xcb EGL_MESA_platform_gbm EGL_KHR_platform_gbm EGL_MESA_platform_surfaceless
DEBUG ]: eglDeviceFromDRMFD: Using device /dev/dri/card1
DEBUG ]: EGL: IMG_context_priority supported, requesting high
DEBUG ]: EGL: EXT_create_context_robustness supported, requesting lose on reset
DEBUG ]: EGL: Got a high priority context
DEBUG ]: DRM syncobj timeline support: yes
DEBUG ]: Found 1 output(s)
DEBUG ]: Monitor eDP-1 has no target: no wp will be created

output from hyprctl monitors:

Monitor eDP-1 (ID 0):
    1920x1200@60.01000 at 0x0
    description: Lenovo Group Limited 0x41B5
    make: Lenovo Group Limited
    model: 0x41B5
    physical size (mm): 340x220
    serial:
    active workspace: 2 (2)
    special workspace: 0 ()
    reserved: 0 0 0 0
    scale: 1.50
    transform: 0
    focused: yes
    dpmsStatus: 1
    vrr: false
    solitary: 0
    solitaryBlockedBy: windowed mode,missing candidate
    activelyTearing: false
    tearingBlockedBy: next frame is not torn,user settings,missing candidate
    directScanoutTo: 0
    directScanoutBlockedBy: user settings,missing candidate
    disabled: false
    currentFormat: XRGB8888
    mirrorOf: none
    availableModes: 1920x1200@60.01Hz 1920x1080@60.01Hz 1600x1200@60.00Hz 1680x1050@60.01Hz 1280x1024@60.01Hz 1440x900@60.01Hz 1280x800@60.01Hz 1280x720@60.01Hz 1024x768@60.01Hz 800x600@60.01Hz 640x480@60.01Hz
    colorManagementPreset: srgb
    sdrBrightness: 1.00
    sdrSaturation: 1.00
    sdrMinLuminance: 0.20
    sdrMaxLuminance: 80

My config file is in ~/.config/hypr/hyprpaper.conf:

wallpaper {
    monitor = eDP-1
    path = home/Cabbage/.config/backgrounds/AestheticLake.jpg
    fit_mode = cover
}

Offline

#15 2026-01-01 22:02:35

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 72,057

Re: [solved] Hyprpaper, Monitor eDP-1 has no target: no wp will be created

- path = home/Cabbage/.config/backgrounds/AestheticLake.jpg
+ path = ~/.config/backgrounds/AestheticLake.jpg
+ path = /home/Cabbage/.config/backgrounds/AestheticLake.jpg

Edit: either of the two options, not both.

Last edited by seth (2026-01-01 22:19:06)

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#16 2026-01-01 22:17:28

BrentCabbage
Member
Registered: 2026-01-01
Posts: 6

Re: [solved] Hyprpaper, Monitor eDP-1 has no target: no wp will be created

seth wrote:
- path = home/Cabbage/.config/backgrounds/AestheticLake.jpg
+ path = ~/.config/backgrounds/AestheticLake.jpg
+ path = /home/Cabbage/.config/backgrounds/AestheticLake.jpg

Edit: either of the to options, not both.

Thank you very much, sir!!

Offline

#17 2026-01-10 19:02:45

AshLake
Member
Registered: 2026-01-10
Posts: 1

Re: [solved] Hyprpaper, Monitor eDP-1 has no target: no wp will be created

They changed the syntax lol here it is
wallpaper{
               monitor = eDP-1
               path = /path/to image.png
               fit_mode = cover
}

Offline

Pages: 1

Board footer

Powered by FluxBB