Since May I can not Play any type of Game with Steam on Manjaro Linux

Kurogane1412 · 6 September 2024 09:32

Hi Dear Manjaro Community ,

I am not new to Manjaro Linux using it already for 8 years and since 2019 on my Gaming PC and since a May Update I think it was at that when I could play last time without problems.

Here is the Console output of Steam when I tried to run : Cyberpunk 2077 ,Half Life 2 , Metro 2033 Redux and I downgraded Steam from Beat to non Beta and tried steam --reset non helped

But the Flatpack version of Steam seems to work Normal tried with Hald Life 2 and DmC Devil may cry for testing both worked without problems

(base) [dean@MeshifyC-Manjaro ~]$ steam
steam.sh[21705]: Running Steam on manjarolinux 24.0.8 64-bit
steam.sh[21705]: STEAM_RUNTIME is enabled automatically
setup.sh[21780]: Steam runtime environment up-to-date!
steam.sh[21705]: Steam client's requirements are satisfied
[2024-09-06 11:11:23] Startup - updater built Jul 16 2024 23:21:18
[2024-09-06 11:11:23] Startup - Steam Client launched with: '/home/dean/.local/share/Steam/ubuntu12_32/steam' '-srt-logger-opened'
09/06 11:11:23 minidumps folder is set to /tmp/dumps
09/06 11:11:23 Init: Installing breakpad exception handler for appid(steam)/version(1721173382)/tid(21841)
[2024-09-06 11:11:23] Loading cached metrics from disk (/home/dean/.local/share/Steam/package/steam_client_metrics.bin)
[2024-09-06 11:11:23] Using the following download hosts for Public, Realm steamglobal
[2024-09-06 11:11:23] 1. https://client-update.akamai.steamstatic.com, /, Realm 'steamglobal', weight was 1000, source = 'update_hosts_cached.vdf'
[2024-09-06 11:11:23] 2. https://cdn.cloudflare.steamstatic.com, /client/, Realm 'steamglobal', weight was 1, source = 'update_hosts_cached.vdf'
[2024-09-06 11:11:23] 3. https://cdn.steamstatic.com, /client/, Realm 'steamglobal', weight was 1, source = 'baked in'
[2024-09-06 11:11:23] Verifying installation...
[2024-09-06 11:11:23] Verification complete
UpdateUI: skip show logo
Steam logging initialized: directory: /home/dean/.local/share/Steam/logs

/usr/share/themes/Breath/gtk-2.0/widgets/entry:70: error: unexpected identifier 'direction', expected character '}'
/usr/share/themes/Breath/gtk-2.0/widgets/styles:36: error: invalid string constant "combobox_entry", expected valid string constant
XRRGetOutputInfo Workaround: initialized with override: 0 real: 0xe841adc0
XRRGetCrtcInfo Workaround: initialized with override: 0 real: 0xe8419500
CAppInfoCacheReadFromDiskThread took 28 milliseconds to initialize
Steam Runtime Launch Service: starting steam-runtime-launcher-service
Steam Runtime Launch Service: steam-runtime-launcher-service is running pid 21969
bus_name=com.steampowered.PressureVessel.LaunchAlongsideSteam
BRefreshApplicationsInLibrary 1: 1ms
BuildCompleteAppOverviewChange: 216 apps
RegisterForAppOverview 1: 9ms
RegisterForAppOverview 2: 9ms
chdir "/run/media/dean/Data/Dean/steamapps/common/Half-Life 2"
ERROR: ld.so: object '/home/dean/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/dean/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
ERROR: ld.so: object '/home/dean/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
Adding process 22533 for gameID 220
Adding process 22534 for gameID 220
Uploaded AppInterfaceStats to Steam
Removing process 22534 for gameID 220
Removing process 22533 for gameID 220
Fossilize INFO: Setting autogroup scheduling.
chdir "/run/media/dean/Data/Dean/steamapps/common/Cyberpunk 2077"
ERROR: ld.so: object '/home/dean/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/dean/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
ERROR: ld.so: object '/home/dean/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
Adding process 22663 for gameID 1091500
Adding process 22664 for gameID 1091500
Uploaded AppInterfaceStats to Steam
Removing process 22664 for gameID 1091500
Removing process 22663 for gameID 1091500
Fossilize INFO: Setting autogroup scheduling.
chdir "/run/media/dean/Data/Dean/steamapps/common/Metro 2033 Redux"
ERROR: ld.so: object '/home/dean/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/dean/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
pid 22897 != 22896, skipping destruction (fork without exec?)
ERROR: ld.so: object '/home/dean/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/dean/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/dean/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
ERROR: ld.so: object '/usr/$LIB/mangohud/libMangoHud_opengl.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/home/dean/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
Adding process 22896 for gameID 286690
Adding process 22898 for gameID 286690
Adding process 22899 for gameID 286690
Uploaded AppInterfaceStats to Steam
Removing process 22899 for gameID 286690
Removing process 22898 for gameID 286690
Removing process 22896 for gameID 286690
[2024-09-06 11:13:24] Background update loop checking for update. . .
[2024-09-06 11:13:24] Checking for available updates...
[2024-09-06 11:13:24] Downloading manifest: https://client-update.akamai.steamstatic.com/steam_client_ubuntu12?t=3318101149
[2024-09-06 11:13:24] Manifest download: send request
[2024-09-06 11:13:25] Manifest download: waiting for download to finish
[2024-09-06 11:13:25] Manifest download: finished
[2024-09-06 11:13:25] Download skipped: /steam_client_ubuntu12?t=3318101149 version 1721173382, installed version 1721173382, existing pending version 0
[2024-09-06 11:13:25] Nothing to do

So at the beginning thought that it was a Proton Problem but with Half Life 2 not Starting at all does not seam like that.

and here maybe also some useful output :

