xavier666 @ xavier666 @lemm.ee

Just another Reddit refugee

---

Read more

Posts

30

Comments

1,256

Joined

2 yr. ago

Moderating

---

Check how your environment variables differ between i3 and sway and see if that might be the issue

Just running set for each session and then diff should be enough, right?

Just the way I launch sway; via gdm.

As what user are you executing all these ‘groups’ commands?

I'm using my default user (xavier666)

The “normal” user should not be in the root group, and root should not be in the normal user’s group.

I just made the user a root user/system administrator during the Ubuntu installation process, which is very standard.

Have you done other things beside the “fix” you mentioned?

AFAIK, I haven't done any changes. This is a single user system. I checked the contents of /etc/sudoers and these are the only other lines of significance. I didn't change them (Why are there % signs?)

    
# User privilege specification
root    ALL=(ALL:ALL) ALL
xavier666    ALL=(ALL:ALL) ALL

# Members of the admin group may gain root privileges
%admin ALL=(ALL) ALL

# Allow members of group sudo to execute any command
%sudo   ALL=(ALL:ALL) ALL

  

That “fix” from your op, btw, looks totally valid to me.

It's working fine also. However, I believe in "don't touch what ain't broke" and "why isn't it documented?"

However, in my installations I have never touched the sudoer file to make the ONLY user part of sudo group post install. Either I'm dumb or I'm launching sway/wayland with improper permissions.

I also can't find anything on the arch wiki which deals with this.

Why isn't the same problem happening on i3?

Yeah, I ran it and rebooted it. But no change :(

I'll do it once more just in case.

I'm unsure how to use the command. I added it to the main Sway config file, which means it's executed whenever Sway starts (Post login).

However, it didn't make any difference. I also ran it manually

    
$ loginctl enable-linger xavier666
$ sudo visudo
[sudo] password for xavier666:
Sorry, user xavier666 is not allowed to execute '/usr/sbin/visudo' as root on <HOSTNAME>.

  

My lazy hack

If it looks stupid but works, then it's not stupid

these are all text files

Yeah, it just calls the executable mentioned in the .desktop file (/usr/bin/sway). It should not be a GDM, issue, right?

I also checked that I don't have seatd installed, which is a "minimal user, seat and session management daemon" mentioned in arch wiki (https://wiki.archlinux.org/title/Sway). Could it be related?

Sorry, I have to go now. More tonight, if you want.

No hurry, the fix I am using is not causing issue. I just want to know why this is happening. This is a fun research problem.

PS: I checked Google and I didn't find anyone who has faced the same issue.

Inisde i3 WITHOUT FIX

    
$ groups

xavier666 adm cdrom sudo dip plugdev lpadmin lxd sambashare

$ groups xavier666

xavier666 : xavier666 adm cdrom sudo dip plugdev lpadmin lxd sambashare

  

Inside sway WITH/WITHOUT FIX

    
$ groups

xavier666 root

$ groups xavier666

xavier666 : xavier666 adm cdrom sudo dip plugdev lpadmin lxd sambashare

  

PS: I corrected the username, it should be xavier666. I corrected the main post.

but with the way the sway session is started, as opposed to the i3 session. We need more info on this.

I'm using gdm to start sway. I'm using the laptop's built-in fingerprint scanner to unlock (Not sure if it matters). I saved the fingerprint in the Gnome session long back.

gdm probably looks inside /usr/share/wayland-sessions and finds sway.desktop and uses it to launch Sway.

I've tried to keep things as vanilla as possible.

Isn’t i3 Xorg only, and sway wayland only?

Correct.

Maybe wayland is launched using restrictive set of permissions.

"Sorry, we can't adjust the thermostat until we have audio evidence of whether the family is going through a divorce"

Just giving you an update. I gave it for repair and it got accepted for warranty. I kept my Ally like a baby so they couldn't find any physical fault with it. They changed the motherboard for free and now the SD card reader is working again. However, I am not sure if the problem will recur again.

Learn Docker even if you have a single app. I do the same with a Minecraft server.

• No dependency issues
• All configuration (storage/network/application management) can be done via a single file (compose file)
• Easy roll-backs possible
• Maintain multiple versions of the app while keeping them separate
• Recreate the server on a different server/machine using only the single configuration file
• Config is standardized so easy to read

You will save a huge amount of time managing your app.

PS: I would like to give a shout out to podman as the rootless version of Docker

We will have to accept AIs are here to stay. Since putting wheels on grandama is the only way we can get a bike.

OP doesn't need to hear this. OP's a highly trained professional.

You will own nothing, and you will be happy.

I can imagine a dystopian future, where only few hardcopies/offline copies of literature survive. All art/media is only available on the cloud, which is constantly changed as per the agenda of the day. All communication has to go through the cloud for authenticated. The police state is constantly scanning people if they have any sort of external storage device. USB ports are banned from being manufactured. Radio is banned. Few people, the rebels, hoard the last bit of art and music in the form of LPs/cassettes,/canvas but it's shared among people like contraband.

This can be an awesome movie :P

Buddy, I have tried docked mode on windows (Ally + Windows + Bluetooth controller). It's hell! I can't wait to get back to SteamOS/Bazzite.

What problems have you faced in docked mode?

"Hey, I've seen this one before. It's a classic."

The Sun provides us with life, skin cancer, and heatwaves. Nothing is perfect.

What, you didn't know you had to crank the power to high before microwaving your phone? Rookie mistake

Damn...I've been discovered