That’s in the pacman-contrib package, which you won’t have installed, because that was split off from the pacman package in more recent times than the last time you updated your system. And the problem is that, because your system is not up to date, you won’t be able to install that at this time.
sudo pacman -Rns python2-cairo python2-gobject2 python2-numpy python2-setuptools python2
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: removing python2-cairo breaks dependency 'python2-cairo' required by pygtk
:: removing python2-gobject2 breaks dependency 'python2-gobject2' required by pygtk
Add it to the pile.
sudo pacman -Rns python2-cairo python2-gobject2 python2-numpy python2-setuptools python2 pygtk
(unless you now realize you do want those things because you dont want to sacrifice pygtk …)
sudo pacman -Rns python2-cairo python2-gobject2 python2-numpy python2-setuptools python2 pygtk 127 ✘
[sudo] password for sham:
checking dependencies...
:: jdk-openjdk optionally requires gtk2: for the Gtk+ 2 look and feel - desktop usage
:: jre11-openjdk optionally requires gtk2: for the Gtk+ 2 look and feel - desktop usage
:: pass optionally requires gtk2: pinentry backend (gtk2)
:: pinentry optionally requires gtk2: gtk2 backend
Packages (9) gtk2-2.24.33-3 libglade-2.6.4-8 openssl-1.1-1.1.1.w-1 pygtk-2.24.0-12 python2-2.7.18-8 python2-cairo-1.19.1-2 python2-gobject2-2.28.7-7 python2-numpy-1.16.6-3
python2-setuptools-2:44.1.1-2
Total Removed Size: 142.65 MiB
:: Do you want to remove these packages? [Y/n] Y
:: Processing package changes...
(1/9) removing pygtk [##################################################################] 100%
(2/9) removing libglade [##################################################################] 100%
(3/9) removing gtk2 [##################################################################] 100%
(4/9) removing python2-setuptools [##################################################################] 100%
(5/9) removing python2-numpy [##################################################################] 100%
(6/9) removing python2-gobject2 [##################################################################] 100%
(7/9) removing python2-cairo [##################################################################] 100%
(8/9) removing python2 [##################################################################] 100%
(9/9) removing openssl-1.1 [##################################################################] 100%
:: Running post-transaction hooks...
(1/2) Arming ConditionNeedsUpdate...
(2/2) Refreshing PackageKit...
That worked! Now I still have those ocaml and lib things
If you are intent on just removing all the foreign packages then we can print them onto the removal line like so;
sudo pacman -Rns $(pacman -Qmq)
1 Like
Perfect, it’s saying that my system is up to date.
So now, you guys were saying that I need a new Kernal. How do I get that? Do I just reinstall Manjaro?
No reinstall needed.
You can just install the packages, but rather I suggest using the in-house tool;
sudo mhwd-kernel -i linux66
That will install 6.6 which is the latest LTS (long term support) … it will be around for a few years.
Let us know if there is any error.
You should be able to select your kernel from GRUB during boot.
1 Like
I installed it but I don’t see where I can select my kernalduring boot.
Are you talking about selecting it in the BIOS?
When I reset my computer I just get my KDE desktop.
Depending on configuration GRUB may be hidden.
Grub is the default bootloader.
It is different from BIOS, but in terms of menus or visuals, it would be after BIOS, before Login.
I started to write about it but its mostly in this wiki entry here:
https://wiki.archlinux.org/title/GRUB#GRUB_is_installed_but_the_menu_is_not_shown_at_boot
If its not too important and you just want to see what kernel you are running now you could use
uname -r
1 Like
uname -r
6.6.26-1-MANJARO
GRUB_TIMEOUT_STYLE was set to hidden so I changed it to menu
I see grub on boot, thanks.
Ok, so the system is up to date and I have the updated Kernel.
So, moving forward I shouldn’t have any problems right? I just have to keep it updated?
1 Like
So now that we are relatively sure you have the right base packages…
Lets check on those pacnews 
pacdiff -o
pacdiff -o
zsh: command not found: pacdiff
Oh still no?
I thought we installed it…
sudo pacman -Syu pacman-contrib
then
pacdiff -o
pacdiff -o
/usr/share/icons/default/index.theme.pacnew
/etc/passwd.pacnew
/etc/shells.pacnew
/etc/locale.gen.pacnew
/etc/default/grub.pacnew
/etc/pamac.conf.pacnew
/etc/mkinitcpio.conf.pacnew
/etc/pacman.conf.pacnew
/etc/pam.d/sddm.pacnew
1 Like
Actually not too bad.
The basic idea is this:
pacman wont overwrite configuration files that have changes in them.
Instead it will create a *.pacnew file.
The pacnew file should be compared to the current file … moving in any upstream changes while preserving your local settings.
I use meld as probably the easiest comparison tool.
We can make sure its installed first;
sudo pacman -Syu meld
And now we can use pacdiff to manage those pacnews.
Use s to skip files (do that for passwd), v to view and make changes, etc, as the prompt shows.
DIFFPROG=meld pacdiff -s
I will also give an example …
pacman,conf.pacnew will contain some differences to your existing pacman.conf.
You will want to merge those changes. In meld you can use the little arrow buttons on highlighted lines to add text from one sample to the other.
You will notice that for example the section for the [community] repo will be missing from the pacnew. Edit your exisintg pacman.conf to remove that section, save, exit, and remove the pacnew when satisfied.
Note you can also skip pacnews, even after investigating them, and they will be retained until you check again.
It might seem scary, or a little too daunting, but its really not all that difficult, preserves user settings, and once you have these handled you will notice that you only get a few at a time every once in a while.
Heres the wiki.
1 Like
sudoedit: /etc/pamac.conf.pacnew unchanged
sudoedit: /etc/pamac.conf unchanged
:: (V)iew, (M)erge, (S)kip, (R)emove pacnew, (O)verwrite with pacnew, (Q)uit: [v/m/s/r/o/q] m
-> Unable to find a base package.
:: (V)iew, (M)erge, (S)kip, (R)emove pacnew, (O)verwrite with pacnew, (Q)uit: [v/m/s/r/o/q]
I dont know much about the m function.
Use v to view and while open also do the merges using meld.
I should also mention that manjaro-pacnew-checker exists and it aims to do pretty much the same job but using a GUI interface.
2 Likes
To be honest, I’m not sure I did that right but I finished editing it.
It should match the pacnew besides any extra configurations you may want to preserve.
So in the case of pacman.conf; if you have a custom repository then your local file should equal the pacnew plus that repository.
By the nature of pacnews it is difficult to give exact guidance beyond a case-by-case basis.
1 Like
I think I did that