LOG] [AQ] Creating an Aquamarine backend!
[LOG] [AQ] [libseat] [libseat/backend/seatd.c:64] Could not connect to socket /run/seatd.sock: No such file or directory
[LOG] [AQ] [libseat] [libseat/libseat.c:76] Backend 'seatd' failed to open seat, skipping
[LOG] [AQ] [libseat] [libseat/libseat.c:73] Seat opened with backend 'logind'
[LOG] [AQ] Session is not active, waiting for 5s
[LOG] [AQ] libinput: New device AT Translated Set 2 keyboard: 1-1
[LOG] [AQ] libinput: New device VirtualPS/2 VMware VMMouse: 2-19
[LOG] [AQ] libinput: New device VirtualPS/2 VMware VMMouse: 2-19
[LOG] [AQ] libinput: New device ydotoold virtual device: 9011-26214
[LOG] [AQ] Session timeout reached
[LOG] [AQ] Session could not be activated in time
[ERR] [AQ] DRM Backend failed
[LOG] [AQ] Starting the Aquamarine backend!
[LOG] [AQ] Starting the Wayland backend!
[ERR] [AQ] Wayland backend cannot start: wl_display_connect failed (is a wayland compositor running?)
[ERR] [AQ] Requested backend (wayland) could not start, enabling fallbacks
[ERR] [AQ] Implementation wayland failed, erasing.
[CRITICAL] m_pAqBackend couldn't start! This usually means aquamarine could not find a GPU or encountered some issues. Make sure you're running either on a tty or on a Wayland session, NOT an X11 one.
[CRITICAL] Critical error thrown: CBackend::create() failed!
#[Solved] Hyprland crashes when launched through lightdm login
6 messages · Page 1 of 1 (latest)
Why use lightdm, even the hyprland wiki mentions proper support with sddm only
I actually just got it working, I liked SDDM a lot, but I am having an issue that seems to be identified last month in vmware workstation where multimonitor instead of taking over the monitors it adds scroll bars to the main monitor session and LIGHTDM was listed as a potential work around
But as I'm still having the issue, that might be a lie lol
Hello.Host- VMware Workstation 17 Player - 17.5.2 build-23775571- OS: Windows 11 Pro (10.0, Build 22631)- GPU: NVIDIA GeForce RTX 4080 - Studio Driver560.81- CP
I'll mark this one as solved, thank you for responding 🙂