PacUI: Bash script providing advanced Pacman and Yay/Pikaur/Aurman/Pakku/Trizen/Pacaur functionality in a simple UI

cli
pacui
aur
pacman
yay

#281

I’ve never used the unstable branch on this laptop.
It is an unchanged stable install since may 2016.


#282

Well, this is great, I ran the clean system option and it removed my uncommented lines in pacman.conf I think.
It wanted to update networkmanager and 3 others, failed and the screen went black and now I’m unable to boot. :hushed:


#283

About your second screenshot. It looks you have both libnm-glib and networkmanager have the same files in libnm-glib folder, which is highly impossible as networkmanager package from manjaro’s extra repo doesn’t have those files ( running pacman -Fl extra/networkmanager | grep libnm yeilds no output ).

Also reading this :

It seems the errors are usually caused by using --force when installing packages…

So uhmm…

Did you get networkmanager package from outside source? And did you also by any chance using Force Update System from pacui options or using pacman’s --force option before?


#284

I don’t recall forcing the update, I always use Pamac to update.
I only haven’t updated networkmanager and it’s applet for quite a long time because of a broken icon.

I’ve installed pacUI just yesterday.

I guess I have to chroot into the system? I still can’t boot the system.


#285

Okay, I’ve chrooted into the system, but still getting the same errors while trying to update…
blabla is newer than bla bla…


#286

No. What it does, is to replace all SigLevel = strings with SigLevel = Never #. This allows pacman download and install packages without integrity check. You can easily undo it with this command :

sudo sed -i 's/SigLevel = Never #/SigLevel =/' /etc/pacman.conf

And that might explains why you got that unique errors from the second screenshot, and why you have failed to updated networkmanager ( most likely because of conflicting files)

As explained here from the ArchWiki, holding back packages ( or partial upgrades ) are not supported as there will be a breakage when your outdated packages use a newer library…


And did you do anything in it besides running Clean System option?


If you are sure you never changed branch, then what happened most likely because your mirrors got switched into outdated mirrors. Which most likely explains why the package in your local system is ‘newer’ than the one in the mirrors…


#287

Weird isn’t it?
I’m sure I never switched branch, absolutely, because this is my production machine. :thinking:

Do you know what I can do to fix it?

[root@manjaro /]# pacman -Syu
:: Pakket-databases synchroniseren...
 core is up-to-date
 extra is up-to-date
 community is up-to-date
 multilib is up-to-date
