Hyprland not executing

[morpheuslord]

At the last after all the installation is done, I am facing this error.

What should I do ??

[SolDoesTech]

try this: sudo pacman -S hyprland

[morpheuslord]

Then?. I am stuck in a login loop cause of this

hypr.mp4

[SolDoesTech]

Is this running on a VM?

[morpheuslord]

Is this running on a VM?

yes

[SolDoesTech]

Hello, Hyprland is not meant to run on a VM, the only way I was able to get it to work on a VM is with a GPU passthrough. 3D acceleration could work but its super slow and some programs wont open.

I rebooted the system and it worked

[SolDoesTech]

very nice, is it usable? if so please provide some details about your VM and your GPU. Thanks!

Black lines are coming throughout the whole screen. I think its hyprland's problem.
GPU - Integrated GPU inside Ryzen 5600G
VM - QEMU/KVM with Virt-Manager

[SolDoesTech]

Yeah I would agree its a hyprland issue https://wiki.hyprland.org/Getting-Started/Master-Tutorial/#vm

I didn't knew about that thanks for the info. BTW really appreciate your work though. It looks really cool

[SolDoesTech]

Thank you, glad you like it :)

[morpheuslord]

Then I will try it with a live install

[khar34]

When i try to launch Hyprland, it always results in this error [libseat] [libseat/backend/seatd.c:64 could not connect to socket /run/seatd.sock: No such file or directory
When i solved the no such file problem, it will result in new error
[libseat] [libseat/backend/seatd.c:64 could not connect to socket /run/seatd.sock: Permission denied
What should I do, should I just reinstall Hyprland, this is my first time install arch linux so

[RhaZenZ0]

Check user permissions: If you encounter the "Permission denied" error after ensuring that the socket file exists, make sure that the current user has the necessary permissions to access the socket. The socket file should be owned by the same user running the Wayland compositor or should have appropriate read/write permissions for all users. You can try running the compositor with elevated privileges (using sudo) temporarily to see if the error persists.

Please close this issue