Arch Linux

bonjovi2030

Member

Registered: Today

Posts: 1

Error when trying to open hyprland after installation

I installed hyprland through sudo yay -S hyprland, and after trying to open it with start-hyprland i got a lot of errors

WARN ]: Failed to change process scheduling strategy
DEBUG ]: Old rlimit: soft -> 1024, hard -> 524288
DEBUG ]: New rlimit: soft -> 524288, hard -> 524288
DEBUG ]: Creating the EventLoopManager!
DEBUG ]: Creating the KeybindManager!
DEBUG ]: Creating the AnimationManager!
DEBUG ]: Creating the DynamicPermissionManager!
DEBUG ]: Creating the MonitorState!
DEBUG ]: Creating the WorkspaceState!
DEBUG ]: Creating the ConfigManager!
DEBUG ]: [cfg] Regular config at /home/Filip/.config/hypr/hyprland.lua
DEBUG ]: [cfg] Using lua config found at /home/Filip/.config/hypr/hyprland.lua
DEBUG ]: Creating the Error Overlay!
DEBUG ]: Creating the LayoutManager!
DEBUG ]: Creating the TokenManager!
DEBUG ]: Creating the EventManager!
DEBUG ]: Disabling stdout logs (debug.enable_stdout_logs = 0). Further logs will be written to /run/user/1000/hypr/efb50993780079460b0cbed1363e2166a2de1d9f_1788334249_670703651/hyprland.log
DEBUG ]: Creating the PointerManager!
DEBUG ]: Creating the AsyncResourceGatherer!
Hyprland has crashed Consult the crash report at /home/Filip/.cache/hyprland/hyprlandCrashReport5391.txt for more information.
ERR from start-hyprland ]: Couldn't waitpid for hyprland: No child processes
DEBUG from start-hyprland ]: hyprland exit, breaking poll, checking state
DEBUG from start-hyprland ]: Hyprland exit cleanly.

The crash report says this