(base) [dean@MeshifyC-Manjaro ~]$ sudo ldconfig -v | grep ':'
[sudo] password for dean: 
ldconfig: Path `/usr/lib64' given more than once
(from <builtin>:0 and <builtin>:0)
ldconfig: Can't stat /usr/libx32: No such file or directory
/usr/lib32: (from /etc/ld.so.conf.d/lib32-glibc.conf:1)
/opt/rocm-5.1.1/opencl/lib: (from /etc/ld.so.conf.d/opencl-amd.conf:1)
/opt/rocm-5.1.1/lib: (from /etc/ld.so.conf.d/opencl-amd.conf:2)
/opt/rocm-5.1.1/hip/lib: (from /etc/ld.so.conf.d/opencl-amd.conf:3)
/usr/lib: (from <builtin>:0)
(base) [dean@MeshifyC-Manjaro ~]$ ls -al /usr/lib32 | grep libc.so 
-rw-r--r--  1 root root       252  5. Aug 22:00 libc.so
-rwxr-xr-x  1 root root   2300680  5. Aug 22:00 libc.so.6
(base) [dean@MeshifyC-Manjaro ~]$ ls -al /usr/lib | grep libc.so
-rw-r--r--   1 root root       255  5. Aug 22:00 libc.so
-rwxr-xr-x   1 root root   2014520  5. Aug 22:00 libc.so.6

and a screenfetch

(base) [dean@MeshifyC-Manjaro ~]$ screenfetch

 ██████████████████  ████████     dean@MeshifyC-Manjaro
 ██████████████████  ████████     OS: Manjaro 24.0.8 Wynsdey
 ██████████████████  ████████     Kernel: x86_64 Linux 6.6.47-1-MANJARO
 ██████████████████  ████████     Uptime: 1h 42m
 ████████            ████████     Packages: 2240
 ████████  ████████  ████████     Shell: bash 5.2.32
 ████████  ████████  ████████     Resolution: 6400x2160
 ████████  ████████  ████████     DE: KDE
 ████████  ████████  ████████     WM: KWin
 ████████  ████████  ████████     GTK Theme: Breath [GTK2/3]
 ████████  ████████  ████████     Icon Theme: breeze
 ████████  ████████  ████████     Disk: 5,6T / 9,9T (60%)
 ████████  ████████  ████████     CPU: AMD Ryzen 9 5900X 12-Core @ 24x 3.7GHz
 ████████  ████████  ████████     GPU: AMD Radeon RX 6800 (radeonsi, navi21, LLVM 18.1.8, DRM 3.54, 6.6.47-1-MANJARO)
                                  RAM: 6964MiB / 32003MiB

I have seen similar problems but no solution I hope someone can help.

Kind regards Dean

soundofthunder · 6 September 2024 09:49

Hi @Kurogane1412 and welcome to the Manjaro community.

You might find fastfetch an nice replacement for screenfetch.

However, output from the following command will generally provide more useful information for those wishing to help:

inxi --admin --verbosity=8 --filter --no-host --width

Now, we return you to our regular programming…

Cheers.

Kurogane1412 · 6 September 2024 11:53

thank you for the tip

and here the output

(base) [dean@MeshifyC-Manjaro ~]$ inxi --admin --verbosity=8 --filter --no-host --width
System:
  Kernel: 6.6.47-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.6-x86_64
    root=UUID=c13a924e-f23f-443d-93b3-0384a2541f36 rw quiet amdgpu.dpm=1
    amdgpu.ppfeaturemask=0xffffffff
  Desktop: KDE Plasma v: 6.0.5 tk: Qt v: N/A info: frameworks v: 6.5.0
    wm: kwin_x11 with: krunner vt: 2 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
  Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
  Mobo: ASUSTeK model: TUF GAMING X570-PRO (WI-FI) v: Rev X.0x
    serial: <superuser required> part-nu: SKU uuid: <superuser required>
    UEFI: American Megatrends v: 4408 date: 10/28/2022
Battery:
  Message: No system battery data found. Is one present?
Memory:
  System RAM: total: 32 GiB available: 31.25 GiB used: 8.72 GiB (27.9%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 128 GiB slots: 4 modules: 2 EC: None
    max-module-size: 32 GiB note: est.
  Device-1: DIMM_A1 type: DDR4 detail: synchronous unbuffered (unregistered)
    size: 16 GiB speed: 3200 MT/s volts: note: check curr: 1 min: 1 max: 1
    width (bits): data: 64 total: 64 manufacturer: G-Skill
    part-no: F4-4000C18-16GVK serial: N/A
  Device-2: DIMM_A2 type: no module installed
  Device-3: DIMM_B1 type: DDR4 detail: synchronous unbuffered (unregistered)
    size: 16 GiB speed: 3200 MT/s volts: note: check curr: 1 min: 1 max: 1
    width (bits): data: 64 total: 64 manufacturer: G-Skill
    part-no: F4-4000C18-16GVK serial: N/A
  Device-4: DIMM_B2 type: no module installed
PCI Slots:
  Permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: AMD Ryzen 9 5900X bits: 64 type: MT MCP arch: Zen 3+ gen: 3
    level: v3 note: check built: 2022 process: TSMC n6 (7nm) family: 0x19 (25)
    model-id: 0x21 (33) stepping: 0 microcode: 0xA201016
  Topology: cpus: 1x dies: 1 clusters: 1 cores: 12 threads: 24 tpc: 2
    smt: enabled cache: L1: 768 KiB desc: d-12x32 KiB; i-12x32 KiB L2: 6 MiB
    desc: 12x512 KiB L3: 64 MiB desc: 2x32 MiB
  Speed (MHz): avg: 2200 min/max: 2200/4950 boost: enabled 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: 177653
  Flags: 3dnowprefetch abm adx aes aperfmperf apic arat avic avx avx2 bmi1
    bmi2 bpext cat_l3 cdp_l3 clflush clflushopt clwb clzero cmov cmp_legacy
    constant_tsc cpb cpuid cqm cqm_llc cqm_mbm_local cqm_mbm_total
    cqm_occup_llc cr8_legacy cx16 cx8 de debug_swap decodeassists erms extapic
    extd_apicid f16c flushbyasid fma fpu fsgsbase fsrm fxsr fxsr_opt ht
    hw_pstate ibpb ibrs ibs invpcid irperf lahf_lm lbrv lm mba mca mce
    misalignsse mmx mmxext monitor movbe msr mtrr mwaitx nonstop_tsc nopl npt
    nrip_save nx ospke osvw overflow_recov pae pat pausefilter pclmulqdq
    pdpe1gb perfctr_core perfctr_llc perfctr_nb pfthreshold pge pku pni popcnt
    pse pse36 rapl rdpid rdpru rdrand rdseed rdt_a rdtscp rep_good sep sha_ni
    skinit smap smca smep ssbd sse sse2 sse4_1 sse4_2 sse4a ssse3 stibp succor
    svm svm_lock syscall tce topoext tsc tsc_scale umip user_shstk v_spec_ctrl
    v_vmsave_vmload vaes vgif vmcb_clean vme vmmcall vpclmulqdq wbnoinvd wdt
    x2apic xgetbv1 xsave xsavec xsaveerptr xsaveopt xsaves
  Vulnerabilities:
  Type: gather_data_sampling 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 status: Not affected
  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; IBPB: conditional; IBRS_FW;
    STIBP: always-on; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not
    affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Navi 21 [Radeon RX 6800/6800 XT /
    6900 XT] vendor: Sapphire driver: amdgpu v: kernel arch: RDNA-2
    code: Navi-2x process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4
    speed: 16 GT/s lanes: 16 ports: active: DP-1,HDMI-A-1 empty: DP-2,DP-3
    bus-ID: 0c:00.0 chip-ID: 1002:73bf class-ID: 0300
  Display: x11 server: X.Org v: 21.1.13 with: Xwayland v: 24.1.2
    compositor: kwin_x11 driver: X: loaded: modesetting unloaded: radeon
    alternate: fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
  Screen-1: 0 s-res: 6400x2160 s-dpi: 96 s-size: 1693x571mm (66.65x22.48")
    s-diag: 1787mm (70.34")
  Monitor-1: DP-1 pos: primary,right model: LG (GoldStar) ULTRAGEAR
    serial: <filter> built: 2023 res: 2560x1440 dpi: 93 gamma: 1.2 chroma: red:
    x: 0.647 y: 0.337 green: x: 0.314 y: 0.631 blue: x: 0.153 y: 0.075 white:
    x: 0.314 y: 0.329 size: 697x392mm (27.44x15.43") diag: 800mm (31.5")
    ratio: 16:9 modes: 2560x1440, 1920x1200, 1920x1080, 1600x1200, 1680x1050,
    1280x1024, 1440x900, 1280x800, 1280x720, 1024x768, 800x600, 720x576,
    720x480, 640x480
  EDID-Warnings: 1: parse_edid: unknown tag 112
  Monitor-2: HDMI-A-1 mapped: HDMI-1 pos: left model: Samsung U28E590
    serial: <filter> built: 2019 res: 3840x2160 hz: 30 dpi: 160 gamma: 1.2
    chroma: red: x: 0.635 y: 0.341 green: x: 0.310 y: 0.635 blue: x: 0.157
    y: 0.059 white: x: 0.314 y: 0.329 size: 608x345mm (23.94x13.58")
    diag: 699mm (27.5") ratio: 16:9 modes: 3840x2160, 2560x1440, 1920x1200,
    1920x1080, 1600x1200, 1680x1050, 1600x900, 1280x1024, 1440x900, 1280x800,
    1152x864, 1280x720, 1024x768, 832x624, 800x600, 720x576, 720x480, 640x480,
    720x400
  EDID-Warnings: 1: parse_edid: unhandled CEA mode 95
  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 x11:
    drv: radeonsi inactive: wayland
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.1.6-arch1.1
    glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 6800 (radeonsi navi21
    LLVM 18.1.8 DRM 3.54 6.6.47-1-MANJARO) device-ID: 1002:73bf
    memory: 15.62 GiB unified: no
  API: Vulkan v: 1.3.279 layers: 7 device: 0 type: discrete-gpu
    name: AMD Radeon RX 6800 driver: amd device-ID: 1002:73bf surfaces: xcb,xlib
    device: 1 type: discrete-gpu name: AMD Radeon RX 6800 driver: amd
    v: 2024.Q3.1 (LLPC) device-ID: 1002:73bf surfaces: xcb,xlib
Audio:
  Device-1: Advanced Micro Devices [AMD/ATI] Navi 21/23 HDMI/DP Audio
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
    bus-ID: 0c:00.1 chip-ID: 1002:ab28 class-ID: 0403
  Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio
    vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s
    lanes: 16 bus-ID: 0e:00.4 chip-ID: 1022:1487 class-ID: 0403
  API: ALSA v: k6.6.47-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.2.3 status: off with: pipewire-media-session
    status: active tools: pw-cli
  Server-4: PulseAudio v: 17.0 status: active with: 1: pulseaudio-alsa
    type: plugin 2: pulseaudio-jack type: module tools: pacat,pactl
Network:
  Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: gen: 2
    speed: 5 GT/s lanes: 1 bus-ID: 05:00.0 chip-ID: 8086:2723 class-ID: 0280
  IF: wlp5s0 state: up mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: dynamic noprefixroute scope: global
  IP v6: <filter> type: noprefixroute scope: link
  Device-2: Intel Ethernet I225-V vendor: ASUSTeK driver: igc v: kernel pcie:
    gen: 2 speed: 5 GT/s lanes: 1 port: N/A bus-ID: 06:00.0 chip-ID: 8086:15f3
    class-ID: 0200
  IF: enp6s0 state: down mac: <filter>
  Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
  WAN IP: <filter>
Bluetooth:
  Device-1: Intel AX200 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-4:2 chip-ID: 8087:0029
    class-ID: e001
  Report: btmgmt ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 5.2
    lmp-v: 11 status: discoverable: no pairing: yes class-ID: 6c0104
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 10.01 TiB used: 5.59 TiB (55.9%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:2 vendor: Samsung
    model: SSD 970 EVO Plus 500GB size: 465.76 GiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: 1B2QEXM7 temp: 32.9 C scheme: GPT
  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: 34.9 C
    scheme: GPT
  ID-3: /dev/sda maj-min: 8:0 vendor: Seagate model: ST4000NE001-2MA101
    size: 3.64 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: HDD rpm: 7200 serial: <filter> fw-rev: EN01 scheme: GPT
  ID-4: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST4000DM004-2CV104
    size: 3.64 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: HDD rpm: 5425 serial: <filter> fw-rev: 0001 scheme: GPT
  ID-5: /dev/sdc maj-min: 8:32 vendor: Samsung model: SSD 870 QVO 1TB
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 1B6Q scheme: GPT
  ID-6: /dev/sdd maj-min: 8:48 vendor: Samsung model: SSD 860 EVO 500GB
    size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 1B6Q scheme: GPT
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 465.46 GiB size: 457.09 GiB (98.20%)
    used: 345.41 GiB (75.6%) fs: ext4 dev: /dev/sdd2 maj-min: 8:50 label: N/A
    uuid: c13a924e-f23f-443d-93b3-0384a2541f36
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 16.3 MiB (5.4%) fs: vfat dev: /dev/sdd1 maj-min: 8:49 label: N/A
    uuid: D6CA-1692
  ID-3: /run/media/dean/Data raw-size: 465.76 GiB size: 457.38 GiB (98.20%)
    used: 347.74 GiB (76.0%) fs: ext4 dev: /dev/nvme0n1p1 maj-min: 259:3
    label: Data uuid: cd4fd70b-4e24-46ac-8092-8f44409ed6d1
  ID-4: /run/media/dean/Data-Disk1 raw-size: 3.64 TiB size: 3.58 TiB (98.40%)
    used: 3.25 TiB (90.8%) fs: ext4 dev: /dev/sdb1 maj-min: 8:17
    label: Data-Disk1 uuid: 410c13a5-f1cd-4811-80ba-1592de5069fa
  ID-5: /run/media/dean/Data-Disk2 raw-size: 3.64 TiB size: 3.58 TiB (98.40%)
    used: 914.87 GiB (25.0%) fs: ext4 dev: /dev/sda1 maj-min: 8:1
    label: Data-Disk2 uuid: 1d017fab-600b-43cc-86d8-4d6163224307
  ID-6: /run/media/dean/Game-data raw-size: 931.51 GiB
    size: 915.81 GiB (98.31%) used: 785.78 GiB (85.8%) fs: ext4 dev: /dev/sdc1
    maj-min: 8:33 label: Game-data uuid: 9bd1d750-888e-41c9-a5a3-8a323f1a8e8c
  ID-7: /run/media/dean/NVME-Data2 raw-size: 931.51 GiB
    size: 915.81 GiB (98.31%) used: 4.43 GiB (0.5%) fs: ext4 dev: /dev/nvme1n1p1
    maj-min: 259:1 label: NVME-Data2 uuid: 84da62d9-01fd-4971-90d6-4602976ac9da
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: yes
    compressor: zstd max-pool: 20%
  ID-1: swap-1 type: file size: 16 GiB used: 160 KiB (0.0%) priority: -2
    file: /swapfile
Unmounted:
  Message: No unmounted partitions found.
USB:
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 6 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-4:2 info: Intel AX200 Bluetooth type: bluetooth driver: btusb
    interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1
    power: 100mA chip-ID: 8087:0029 class-ID: e001
  Hub-2: 2-0:1 info: super-speed hub ports: 4 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: 6 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: 3-4:2 info: ASUSTek AURA LED Controller type: HID
    driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 16mA chip-ID: 0b05:1939 class-ID: 0300
    serial: <filter>
  Hub-4: 4-0:1 info: super-speed hub ports: 4 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
  Device-1: 5-3:2 info: Razer USA BlackWidow V3 type: keyboard,mouse,HID
    driver: razerkbd,usbhid interfaces: 5 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 500mA chip-ID: 1532:024e class-ID: 0300
  Device-2: 5-4:3 info: Razer USA RZ01-0316 Gaming Mouse [Basilisk V2]
    type: mouse,keyboard driver: razermouse,usbhid interfaces: 3 rev: 2.0
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 100mA
    chip-ID: 1532:0085 class-ID: 0301
  Hub-6: 6-0:1 info: super-speed hub ports: 4 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
Sensors:
  System Temperatures: cpu: 33.0 C mobo: 31.0 C gpu: amdgpu temp: 44.0 C
    mem: 42.0 C
  Fan Speeds (rpm): fan-1: 0 fan-2: 474 fan-3: 0 fan-4: 0 fan-5: 0 fan-6: 0
    fan-7: 569 gpu: amdgpu fan: 0
Repos:
  Packages: 2275 pm: pacman pkgs: 2225 libs: 579 tools: octopi,pamac,yay
    pm: flatpak pkgs: 34 pm: snap pkgs: 16
  Active pacman repo servers in: /etc/pacman.d/mirrorlist
    1: https://mirrors.manjaro.org/repo/stable/$repo/$arch
    2: https://mirror.dkm.cz/manjaro/stable/$repo/$arch
    3: https://mirror.alpix.eu/manjaro/stable/$repo/$arch
    4: http://manjaro.mirrors.uk2.net/stable/$repo/$arch
    5: https://mirrors.ft.uam.es/manjaro/stable/$repo/$arch
    6: https://mirror.math.princeton.edu/pub/manjaro/stable/$repo/$arch
    7: https://nocix.mm.fcix.net/manjaro/stable/$repo/$arch
    8: https://gsl-syd.mm.fcix.net/manjaro/stable/$repo/$arch
Processes:
  CPU top: 5 of 761
  1: cpu: 1.7% command: Xorg pid: 1440 mem: 172.0 MiB (0.5%)
  2: cpu: 1.7% command: firefox pid: 4090 mem: 651.9 MiB (2.0%)
  3: cpu: 0.9% command: firefox pid: 5979 mem: 267.8 MiB (0.8%)
  4: cpu: 0.8% command: plasmashell pid: 2102 mem: 608.9 MiB (1.9%)
  5: cpu: 0.6% command: kwin_x11 pid: 2024 mem: 323.2 MiB (1.0%)
  Memory top: 5 of 761
  1: mem: 681.8 MiB (2.1%) command: thunderbird pid: 2586 cpu: 0.3%
  2: mem: 651.9 MiB (2.0%) command: firefox pid: 4090 cpu: 1.7%
  3: mem: 608.9 MiB (1.9%) command: plasmashell pid: 2102 cpu: 0.8%
  4: mem: 323.2 MiB (1.0%) command: kwin_x11 pid: 2024 cpu: 0.6%
  5: mem: 284.4 MiB (0.8%) command: firefox pid: 4516 cpu: 0.1%
Info:
  Processes: 761 Power: uptime: 4h 9m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 1 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 12.49 GiB services: org_kde_powerdevil,upowerd
    Init: systemd v: 256 default: graphical tool: systemctl
  Compilers: clang: 18.1.8 gcc: 14.2.1 alt: 11 Shell: Bash v: 5.2.32
    running-in: konsole inxi: 3.3.36

I hope that helps to figure out what is the problem

MrLavender · 6 September 2024 12:45

If that is a NTFS drive then maybe the problem is incorrect mount options. See

https://github.com/ValveSoftware/Proton/wiki/Using-a-NTFS-disk-with-Linux-and-Windows

I have a very similar system to yours (5800X + RX6800 + 32GB + KDE Plasma) and have no problems. I just tested Half Life 2 and it works fine.

Kurogane1412 · 6 September 2024 13:44

No all my drives are ext4

but I did have mounting problems with the KDE Auto Mount in the settings could not find out why I needed to type my password to mount my drives because it worked before for years without with the KDE settings

then I did add all needed drives to the fstab as seen below

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=D6CA-1692                              /boot/efi                    vfat    noatime             0 2 
UUID=c13a924e-f23f-443d-93b3-0384a2541f36   /                            ext4    noatime,discard     0 1 
tmpfs                                       /tmp                         tmpfs   noatime,mode=1777   0 0 
/swapfile                                   none                         swap    defaults            0 0 
UUID=410c13a5-f1cd-4811-80ba-1592de5069fa   /run/media/dean/Data-Disk1   ext4    users               0 0 
UUID=84da62d9-01fd-4971-90d6-4602976ac9da   /run/media/dean/NVME-Data2   ext4    users               0 0 
UUID=cd4fd70b-4e24-46ac-8092-8f44409ed6d1   /run/media/dean/Data         ext4    users               0 0 
UUID=9bd1d750-888e-41c9-a5a3-8a323f1a8e8c   /run/media/dean/Game-data    ext4    users               0 0

Did I made a mistake somewhere?
I did edit the fstab file on 26 of April and I can not really remember if I played something after that but Steam is seeing the drives ok as it seems from this picture

h ttp s :// drive. google . com/ drive/folders/1hsjsTvTtvfLR5Vftt5VVJZOxqGhhjQik?usp=sharing

Just remove the space for the Link then you can see the picture from google drive because I can not post a link or media

Kobold · 19 September 2024 01:10

Since May, that means it has something to do with the change from Plasma5 to Plasma6.

Maybe something wrong on your user profile or around the ./cache folder.
A lot people recommend to refresh ./cache but you can take a look at the old announcement topic.

If this has something to do with fstab, then its important to know if you use a secondary library and on which drive, if the library still in sync with your Steam install around /home.

It could be problematic since you can install Proton even on another drive with a steam library.

BG405 · 19 September 2024 03:20

In addition to @Kobold’s post: I suggest running pacdiff -o and see what shows up.

Kurogane1412 · 20 September 2024 12:48

I have tried deleting ./cache that did nothing I think and the install is from 2019 so there could be many thinks wrong in the system.

and I have tried going back to Steam Beta and tried editing the mount points with the KDE partition manger because I have seen something on the Manjaro Forum but it is besically the same what I did with the Fstab just easier without using Nano and checked with Arch linux wiki for Fstab.

As said before it seems to Work with the Flatpack Version of Steam but not on other drives and the install files I moved from the Home directory to the other Steam Flatpack on Game-Data SSD was not any more visible after a reboot suddenly so it is not very practical.

and Yes I use 3 drives for my Steam 1 ,I my Home ,2 Data(Nvme) ,3 Game-Data (SSD)

everything worked well before and Steam still sees all the drives and downloads updates and other things just can not run most of them if they are not on Home

Kurogane1412 · 20 September 2024 12:52

and here it is

(base) [dean@MeshifyC-Manjaro ~]$ pacdiff -o 
/etc/bluetooth/main.conf.pacnew
/etc/passwd.pacnew
/etc/shadow.pacnew
/etc/shells.pacnew
/etc/fonts/fonts.conf.pacnew
/etc/locale.gen.pacnew
/etc/default/grub.pacnew
/etc/pam.d/kde.pacnew
/etc/pamac.conf.pacnew
/etc/mkinitcpio.conf.pacnew
/etc/pacman.conf.pacnew
/etc/pacman-mirrors.conf.pacnew
/etc/sane.d/canon_lide70.conf.pacnew
/etc/sane.d/escl.conf.pacnew
/etc/pam.d/sddm.pacnew
/etc/systemd/homed.conf.pacnew
/etc/texmf/web2c/fmtutil.cnf.pacsave

what should that show?

At this point maybe it is easier to reinstall Manjaro than find the problem but at the moment I do not have the time for this

soundofthunder · 20 September 2024 17:30

It should show something more like;

(base) [dean@MeshifyC-Manjaro ~]$ pacdiff -o

in a well maintained system.

This of course is your choice; certainly, reinstalling is probably the fastest route to a working system. Then, you need to set everything up again, just the way you like it. I suppose that what I’m trying to say here is that it’s likely going to take time, either way.

The .pacnew files should best have been addressed as they came to be. Skimming through that list, some of them might have even had system security implications.

Going forward, whether you choose to reinstall, or not, you should certainly pay more attention to system maintenance.

Make a habit of checking the latest Update Announcements for any condition that might affect you; the issues and solutions are generally listed for anyone who will take the time to read them.

When using a rolling release distribution, the expectation is that you (the system admin) will take a more hands-on approach.

However, if that’s not you, there is a new edition of Manjaro in the pipeline that might be more appealing. For the time being it’s called Manjaro Immutable; if you search the forum, you will find a few references to it; like this one, for example:

Manjaro Immutable Out Now For Community Testing

Cheers.

Kobold · 20 September 2024 20:08

The problem is that you waited to long to deal with your problems, makes everything more and more difficult.

Ignoring the problem for around 4month and the point that you did additional changes around your systems + not maintaining your pacnew files.

This pacnew files are changes around your setting files that showing up after the developer created some changes. Stuff that gets removed or stuff that adds in there.

Even after reinstall you will face them after time, it won’t take long to merge this stuff, but its a part of the maintaining.

BG405 · 21 September 2024 04:30

In this list I see a few you should definitely not blindly merge, and another few you need to be careful with:

(base) [dean@MeshifyC-Manjaro ~]$ pacdiff -o 
/etc/passwd.pacnew
/etc/shadow.pacnew
/etc/locale.gen.pacnew
/etc/pam.d/kde.pacnew

These can affect the upgrade process:

/etc/pamac.conf.pacnew
/etc/mkinitcpio.conf.pacnew
/etc/pacman.conf.pacnew
/etc/pacman-mirrors.conf.pacnew

Be careful with this one too:

/etc/pam.d/sddm.pacnew

This might complicate things if you do reinstall: I am unfamiliar with how systemd-homed works, but you’ll most likely want to save all the configurations and stuff from your /home:

/etc/systemd/homed.conf.pacnew

Hope this is of some use.

Kurogane1412 · 21 September 2024 09:53

so it should be empty?
if so how to do that?

I have also a Tuxedo Laptop running Manjaro since October 2022 there should it be easier done

soundofthunder:

his of course is your choice; certainly, reinstalling is probably the fastest route to a working system. Then, you need to set everything up again, just the way you like it. I suppose that what I’m trying to say here is that it’s likely going to take time, either way.

The .pacnew files should best have been addressed as they came to be. Skimming through that list, some of them might have even had system security implications.

Going forward, whether you choose to reinstall, or not, you should certainly pay more attention to system maintenance.

Make a habit of checking the latest Update Announcements for any condition that might affect you; the issues and solutions are generally listed for anyone who will take the time to read them.

When using a rolling release distribution, the expectation is that you (the system admin) will take a more hands-on approach.

However, if that’s not you, there is a new edition of Manjaro in the pipeline that might be more appealing. For the time being it’s called Manjaro Immutable; if you search the forum, you will find a few references to it; like this one, for example:

If I reinstall then it will be totally new so deleting my Home directory and probably changing from Sata SSD to an NVME drive

Also I look sometimes at the Update Announcements or if I am having a problem then for sure.

Googling and reading something from the Manjaro Forum maybe I found something I did wrong
somewhere last year as I got an problem stopped using sudo pacman -Syu then instead used sudo pamac update

Kurogane1412 · 21 September 2024 10:04

I was busy with life and my System works fine only the KDE Auto Mount stopped working but probably for every one else too

and Steam showing strange behavior from time to time so Thought it was a Proton Problem and I did remember now that I did play in Summer once Supreme commander to test if games Worked mid June or something and it worked after that I did not even turn on my Desktop because it was to hot here Vienna in Summer used my laptop instead.

Yeah you are right I should provably learn about pacnew Stuff since I am using Manajaro for a long time now and probably will continue

Kurogane1412 · 21 September 2024 10:14

Thanks for trying to explain what is important

but If I can not really understand what I am doing I should probably not touch these
as long as my system works mostly fine

As said in a previous replay If I reinstall then I will format everything in the Root/Home directory or even Change from a Sata SDD to an NVME Drive

For now If I want to play really badly Games Steam Flatpak works mostly without a problem and started with God Of War there no problems there as long as the Install files are in the Home directory

or in the Future Change to Manjaro Immutable could give it a try next year when it is stable enough

soundofthunder · 21 September 2024 10:15

2022, you say?

Well, one way is to carefully read through the update announcements from 2022 to current, and find every reference to a .pacnew file being provided via an update.

Naturally, that would be time-consuming, but effective nonetheless. This is an important step, as simply merging each .pacnew can potentially cause more complication; each should be handled carefully, case by case.

You can see the System Maintenance page in the Manjaro Wiki for a brief overview under the heading Pacnew and Pacsave files – a forum search will reveal more specific information on how to use the respective tools available.

I’m afraid if you’re looking for a quick fix, you won’t find one; each file should be merged or replaced dependent on the reason for the file existing in the first place.

In some cases, replacing a file might overwrite personal settings. In other cases, only specific (usually newer) content should be merged, and so on.

As @BG405 warned, these files should not be handled blindly.

Pamac should never be used with sudo; if elevated privileges are needed, it will prompt you to enter your password.

So, yes, if you made a habit of using sudo pamac ... it’s likely you’ve not done yourself any favours.

Using pacman is almost always my preference. The only time I use pamac is to install an occasional flatpak or rebuild one of the few AUR packages I use.

Pacman isn’t difficult once you get used to it.

Pacman Overview (Manjaro Wiki)
Pacman (Arch Wiki)

And a quick reference guide can be found here:

11 Ways to Use Pacman on Manjaro Linux (ignore the last section where the author infers that Pamac is a frontend for pacman – this simply isn’t true).

Handling the .pacnew files isn’t overly difficult, but I imagine it can seem daunting if you’re not confident with the concept.

As you already seem amenable to performing a reinstall, that is always an option. It might also give you the opportunity to invest more time in learning important maintenance tasks.

All the information you will probably need already exists as Tutorials from other members, or in the Manjaro Wiki.

So, all it takes, really, is to make a conscious choice between reading or playing a game for a few hours.

Cheers.

Edit:- Typos.

Kobold · 21 September 2024 16:52

I also loved Total Annihilation and Supreme Commander…

If you still into RTS i can recommend to try out Beyond All Reason (its also free and with native Linux support as Flatpak or AppImage):

To Merge Pacnew files is just a little learning curve. You should use Meld for this, but there are enough info’s on our forum how to deal with pacnew files.

Create a system snapshot with Timeshift for example and also have a bootstick prepared (just in case if something went wrong), before you playing with that files.

You mostly just use your brain, if new code added behind a # its a no brainer to simple add this stuff.

Sometimes there is new active code or sometimes some code is removed or deactivated with a # and then you might need to collect information about this feature.

But as we said, there is more than enough information about this stuff available in our Forum already and there is no need to repeat it again,
so just use the search function.

But you are free to ask again, if you still need help, when you cant find a solution.

Kurogane1412 · 23 September 2024 10:41

Jup and on the second try with something important like passwd I messed up but lucky had a Back up before made

this shows me I do not understand somethings even like 2 years of changes so I probably will not touch my desktop now and do the reinstall next year or something

but another try on the laptop

    ~  pacdiff -o                                                   ✔ 
/etc/passwd.pacnew
/etc/shells.pacnew
/etc/locale.gen.pacnew
/etc/default/grub.pacnew
/etc/pam.d/kde.pacnew
/etc/pamac.conf.pacnew
/etc/mkinitcpio.conf.pacnew
/etc/pacman.conf.pacnew
/etc/pacman-mirrors.conf.pacnew
    ~  sudo DIFFPROG=meld DIFFSEARCHPATH="/ /etc " MERGEPROG="git tlp.conf.pacnew -p" pacdiff
[sudo] password for dean: 
==> pacnew file found for /etc/passwd
:: (V)iew, (M)erge, (S)kip, (R)emove pacnew, (O)verwrite with pacnew, (Q)uit: [v/m/s/r/o/q] v
:: (V)iew, (M)erge, (S)kip, (R)emove pacnew, (O)verwrite with pacnew, (Q)uit: [v/m/s/r/o/q] r
removed '/etc/passwd.pacnew'
==> pacnew file found for /etc/shells
:: (V)iew, (M)erge, (S)kip, (R)emove pacnew, (O)verwrite with pacnew, (Q)uit: [v/m/s/r/o/q] v
:: (V)iew, (M)erge, (S)kip, (R)emove pacnew, (O)verwrite with pacnew, (Q)uit: [v/m/s/r/o/q] r
removed '/etc/shells.pacnew'
==> pacnew file found for /etc/locale.gen
:: (V)iew, (M)erge, (S)kip, (R)emove pacnew, (O)verwrite with pacnew, (Q)uit: [v/m/s/r/o/q] v
:: (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] v
:: (V)iew, (M)erge, (S)kip, (R)emove pacnew, (O)verwrite with pacnew, (Q)uit: [v/m/s/r/o/q] r
removed '/etc/locale.gen.pacnew'
==> pacnew file found for /etc/default/grub
:: (V)iew, (M)erge, (S)kip, (R)emove pacnew, (O)verwrite with pacnew, (Q)uit: [v/m/s/r/o/q] v
:: (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] r
removed '/etc/default/grub.pacnew'
==> pacnew file found for /etc/pam.d/kde
:: (V)iew, (M)erge, (S)kip, (R)emove pacnew, (O)verwrite with pacnew, (Q)uit: [v/m/s/r/o/q] v
:: (V)iew, (M)erge, (S)kip, (R)emove pacnew, (O)verwrite with pacnew, (Q)uit: [v/m/s/r/o/q] o
renamed '/etc/pam.d/kde.pacnew' -> '/etc/pam.d/kde'
==> pacnew file found for /etc/pamac.conf
:: (V)iew, (M)erge, (S)kip, (R)emove pacnew, (O)verwrite with pacnew, (Q)uit: [v/m/s/r/o/q] v
:: (V)iew, (M)erge, (S)kip, (R)emove pacnew, (O)verwrite with pacnew, (Q)uit: [v/m/s/r/o/q] r
removed '/etc/pamac.conf.pacnew'
==> pacnew file found for /etc/mkinitcpio.conf
:: (V)iew, (M)erge, (S)kip, (R)emove pacnew, (O)verwrite with pacnew, (Q)uit: [v/m/s/r/o/q] v
:: (V)iew, (M)erge, (S)kip, (R)emove pacnew, (O)verwrite with pacnew, (Q)uit: [v/m/s/r/o/q] r
removed '/etc/mkinitcpio.conf.pacnew'
==> pacnew file found for /etc/pacman.conf
:: (V)iew, (M)erge, (S)kip, (R)emove pacnew, (O)verwrite with pacnew, (Q)uit: [v/m/s/r/o/q] v
:: (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] r
removed '/etc/pacman.conf.pacnew'
==> pacnew file found for /etc/pacman-mirrors.conf
:: (V)iew, (M)erge, (S)kip, (R)emove pacnew, (O)verwrite with pacnew, (Q)uit: [v/m/s/r/o/q] v
:: (V)iew, (M)erge, (S)kip, (R)emove pacnew, (O)verwrite with pacnew, (Q)uit: [v/m/s/r/o/q] r
removed '/etc/pacman-mirrors.conf.pacnew'

Merge does not work for some reason but if I made it right it will boot wish me luck if not I will restore it again

I did not know that so I will be careful in the future with pamac

Kurogane1412 · 23 September 2024 11:00

that looks nice will give it a try

thanks for the tip you saved me from trouble as I was trying it out on my laptop and the last reboot with a lot of changes worked

But I am not 100 % sure if did it right but at the same time I did notice some changes I made in the past so I deleted the pacnew because there were a lot with # so could ignore these probably and I have a working system on my laptop.

As for my Desktop it will be easier to track the changes after a reinstall and there is a tool for that made manjaro-pacnew-checker already installed on my laptop

But one last question from this output:

Kurogane1412:

base) [dean@MeshifyC-Manjaro ~]$ pacdiff -o 
/etc/bluetooth/main.conf.pacnew
/etc/passwd.pacnew
/etc/shadow.pacnew
/etc/shells.pacnew
/etc/fonts/fonts.conf.pacnew
/etc/locale.gen.pacnew
/etc/default/grub.pacnew
/etc/pam.d/kde.pacnew
/etc/pamac.conf.pacnew
/etc/mkinitcpio.conf.pacnew
/etc/pacman.conf.pacnew
/etc/pacman-mirrors.conf.pacnew
/etc/sane.d/canon_lide70.conf.pacnew
/etc/sane.d/escl.conf.pacnew
/etc/pam.d/sddm.pacnew
/etc/systemd/homed.conf.pacnew
/etc/texmf/web2c/fmtutil.cnf.pacsave

can it mess up Steam,Proton, or file permissions on other drives?

when it worked before mostly without problems and mean sometimes some games would not start but after changing Proton Version after a bit of time they would work only after trying Half life 2 end of August I did know it must be something else

soundofthunder · 23 September 2024 14:58

Kurogane1412:

another try on the laptop

    ~  pacdiff -o                                                   ✔ 
/etc/passwd.pacnew
/etc/shells.pacnew
/etc/locale.gen.pacnew
/etc/default/grub.pacnew
/etc/pam.d/kde.pacnew
/etc/pamac.conf.pacnew
/etc/mkinitcpio.conf.pacnew
/etc/pacman.conf.pacnew
/etc/pacman-mirrors.conf.pacnew
    ~  sudo DIFFPROG=meld DIFFSEARCHPATH="/ /etc " MERGEPROG="git tlp.conf.pacnew -p" pacdiff
[sudo] password for dean: 
==> pacnew file found for /etc/passwd
:: (V)iew, (M)erge, (S)kip, (R)emove pacnew, (O)verwrite with pacnew, (Q)uit: [v/m/s/r/o/q] v
:: (V)iew, (M)erge, (S)kip, (R)emove pacnew, (O)verwrite with pacnew, (Q)uit: [v/m/s/r/o/q] r
removed '/etc/passwd.pacnew'
==> pacnew file found for /etc/shells
:: (V)iew, (M)erge, (S)kip, (R)emove pacnew, (O)verwrite with pacnew, (Q)uit: [v/m/s/r/o/q] v
:: (V)iew, (M)erge, (S)kip, (R)emove pacnew, (O)verwrite with pacnew, (Q)uit: [v/m/s/r/o/q] r
removed '/etc/shells.pacnew'
==> pacnew file found for /etc/locale.gen
:: (V)iew, (M)erge, (S)kip, (R)emove pacnew, (O)verwrite with pacnew, (Q)uit: [v/m/s/r/o/q] v
:: (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] v
:: (V)iew, (M)erge, (S)kip, (R)emove pacnew, (O)verwrite with pacnew, (Q)uit: [v/m/s/r/o/q] r
removed '/etc/locale.gen.pacnew'
==> pacnew file found for /etc/default/grub
:: (V)iew, (M)erge, (S)kip, (R)emove pacnew, (O)verwrite with pacnew, (Q)uit: [v/m/s/r/o/q] v
:: (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] r
removed '/etc/default/grub.pacnew'
==> pacnew file found for /etc/pam.d/kde
:: (V)iew, (M)erge, (S)kip, (R)emove pacnew, (O)verwrite with pacnew, (Q)uit: [v/m/s/r/o/q] v
:: (V)iew, (M)erge, (S)kip, (R)emove pacnew, (O)verwrite with pacnew, (Q)uit: [v/m/s/r/o/q] o
renamed '/etc/pam.d/kde.pacnew' -> '/etc/pam.d/kde'
==> pacnew file found for /etc/pamac.conf
:: (V)iew, (M)erge, (S)kip, (R)emove pacnew, (O)verwrite with pacnew, (Q)uit: [v/m/s/r/o/q] v
:: (V)iew, (M)erge, (S)kip, (R)emove pacnew, (O)verwrite with pacnew, (Q)uit: [v/m/s/r/o/q] r
removed '/etc/pamac.conf.pacnew'
==> pacnew file found for /etc/mkinitcpio.conf
:: (V)iew, (M)erge, (S)kip, (R)emove pacnew, (O)verwrite with pacnew, (Q)uit: [v/m/s/r/o/q] v
:: (V)iew, (M)erge, (S)kip, (R)emove pacnew, (O)verwrite with pacnew, (Q)uit: [v/m/s/r/o/q] r
removed '/etc/mkinitcpio.conf.pacnew'
==> pacnew file found for /etc/pacman.conf
:: (V)iew, (M)erge, (S)kip, (R)emove pacnew, (O)verwrite with pacnew, (Q)uit: [v/m/s/r/o/q] v
:: (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] r
removed '/etc/pacman.conf.pacnew'
==> pacnew file found for /etc/pacman-mirrors.conf
:: (V)iew, (M)erge, (S)kip, (R)emove pacnew, (O)verwrite with pacnew, (Q)uit: [v/m/s/r/o/q] v
:: (V)iew, (M)erge, (S)kip, (R)emove pacnew, (O)verwrite with pacnew, (Q)uit: [v/m/s/r/o/q] r
removed '/etc/pacman-mirrors.conf.pacnew'

Merge does not work for some reason but if I made it right it will boot wish me luck if not I will restore it again

Well, deleting all of the .pacnew files wasn’t the expected outcome. Now the updated settings and fixes they would have provided are just… gone…

Sometimes .pacnew files are provided when there is a change that only the system administrator (you) can fix.

The files will contain the necessary changes, and you’re expected to edit or merge configurations as needed, to make sure your system works according to the new changes.

I’ve seen threads with all kinds of issues resulting from pacnews not being properly merged, or simply ignored.

Printers can stop working; Fonts can display incorrectly; Pacman might stop working as expected; Logins can fail because password handling has changed; Internet connections may be affected; and so on…

So, it’s possible that an application that has a login, or relies on specific permissions fro proper operation, might be affected by ignoring (or deleting) pacnew files. It’s hard to say, because it depends on what changes had to be made and how critical not merging the pacnew might be.

With regard Steam, and related software, users frequently have issues that are not related at all, so…