| View previous topic :: View next topic |
| Author |
Message |
an7h
Tux's lil' helper
Joined: 10 Jan 2018
Posts: 94
|
 Posted: Wed Nov 27, 2024 11:30 am Post subject: [SOLVED] sway broken upd - SUID operation no longer supp |
 |
|
After the latest system update sway just stopped working all of a sudden. I've got sway starting up via dbus-run-session as suggested by the info on the Gentoo Wiki, and everything was working smoothly until the latest update, which went through without a hitch, but when rebooting my laptop it would refuse to start up, and instead I get an error...
| Code: | | 00:00:00.000 [sway/main.c:123] SUID operation is no longer supported, refusing to start. This check will be removed in a future release. |
I tried installing different versions of sway, but that did not help. I have elogind enabled as a global use flag in make.conf and it's basically configured to be used by my system, so that's definitely not causing this problem. This does not seem to be a problem with wayland either, because I can use something like weston just fine via i3, that I switched to for now. I'm not sure what kind of info to provide here... but I was wondering that perhaps I missed something obvious entirely and this is something most people are aware of. I could use some help getting sway running again. Thanks.
-----
Oh, after looking at it a second time I've got a bit of additional info that might help you guys tell me what's wrong.
1. while compiling it says at the start
| Code: | | Subproject wlroots is buildable: NO (disabling) |
and
| Code: | Subprojects
wlroots : NO Neither a subproject directory nor a wlroots.wrap file was found. |
it seems wlroots is a sway dependency, which IS installed, but not detected somehow??
2. after installing it says something about a misconfigured kernel, which is a bit strange, because I didn't really touch it and things were working with previous kernel config just fine before updating sway, but the message after compilation and install says
| Code: | >>> Installing (1 of 1) gui-wm/sway-1.10::gentoo
* Could not set caps on '/usr/bin/sway' due to missing filesystem support:
* * enable XATTR support for 'ext2/ext3' in your kernel (if configurable)
* * mount the fs with the user_xattr option (if not the default)
* * enable the relevant FS_SECURITY option (if configurable) |
Perhaps I need to enable something within the kernel? I'm not sure what to look at, because the warning after install is not giving precise info about which config I should look at. Guess I'll try sys-kernel/gentoo-kernel-bin to see if it works with that...
...so there's that as well, hope it helps someone around here to pinpoint what's wrong with sway on my system. thank you in advance. 
_________________
If dreams were horses, beggars would ride.
Last edited by an7h on Wed Nov 27, 2024 6:38 pm; edited 1 time in total |
|
| Back to top |
|
 |
JimRockford74
n00b
Joined: 26 Nov 2024
Posts: 5
|
| Posted: Wed Nov 27, 2024 1:51 pm Post subject: |
|
|
1. First, ensure you have the correct kernel configuration. You need to enable these options in your kernel's .config
| Code: | File Systems ->
[*] Extended attributes
[*] Extended user attributes support
[*] File system security labels
Security options ->
[*] Enable different security models |
2a. Make sure wlroots is properly installed:
| Code: | | doas/sudo emerge --ask gui-libs/wlroots |
2b. Make sure elogind is running
| Code: | rc-service elogind start
rc-update add elogind default |
3. Then start sway
| Code: | | exec dbus-run-session sway |
If that doesnt work you can try to get it running via seatd
| Code: | # Install seatd
emerge --ask sys-auth/seatd
# Add your user to seat group
usermod -a -G seat yourusername
# Enable and start seatd
rc-update add seatd default
rc-service seatd start |
_________________
This is Jim Rockford. I'm either working a case or waiting for something to finish. If you're selling patience, I'm interested. $200 a day plus expenses. Leave your message at the tone. *beep* |
|
| Back to top |
|
|
nicop
Tux's lil' helper
Joined: 10 Apr 2014
Posts: 98
|
| Posted: Wed Nov 27, 2024 3:27 pm Post subject: |
|
|
And check SUID :
| Code: | | ls -l /usr/bin/sway |
Remove it if output shows a 's' flag :
| Code: | | chmod -s /usr/bin/sway |
|
|
| Back to top |
|
|
an7h
Tux's lil' helper
Joined: 10 Jan 2018
Posts: 94
|
| Posted: Wed Nov 27, 2024 6:37 pm Post subject: |
|
|
@JimRockford74
@nicop
Okay, I found out what was causing this error during sway startup, and I figured it out by accident.
After removing everything related to sway (i don't like having extra packages installed I do not need) and writing here for help, I had to reinstall everything again and set use flags I wanted as well for those packages. When doing so, one by one, I forgot to enable the wallpapers use flag for gui-wm/sway, but I didn't realize this has to with anything at first... When I saw everything working again, I thought that, yeah, something WAS incorrectly configured within the kernel or perhaps the use flags I enabled for seatd (which, as it turns out, is a sway dependency) is something required now, but I kept enabling things I needed one by one according to my ~/.config/sway/config file, and then it came to getting my wallpapers showing up again, I enabled the wallpapers use flag, recompiled/installed, and that's when it started to give me that error again. I was "okay, this is weird, why am I getting this error again?", and literally the only thing I changed before it broke was the use flag. I disabled the flag, recompiled everything, and it worked right away.
Now, what is really weird is that it's not even the package that becomes a dependency, which is gui-apps/swaybg, that is the problem. You can install it separately and it'll do the job just fine. The problem is literally just having gui-wm/sway compiled with the wallpapers use flag enabled! I even removed kernel changes and use flag changes for seatd afterwards to double confirm this, and as it turns out this one use flag broke it in such a way, that it was giving a misleading error that had nothing do with whatever was really going on, plus after installing sway itself it would give a warning about an incorrect kernel configuration as well (now gone even after reverting back to previous config).
Whoever is maintaining this package should take a look at what is going on. It seems the ebuild is somehow incorrectly configured.
TL;DR
just disable the wallpapers use flag for gui-wm/sway to fix the following error:
| Code: | | 00:00:00.000 [sway/main.c:123] SUID operation is no longer supported, refusing to start. This check will be removed in a future release. |
_________________
If dreams were horses, beggars would ride. |
|
| Back to top |
|
|
pjp
Administrator
Joined: 16 Apr 2002
Posts: 20496
|
| Posted: Wed Nov 27, 2024 9:39 pm Post subject: |
|
|
| an7h wrote: | | [Whoever is maintaining this package should take a look at what is going on. It seems the ebuild is somehow incorrectly configured. |
If you use IRC, you could try to contact the maintainers there. Otherwise a bug report might help. They can only "take a look" if they know there is something to look at.
_________________
Quis separabit? Quo animo? |
|
| Back to top |
|
|
Anon-E-moose
Watchman
Joined: 23 May 2008
Posts: 6169
Location: Dallas area
|
| Posted: Wed Nov 27, 2024 10:30 pm Post subject: |
|
|
fcaps_pkg_postinst is probably the culprit for the suid stuff, it's an eclass function.
I'm not sure that suid is needed, I think it hasn't been needed in years, if one is running any 6.* series of the kernel.
_________________
UM780, 6.1 zen kernel, gcc 13, profile 17.0 (custom bare multilib), openrc, wayland |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Desktop Environments
