Thats because flatpaks treat each apps directory as their own $HOME so instead of $HOME/.mozilla its $HOME/.var/app/{app_name}/.mozilla
Which is still fantastic dont get me wrong. But Mozilla hasn’t stopped hardcoding their Mozilla folder instead of the xdg dirs even throughf firefox issue tracker has had it on there for 20 years
This is why I use flatpaks. Keeps most of the offending the dotfiles in .var directory scoped to the app itself
My Thinkpad T14s Gen 4 has a few annoying bugs still on linux…
The WiFi chip will randomly be stuck at make 1kbps download speed after waking up from sleep
And occasionally on waking up sleep as well the screen never comes back on.
I wish I had something more compatible with linux even if I do love this thinkpad
Who cares tbh
I love Ubuntu’s default yaru theme, and gnome extensions. It seems currently the best distro on my Thinkpad which is unfortunately pretty incompatible to most linux distros due to the shitty Qualcomm WLAN drivers.
Plus Ubuntus package repository is pretty robust.
The only negative thing IMO is snaps being kind of iffy. I don’t think they are that bad but they seem a little too forced on the user.
Like Flatpak is kind of default on Fedora but they almost never force them on you.
The current beta versions of Thunderbird are implementating a tray icon for linux so soon this fork seems like it’ll only have 2 unique features…
How doesn’t it work properly for you?
I use the flatpak on Fedora but have used the tar version in the past because the package managed version is hijacked with stupid Redhat bookmarks and homepage that loves to return after being removed randomly.
I don’t really remember signing up for mastodon so I tested it.
mastodon.social -> create new account -> agree to terms -> username + email + password -> click email verification
It’s literally standard. Maybe in the past it was worse I vaguely remember giving up maybe a year or two before I made an account on mastodon.social.
80 year old grandmas trying to find the Ctrl and Alt buttons on her printer…
I think the premise is:
Debian stable, slow release cycle
Arch bleeding edge, always latest updates to packages
Fedora - 6 month release cycle? So something in between?
deleted by creator
EndeavorOS is essential in the top tier of my dingo the most corrupt politicians say dumb things like periscopes of my own game company in Ohio
The original large gameboys had a lock that utilized the slot via the power switch. The pocket removed the lock therefore allowing the non slotted Color games to be used in a pocket gameboy.
Pretty FOSS?
PC - Thinkpad T14s Gen 4: EndeavourOS, Firefox and Thunderbird with the Proton suite of things such as Mail, Pass and VPN - I do pay for them but I think it’s worth it.
Phone - Pixel 8 with GrapheneOS and as many F-Droid apps as possible. Proton apps for Mail, Pass, Drive, VPN. Cromite browser. The only that aren’t are probably my banking apps, but I could always switch to web I guess.
I think my biggest hurdle is a Map app that has traffic data that isn’t Google maps.
I’ve played maybe an hour or 2 on my PS2 maybe a year or two ago and the mechanics sounded so amazing, but in execution they don’t seem to work as intended like you said.
Per this article from EndeavourOS discovery I was able to repair my similar issue.
https://discovery.endeavouros.com/system-rescue/arch-chroot/2022/12/
However my device wasn’t encrypted. However near the bottom are instructions if you are and they don’t quite match what you said you did. Maybe give it a try?
"Encrypted installs In case /dev/sda2 is the encrypted root partition you need to unlock:
sudo cryptsetup open /dev/sda2 mycryptdevice
It will ask for your LUKS passphrase and unlocks the device into the path /dev/mapper/mycryptdevice
This path can be used to mount the device:
sudo mount /dev/mapper/mycryptdevice /mnt
Followed by mounting the ESP (EFI-System-Partition) into the already mounted system:
sudo mount /dev/sdXn /mnt/efi
where in all cases /dev/sdXn needs to be changed according to what is used on your install as partition/device path and the mount path for the ESP needs to get changed according to your installed system in case. If it is /efi you need to mount on /mnt/efi if it is /boot/efi it would be /mnt/boot/efi …"
Great read. Thanks
I legit thought that was about to be the joke he was going for at first.
Basically all KDE apps have the same dependency set. So install one and the next ones will only install the app most likely. On KDE itself you’d already have these.