[SOLVED] Wayland sessions won't start.

Eysse · 2023-09-26 18:30:10

Upon running wayland sessions ( I have no others), I get: Could not connect to socket /run/seatd.socket: No such file or directory, despite seatd being installed.
I have tried:
- reinstalling seatd
- switching to seatd-git from AUR
- adding LIBSEAT_BACKEND=logind to /etc/environment
- restarting the service
- enabling the service, and reinstalling

``A_platform_gbm EGL_KHR_platform_gbm EGL_MES`` is also getting thrown to my face.

I couldn't fund anything else on the matter.

Last edited by Eysse (2023-09-27 22:20:41)

Trilby · 2023-09-26 19:01:10

What's the output from `systemctl status seatd`? Which compositors have you tried? And are you starting them directly from a tty, or how?

Last edited by Trilby (2023-09-26 19:01:49)

Eysse · 2023-09-26 19:21:27

`systemctl status seatd >` gives:
http://ix.io/4HvJ

`sway 2>` gives:
http://ix.io/4HvK

`Hyprland 2>` gives:
http://ix.io/4HvL

`labwc 2>` gives:
http://ix.io/4HvM

`Hyprland >` gives:
http://ix.io/4HvN

`$HOME/.hyprland/hyprlandCrashReport991.txt` holds:
http://ix.io/4HvO

`labwc >` and `sway >` were both empty.

Running `systemctl start seatd` or enable --now, still causes the sessions not to start, this time with error: `Could not connect to socket /run/seatd.sock: Permission denied`.
I am indeed running Hyprland from tty. Same error occurs with labwc. I have no other sessions installed to test it on.

Last edited by Eysse (2023-09-26 20:59:59)

Trilby · 2023-09-26 19:29:40

Eysse wrote:

`systemctl status seatd` shows it's disabled and inactive.

That's the problem. Forget trying to start a compositor until you solve the problem with seatd (unless you want polkit). And if you want help solving the problem, post the actual output requested, not a summary.

Eysse · 2023-09-26 19:44:51

How do I get that output from tty though?

Eysse · 2023-09-26 19:48:14

And what does it mean to 'use polkit'? Do I need seatd? Is polkit better/different?

seth · 2023-09-26 20:05:30

Seatd is an optional alternative to the (more default) logind, but that requires polkit.

Why are you using seatd if you're apparently not aware of that?
What advices are you currently following?

See the 1st link below on how to post from the console and please don't multi-post, edit your previous post to mend it if nobody has replied so far.

Trilby · 2023-09-26 20:34:58

The default arch package for hyprland (which you claim to be using) also has a hard dependency on polkit. So if you are using arch packages, you already have polkit and need not bother with seatd ~~(and you should likely then remove seatd)~~. If you are not using arch packages, you really need to mention that and describe how you built / installed hyprland.

Personally I have strong negative opinions about polkit and refuse to have it installed. So I use seatd. And given where this thread started, I figured you were of a similar opinion. If you do not have reasons to explicitly avoid polkit, ~~then just get rid of seatd~~ - polkit is socket activated (or similarly handles stuff itself behind the scenes) so you don't have to do anything specific to use / enable it.

EDIT: the repo hyprland package apparently depends on both polkit and seatd ... a very odd packaging choice, but in any case, if you installed hyprland via pacman, you have polkit already.

