Because I don’t know which information from there is important. I have written here every information of which I think that it is helpful.
1 Like
Normally that would just be the grub package, and possibly os-prober, although the grub package should normally pull that in as a dependency. I would suggest rolling back os-prober first and grub afterwards, just to be sure.
output from
inxi -zv8
would be a good start. Then post that using the </> button.
2 Likes
Thank you!
The rollback helped; more or less. Grub seems to work. When I booted Manjaro the first time after the rollback I got a black screen just after the login and the monitor showed that there was no signal. After I rebooted the system I found out that the system wanted to start Kodi instead of the desktop. After I had chosen Wayland Linux started normal. To be safe I shall test the system the next days. Than I shall report, if the problem is solved.
1 Like
If the old grub works, the problem has to be the version discrepancy between the mbr part of grub and the root partition part. Which should have been fixed with reinstallation of the newer grub on the mbr from chroot, as per wiki, posted in the second post. But you said it had not worked so… 
I believe @Molski asked whether you simply replaced the content of mkinitcpio.conf with that of mkinitcpio.conf.pacnew, in an attempt to establish whether that might have been the cause of the subsequent boot failure.
Once the large update has been performed, use of the following ISO file might be prudent from that point on, or until the respective ISOs are made available from Manjaro Downloads.
Links to the Anh-Linh 25.1-pre1 (2025-12-08) ISO for your preferred Manjaro edition can be found in the Stable Update 2025-12-08 thread under the heading Additional Info.
1 Like
I believe @Molski asked whether you simply replaced the content of
mkinitcpio.confwith that ofmkinitcpio.conf.pacnew, in an attempt to establish whether that might have been the cause of the subsequent boot failure.
I did nothing but a normal update.
So the update 100% successfully completed, you rebooted, and nothing but a black screen. (Using the old mkinitcpio configuration, as you do not do know how to deal with pacnew files.)
You can’t run Manjaro for long until you learn how to handle configuration changes via pacnew files. It will most likely break, it will just take a matter of time.
Almost all booting problems with this update, are related to this one certain change. I know other systems boot fine not using the new format, but not much beyond that. But you didn’t even implement it, so I think it should still boot just fine.
In the other thread, we disabled os-prober, and got the menu hard coded booting MBR via UUID. So it should be solid there, with nothing tampering with grub. And I don’t know what would make it not boot off hand. There is not much to go off of to be honest.
Umbra_noctis provide everyone this information, and copy and paste the output. It is hard for anyone to help with no information. (You can’t just say, “Just go look at the 100+ messages over there.”)
Last thing I knew, was helping you get manjaro-chroot working. Did that work? I’m lost.
1 Like
I have been using manjaro since 2017. It has been working on 4 Computers and I hardly ever had a problem. To be honest the only major problem was an update in Decembre 2018.
I have never heard about pacnew-files until you mentioned them.
Umbra_noctis provide everyone this information, and copy and paste the output. It is hard for anyone to help with no information. (You can’t just say, “Just go look at the 100+ messages over there.”)
I was so happy about the working Grub that I have forgotten this:
System:
Kernel: 6.12.61-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/boot/vmlinuz-6.12-x86_64
root=UUID=7577eecb-23f7-4a07-8eac-a01a3d8d9240 rw quiet splash
resume=UUID=8708d9e9-4e5b-490b-b93e-465abbd4a30a udev.log_priority=3
Desktop: KDE Plasma v: 6.5.3 tk: Qt v: N/A info: frameworks v: 6.20.0
wm: kwin_wayland vt: 1 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
Type: Desktop Mobo: Micro-Star model: X399 SLI PLUS (MS-7B09) v: 2.0
serial: <superuser required> uuid: <superuser required>
Firmware: UEFI-[Legacy] vendor: American Megatrends v: A.00
date: 09/21/2017
Battery:
Message: No system battery data found. Is one present?
Memory:
System RAM: total: 128 GiB available: 125.69 GiB used: 3.05 GiB (2.4%)
Message: For most reliable report, use superuser + dmidecode.
Array-1: capacity: 512 GiB slots: 8 modules: 4 EC: None
max-module-size: 64 GiB note: est.
Device-1: Channel-A DIMM 0 type: no module installed
Device-2: Channel-A DIMM 1 type: DDR4 detail: synchronous unbuffered
(unregistered) size: 32 GiB speed: spec: 2133 MT/s actual: 1067 MT/s
volts: note: check curr: 1 min: 1 max: 1 width (bits): data: 64 total: 64
manufacturer: Corsair part-no: CMK128GX4M4A2666C16 serial: N/A
Device-3: Channel-B DIMM 0 type: no module installed
Device-4: Channel-B DIMM 1 type: DDR4 detail: synchronous unbuffered
(unregistered) size: 32 GiB speed: spec: 2133 MT/s actual: 1067 MT/s
volts: note: check curr: 1 min: 1 max: 1 width (bits): data: 64 total: 64
manufacturer: Corsair part-no: CMK128GX4M4A2666C16 serial: N/A
Device-5: Channel-C DIMM 0 type: no module installed
Device-6: Channel-C DIMM 1 type: DDR4 detail: synchronous unbuffered
(unregistered) size: 32 GiB speed: spec: 2133 MT/s actual: 1067 MT/s
volts: note: check curr: 1 min: 1 max: 1 width (bits): data: 64 total: 64
manufacturer: Corsair part-no: CMK128GX4M4A2666C16 serial: N/A
Device-7: Channel-D DIMM 0 type: no module installed
Device-8: Channel-D DIMM 1 type: DDR4 detail: synchronous unbuffered
(unregistered) size: 32 GiB speed: spec: 2133 MT/s actual: 1067 MT/s
volts: note: check curr: 1 min: 1 max: 1 width (bits): data: 64 total: 64
manufacturer: Corsair part-no: CMK128GX4M4A2666C16 serial: N/A
PCI Slots:
Permissions: Unable to run dmidecode. Root privileges required.
CPU:
Info: model: AMD Ryzen Threadripper 1920X bits: 64 type: MT MCP arch: Zen
level: v3 note: check built: 2017-19 process: GF 14nm family: 0x17 (23)
model-id: 1 stepping: 1 microcode: 0x8001129
Topology: cpus: 1x dies: 1 clusters: 1 cores: 12 threads: 24 tpc: 2
smt: enabled cache: L1: 1.1 MiB desc: d-12x32 KiB; i-12x64 KiB L2: 6 MiB
desc: 12x512 KiB L3: 32 MiB desc: 4x8 MiB
Speed (MHz): avg: 2200 min/max: 2200/3500 boost: disabled scaling:
driver: acpi-cpufreq governor: schedutil cores: 1: 2200 2: 2200 3: 2200
4: 2200 5: 2200 6: 2200 7: 2200 8: 2200 9: 2200 10: 2200 11: 2200 12: 2200
13: 2200 14: 2200 15: 2200 16: 2200 17: 2200 18: 2200 19: 2200 20: 2200
21: 2200 22: 2200 23: 2200 24: 2200 bogomips: 168036
Flags: 3dnowprefetch abm adx aes amd_dcm aperfmperf apic arat avic avx
avx2 bmi1 bmi2 bpext clflush clflushopt clzero cmov cmp_legacy
constant_tsc cpb cpuid cr8_legacy cx16 cx8 de decodeassists extapic
extd_apicid f16c flushbyasid fma fpu fsgsbase fxsr fxsr_opt ht hw_pstate
lahf_lm lbrv lm mca mce misalignsse mmx mmxext monitor movbe msr mtrr
mwaitx nonstop_tsc nopl npt nrip_save nx osvw overflow_recov pae pat
pausefilter pclmulqdq pdpe1gb perfctr_core perfctr_llc perfctr_nb
pfthreshold pge pni popcnt pse pse36 rapl rdrand rdseed rdtscp rep_good
sep sev sha_ni skinit smap smca smep ssbd sse sse2 sse4_1 sse4_2 sse4a
ssse3 succor svm svm_lock syscall tce topoext tsc tsc_scale
v_vmsave_vmload vgif vmcb_clean vme vmmcall wdt xgetbv1 xsave xsavec
xsaveerptr xsaveopt
Vulnerabilities:
Type: gather_data_sampling status: Not affected
Type: indirect_target_selection status: Not affected
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data status: Not affected
Type: reg_file_data_sampling status: Not affected
Type: retbleed mitigation: untrained return thunk; SMT vulnerable
Type: spec_rstack_overflow status: Vulnerable: Safe RET, no microcode
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
sanitization
Type: spectre_v2 mitigation: Retpolines; STIBP: disabled; RSB filling;
PBRSB-eIBRS: Not affected; BHI: Not affected
Type: srbds status: Not affected
Type: tsa status: Not affected
Type: tsx_async_abort status: Not affected
Type: vmscape status: Vulnerable
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Navi 48 [Radeon RX 9070/9070
XT/9070 GRE] vendor: Sapphire driver: amdgpu v: kernel arch: RDNA-4
code: Navi-4x process: TSMC n4 (4nm) built: 2025+ pcie: gen: 5
speed: 32 GT/s lanes: 16 ports: active: DP-1 empty: DP-2, HDMI-A-1,
HDMI-A-2, Writeback-1 bus-ID: 0c:00.0 chip-ID: 1002:7550 class-ID: 0300
Display: wayland server: X.org v: 1.21.1.21 with: Xwayland v: 24.1.9
compositor: kwin_wayland driver: X: loaded: amdgpu
unloaded: modesetting,radeon alternate: fbdev,vesa dri: radeonsi
gpu: amdgpu display-ID: 0
Monitor-1: DP-1 model: EIZO NANAO S2233W serial: <filter> built: 2009 res:
mode: 1680x1050 hz: 60 scale: 100% (1) dpi: 89 gamma: 1.2 chroma: red:
x: 0.659 y: 0.325 green: x: 0.216 y: 0.682 blue: x: 0.145 y: 0.071 white:
x: 0.314 y: 0.329 size: 474x297mm (18.66x11.69") diag: 566mm (22.3")
ratio: 16:10 modes: 1680x1050, 1280x1024, 1440x900, 1280x960, 1280x800,
1152x864, 1280x720, 1024x768, 800x600, 640x480, 720x400
API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
device: 1 drv: swrast gbm: drv: kms_swrast surfaceless: drv: radeonsi
wayland: drv: radeonsi x11: drv: radeonsi
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 25.3.1-arch1.2
glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 9070 (radeonsi
gfx1201 LLVM 21.1.6 DRM 3.61 6.12.61-1-MANJARO) device-ID: 1002:7550
memory: 15.62 GiB unified: no display-ID: :1.0
API: Vulkan v: 1.4.328 layers: 9 device: 0 type: discrete-gpu name: AMD
Radeon RX 9070 (RADV GFX1201) driver: mesa radv v: 25.3.1-arch1.2
device-ID: 1002:7550 surfaces: N/A
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: lact,radeontop wl: wayland-info
x11: xdpyinfo, xprop, xrandr
Audio:
Device-1: Creative Labs CA0132 Sound Core3D [Sound Blaster Recon3D /
Z-Series BlasterX AE-5 Plus] driver: snd_hda_intel v: kernel pcie: gen: 1
speed: 2.5 GT/s lanes: 1 bus-ID: 04:00.0 chip-ID: 1102:0012 class-ID: 0403
Device-2: Advanced Micro Devices [AMD/ATI] Navi 48 HDMI/DP Audio
driver: snd_hda_intel v: kernel pcie: gen: 5 speed: 32 GT/s lanes: 16
bus-ID: 0c:00.1 chip-ID: 1002:ab40 class-ID: 0403
API: ALSA v: k6.12.61-1-MANJARO status: kernel-api with: aoss
type: oss-emulator tools: alsactl,alsamixer,amixer
Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
Server-2: JACK v: 1.9.22 status: off tools: N/A
Server-3: PipeWire v: 1.4.9 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel I211 Gigabit Network vendor: Micro-Star MSI driver: igb
v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: 7000 bus-ID: 08:00.0
chip-ID: 8086:1539 class-ID: 0200
IF: enp8s0 state: down mac: <filter>
Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
vendor: TP-LINK TG-3468 driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 port: f000 bus-ID: 43:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp67s0 state: down mac: <filter>
Info: services: NetworkManager
WAN IP: No WAN IP found. Connected to web? SSL issues? Try enabling dig
Bluetooth:
Message: No bluetooth data found.
Logical:
Message: No logical block device data found.
RAID:
Message: No RAID data found.
Drives:
Local Storage: total: 10.92 TiB used: 385.88 GiB (3.5%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:4 vendor: Western Digital
model: WD BLACK SN770 2TB size: 1.82 TiB block-size: physical: 512 B
logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: 731130WD temp: 32.9 C scheme: MBR
ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Samsung model: SSD 980 PRO 1TB
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: 5B2QGXA7 temp: 24.9 C
scheme: MBR
ID-3: /dev/sda maj-min: 8:0 vendor: Seagate model: ST8000NM000A-2KE101
size: 7.28 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 7200 serial: <filter> fw-rev: SC03 scheme: GPT
ID-4: /dev/sdb maj-min: 8:16 vendor: Western Digital
model: WD1003FZEX-00MK2A0 size: 931.51 GiB block-size: physical: 4096 B
logical: 512 B speed: 6.0 Gb/s tech: HDD rpm: 7200 serial: <filter>
fw-rev: 1A01 scheme: MBR
Optical-1: /dev/sr0 vendor: HL-DT-ST model: DVDRAM GH24NSD1 rev: LG00
dev-links: cdrom
Features: speed: 12 multisession: yes audio: yes dvd: yes
rw: cd-r,cd-rw,dvd-r,dvd-ram state: running
Partition:
ID-1: / raw-size: 1.81 TiB size: 1.78 TiB (98.37%) used: 385.88 GiB (21.2%)
fs: ext4 dev: /dev/nvme0n1p1 maj-min: 259:5 label: N/A
uuid: 7577eecb-23f7-4a07-8eac-a01a3d8d9240
Swap:
Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: partition size: 8.8 GiB used: 0 KiB (0.0%) priority: -2
dev: /dev/nvme0n1p2 maj-min: 259:6 label: swap
uuid: 8708d9e9-4e5b-490b-b93e-465abbd4a30a
Unmounted:
ID-1: /dev/nvme1n1p1 maj-min: 259:1 size: 549 MiB fs: ntfs
label: System-reserviert uuid: 707C2F317C2EF190
ID-2: /dev/nvme1n1p2 maj-min: 259:2 size: 930.46 GiB fs: ntfs label: N/A
uuid: 886E30756E305E5E
ID-3: /dev/nvme1n1p3 maj-min: 259:3 size: 530 MiB fs: ntfs label: N/A
uuid: 1CB842C1B84298E2
ID-4: /dev/sda1 maj-min: 8:1 size: 128 MiB fs: <superuser required>
label: N/A uuid: N/A
ID-5: /dev/sda2 maj-min: 8:2 size: 7.28 TiB fs: ntfs label: Volume
uuid: C8465A87465A7662
ID-6: /dev/sdb1 maj-min: 8:17 size: 931.51 GiB fs: ntfs label: Volume
uuid: 3AFD0023FCFFD6DB
USB:
Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 14 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
class-ID: 0900
Device-1: 1-12:2 info: [Maxxter] USB GAMING MOUSE type: mouse,keyboard
driver: hid-generic,usbhid interfaces: 2 rev: 1.1
speed: 1.5 Mb/s (183 KiB/s) lanes: 1 mode: 1.0 power: 100mA
chip-ID: 18f8:1286 class-ID: 0300
Hub-2: 2-0:1 info: super-speed hub ports: 8 rev: 3.1
speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
class-ID: 0900
Hub-3: 3-0:1 info: hi-speed hub with single TT ports: 2 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
class-ID: 0900
Hub-4: 4-0:1 info: super-speed hub ports: 2 rev: 3.1
speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
class-ID: 0900
Hub-5: 5-0:1 info: hi-speed hub with single TT ports: 4 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
class-ID: 0900
Hub-6: 6-0:1 info: super-speed hub ports: 4 rev: 3.0
speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 1d6b:0003
class-ID: 0900
Hub-7: 7-0:1 info: hi-speed hub with single TT ports: 4 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
class-ID: 0900
Hub-8: 8-0:1 info: super-speed hub ports: 4 rev: 3.0
speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 1d6b:0003
class-ID: 0900
Sensors:
System Temperatures: cpu: 25.4 C mobo: N/A gpu: amdgpu temp: 27.0 C
mem: 26.0 C
Fan Speeds (rpm): N/A gpu: amdgpu fan: 0
Repos:
Packages: pm: pacman pkgs: 1888 libs: 453 tools: octopi,pamac,yay
pm: flatpak pkgs: 0
Active pacman repo servers in: /etc/pacman.d/mirrorlist
1: https://mirror.easyname.at/manjaro/stable/$repo/$arch
2: https://mirror.init7.net/manjaro/stable/$repo/$arch
3: https://mirror1.sox.rs/manjaro/stable/$repo/$arch
4: https://mirror.math.princeton.edu/pub/manjaro/stable/$repo/$arch
5: https://volico.mm.fcix.net/manjaro/stable/$repo/$arch
6: https://mirrors.sonic.net/manjaro/stable/$repo/$arch
7: https://mirror.2degrees.nz/manjaro/stable/$repo/$arch
8: https://mirrors.sjtug.sjtu.edu.cn/manjaro/stable/$repo/$arch
Processes:
CPU top: 5 of 492
1: cpu: 13.1% command: plasmashell pid: 1401 mem: 387.7 MiB (0.3%)
2: cpu: 3.6% command: kwin_wayland pid: 1160 mem: 229.7 MiB (0.1%)
3: cpu: 1.9% command: init pid: 1 mem: 13.4 MiB (0.0%)
4: cpu: 1.6% command: konsole pid: 2308 mem: 137.4 MiB (0.1%)
5: cpu: 1.6% command: zsh pid: 2334 mem: 10.2 MiB (0.0%)
Memory top: 5 of 492
1: mem: 387.7 MiB (0.3%) command: plasmashell pid: 1401 cpu: 13.1%
2: mem: 229.7 MiB (0.1%) command: kwin_wayland pid: 1160 cpu: 3.6%
3: mem: 146.8 MiB (0.1%) command: akonadi_mailfilter_agent pid: 2009
cpu: 1.0%
4: mem: 146.1 MiB (0.1%) command: akonadi_archivemail_agent pid: 2001
cpu: 1.0%
5: mem: 146.0 MiB (0.1%) command: kalendarac pid: 1654 cpu: 1.1%
Info:
Processes: 492 Power: uptime: 1m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 50.25 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 258 default: graphical
tool: systemctl
Compilers: clang: 21.1.6 gcc: 15.2.1 Shell: Zsh v: 5.9 default: Bash
v: 5.3.8 running-in: konsole inxi: 3.3.40
Last thing I knew, was helping you get
manjaro-chrootworking. Did that work? I’m lost.
manjaro-chroot worked. I have used it to use pacman -U to undo the grub-update.
Then you never paid any attention to the messages pertaining to them that surely where many over the course of all those years.
granted:
the pamac-GUI does nothing to alert you to these - as far as I kow
unless you watch the terminal output of the update process
one more reason to not like it - why I don’t use it …
The version I have used is still provided by the official Manjaro-homepage. I thought this is the only place to find the official mirrors.
But the main problem: The computer that I wasn’t able to boot is the only one, that can create a bootable USB-Stick. And the ISO-file is too big for a DVD.
pamac-GUI
What is this? I am using Octopi or for a simple update just pacman -Syu.
1 Like
the arguably best way would be to use Ventoy
- install it (not even really needed - just download, unpack and run from there …)
- use it to prepare your USB stick
- copy the ISO to it
The very easy way is:
sudo cp Manjaro.iso /dev/sdy
where you need to adapt the PATH to your Manjaro ISO as well as the device name of your USB stick
(/dev/sdy is just an example here)
pamac-manager is what I mean by pamac GUI
It’s the Manjaro default package manager - Octopi does the same.
And better, as some would argue.
If you often or always used
pacman -Syu
you’d have seen the messages about .pacnew files for sure
The strange program with the green arrow that never works as it should?
1 Like
that is probably right 
supposed to be a distinct good feature of Manjaro
but it failed me too many times and I now don’t even bother to even think of using it
… I came from ARCH
pacman always worked and I’m used to it as well
so: I use it …
1 Like
If you don’t know what is important and what is not you will most likely not recognise it as long as everything works fine.
That may be true -
and it will indeed keep working for some time, most of the time
but eventually it will break … assume that to be sooner rather than later
I, myself, would have been curious about messages along the lines:
… has been installed as … .pacnew
I guess these where prepended by “Warning” … - not sure now from memory
they where definitely there
and for quite some time a year or two ago you would also have seen messages that the community repo was invalid
even errors because of it
That should have ticked you off - but you may have missed that when not updating during that time.
just tend to them now … better late than never
1 Like
but eventually it will break … assume that to be sooner rather than later
Well, 6 years… I haven’t expect a problem after using the updates so long this way.
BTW: What shall I do with a pacnew file?
1 Like
When a new configuration file gets installed, it won’t overwrite yours. It installs it beside it as filename.pacnew. You have to manually bring over the changes, making sure they don’t conflict with your own.
The good news is, this can be very easy to do with tools out there meant for this.
This is the quick run down of what most people just need to know:
Meld is a program just to compare two files.
(I’ve always just used
vim -d/vimdiff, which is the Arch default. But I would not recommend this!) So many people use the GUI program:meld.
As this is new for you, just install meld: sudo -S meld. Try it out. Don’t even use sudo pacdiff until you understand exactly what meld is and does.
Except you can run:
pacdiff -o
pacdiff --output
This shows you what pacnew files you need to deal with.
No sudo needed, this will list all the pacnew files you need to deal with, you will have a lot.
But you could copy one of the files from above, say:
/etc/default/grub.pacnew
Your actual config is without the .pacnew at the end:
/etc/default/grub
If you copied these two files to your Documents, you could load them both in Meld to see how it works.
After dealing with the changes, copying that file back to /etc/default, and deleting the original pacnew file is one manual way to deal with that particular pacnew.
Once you are comfortable there, pacdiff has ways to make this quicker.
3 Likes