pacdiff does not find
/etc/pulse/default.pa.pacnew
Its really old , so i don’t care. But is that an error of pacdiff ?
[john1@manjaro ~]$ sudo find /etc -name '*.pacnew'
[sudo] Passwort für john1:
/etc/pulse/default.pa.pacnew
[john1@manjaro ~]$ pacdiff -s
[john1@manjaro ~]$ ls -lha /etc/pulse/default.pa.pacnew
-rw-r--r-- 1 root root 4,9K 28. Jul 2021 /etc/pulse/default.pa.pacnew
I don’t know, but it’s interesting that you bring this up, as it failed to find the /etc/mkinitcpio.conf.pacnew on my system after the update. 
From the manpage, a script that looks for pacnew/pacsave files from backup entries in the pacman db… not in the filesystem.
Hmm, it did find mkinit pacnew by me.
What happens if you play with the options and choose another backend. Or run sudo updatedb. I think it uses locate in some cases.
Well, I don’t use pacdiff itself. Instead I use pacnew-chaser from the AUR. It’s a GUI front-end to pacdiff.
I installed pacnew-chaser on my system, reboot … it does also not find
/etc/pulse/default.pa.pacnew
/etc/pulse/default.pa.pacsave
In short: pacdiff , pacnew-chaser and manjaro-pacnew-checker fails
I don’t know how to solve this issue.
Interesting how these files are left from 2021… I can’t find them…
I’m not sure what the difference is between pacdiff, but I used pacnew-chaser for years now - manjaro-pacnew-checker is installed and my system is still working after 9 years… so I wouldn’t waste time fixing it; and just delete any leftover pacnew files that strangely slipped through the net.
Just try creating and finding it again… no idea how it got skipped… it’s instant for me; try it for yourself again…
Probably not, but best practice would be to compare /etc/pulse/default.pa.pacnew and /etc/pulse/default.pa
PulseAudio default.pa.pacnew files used to happen when the default configuration file was modified to disable an unwanted module
But modules can also be reconfigured by creating a custom configuration in home folder
~/.config/pulse/default.pa or by adding a file to /etc/pulse/default.pa.d
If the audio source is “suspended” then create the folowing .pa file:
/etc/pulse/default.pa.d/no-module-suspend-on-idle.paunload-module module-suspend-on-idle
Have a look at man pacdiff and use:
sudo updatedb && pacdiff -l -s
That will first update the FileName Database and then use this Database per parameter -l to find and handle *.pacnew and *.pacsave files.
That worked for me and i think i saw *.pacsave files for the first time ?!
Have to remember that for the future !
Remark:
Sound is working … so i will not change anything , bad experience !
From the man page, pacdiff has no less than three ways for scanning; the one which uses find looks like it has the least dependency on anything else being up-to-date:
Search Options
-f, --find
Scan using find.
-l, --locate
Scan using locate.
-p, --pacmandb
Scan active config files from pacman database. (default)
Yes, but you have to use
sudo pacdiff -s -f
Otherwise:
[john1@manjaro ~]$ pacdiff -s -f
find: ‘/etc/cups/ssl’: Keine Berechtigung
find: ‘/etc/credstore’: Keine Berechtigung
find: ‘/etc/sudoers.d’: Keine Berechtigung
find: ‘/etc/audit/plugins.d’: Keine Berechtigung
find: ‘/etc/lvm/cache’: Keine Berechtigung
find: ‘/etc/NetworkManager/system-connections’: Keine Berechtigung
find: ‘/etc/ssl/private’: Keine Berechtigung
find: ‘/etc/pacman.d/gnupg/openpgp-revocs.d’: Keine Berechtigung
find: ‘/etc/pacman.d/gnupg/crls.d’: Keine Berechtigung
find: ‘/etc/pacman.d/gnupg/private-keys-v1.d’: Keine Berechtigung
find: ‘/etc/credstore.encrypted’: Keine Berechtigung
find: ‘/etc/polkit-1/rules.d’: Keine Berechtigung
find: ‘/etc/cryptsetup-keys.d’: Keine Berechtigung
[john1@manjaro ~]$ sudo pacdiff -s -f
[sudo] Passwort für john1:
Have to learn what the simple
pacdiff -s
does when its doing its job correct as in the past ?!
Previous post from Oct 21 suggests there is probably no /etc/pulse/default.pa file
Changed sound server to pipewire but some pulseaudio component remain
Then this behavior may be by design. If the pacnew original config is gone because a package is uninstalled, it will no longer be in the pacman database. And this is the default scanning option.
I that case a pacnew is just junk so it is not wrong that it is being ignored.
That was also my idea tonight: *.pacnew is the result from an uninstalled package.
Fazit: all is fine with using pacdiff -s … i hope … we’ll see on next big update !
/etc/pulse/default.pa.pacnew was probably created after pulseaudio was updated
ArchWiki - pacman/Pacnew and Pacsave
A .pacnew file may be created during a package upgrade to avoid overwriting a file which already exists and was previously modified by the user.
A .pacsave file may be created during a package removal, or by a package upgrade (the package must be removed first).
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.