EDIT 2: probably something I should have asked for at the very start of this thread: please post the full and complete output of attempting to run a wayland compositor. If you have sway installed, I'd personally prefer seeing output from that as I'm a bit familiar with it (I've never used hyprland).

Last edited by Trilby (2023-09-26 20:46:22)

Eysse · 2023-09-26 20:41:36

I have not manually installed seatd nor polkit. It also used to work for a very long time. I have been using Hyprland on this machine since beta 0.6 if I'm not mistaking. It has always worked perfectly. I wouldn't know what I could have done for it not to work. Have no installed anything new as far as I am aware. I will try to uninstall seatd, though, thanks!

seth · 2023-09-26 20:49:41

seatd is also a dependecy of hyprland and I suspect it to be a red herring.
Please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

and also the hyprland log https://wiki.hyprland.org/Crashes-and-Bugs/

Eysse · 2023-09-26 21:01:32

http://0x0.st/HV2z.txt
I have also updated the logs in the comment above, as requested.

seth · 2023-09-26 21:14:35

Sep 26 22:44:05 Arch-Eysse polkitd[856]: Error opening rules directory: Error opening directory “/etc/polkit-1/rules.d”: Permission denied (g-file-error-quark, 2)

stat /etc/polkit-1/rules.d
id polkitd

Sep 26 22:43:59 Arch-Eysse kernel: [drm] Initialized simpledrm 1.0.0 20200625 for simple-framebuffer.0 on minor 0
Sep 26 22:43:59 Arch-Eysse kernel: simple-framebuffer simple-framebuffer.0: [drm] fb0: simpledrmdrmfb frame buffer device

https://www.reddit.com/r/hyprland/comme … _hyprland/
Try to add "initcall_blacklist=simpledrm_platform_driver_init" to the https://wiki.archlinux.org/title/Kernel_parameters

Edit: 0.30 is in the repos but you're still using 0.29.1-81-gd126d2c0
Edit #2: which also seems to be an AUR page.

Last edited by seth (2023-09-26 21:18:14)

Eysse · 2023-09-26 21:30:06

`stat /etc/polkit-1/rules.d` gives:
http://0x0.st/HV2A.txt

`id polkitd` gives:
http://0x0.st/HV2B.txt

I have add your line to the `GRUB_CMDLINE_LINUX_DEFAULT=` field in /etc/default/grub, and rebuilt my grub config with `sudo grub-mkconfig -o /boot/grub/grub.cfg`, no succes. Error after running Hyprland is still the exact same.

seth · 2023-09-26 21:31:57

/etc/polkit-1/rules.d is supposed to be root:polkitd, not root:root
Did you try hyprland 0.30 ?

Edit: and disable seatd again.

Last edited by seth (2023-09-26 21:32:16)

Eysse · 2023-09-26 21:36:15

Yes, I tried hyprland 0.30. I have also just tried downgrading hyprland to 0.29.1 and 0.29.0, no succes.
seatd disabled.

seth · 2023-09-26 21:41:02

Try the behavior w/ the LTS kernel and post an updated journal.

So that we're not chasing gooses:

WLR_RENDERER_ALLOW_SOFTWARE=1 Hyprland

Last edited by seth (2023-09-26 21:48:37)

Eysse · 2023-09-27 15:27:20

Hereby:
http://0x0.st/HVfv.txt

seth · 2023-09-27 16:23:28

seatd is still running, did you try to run Hyprland while allowing the software renderer?
And move away your hyprland config, /home/rat/.config/hypr/hyprland.conf

However hyprland is still aborting and your previous outputs include

libEGL warning: MESA-LOADER: failed to open radeonsi: libLLVM-16.so: cannot open shared object file: No such file or directory (search paths /usr/lib/dri, suffix _dri)

00:00:00.021 [ERROR] [wlr] [EGL] command: eglInitialize, error: EGL_NOT_INITIALIZED (0x3001), message: "DRI2: failed to load driver"
libEGL warning: MESA-LOADER: failed to open radeonsi: libLLVM-16.so: cannot open shared object file: No such file or directory (search paths /usr/lib/dri, suffix _dri)

00:00:00.024 [ERROR] [wlr] [EGL] command: eglInitialize, error: EGL_NOT_INITIALIZED (0x3001), message: "DRI2: failed to load driver"
00:00:00.024 [ERROR] [wlr] [EGL] command: eglInitialize, error: EGL_NOT_INITIALIZED (0x3001), message: "eglInitialize"
00:00:00.024 [ERROR] [wlr] [render/egl.c:264] Failed to initialize EGL
00:00:00.024 [ERROR] [wlr] [render/egl.c:554] Failed to initialize EGL context
00:00:00.024 [ERROR] [wlr] [render/gles2/renderer.c:679] Could not initialize EGL
00:00:00.024 [ERROR] [wlr] [render/wlr_renderer.c:333] Could not initialize renderer
00:00:00.024 [ERROR] [sway/server.c:79] Failed to create renderer

00:00:00.000 [INFO] [libseat] [libseat/libseat.c:73] Seat opened with backend 'seatd'
00:00:00.000 [INFO] [libseat] [libseat/backend/seatd.c:212] Enabling seat
00:00:00.000 [INFO] [backend/session/session.c:109] Successfully loaded libseat session
00:00:00.002 [INFO] [backend/backend.c:220] Found 1 GPUs
00:00:00.002 [INFO] [backend/drm/backend.c:202] Initializing DRM backend for /dev/dri/card1 (amdgpu)
00:00:00.002 [INFO] [backend/drm/drm.c:249] Found 6 DRM CRTCs
00:00:00.012 [INFO] [backend/drm/drm.c:207] Found 14 DRM planes
00:00:00.013 [INFO] [render/egl.c:206] Supported EGL client extensions: 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_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
libEGL warning: MESA-LOADER: failed to open radeonsi: libLLVM-16.so: cannot open shared object file: No such file or directory (search paths /usr/lib/dri, suffix _dri)

00:00:00.016 [ERROR] [EGL] command: eglInitialize, error: EGL_NOT_INITIALIZED (0x3001), message: "DRI2: failed to load driver"
libEGL warning: MESA-LOADER: failed to open radeonsi: libLLVM-16.so: cannot open shared object file: No such file or directory (search paths /usr/lib/dri, suffix _dri)

00:00:00.017 [ERROR] [EGL] command: eglInitialize, error: EGL_NOT_INITIALIZED (0x3001), message: "DRI2: failed to load driver"
00:00:00.017 [ERROR] [EGL] command: eglInitialize, error: EGL_NOT_INITIALIZED (0x3001), message: "eglInitialize"
00:00:00.017 [ERROR] [render/egl.c:269] Failed to initialize EGL
00:00:00.017 [ERROR] [render/egl.c:572] Failed to initialize EGL context
00:00:00.017 [ERROR] [render/gles2/renderer.c:804] Could not initialize EGL
terminate called after throwing an instance of 'std::runtime_error'
  what():  wlr_gles2_renderer_create_with_drm_fd() failed!

pacman -Qikk llvm-libs mesa

Eysse · 2023-09-27 17:23:23

I had run `systemctl start seatd` just to test if it would work, should have been disabled once I ran the journalctl.
Furtermore, here is output of `pacman -Qikk llvm-libs mesa`:
http://0x0.st/HVVm.txt

edit: forgot to mention: Yes, I have tried running Hyprland while allowing software to the renderer or whatever the variable is called.

Last edited by Eysse (2023-09-27 17:25:12)

seth · 2023-09-27 17:40:56

What was the stderr output?
Re-instal llvm-libs, it's clearly corrupted.
Any idea as to why?

Eysse · 2023-09-27 18:01:42

That worked beautifully!! And no, I have no idea how has gotten corrupted. Anyway, with has worked, so the post can be marked as fixed.
Furthermore, I want to point out I am very very grateful for your willingness to help me, and several others, out all day. You can't be missed!
On that note, I would like to know more about troubleshooting. How can I make sure I can fix my own, but also others' issues myself in the future?

seth · 2023-09-27 19:29:44

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.

If there's been no explicit incident (hard reboot, ideally during an update) you might want to explore https://wiki.archlinux.org/title/SMART and in case https://wiki.archlinux.org/title/Solid_ … leshooting
Generally over-aggressive trimming strategies can make some SSD lose data and the more experimental *cough* btrfs *cough*filesystems are somewhat prone to that.

Troubleshooting starts with reading what the system tells you.
I had initially ignored the "… 2" outputs, ass·u·me/ing they'd just be copies of the others, but as soon as I saw the unresolvable library, the answer was rather obvious.
The rest is experience - and I guess you can learn something by hanging out here and reading threads where the answer might interest you. Even if you don't have the problem or know the answer but just wonder "ok, how'd I solve this if I was in the situation"

Eysse · 2023-09-27 22:22:08

Done! I'll look into my drive health, thanks. And I will also hang around here to see how to fix my isssues. Cheers!

Arch Linux

#1 2023-09-26 18:30:10

[SOLVED] Wayland sessions won't start.

#2 2023-09-26 19:01:10

Re: [SOLVED] Wayland sessions won't start.

#3 2023-09-26 19:21:27

Re: [SOLVED] Wayland sessions won't start.

#4 2023-09-26 19:29:40

Re: [SOLVED] Wayland sessions won't start.

#5 2023-09-26 19:44:51

Re: [SOLVED] Wayland sessions won't start.

#6 2023-09-26 19:48:14

Re: [SOLVED] Wayland sessions won't start.

#7 2023-09-26 20:05:30

Re: [SOLVED] Wayland sessions won't start.

#8 2023-09-26 20:34:58

Re: [SOLVED] Wayland sessions won't start.

#9 2023-09-26 20:41:36

Re: [SOLVED] Wayland sessions won't start.

#10 2023-09-26 20:49:41

Re: [SOLVED] Wayland sessions won't start.

#11 2023-09-26 21:01:32

Re: [SOLVED] Wayland sessions won't start.

#12 2023-09-26 21:14:35

Re: [SOLVED] Wayland sessions won't start.

#13 2023-09-26 21:30:06

Re: [SOLVED] Wayland sessions won't start.

#14 2023-09-26 21:31:57

Re: [SOLVED] Wayland sessions won't start.

#15 2023-09-26 21:36:15

Re: [SOLVED] Wayland sessions won't start.

#16 2023-09-26 21:41:02

Re: [SOLVED] Wayland sessions won't start.

#17 2023-09-27 15:27:20

Re: [SOLVED] Wayland sessions won't start.

#18 2023-09-27 16:23:28

Re: [SOLVED] Wayland sessions won't start.

#19 2023-09-27 17:23:23

Re: [SOLVED] Wayland sessions won't start.

#20 2023-09-27 17:40:56

Re: [SOLVED] Wayland sessions won't start.

#21 2023-09-27 18:01:42

Re: [SOLVED] Wayland sessions won't start.

#22 2023-09-27 19:29:44

Re: [SOLVED] Wayland sessions won't start.

#23 2023-09-27 22:22:08

Re: [SOLVED] Wayland sessions won't start.

Board footer