[SOLVED] Getting Rootless Xorg Working in Slackware-current

Charadon · 12-09-2021, 12:34 PM

I was wondering if anyone has actually gotten Rootless Xorg working in Slackware-current, now that it uses elogind? I've been trying to get it working, but so far i've been stumped. I've tried:

- Setting --enable-systemd-logind in x11's slackbuild.
- Removing the suid bit from /usr/bin/Xorg, /usr/libexec/Xorg.wrap, and /usr/libexec/Xorg.
- Creating a file called /etc/X11/Xwrapper.config and adding the lines:

Code:

needs_root_rights = no 
allowed_users = anybody

(Also tried it with needs_root_rights = yes)

- Adding elogind.so to /etc/pam.d/system-auth.
- Making sure dbus is loaded before startx is called via:

Code:

eval $(dbus-launch --sh-syntax)

- Adding user to the following groups: video, audio, input.

If anyone has any suggestions on how to get this working, i'm all ears. Also, it's not a neccesity that I got rootless xorg working, but it'd be really cool though, wouldn't it?

Petri Kaukasoina · 12-09-2021, 02:48 PM

Quote:

Originally Posted by Charadon

I was wondering if anyone has actually gotten Rootless Xorg working in Slackware-current, now that it uses elogind?

Did you try this: https://www.linuxquestions.org/quest...3/#post6274841

truepatriot76 · 12-09-2021, 02:50 PM

Sounds like a privilege issue. I use the adduser script when adding users, it's pretty handy in assigning the proper groups, then add the wheel group applicable.

https://docs.slackware.com/slackbook:users

Nevermind - (rootless).

Charadon · 12-09-2021, 04:22 PM

Quote:

Originally Posted by Petri Kaukasoina

Did you try this: https://www.linuxquestions.org/quest...3/#post6274841

Awesome, that actually worked! I hope that slackware adopts that change, as it doesn't really have any downsides from what I know, and only increases security, even if some would debate that it's marginal. Thanks for pointing me in the right direction =)

drgibbon · 12-09-2021, 06:15 PM

Quote:

Originally Posted by Charadon

Awesome, that actually worked!

I might test this out, but how do you know if it's worked or not?

Charadon · 12-09-2021, 06:21 PM

Quote:

Originally Posted by drgibbon

I might test this out, but how do you know if it's worked or not?

To see if it worked, you simply run

Code:

ps -af | grep X

And it should tell you what's running /usr/bin/X, and if it worked, it'll be your username.
Example:

Code:

charadon  3983 31076  0 19:20 pts/2    00:00:00 grep --color=auto --exclude-dir=.bzr --exclude-dir=CVS --exclude-dir=.git --exclude-dir=.hg --exclude-dir=.svn --exclude-dir=.idea --exclude-dir=.tox X
charadon 13619 13598  0 17:19 tty1     00:00:00 xinit /home/charadon/.xinitrc -- /usr/bin/X :0 vt1 -keeptty -auth /home/charadon/.serverauth.13598
charadon 13620 13619  2 17:19 tty1     00:03:23 /usr/bin/X :0 vt1 -keeptty -auth /home/charadon/.serverauth.13598

Petri Kaukasoina · 12-10-2021, 12:47 AM

Quote:

Originally Posted by Charadon

Just be sure to add yourself to the video and input group.

https://www.linuxquestions.org/quest...ml#post6275120
Why not?
https://www.linuxquestions.org/quest...ml#post6275119

Charadon · 12-10-2021, 12:04 PM

Quote:

Originally Posted by Petri Kaukasoina

https://www.linuxquestions.org/quest...ml#post6275120
Why not?
https://www.linuxquestions.org/quest...ml#post6275119

Right... forgot logind makes it so you don't need to be in the video/input group. I think that was my BSD experience peeking lol

Thom1b · 12-11-2021, 07:40 AM

Quote:

Originally Posted by Petri Kaukasoina

Did you try this: https://www.linuxquestions.org/quest...3/#post6274841