:: Volledige systeemsupgrade starten...
waarschuwing:avahi: lokaal (0.7-1) is nieuwer dan extra (0.6.32-3)
waarschuwing:bluez: lokaal (5.46-1) is nieuwer dan extra (5.45-1)
waarschuwing:bluez-libs: lokaal (5.46-1) is nieuwer dan extra (5.45-1)
waarschuwing:cups-filters: lokaal (1.16.0-2) is nieuwer dan extra (1.14.1-1)
waarschuwing:device-mapper: lokaal (2.02.173-1) is nieuwer dan core (2.02.172-2)
waarschuwing:dunstify: lokaal (1.2.0-1) is nieuwer dan community (1.1.0-1)
waarschuwing:faac: lokaal (1.29.3-1) is nieuwer dan extra (1.28-5)
waarschuwing:faad2: lokaal (2.8.1-1) is nieuwer dan extra (2.7-4)
waarschuwing:fontconfig: lokaal (2.12.4-1) is nieuwer dan extra (2.12.3-1)
waarschuwing:fzf: lokaal (0.16.10-1) is nieuwer dan community (0.16.8-1)
waarschuwing:gedit: lokaal (3.22.1+1+gd21912e3e-1) is nieuwer dan extra (3.22.0+44+ge706c1259-1)
waarschuwing:ghostscript: lokaal (9.21-3) is nieuwer dan extra (9.21-2)
waarschuwing:git: lokaal (2.13.4-1) is nieuwer dan extra (2.13.3-2)
waarschuwing:glew: lokaal (2.1.0-1) is nieuwer dan extra (2.0.0-1)
waarschuwing:gnome-online-accounts: lokaal (3.24.2-1) is nieuwer dan extra (3.24.1-1)
waarschuwing:gptfdisk: lokaal (1.0.3-1) is nieuwer dan extra (1.0.1-2)
waarschuwing:gsfonts: lokaal (20170720-1) is nieuwer dan extra (20170501-1)
waarschuwing:gtk-update-icon-cache: lokaal (3.22.17-1) is nieuwer dan extra (3.22.16-1)
waarschuwing:gtk3: lokaal (3.22.17-1) is nieuwer dan extra (3.22.16-1)
waarschuwing:gtk3-print-backends: lokaal (3.22.17-1) is nieuwer dan extra (3.22.16-1)
waarschuwing:gtkspell: lokaal (2.0.16-4) is nieuwer dan extra (2.0.16-3)
waarschuwing:gvfs: lokaal (1.32.1+5+gf0d758df-1) is nieuwer dan extra (1.32.1+3+gd852665e-1)
waarschuwing:gvfs-afc: lokaal (1.32.1+5+gf0d758df-1) is nieuwer dan extra (1.32.1+3+gd852665e-1)
waarschuwing:gvfs-gphoto2: lokaal (1.32.1+5+gf0d758df-1) is nieuwer dan extra (1.32.1+3+gd852665e-1)
waarschuwing:gvfs-mtp: lokaal (1.32.1+5+gf0d758df-1) is nieuwer dan extra (1.32.1+3+gd852665e-1)
waarschuwing:gvfs-smb: lokaal (1.32.1+5+gf0d758df-1) is nieuwer dan extra (1.32.1+3+gd852665e-1)
waarschuwing:gvim: lokaal (8.0.0851-1) is nieuwer dan extra (8.0.0722-1)
waarschuwing:hplip: lokaal (3.17.7-1) is nieuwer dan extra (3.17.6-2)
waarschuwing:inxi: lokaal (2.3.28-1) is nieuwer dan community (2.3.23-1)
waarschuwing:jre8-openjdk: lokaal (8.u144-1) is nieuwer dan extra (8.u141-1)
waarschuwing:jre8-openjdk-headless: lokaal (8.u144-1) is nieuwer dan extra (8.u141-1)
waarschuwing:lib32-expat: lokaal (2.2.2-1) is nieuwer dan multilib (2.2.0-1)
waarschuwing:lib32-glew: lokaal (2.1.0-1) is nieuwer dan multilib (2.0.0-1)
waarschuwing:lib32-libdrm: lokaal (2.4.82-1) is nieuwer dan multilib (2.4.81-1)
waarschuwing:lib32-libjpeg-turbo: lokaal (1.5.2-1) is nieuwer dan multilib (1.5.1-1)
waarschuwing:lib32-libpng: lokaal (1.6.30-1) is nieuwer dan multilib (1.6.29-1)
waarschuwing:lib32-mesa-demos: lokaal (8.3.0-3) is nieuwer dan multilib (8.3.0-2)
waarschuwing:lib32-systemd: lokaal (234.11-0) is nieuwer dan multilib (233.75-2)
waarschuwing:lib32-util-linux: lokaal (2.30.1-1) is nieuwer dan multilib (2.29.2-1)
waarschuwing:libdrm: lokaal (2.4.82-1) is nieuwer dan extra (2.4.81-1)
waarschuwing:libgcrypt: lokaal (1.8.0-1) is nieuwer dan core (1.7.8-1)
waarschuwing:libgusb: lokaal (0.2.11-1) is nieuwer dan extra (0.2.10-1)
waarschuwing:libmwaw: lokaal (0.3.12-1) is nieuwer dan extra (0.3.11-1)
waarschuwing:libpipeline: lokaal (1.4.2-1) is nieuwer dan core (1.4.1-1)
waarschuwing:libpng: lokaal (1.6.31-1) is nieuwer dan extra (1.6.30-1)
waarschuwing:libproxy: lokaal (0.4.15-4) is nieuwer dan extra (0.4.15-3)
waarschuwing:libreoffice-still: lokaal (5.3.5-1) is nieuwer dan extra (5.2.7-1)
waarschuwing:libreoffice-still-nl: lokaal (5.3.5-1) is nieuwer dan extra (5.2.7-1)
waarschuwing:libsrtp: lokaal (1:1.5.4-2) is nieuwer dan extra (1:1.5.4-1)
waarschuwing:libsystemd: lokaal (234.11-4) is nieuwer dan core (233.75-3)
waarschuwing:libva: lokaal (1.8.3-1) is nieuwer dan extra (1.8.2-1)
waarschuwing:libva-intel-driver: lokaal (1.8.3-1) is nieuwer dan extra (1.8.2-1)
waarschuwing:libwnck3: lokaal (3.24.1-1) is nieuwer dan extra (3.24.0-1)
waarschuwing:libwps: lokaal (0.4.7-1) is nieuwer dan extra (0.4.6-1)
waarschuwing:libxkbcommon: lokaal (0.7.2-1) is nieuwer dan extra (0.7.1-1)
waarschuwing:libxkbcommon-x11: lokaal (0.7.2-1) is nieuwer dan extra (0.7.1-1)
waarschuwing:light-locker: lokaal (1.8.0-1) is nieuwer dan community (1.6.0-3)
waarschuwing:linux-firmware: lokaal (20170622.7d2c913-1) is nieuwer dan core (20170422.ade8332-1)
waarschuwing:linux44: lokaal (4.4.79-1) is nieuwer dan core (4.4.78-1)
waarschuwing:linux44-ndiswrapper: lokaal (1.61-23) is nieuwer dan extra (1.61-22)
waarschuwing:linux49: lokaal (4.9.40-1) is nieuwer dan core (4.9.39-1)
waarschuwing:linux49-ndiswrapper: lokaal (1.61-32) is nieuwer dan extra (1.61-31)
waarschuwing:lvm2: lokaal (2.02.173-1) is nieuwer dan core (2.02.172-2)
waarschuwing:man-pages: lokaal (4.12-1) is nieuwer dan core (4.11-1)
waarschuwing:manjaro-hello: lokaal (0.5.5-1) is nieuwer dan extra (0.5.3-1)
waarschuwing:mesa-demos: lokaal (8.3.0-3) is nieuwer dan extra (8.3.0-2)
waarschuwing:mhwd-nvidia: lokaal (1:375.82-1) is nieuwer dan core (1:375.66-1)
waarschuwing:mpg123: lokaal (1.25.4-1) is nieuwer dan extra (1.25.3-1)
waarschuwing:nano: lokaal (2.8.6-1) is nieuwer dan core (2.8.5-1)
waarschuwing:netctl: lokaal (1.13-2) is nieuwer dan core (1.12-2)
waarschuwing:openal: lokaal (1.18.1-1) is nieuwer dan extra (1.18.0-2)
waarschuwing:openvpn: lokaal (2.4.3-3) is nieuwer dan core (2.4.3-2)
waarschuwing:pamac: lokaal (4.9.1-1) is nieuwer dan extra (4.3.7-1)
waarschuwing:perl-http-cookies: lokaal (6.04-1) is nieuwer dan extra (6.03-2)
waarschuwing:perl-uri: lokaal (1.72-1) is nieuwer dan extra (1.71-2)
waarschuwing:poppler: lokaal (0.57.0-1) is nieuwer dan extra (0.56.0-1)
waarschuwing:poppler-glib: lokaal (0.57.0-1) is nieuwer dan extra (0.56.0-1)
waarschuwing:python-requests: lokaal (2.18.3-1) is nieuwer dan extra (2.18.1-1)
waarschuwing:python-setuptools: lokaal (1:36.2.7-1) is nieuwer dan extra (1:36.2.2-1)
waarschuwing:python-urllib3: lokaal (1.22-1) is nieuwer dan extra (1.21.1-1)
waarschuwing:python2-cryptography: lokaal (2.0.3-1) is nieuwer dan extra (2.0-1)
waarschuwing:python2-pyopenssl: lokaal (17.2.0-1) is nieuwer dan extra (17.1.0-1)
waarschuwing:python2-setuptools: lokaal (1:36.2.7-1) is nieuwer dan extra (1:36.2.2-1)
waarschuwing:recode: lokaal (3.6-10) is nieuwer dan extra (3.6-9)
waarschuwing:sdl: lokaal (1.2.15-9) is nieuwer dan extra (1.2.15-8)
waarschuwing:sqlite: lokaal (3.20.0-1) is nieuwer dan core (3.19.3-1)
waarschuwing:systemd: lokaal (234.11-4) is nieuwer dan core (233.75-3)
waarschuwing:systemd-sysvcompat: lokaal (234.11-4) is nieuwer dan core (233.75-3)
waarschuwing:talloc: lokaal (2.1.10-1) is nieuwer dan extra (2.1.9-1)
waarschuwing:unrar: lokaal (1:5.5.7-1) is nieuwer dan extra (1:5.5.6-2)
waarschuwing:update-notifier: lokaal (0.6.4-1) is nieuwer dan community (0.6.2-3)
waarschuwing:vim-runtime: lokaal (8.0.0851-1) is nieuwer dan extra (8.0.0722-1)
waarschuwing:wine: lokaal (2.14-1) is nieuwer dan multilib (2.13-1)
waarschuwing:xf86-input-wacom: lokaal (0.35.0-1) is nieuwer dan extra (0.34.2-1)
waarschuwing:youtube-dl: lokaal (2017.07.30.1-1) is nieuwer dan community (2017.07.15-1)
waarschuwing:zziplib: lokaal (0.13.67-1) is nieuwer dan extra (0.13.66-2) ```

#288

First try switching your mirrors to the one that are more up-to-date :

sudo pacman-mirrors -c all -f 1 -y
sudo pacman -Syu

And then we try resolve on what went failed in clean system option from pacui. Can you give a little details on what exactly that went failed in there? Is it from installing networkmanager-dispatcher-ntpd ? Or reinstalling systemd packages and its friends?

Also it might be a good idea to explain what exactly shows from your screen when you fail to boot…


#289

I did a system clean, this went fine, but after doing this pamac’s icon went green and I had 4 updates, all had to do with the network and its icon.

I tried to update this and pamac crashed, actually, the whole system crashed and was unable to reboot.

I can see the grub and that is all.

:: Pakket-databases synchroniseren...
 core is up-to-date
 extra is up-to-date
 community is up-to-date
 multilib is up-to-date
:: Volledige systeemsupgrade starten...
afhankelijkheden oplossen...
fout:kan bestand /var/lib/pacman/local/networkmanager-1.8.2-1/desc: Bestand of map bestaat niet niet openen
zoeken naar conflicterende pakketten...

Pakketten (1) gnupg-2.1.22-1

Totale Download Grootte:         2,04 MiB
Totale Geïnstalleerde Grootte:   9,06 MiB
Netto Upgrade Grootte:           0,24 MiB

:: Doorgaan met de installatie? [J/n] j
:: Pakketten ophalen...
 gnupg-2.1.22-1-x86_64      2,0 MiB   908K/s 00:02 [######################] 100%
(1/1) sleutels in sleutelbos controleren           [######################] 100%
(1/1) pakketintegriteit controleren                [######################] 100%
(1/1) pakketbestanden laden                        [######################] 100%
(1/1) controleren van conflicterende bestanden     [######################] 100%
(1/1) beschikbare schijfruimte controleren         [######################] 100%
:: Pakketveranderingen verwerken...
(1/1) upgraden gnupg                               [######################] 100%
:: Uitvoeren na-transactie hooks...
(1/2) Arming ConditionNeedsUpdate...
(2/2) Updating the info directory file... ```

