Sorry, I am too new at this. Where is /etc/ - it is not in home
/home/username is in /home
/etc/pacman.conf is in /etc
new or not - you just need to look - use your file manager to look around
Iād rather not give you a command to easily edit the file because it would require you to use a terminal editor which you likely donāt know how to use
and damaging that file would ā¦ not be good
here it is anyway - figure out (read) how to operate that editor on some other files before you mess with files in /etc
sudo nano /etc/pacman.conf
You could probably do it with a GUI editor, but believe it or not:
I simply do not know how to use such thing to edit root owned files because I never do that.
plus: I donāt know which editor youād even have present
nano is definitely there
1 Like
Point of information;
If the GUI editor is modern enough and uses polkit nicely ā¦ then you dont need to do anything at all.
kate is one such example ā¦ simply open the file with kate, make edits, and if privileges are required you will be asked for them (password popup) when you attempt to save the file.
And I know you know this following bit, but Imma repeat it here
Under virtually no circumstances should one āsudo my-gui-programā.
1 Like
My file manager Thunar does not find it. Neither does Catfish. And no folder called etc
Are you still looking in your HOME folder?
A path like /etc/pacman.conf shows a full, not relative, path.
/ means Root, or the lowest level of the entire file system.
(Your users HOME, for example, is /home/scamidge/)
To empirically see if you have the file let us use a command;
find /etc/ -type f -name pacman.conf
PS.
Your comments seem to indicate an XFCE system.
I do not believe XFCE has a polkit-aware editor by default.
Which will mean you likely need to use a terminal text editor in any case, like nano or micro.
It would also mean finding the file through your file manager is unimportant.
And in which case nachlese already gave the command
1 Like
Terminal said
[steve@steve ~]$ find /etc/ -type f -name pacman.conf
find: ā/etc/cups/sslā: Permission denied
find: ā/etc/cryptsetup-keys.dā: Permission denied
find: ā/etc/optā: Permission denied
find: ā/etc/credstore.encryptedā: Permission denied
/etc/pacman.conf
find: ā/etc/NetworkManager/system-connectionsā: Permission denied
find: ā/etc/wireguardā: Permission denied
find: ā/etc/credstoreā: Permission denied
find: ā/etc/audit/plugins.dā: Permission denied
find: ā/etc/pacman.d/gnupg/crls.dā: Permission denied
find: ā/etc/pacman.d/gnupg/private-keys-v1.dā: Permission denied
find: ā/etc/pacman.d/gnupg/openpgp-revocs.dā: Permission denied
find: ā/etc/lvm/cacheā: Permission denied
find: ā/etc/polkit-1/rules.dā: Permission denied
find: ā/etc/samba/privateā: Permission denied
/etc/PackageKit/alpm.d/pacman.conf
find: ā/etc/sudoers.dā: Permission denied
[steve@steve ~]$ sudo find /etc/ -type f -name pacman.conf
[sudo] password for steve:
/etc/pacman.conf
/etc/PackageKit/alpm.d/pacman.conf
[steve@steve ~]$
This is after a backup done a week ago, and I am now also back to conflicts preventing updates.
So, yes, you do have the file.
Also apparently packagekit, which should be banished with prejudice.
We can come back to that later, but theres no good reason to have any packagekit packages installed, and every reason to avoid using packagekit anything on an Arch/Manjaro system.
Back to pacman.conf ā¦ please use the command already supplied to open and edit the file.
Ctrl+s will save, and Ctrl+x will exit, when you are finished.
1 Like
I tried sudo nano /etc/pacman.conf but do not see where to put the #
GNU nano 8.2 /etc/pacman.conf
/etc/pacman.conf
See the pacman.conf(5) manpage for option and repository directives
GENERAL OPTIONS
[options]
The following paths are commented out with their default values listed.
If you wish to use different paths, uncomment and update the paths.
#RootDir = /
#DBPath = /var/lib/pacman/
CacheDir = /var/cache/pacman/pkg/
#LogFile = /var/log/pacman.log
#GPGDir = /etc/pacman.d/gnupg/
#HookDir = /etc/pacman.d/hooks/
HoldPkg = pacman glibc manjaro-system
#XferCommand = /usr/bin/curl -C - -f %u > %o
#XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u
^G Help ^O Write Out ^F Where Is ^K Cut ^T Execute ^C Location
^X Exit ^R Read File ^\ Replace ^U Paste ^J Justify ^/ Go To Line
Keep scrolling down.
Or just press the down arrow ā to move the cursor line by line.
The next lines, in the middle of the file, are just below;
[...]
#XferCommand = /usr/bin/curl -L -C - -f -o %o %u
#XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u
#CleanMethod = KeepInstalled
Architecture = auto
# Pacman won't upgrade packages listed in IgnorePkg and members of IgnoreGroup
#IgnorePkg =
#IgnoreGroup =
#NoUpgrade =
#NoExtract =
[...]
The only Ignore has a # in front of it
Curious.
Well, you can exit out of there if you want.
We will run a command again to see about all āIgnoreā lines in the file;
grep Ignore /etc/pacman.conf
If we dont see anything relevant there then maybe check also drop-in files;
grep Ignore /etc/pacman.conf.d/*
[steve@steve ~]$ grep Ignore /etc/pacman.conf
#IgnorePkg =
#IgnorePkg =
#IgnoreGroup =
[steve@steve ~]$
As you said, theres nothing important there.
Please also check drop-ins with
grep Ignore /etc/pacman.conf.d/*
[steve@steve ~]$ grep Ignore /etc/pacman.conf.d/*
grep: /etc/pacman.conf.d/*: No such file or directory
That is actually a thing. It happened on my partners machine. The solution was to change to a different repository. In our case one in the US, because the Australian ones appeared not to be fully updated.
Mine is in Canada. I am not clear on how to change. Willing to try.
Then there shouldnt be any packages ignored by pacman.
Having just installed and tested ignoring a package with pamac - I am relatively confident it would have used the /etc/pacman.conf file for adding any ignored packages.
So the same should be true for pamac.
Is there a reason we are still looking? Do they act as if still ignored?
Or was this just to verify they are no longer ignored?
Not sure. Add/Remove Software advanced prefs say I have lots of ignored updates. So I thought that might help resolve the conflict when I try to update.
Message says
Preparingā¦
Synchronizing package databasesā¦
Refreshing extra.dbā¦
Checking windscribe-v2-bin dependenciesā¦
Checking v86d dependenciesā¦
Checking python-pyrsistent dependenciesā¦
Resolving dependenciesā¦
Checking inter-conflictsā¦
Error: unresolvable package conflicts detected
Failed to prepare transaction:
conflicting dependencies:
Transaction cancelled.
Now Iām confused again.
You have no packages set to ignored according to the conf files.
But pamac still lists packages as ignored?
EDIT.
That does not say anything about something being ignored.
Its simply saying you have conflicting dependencies. Though, at least in what is shared here, it does not say what.
OK, Iām going to cut through all the fat here.
Lets stop using pamac. and lets sort your mirrors.
This will reset the mirror pool:
sudo pacman-mirrors -c all
We can (optionally) try to use your region to narrow it down:
sudo pacman-mirrors --continent
Or we can just sort them all based on speed:
sudo pacman-mirrors -f
Once that is done lets move forward with a pacman sync**:
sudo pacman -Syu
I also noticed in your output the v86d package, which was a package erroneously included in manjaro. And a package that only exists in the third-party AUR (not in the repos). So unless you know you need it, it should be removed.
sudo pacman -Rns v86d
While we are in the business of removing things lets also banish packagekit
sudo pacman -Rns $(pacman -Qsq packagekit)
You may want to also check on foreign packages in general. This will print them:
pacman -Qmq
** - If you get any errors during the pamac sync+upgrade please share them here.
1 Like
Hamburger menu ā Preferences ā Enter Password when prompted ā In General: scroll down to Official Repositories ā select a new mirror from the drop down at use Mirrors from, then Refresh Mirrors
1 Like