These people have been stealing our pixels for so long. Have you seen how much China has been stealing? There memes are twice as large as ours. But everyone has been crying to me "Sir, but pixies aren't real." THEY ARE REAL!. My uncle has seen pixies. He was very smart, the smartest person I know perhaps. So from tomorrow, the pixel tariffs are being launched. Or pixies. I don't know, doesn't matter.
on my own network a whopping 66.6% of all traffic is blocked
I stated it's actually 66.6% DNS requests being blocked, not the raw bandwidth utilization.
Raw bandwidth savings (by not downloading the non-zero ads) would be much lesser.
Correct. The payload of DNS requests is tiny compared to, say requesting a webpage. So there might not be a huge decrease of bandwidth usage reduction. However, having 66.6% less DNS requests is still a win. The router/gateway doesn't have to work that hard because of the dropped requests.
It was swhkd. Thank you very much for your insight and extremely detailed response!
$ ls -l $(which swhkd)
-rwsr-xr-x 1 root root 2583192 Mar 10 17:16 /usr/bin/swhkd
Since we know what's causing it, can you make a "guesstimate" of what it's doing? Why are other applications are getting infected by it? And why is a keybind manager affecting permissions?
I will raise an issue on their github. The project is already looking for maintainers.
How do you open the shell inside sway? Keyboard binding from sway config? Launcher? Which terminal? Do any of the involved programs have setuid root bit set (looks like rws instead of x in ls -l output)?
I think you may have just pointed me to the correct direction.
My keybinds setup is a bit weird. I'm using swhkd instead of sway's built in keybinds.
swhkd is a setuid binary (https://github.com/waycrate/swhkd?tab=readme-ov-file#running) which might be causing the issue.
I'll quickly disable swhkd and check if the issue is resolved.
Will keep you posted.
A funny thing; I think this has nothing to do with gdm. I have gdm disabled now and launching sway directly from the terminal and the issue still persists.
The problem goes away (xavier666 becomes part of sudo like expected) when I type exec su - xavier666 for that terminal session only.
If I open a new terminal, it problem reappears. I'll just in case check if zsh/omyzsh is doing something funny.
My brother in Christ, do you think an average person knows what BIOS/boot menu are?