I just installed Artix Linux on a new Framework (AMD64) laptop.
Installation done through community-qt: artix-community-qt-openrc-20230814-x86_64.iso
I have two issues:
1) When I launch many executables, they return an error message and fail to run; e.g.:
~> vi
OK
~> kate
OK
~> qtcreator
qtcreator: error while loading shared libraries: libicuuc.so.74: cannot open shared object file: No such file or directory
~> gimp
gimp: symbol lookup error: /usr/lib/libgimpbase-2.0.so.0: undefined symbol: g_once_init_leave_pointer
~> clang
clang: error while loading shared libraries: libLLVM-17.so: cannot open shared object file: No such file or directory
~> meld
Traceback (most recent call last):
File "/usr/bin/meld", line 96, in <module>
import meld.conf # noqa: E402
^^^^^^^^^^^^^^^^
ModuleNotFoundError: No module named 'meld'
It looks like during the installation a set of shared libraries have not been installed.
2) When I update the system I keep getting error messages no matter which options I select during the process.
# rm -r /etc/pacman.d/gnupg
# pacman-key --init
# pacman -Sy archlinux-keyring artix-keyring
# pacman-key --populate archlinux artix
# pacman -Scc
# pacman -Syyu
:: Synchronising package databases...
:: Starting full system upgrade...
:: Replace kactivities with world/kactivities5? [Y/n]
...same question for tens of packages...
looking for conflicting packages...
warning: removing 'alpm-octopi-utils' from target list because it conflicts with 'liboctopi'
error: failed to prepare transaction (could not satisfy dependencies)
:: unable to satisfy dependency 'libalpm_octopi_utils.so=1-64' required by octopi
:: removing kactivities breaks dependency 'kactivities' required by telepathy-kde-integration-module
The package involved is not always the same.
Thank you for your help.
I guess some stuff got bootstrapped wrong if the installation was done through UI. You'd have to reinstall with weekly ISO. As far as I know those official ISOs were not updated in quite a while due to devs spinning up some new way of creating those + cooking new installer, but that's something the devs should answer. That said, I never seen a point of installing rolling release distro from old ISO, it's just seems kinda pointless.
@Shoun2137 - I used an "old" official ISO because I thought it was more stable and tested than a weekly one.
Yep, the thing I can confirm and agree upon is that those current community ISOs are really bad - I had similar issues down the line with pacman config, keyring issues, locale issues, etc. Welp, We should hope the stuff that Artix devs cook is based enough and just works, because those ISOs definitely don't. ;/
It is a common mistake to think that a stable installer image is better. Currently Artix can only be installed using a weekly image.
I don't think it's related to the ISO's. My Artix linux install which was 6 years old got nuked last night by an ICU update and it's stupidity except mine was looking for 75 not 74 like the OP. Still in the process of rebuilding as I type this.
This is not an iso issue, something updated in the last day that's causing this.
Seems like the issue is that liboctopi wants to replace alpm_octopi_utils
just tried a full update and all completed without issue. :D cheers devs.