• 0 Posts
  • 31 Comments
Joined 1 year ago
cake
Cake day: June 16th, 2023

help-circle


  • This issue with glibc should have been sorted out. But yeah, if you use arch you may have some issues from time to time cause some projects broke their ABIs sometimes, but I prefer to use the one with pacman cause I only have to update my entire system with one command, also theming is an issue with flatpak that I know there is solutions out there but AFAIK are always adhoc solutions for each app.

    Also, IIRC steam folder is always in a weird place using flatpak.



  • Yeah, but you can also run as a windows user and be happy. I have my moments of “from scratch” guy, but sometimes I just throw all away and reinstall (or install another) my distro when I feel the issue is too obscure and should not be occurring. A lot of ppl judge me but I’m using only Linux for the past 3 years and I’m happy as removed with it. Even liking problem solving sometimes I just want to open a game and run, and yeah, I can do it in the exactly same lazy way of windows.













  • It should work, afaik chroot always use the binaries of the system you chrooted, so you will be able to use pacman normally. I don´t remember if chroot will mount the efi partition by default, you can do this before go to chroot (again, I’m have some memory issues but I believe that /dev does not mount as well if you just use chroot, this is why arch have arch-chroot that mounts this kind of stuff but you can mount before so it should work).

    Assuming you are using systemd boot on efi partition (that is likelly if you have not changed the installer defaults), what I would do:

    • On your live CD run sudo fdisk -l to get what is the efi partition, usually will be /dev/sdb1 since sda will be your usb, you should be able to see something like that.

    • Then you will mount your endevour partition, in your situation should be sudo mount /dev/sdb2 /mnt/mydisk but check your fdisk command output.

    • Now you will have to mount the efi partition sudo mount /dev/sdb1 /mnt/mydisk/efi

    • Then you can use chroot /mnt/mydisk/ and proceed to do a pacman -Syu, this should trigger the post scripts that create the kernel images on the efi partition.




  • For years I actually want to contribute, for any project that I use I don’t care, I just want to do something, but my English is not fluent, it is reasonable but not fluent, I have a little of social anxiety, and I have no bounds with anyone that contribute with these projects, so I am terrified of taking an issue to work. You know, I don’t want to do removed, and I probably does not know these projects so well so I feel a little stuck.
    I already opened some issues but I only did that