When I check for updates in pamac it crashes with a segmentation fault error
Segmentation fault (core dumped)
I tried reinstalling all the pamac packages
pamac-cli, pamac-common and pamac-gtk
as well as pamac-flatpak-plugin and pamac-snap-plugin
even tho I don’t think it would do anything but didn’t change anything.
Than I Tried removing all the packages including the dependencies and doing sudo pacman -Scc and sudo paccache -r to clear any cached packages but it still does it.
As I see it, Manjaro, as Arch offspring, have no control of anything, just roll on Arch’s back. There is no encouragement for users to go report things upstream, as shown in this example by moderator @Wollie.
Just ignore problem until Arch fixes it, let them do dirty work, or in this case - very weird, because pamac is Manjaro project and bugs should be reported to Manjaro’s Pamac GitLab! Link: Issues · Applications / pamac · GitLab
This worries me, as my daily forum read consists 75% of things being broken, users lamenting and nothing is being done about it.
Yeah I know right, none of my clients or family member have the issue either but I did the command you suggested and everything looks fine but sadly it still crashes when checking for updates
[corey@Corey-PC ~]$ sudo pacman-mirrors -f5 && sudo pacman -Syyu
[sudo] password for corey:
::INFO Downloading mirrors from repo.manjaro.org
::INFO Using default mirror file
::INFO Querying mirrors - This may take some time
1.937 Austria : http://mirror.easyname.at/manjaro/
..... Austria : ftp://mirror.easyname.at/manjaro/
2.096 Chile : https://mirror1.cl.netactuate.com/manjaro/
1.658 Chile : http://mirror1.cl.netactuate.com/manjaro/
..... Chile : ftp://mirror1.cl.netactuate.com/manjaro/
3.032 Netherlands : https://ftp.nluug.nl/pub/os/Linux/distr/manjaro/
..... Netherlands : ftp://ftp.nluug.nl/pub/os/Linux/distr/manjaro/
1.632 United_States : https://mirrors.ocf.berkeley.edu/manjaro/
2.043 Costa_Rica : https://mirrors.ucr.ac.cr/manjaro/
::INFO Writing mirror list
::United_States : https://mirrors.ocf.berkeley.edu/manjaro/stable
::Costa_Rica : https://mirrors.ucr.ac.cr/manjaro/stable
::Chile : https://mirror1.cl.netactuate.com/manjaro/stable
::Austria : http://mirror.easyname.at/manjaro/stable
::Netherlands : https://ftp.nluug.nl/pub/os/Linux/distr/manjaro/stable
::INFO Mirror list generated and saved to: /etc/pacman.d/mirrorlist
:: Synchronizing package databases...
core 167.6 KiB 292 KiB/s 00:01 [################################] 100%
extra 1993.3 KiB 2.21 MiB/s 00:01 [################################] 100%
community 6.4 MiB 3.56 MiB/s 00:02 [################################] 100%
multilib 181.8 KiB 2.69 MiB/s 00:00 [################################] 100%
:: Starting full system upgrade...
there is nothing to do
I hope if anyone runs into this they can figure it out, I reinstalled to fix this issue and to see if it would fix another issue I have posted about which was to do with Steam proton but please don’t close this as we really should investigate what happened so we can work together to fix it
In pamac-manager, if you Refresh databases before selecting Updates, does it make any difference.
In Preferences > AUR, do you have Check for updates set. If so, try the above once with it unchecked.
You were correct in creating a bug report according to this thread.
pacman and pamac have their own sync database (/var/lib/pacman/sync vs /tmp/pamac).
There’s also another program called checkupdates. If there are no updates, there is no other feedback other than an exit status/return code of 2. But otherwise it’ll list the packages, their current version and new version. pacman-mirrors will show the current status of your mirrors, same as https://repo.manjaro.org/.
No refreshing the database with pacman -Syyu for example since that was my only way to do it did not fix it but I did a fresh install so I cant test to see if disabling the AUR will work now but that could of been the issue