DEBUG from aquamarine ]: zwp_linux_dmabuf_v1: Got format S216 with modifier INVALID
DEBUG from aquamarine ]: zwp_linux_dmabuf_v1: Got format S416 with modifier LINEAR
DEBUG from aquamarine ]: zwp_linux_dmabuf_v1: Got format S416 with modifier X_TILED
DEBUG from aquamarine ]: zwp_linux_dmabuf_v1: Got format S416 with modifier INVALID
DEBUG from aquamarine ]: zwp_linux_dmabuf_v1: Got format NV12 with modifier LINEAR
DEBUG from aquamarine ]: zwp_linux_dmabuf_v1: Got format NV12 with modifier X_TILED
DEBUG from aquamarine ]: zwp_linux_dmabuf_v1: Got format NV12 with modifier INVALID
DEBUG from aquamarine ]: zwp_linux_dmabuf_v1: Got format NV21 with modifier LINEAR
DEBUG from aquamarine ]: zwp_linux_dmabuf_v1: Got format NV21 with modifier X_TILED
DEBUG from aquamarine ]: zwp_linux_dmabuf_v1: Got format NV21 with modifier INVALID
DEBUG from aquamarine ]: zwp_linux_dmabuf_v1: Got format P010 with modifier LINEAR
DEBUG from aquamarine ]: zwp_linux_dmabuf_v1: Got format P010 with modifier X_TILED
DEBUG from aquamarine ]: zwp_linux_dmabuf_v1: Got format P010 with modifier INVALID
DEBUG from aquamarine ]: zwp_linux_dmabuf_v1: Got format P012 with modifier LINEAR
DEBUG from aquamarine ]: zwp_linux_dmabuf_v1: Got format P012 with modifier X_TILED
DEBUG from aquamarine ]: zwp_linux_dmabuf_v1: Got format P012 with modifier INVALID
DEBUG from aquamarine ]: zwp_linux_dmabuf_v1: Got format P016 with modifier LINEAR
DEBUG from aquamarine ]: zwp_linux_dmabuf_v1: Got format P016 with modifier X_TILED
DEBUG from aquamarine ]: zwp_linux_dmabuf_v1: Got format P016 with modifier INVALID
DEBUG from aquamarine ]: zwp_linux_dmabuf_v1: Got format NV16 with modifier LINEAR
DEBUG from aquamarine ]: zwp_linux_dmabuf_v1: Got format NV16 with modifier X_TILED
DEBUG from aquamarine ]: zwp_linux_dmabuf_v1: Got format NV16 with modifier INVALID
DEBUG from aquamarine ]: zwp_linux_dmabuf_v1: Got format NV61 with modifier LINEAR
DEBUG from aquamarine ]: zwp_linux_dmabuf_v1: Got format NV61 with modifier X_TILED
DEBUG from aquamarine ]: zwp_linux_dmabuf_v1: Got format NV61 with modifier INVALID
DEBUG from aquamarine ]: zwp_linux_dmabuf_v1: Got format NV24 with modifier LINEAR
DEBUG from aquamarine ]: zwp_linux_dmabuf_v1: Got format NV24 with modifier X_TILED
DEBUG from aquamarine ]: zwp_linux_dmabuf_v1: Got format NV24 with modifier INVALID
DEBUG from aquamarine ]: zwp_linux_dmabuf_v1: Got format NV42 with modifier LINEAR
DEBUG from aquamarine ]: zwp_linux_dmabuf_v1: Got format NV42 with modifier X_TILED
DEBUG from aquamarine ]: zwp_linux_dmabuf_v1: Got format NV42 with modifier INVALID
DEBUG from aquamarine ]: zwp_linux_dmabuf_v1: Got format YUYV with modifier LINEAR
DEBUG from aquamarine ]: zwp_linux_dmabuf_v1: Got format YUYV with modifier X_TILED
DEBUG from aquamarine ]: zwp_linux_dmabuf_v1: Got format YUYV with modifier INVALID
DEBUG from aquamarine ]: zwp_linux_dmabuf_v1: Got format YVYU with modifier LINEAR
DEBUG from aquamarine ]: zwp_linux_dmabuf_v1: Got format YVYU with modifier X_TILED
DEBUG from aquamarine ]: zwp_linux_dmabuf_v1: Got format YVYU with modifier INVALID
DEBUG from aquamarine ]: zwp_linux_dmabuf_v1: Got format UYVY with modifier LINEAR
DEBUG from aquamarine ]: zwp_linux_dmabuf_v1: Got format UYVY with modifier X_TILED
DEBUG from aquamarine ]: zwp_linux_dmabuf_v1: Got format UYVY with modifier INVALID
DEBUG from aquamarine ]: zwp_linux_dmabuf_v1: Got format VYUY with modifier LINEAR
DEBUG from aquamarine ]: zwp_linux_dmabuf_v1: Got format VYUY with modifier X_TILED
DEBUG from aquamarine ]: zwp_linux_dmabuf_v1: Got format VYUY with modifier INVALID
DEBUG from aquamarine ]: zwp_linux_dmabuf_v1: Got main device
DEBUG from aquamarine ]: zwp_linux_dmabuf_v1: Got node /dev/dri/renderD128
DEBUG from aquamarine ]: zwp_linux_dmabuf_v1: Got done
DEBUG from aquamarine ]: zwp_linux_dmabuf_v1: opened node /dev/dri/renderD128 with fd 17
DEBUG from aquamarine ]: Output WAYLAND-1: initialized
DEBUG from aquamarine ]: reopenDRMNode: opening node /dev/dri/renderD128
DEBUG from aquamarine ]: Created a GBM allocator with drm fd 18

Does anyone know how to help??

Succulent of your garden

Member

From: Majestic kingdom of pot plants

Registered: 2024-02-29

Posts: 1,796

Re: Error when trying to open hyprland after installation

Hyprland currently is working fine for users that picks the extra package as you do. Maybe this could be related to the following points:

1) You have not installed yet the "Drivers" for graphics cards.
2) Maybe your hyprland.conf file is making an issue.

But since the debug ends in creating the Generic Buffer Management (GBM), then probably is more related to graphics card issue.

Please check this links if you think the issue is from the GPU:

https://wiki.archlinux.org/title/AMDGPU
https://wiki.archlinux.org/title/NVIDIA

Did you setup your GPU accordingly as the Arch Wiki says ? Let us know and what you had done before and after this post.

Last edited by Succulent of your garden (Today 14:44:26)

---

str( @soyg ) == str( @potplant ) btw!

Also now with avatar logo included!

5hridhyan

Member

Registered: 2025-12-25

Posts: 1,046

Website

Re: Error when trying to open hyprland after installation

Hyprland has crashed Consult the crash report at /home/Filip/.cache/hyprland/hyprlandCrashReport5391.txt

Can you post the entire crash report?

Also, please use [code][/code] tags, and edit your post in this regard

Last edited by 5hridhyan (Today 12:32:11)

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 77,641

Re: Error when trying to open hyprland after installation

trying to open it with start-hyprland

From where? The console? Is there another display server running?

---

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