Hmm, adding another user, some_tester, and another DE seems to have made it work? I can press the audio and brightness keys and they work as expected. But when I log in as my usual user, ian , when I press those buttons it just locks up.
I’m not sure what changed other than me adding some_tester to the sudoers group… I added my ian to the group too but still not working
NOTE: I wonder if it’s something I installed? Because initially my ian worked just fine too?
What do you mean by this? Meaning it’s not something I installed?
Compare the two users’ folders contents.
You mean on the home folder?
Check what you have configured into those buttons. Maybe you have somehow changed their configuration for your first account?
Hmm, gotcha so output the keymaps and compare them? That’s a good idea. But it doesn’t explain why the ian user occasionally freezes for a second or so.
Each user has a folder at /home/$USER/. Those two.
I mean, IIRC i3 has own keybindings configuration in its config file (I don’t use i3…).
There might be a difference in those keybindings between the users’ config files. Or check however you think it does the job
First find the problem and fix it, and then you go to explanations. I guess…
I can guarantee it’s not spotify. Have you tried just installing i3 on its own and nothing else? I’m sure it’s something you have installed or configured because i3 works flawlessly.
Each user has a folder at /home/$USER/. Those two.
Right, but I’ve got probably hundreds of nested files and folders. I’m still not sure what to look for.
Have you tried just installing i3 on its own and nothing else?
Yeah, on fresh installs my i3 works just fine. It’s after installing all the programs that things go sideways. Do you think uninstalling everything then progressively installing them will help? Or do I have to start tabula rasa and then install as I go along. Even using binary search to find the package is going to be a nightmare
The error (pressing brightness key causes the system to seize up) happens on other DEs as well for the ian user. However, it doesn’t manifest when I’m on my test_user even though test_user has access to all the packages installed by ian
If you want answers for a problem you face on your system, nobody but you can give them.
What all the rest of us supposed to doing is looking in our personal Crystal Balls .
Only a few of those have a less foggy picture, but not even one can see inside your own PC.
Install each one at a time and check if each work and don’t cause any problem. Don’t install them all and then try to figure it out. Narrow it down to the culprit!
Should I just do a fresh install and walk through it 1-by-1 ? Or do you think I can do it in a VM? Basically what do you think would make this the least painful because this is really going to be painful as I have disk encryption sooooooo that’s gonna suck. Also, the problem only rears its head on power on, not in the moment
Use the Magician.
Meld can compare folders. There is a filter to show only files that exist on both folders you compare.
Create a folder in your broken usual system and open a terminal in that path. Then copy the 2nd user’s .config folder inside, recursivelly.
mkdir otheruser && cd otheruser
sudo cp -r /home/otheruser/.config .
cd ..
chown -hR ian:ian otheruser
Then run meld and create a folder comparison.
Can you take it from here?
So unfortunately, I don’t have an actual answer for what happened. The best I can gather is that installing snap did something funky to my system and caused everything to SNAFU. After a fresh install and using the aur as opposed to snap, everything worked as expected.
Not satisfactory, but it addressed ALL the issues.
Stupid question from my side. Why do you use snap? I used snap when I was on Ubuntu. But here in Arch Linux world I don’t see the necessity for using snap.