You are not logged in.

Pages: 1

#1 Yesterday 07:33:04

bonjovi2030
Member
Registered: Yesterday
Posts: 4

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 

 [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??

Last edited by bonjovi2030 (Today 09:29:25)

Offline

#2 Yesterday 12:00:35

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 (Yesterday 14:44:26)

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

Also now with avatar logo included!

Offline

#3 Yesterday 12:23:30

5hridhyan
Member
Registered: 2025-12-25
Posts: 1,047
Website

Re: Error when trying to open hyprland after installation

Hyprland has crashed sad 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 (Yesterday 12:32:11)

Offline

#4 Yesterday 13:31:29

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,657

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

Offline

#5 Today 06:33:09

bonjovi2030
Member
Registered: Yesterday
Posts: 4

Re: Error when trying to open hyprland after installation

bonjovi2030 wrote:

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

 [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 INVALI
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??

Offline

#6 Today 06:39:33

bonjovi2030
Member
Registered: Yesterday
Posts: 4

Re: Error when trying to open hyprland after installation

Succulent of your garden wrote:

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.

I do not have an external gpu, if it helps this is a thinkpad T410, before i just installed arch, hyprland (also kitty) and gnome (which works fine). I also downloaded ly display manager which detects hyprland but then the same error happens that i get if i want to use start-hyprland

Offline

#7 Today 06:59:38

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,657

Re: Error when trying to open hyprland after installation

You were supposed to edit your post, not full-quote it.
Also

5hridhyan wrote:

Can you post the entire crash report?

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

Offline

#8 Today 09:28:03

bonjovi2030
Member
Registered: Yesterday
Posts: 4

Re: Error when trying to open hyprland after installation

the entire crash report is here 


 --------------------------------------------
   Hyprland Crash Report
--------------------------------------------
Who tried dividing by zero?!

Hyprland received signal 6(ABRT)
Version: efb50993780079460b0cbed1363e2166a2de1d9f
Tag: v0.56.2
Date: Wed Aug 5 14:13:21 2026
Flags:

System info:
	System name: Linux
	Node name: Ernest-archbtw
	Release: 7.1.11-arch1-1
	Version: #1 SMP PREEMPT_DYNAMIC Fri, 28 Aug 2026 03:36:07 +0000

GPU:
	00:02.0 VGA compatible controller [0300]: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller])


os-release:
	NAME="Arch Linux"
	PRETTY_NAME="Arch Linux"
	ID=arch
	BUILD_ID=rolling
	ANSI_COLOR="38;2;23;147;209"
	HOME_URL="https://archlinux.org/"
	DOCUMENTATION_URL="https://wiki.archlinux.org/"
	SUPPORT_URL="https://bbs.archlinux.org/"
	BUG_REPORT_URL="https://gitlab.archlinux.org/groups/archlinux/-/issues"
	PRIVACY_POLICY_URL="https://terms.archlinux.org/docs/privacy-policy/"
	LOGO=archlinux-logo

Libraries:
Hyprgraphics: built against 0.5.1, system has 0.5.1
Hyprutils: built against 0.14.0, system has 0.14.1
Hyprcursor: built against 0.1.13, system has 0.1.13
Hyprlang: built against 0.6.8, system has 0.6.8
Aquamarine: built against 0.14.0, system has 0.14.0

Backtrace:
	#0 | Hyprland(_Z12getBacktracev+0x73) [0x556cb1cb8473]
		getBacktrace()
		??:?
	#1 | Hyprland(_ZN13CrashReporter18createAndSaveCrashEi+0xad4) [0x556cb1bdc954]
		CrashReporter::createAndSaveCrash(int)
		??:?
	#2 | Hyprland(+0x3bc7ee) [0x556cb1ab27ee]
		void std::println<>(_IO_FILE*, std::basic_format_string<char>)
		??:?
	#3 | /usr/lib/libc.so.6(+0x3e6f0) [0x7fe13403e6f0]
		??
		??:0
	#4 | /usr/lib/libc.so.6(+0x9a17c) [0x7fe13409a17c]
		??
		??:0
	#5 | /usr/lib/libc.so.6(gsignal+0x20) [0x7fe13403e5d0]
		??
		??:0
	#6 | Hyprland(+0x230238) [0x556cb1926238]
		void assertImpl<int&, int&>(int, std::basic_string_view<char, std::char_traits<char> >, std::basic_format_string<char, std::type_identity<int&>::type, std::type_identity<int&>::type>, int&, int&)
		??:?
	#7 | Hyprland(_ZN6Render2GL15CHyprOpenGLImplC1Ev+0xb2f) [0x556cb20bcc5f]
		Render::GL::CHyprOpenGLImpl::CHyprOpenGLImpl()
		??:?
	#8 | Hyprland(_ZN11CCompositor12initManagersE18eManagersInitStage+0xf68) [0x556cb1ab9638]
		CCompositor::initManagers(eManagersInitStage)
		??:?
	#9 | Hyprland(_ZN11CCompositor10initServerENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEi+0x1621) [0x556cb1abedf1]
		CCompositor::initServer(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, int)
		??:?
	#10 | Hyprland(main+0x10e1) [0x556cb1972cb1]
		main
		??:?
	#11 | /usr/lib/libc.so.6(+0x27781) [0x7fe134027781]
		??
		??:0
	#12 | /usr/lib/libc.so.6(__libc_start_main+0x89) [0x7fe1340278b9]
		??
		??:0
	#13 | Hyprland(_start+0x25) [0x556cb1a9b5e5]
		_start
		??:?


Log tail:
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

Offline

#9 Today 12:43:22

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,657

Re: Error when trying to open hyprland after installation

eglinfo -B
glxinfo -B
vulkaninfo --summary

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

Offline

Pages: 1

Board footer

Powered by FluxBB