Conversation
Notices
-
Embed this notice
In addition to getting desecrated with libadw*ita, Gajim also started routinely forgetting passwords and pestering me to type them again.
- :ihavenomouth: likes this.
-
Embed this notice
@mint that happens every other time i restart my computer (twice a year)
-
Embed this notice
@Inginsub @mint Freedesktop Secrets service moment and kwallet being incredibly bad at its job.
-
Embed this notice
@phnt @Inginsub Once I'm free from current wageslavery sesh (one more week) I'll switch to MATE. Would probably have to find a new client as well.
-
Embed this notice
@Inginsub @mint Dude, I had a real linux moment last night, I downloaded mpd & ncmpcpp to play some dsd files. Next thing I know, pacman won't run & errors out saying libicuui.so.76 no file or command found. Try to use browser to download pacman-static, it just closes the browser whenever I download anything. So I end up using curl to download it. Run pacman-static. None of the hooks are working. FUCK FUCK FUCK. I try like 3-4 things, nada. Reboot into live USB. Ah shit I'm running Full Disk Encryption, time to learn how to mount logical and physical volumes in a liveUSB. Chroot in, pacman update. Ducking hell getting errors everywhere about dkms failing exit code 10. Google it, ah. I forgot to make proc and sysfs(?), make those, still getting the same error. Using my phone to troubleshoot, bastard thing has light mode. Exit chroot, go back into chroot try like 10 different things, reinstall linux-hardened. It works. Still don't know what did it but I'm glad. Full Disk Encryption was not easy to setup.
-
Embed this notice
@kirbius @Inginsub Either thar or partial upgrades which then might pull newer libs while not upgrading the rest of the system that link against said libs. As usual, static linking was a mistake. Rolling releases are also a mistake.
-
Embed this notice
@kirbius @Inginsub I thought pacman learned to stop shitting itself during dynalibs updates, did it crash during some previous update or what?
-
Embed this notice
@phnt @Inginsub @kirbius @mirage @mint a friend was having a good time with arch, said, "shoulda tried it sooner" then boom, upgrade, ended up with a broken system, he went back to debian
-
Embed this notice
@kirbius @Inginsub @mirage @mint You can use `pacman -S foobar` safely without updating. Worst case your repos diverged enough that some packages will not have old versions your local repo expects and it will fail. What you should never do unless you know what you are doing is `pacman -Sy foobar`.
Also if you have an AUR helper, always use the AUR helper to update the system, because it is almost always dynamically linked against libalpm which is versioned and the AUR helper won't then run without a rebuild. If you use the helper to update, the old version will already be loaded and the package release will hopefully be bumped for a rebuild when you update the system.
-
Embed this notice
@phnt @Inginsub @mirage @mint "I know what I am doing" vs "Be prepared to read a ton and break a dozen systems in the meantime". I feel like I need to get into the habit of: pacman -Syu [package] instead of pacman -S [package]. or at least upgrade more frequently.
-
Embed this notice
@mirage @Inginsub @kirbius @mint
>"always assume the user is a retarded toddler or a demented grandma"
Yes, at the same time Arch isn't a normie distro and it should never be one. Same with Gentoo. Using them should already come with a "I know what I am doing" requirement.
Should pacman be statically linked by default? Yes. Should issues caused by lack of reading basics docs likely linked in install docs be classified as "Arch broke once again"? No.
-
Embed this notice
@mirage @Inginsub @kirbius @mint dpkg/apt is far far worse. Upgrading between releases is a lottery. Dependency resolution is a meme. Ability to disable annoying safeguards is non-existent.
At least for pacman the lack of partial upgrades support is clearly stated in the wiki and is usually well known.
-
Embed this notice
@phnt @Inginsub @kirbius @mint
>Upgrading between releases is a lottery.
Never had any issues with that. Maybe I should get a lottery ticket :terrylol2:
>usually well known
There is a significant amount of users who refuse to read any wiki or manual. Assuming that users know something will never end good.
Reminds me of something a professor at Uni once told me, "always assume the user is a retarded toddler or a demented grandma".
-
Embed this notice
@mint @Inginsub @kirbius Usually whenever apt breaks something it can be fixed with a `--fix-broken install`. When pacman breaks it blows up the whole installation.
-
Embed this notice
@mirage @Inginsub @kirbius Would argue apt is worse.
-
Embed this notice
@mint @kirbius @Inginsub For pacman to learn its lesson it would have to be completely rewritten from scratch. It's such a bad package manager no amount of updates will ever fix it.
-
Embed this notice
@mint @Inginsub This i think, not the before. The only mistake I made was not upgrading the rest of the system. A bunch of programs all wanted 76, but I had 78 iirc. I tried copying 78 to 76 in /usr/lib/ to see if the part of the library it wanted would still work but no cigar. Rolling release ensures every day is a troubleshooting/learning/headache day.
-
Embed this notice
@kirbius @Inginsub @mint >Dude, I had a real linux moment last night, I downloaded mpd & ncmpcpp to play some dsd files.
could've stopped there
-
Embed this notice
@kirbius @Inginsub @mint how do you not know to mount stuff and arch-chroot?
-
Embed this notice
@mint @Inginsub @phnt mate is neat, i dont like super basic stuff but when i used it it was ncie
-
Embed this notice
@kirbius @Inginsub Sometimes symlinking helps, sometimes it doesn't and I have to whip a hex editor if I'm too lazy to rebuild something (mostly the case with telegram-desktop that I've patched to raise account limit and disable sponsored messages). Sometimes even that doesn't help and it starts smegfaulting then I have no choice but.
-
Embed this notice
@phnt @Inginsub @mint I haven't had kwallet issues until i tried opensuse and the gentoo live install dvd. but on my installed gentoo system i had no issues. that said i wasnt prompted to make a kwallet password on gentoo, but the wallet does exist
-
Embed this notice
@mint @Inginsub @phnt
-
Embed this notice
@mirage @Inginsub @kirbius @mint in rust?
-
Embed this notice
@menherahair @Inginsub @mint
computer-in-the-air.png
-
Embed this notice
@mirage @Inginsub @mint you know what I like, alpine's apk package manager, its pretty nice to use. not sure why i like it though.
-
Embed this notice
@mischievoustomato @Inginsub @mint
So mostly, trying to rediscover LUKS volumes in order to remount. It's been a couple months since I put the system together and was the first time I've tried LUKS, safe to say I semi-blind followed the install guide for Full Disk Encryption, I know how to mount in general and in my case artix-chroot, however trying to upgrade the kernel in a chrooted system requires a few extra commands I didn't know I needed to do before:
mount -t proc proc /mnt/proc
mount --rbind /sys /mnt/sys
mount --rbind /dev /mnt/dev.
This isn't exact for my system, but just from the wiki. If you try and update the system without these directories mounted, there are issues with pacnew and mkinitcpio and a few other things that appear and you need to resolve.
-
Embed this notice
@kirbius @Inginsub @mint odd, to my understanding arch-chroot (which is also on gentoo) does those mounts automatically
-
Embed this notice
@mischievoustomato @Inginsub @mint so the wiki says not to chroot, but to use the --root flag on pacman. however because I was following no less than 3 forum posts I got my wires crossed. and attempted both ways , both without the chroot and the root flag.
-
Embed this notice
@kirbius @Inginsub @mint oot oot lo
-
Embed this notice
@phnt @Inginsub @kirbius @mirage @mint gentoo is ubuntu tier, i could install it
:ihavenomouth:
Phantasm
kirbius
menherahair
All GNU social JP content and data are available under the 