#290

Can you look at the contents of /var/log/pacman.log and paste it here. I need to see what packages are failed to update…


#291

Eeehhm, how can I open pacman.log after chroot into the system?

Oops, got it…

[2017-08-14 12:10] [ALPM] installed expac (8-1)
[2017-08-14 12:10] [ALPM] transaction completed
[2017-08-14 12:10] [ALPM] running 'systemd-update.hook'...
[2017-08-14 12:10] [ALPM] transaction started
[2017-08-14 12:10] [ALPM] removed pacui (1.5-1)
[2017-08-14 12:10] [ALPM] installed pacui-git (1.6.1-1)
[2017-08-14 12:10] [ALPM] transaction completed
[2017-08-14 12:10] [ALPM] running 'systemd-update.hook'...
[2017-08-14 12:11] [PACMAN] Running 'pacman -Rsn --color always a52dec'
[2017-08-14 12:13] [PACMAN] Running 'pacman -Syy'
[2017-08-14 12:13] [PACMAN] synchronizing package lists
[2017-08-14 12:13] [PACMAN] Running 'pacman -Syy'
[2017-08-14 12:13] [PACMAN] synchronizing package lists
[2017-08-14 12:13] [PACMAN] Running 'pacman -Sy --noconfirm networkmanager-dispatcher-ntpd'
[2017-08-14 12:13] [PACMAN] synchronizing package lists
[2017-08-14 12:13] [ALPM] transaction started
[2017-08-14 12:13] [ALPM] reinstalled networkmanager-dispatcher-ntpd (1.0-6)
[2017-08-14 12:13] [ALPM] transaction completed
[2017-08-14 12:13] [ALPM] running 'systemd-update.hook'...
[2017-08-14 12:14] [PACMAN] Running 'pacman -Sy --noconfirm gnupg'
[2017-08-14 12:14] [PACMAN] synchronizing package lists
[2017-08-14 12:14] [ALPM] transaction started
[2017-08-14 12:14] [ALPM] downgraded gnupg (2.1.22-1 -> 2.1.21-3)
[2017-08-14 12:14] [ALPM] transaction completed
[2017-08-14 12:14] [ALPM] running 'systemd-update.hook'...
[2017-08-14 12:14] [ALPM] running 'texinfo-install.hook'...
[2017-08-14 12:14] [PACMAN] Running 'pacman -Sy --noconfirm archlinux-keyring manjaro-keyring'
[2017-08-14 12:14] [PACMAN] synchronizing package lists
[2017-08-14 12:14] [ALPM] transaction started
[2017-08-14 12:14] [ALPM] reinstalled archlinux-keyring (20170611-1)
[2017-08-14 12:14] [ALPM] reinstalled manjaro-keyring (20170603-1)
[2017-08-14 12:14] [ALPM-SCRIPTLET]  >>> Run `pacman-key --init` to set up your pacman keyring.
[2017-08-14 12:14] [ALPM-SCRIPTLET]  >>> Then run `pacman-key --populate manjaro` to install the Manjaro keyring.
[2017-08-14 12:14] [ALPM] transaction completed
[2017-08-14 12:14] [ALPM] running 'systemd-update.hook'...
[2017-08-14 12:14] [PACMAN] Running 'pacman -Sc --noconfirm'
[2017-08-14 12:15] [PACMAN] Running 'pacman -Syu --color always'
[2017-08-14 12:15] [PACMAN] synchronizing package lists
[2017-08-14 12:15] [PACMAN] starting full system upgrade
[2017-08-14 12:15] [PACMAN] Running 'pacman --color auto -Sy'
[2017-08-14 12:15] [PACMAN] synchronizing package lists
[2017-08-14 12:16] [PACMAN] synchronizing package lists
[2017-08-14 12:16] [PACMAN] starting full system upgrade
[2017-08-14 12:23] [PACMAN] Running 'pacman -Syu --color always'
[2017-08-14 12:23] [PACMAN] synchronizing package lists
[2017-08-14 12:23] [PACMAN] starting full system upgrade
[2017-08-14 12:23] [PACMAN] Running 'pacman --color auto -Sy'
[2017-08-14 12:23] [PACMAN] synchronizing package lists
[2017-08-14 13:15] [PACMAN] Running 'pacman -Syy'
[2017-08-14 13:15] [PACMAN] synchronizing package lists
[2017-08-14 13:19] [PAMAC] synchronizing package lists
[2017-08-14 13:20] [ALPM] transaction started
[2017-08-14 13:20] [ALPM] upgraded network-manager-applet (1.4.0-1 -> 1.8.2-1)
[2017-08-14 13:20] [ALPM] warning: directory permissions differ on /etc/NetworkManager/system-connections/
filesystem: 755  package: 700
[2017-08-14 14:33] [PACMAN] Running 'pacman -Syu'
[2017-08-14 14:33] [PACMAN] synchronizing package lists
[2017-08-14 14:33] [PACMAN] Running 'pacman -Syu'
[2017-08-14 14:33] [PACMAN] synchronizing package lists
[2017-08-14 14:34] [PACMAN] Running 'pacman -U /var/cache/pacman/pkg/networkmanager-1.8.2-1-x86_64.pkg.tar.xz'
[2017-08-14 15:03] [PACMAN] Running 'pacman -Syu'
[2017-08-14 15:03] [PACMAN] synchronizing package lists
[2017-08-14 15:03] [PACMAN] starting full system upgrade
[2017-08-14 15:03] [ALPM] transaction started
[2017-08-14 15:03] [ALPM] upgraded xfce4-netload-plugin (1.2.4-3 -> 1.3.1-1)
[2017-08-14 15:03] [ALPM] upgraded xfce4-systemload-plugin (1.1.2-2 -> 1.2.1-1)
[2017-08-14 15:03] [ALPM] transaction completed
[2017-08-14 15:03] [ALPM] running 'gtk-update-icon-cache.hook'...
[2017-08-14 15:03] [ALPM] running 'systemd-update.hook'...
[2017-08-14 15:03] [PACMAN] Running 'pacman -Syu --force'
[2017-08-14 15:03] [PACMAN] synchronizing package lists
[2017-08-14 15:03] [PACMAN] starting full system upgrade
[2017-08-14 16:03] [ALPM] transaction started
[2017-08-14 16:03] [ALPM] upgraded gnupg (2.1.21-3 -> 2.1.22-1)
[2017-08-14 16:03] [ALPM] transaction completed
[2017-08-14 16:03] [ALPM] running 'systemd-update.hook'...
[2017-08-14 16:03] [ALPM] running 'texinfo-install.hook'...

