I’m starting to suspect my HDD failing at this point, so many weird bugs lately

Yes I have polkit installed

Executing startplasma-wayland returns the following:

startplasmacompositor: Could not start D-Bus, Can you call qdbus?

I don’t have an excutable/command named qdbus

Yes I do

Yes everything in TTY works as intended, I can login as my user account and sudo works as it should

better development machine

By developing on a GNU/Linux VM instead? fuck MS for not finding a suitable solution for developing on their OS for years and shoving an entire another OS inside instead

Maybe it’s some marketing thing? Like their feature MUST start with Windows™ regardless of getting confusing as hell, it may also help not techie people who make decisions and want to still use a Windows™ solution suggested by a techie

No it’s not

I see, but FAT32 is pretty limiting for file sizes no?

Don’t forget we also had 6.6.6

I had Fedora and Arch on a 2012 Intel MacBook pro, it’s running well, I think macos manages power consumption better, either way I believe if you have no dGPU you should be good to go, also you probably must check the Arch wiki Mac page (regardless of what disro you choose)

Found it, thx

Yeah that seems like it, thanks

Yes that’s what I’ve been looking for, thanks a lot

Is that Apple-specific?

I think Arch really makes sure stuff are compatible before rolling, my 32bit Void laptop has had Python 3.12 for months, and I get all kind of weird warnings when installing Python packages, while Arch is still on 3.11 (maybe testing is on 3.12 idk)

i didn’t change permissions recursivly, only for the mountpoints root

I’m surprised it installed just normally

I can’t see a reason for it to fail since the root user was functioning just fine, shit got buggy as soon as other users tried to read from the fs

you can chown it all

The permissions inside the partition were set correctly, it was only the “root” of the partition that went off, I only created the partition using Mint, while Arch did the whole installation and wrote all the files

Either way I chown both / and /boot to root:root and chmod both / and /boot to 0755 (looked these up from my other Arch machine) and the bugs are gone

Things weren’t working because of the owner+permission being set by Mint instead of the Arch installer, it prevented non-root from reading anything off the system, now that I chmod the mount points, things are functioning well