It works perfectly for me too. Thanks a lot!

glorsplitz · 12-11-2021, 09:24 AM

This is being asked to not allow root privilege for normal user to xorg?

Charadon · 12-11-2021, 12:31 PM

Quote:

Originally Posted by glorsplitz

This is being asked to not allow root privilege for normal user to xorg?

No, I was asking why Xorg wasn't defaulting to not escalting itself to root, since by default, Xorg tries to deescalate itself back to your user after it's done doing hardware things. And this is possible thanks to logind, which Slackware has now thanks to elogind. As it turned out, the xorg-server package in slackware was built without support for logind, which is why xorg was still running itself as root. Hopefully, they enable logind support in Xorg before Slackware 15 comes out

Thom1b · 12-12-2021, 08:05 AM

Quote:

Originally Posted by Thom1b

It works perfectly for me too. Thanks a lot!

Finally, it doesn't work perfectly. Resuming after hibernation fails on one of my computer when X is not running by root.

Code:

[   82.124452] radeon 0000:00:01.0: scheduling IB failed (-12).
[   82.124454] [drm:radeon_vce_get_create_msg [radeon]] *ERROR* radeon: failed to schedule ib (-12).
[   82.124497] [drm:radeon_vce_ib_test [radeon]] *ERROR* radeon: failed to get create msg (-12).
[   82.124529] [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB on ring 6 (-12).
[   82.124562] radeon 0000:00:01.0: scheduling IB failed (-12).
[   82.124563] [drm:radeon_vce_get_create_msg [radeon]] *ERROR* radeon: failed to schedule ib (-12).
[   82.124594] [drm:radeon_vce_ib_test [radeon]] *ERROR* radeon: failed to get create msg (-12).
[   82.124625] [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB on ring 7 (-12).
[   82.332877] OOM killer enabled.
[   82.332879] Restarting tasks ... done.
[   82.335955] video LNXVIDEO:00: Restoring backlight state
[   82.336085] PM: hibernation: hibernation exit

Charadon · 12-12-2021, 01:48 PM

Quote:

Originally Posted by Thom1b

Finally, it doesn't work perfectly. Resuming after hibernation fails on one of my computer when X is not running by root.

Code:

[   82.124452] radeon 0000:00:01.0: scheduling IB failed (-12).
[   82.124454] [drm:radeon_vce_get_create_msg [radeon]] *ERROR* radeon: failed to schedule ib (-12).
[   82.124497] [drm:radeon_vce_ib_test [radeon]] *ERROR* radeon: failed to get create msg (-12).
[   82.124529] [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB on ring 6 (-12).
[   82.124562] radeon 0000:00:01.0: scheduling IB failed (-12).
[   82.124563] [drm:radeon_vce_get_create_msg [radeon]] *ERROR* radeon: failed to schedule ib (-12).
[   82.124594] [drm:radeon_vce_ib_test [radeon]] *ERROR* radeon: failed to get create msg (-12).
[   82.124625] [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB on ring 7 (-12).
[   82.332877] OOM killer enabled.
[   82.332879] Restarting tasks ... done.
[   82.335955] video LNXVIDEO:00: Restoring backlight state
[   82.336085] PM: hibernation: hibernation exit

What GPU do you have? Because that seems like a driver issue. Seems to be the ancient radeon driver instead of amdgpu.

Jeebizz · 12-12-2021, 02:53 PM

So my question is - thats it? Is a rootless X working ? Also I wonder - is if feasible for Pat to implement it in Slackware down the line? I rather like the idea of rootless X too - primarily for hardening/securing Slackware.

Charadon · 12-12-2021, 03:05 PM

Quote:

Originally Posted by Jeebizz

So my question is - thats it? Is a rootless X working ? Also I wonder - is if feasible for Pat to implement it in Slackware down the line? I rather like the idea of rootless X too - primarily for hardening/securing Slackware.

For me, it's working perfectly. I've had zero issues. And I agree, I would like for this to atleast be an option.