#292

sudo nano /var/log/pacman.log


#293

Nobody?

All I can think of is putting an image back, only it’s from april…so kinda old.


#294

Crap!
After restoring an image from april still nothing.

Now, shoot me, I am completely lost.

Edit: had to reboot twice and it booted, dunno what happened.


#295

BTW, this is USA only?
I don’t live in the USA…


#296

No, -c all argument makes it use mirrors from all locations in case you had set them to one country only.


#297

Are you sure?
I had set them to all country’s with pacman-mirrors -g, but after this command I get 1 mirror only, the USA.

Look…

## Manjaro Linux mirrorlist
## Generated on 2017-08-14 19:16
##
## Use pacman-mirrors to modify
##

## Country : United_States
Server = http://distro.ibiblio.org/manjaro/stable/$repo/$arch``

#298

wow, there are many posts here…

it looks like you ran the “fix pacman errors” option in pacui instead of the “clean system” option as i have suggested.
in any way, this should not have left your system in a state, in which your kernel does not boot. therefore, i am glad that this was not the case.

it has happened to me that xorg was broken or that i did not have internet connection after an update, but this can usually be fixed by switching to tty (ALT+CTRL+F2) and starting pacui there. then, you can run “roll back system” and downgrade xorg/networkmanager and your system should be fixed temporarily.


pacui runs “sudo pacman-mirrors -g -y” for you. it seems that something is not working on pacman-mirrors’ side and you end up with an outdated manjaro mirror.
do you use an old version of pacman-mirrors.conf?
you can manually set your mirror server in the mirrorlist file (the server at the top, which is not commented out, is used).

you can use “configure system” option in pacui to easily find important config files…


please report back, when you know why pacman-mirrors always gives you an outdated mirror. we can report that error to paman-mirrors’ developer or integrate a fix into the “fix pacman errors” option in pacui.


your log file shows that you have now an updated (but still outdated) networkmanager package installed. but this shows an error:

is networkmanager updated properly on your system now?


#299

To set it back with all country, you need to run this command :

sudo pacman-mirrors -c all -g -y

#300

Since I wasn’t able to get things going I decided to put the image I made in april back.
Now the systemmonitorapplet is up to date and really ugly.

Why is there a possibility to downgrade packages when I’m supposed to keep things up to date?
A downgraded package leads to a partial upgraded system imho…