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

Support Gaming
,
21

Indeed, and unless there is an image or whatever to restore, will be difficult to handle. :man_shrugging:

22

If you used the search function as we suggestedā€¦ there is always the recommendation to View your files to compare them.

Never just remove themā€¦ never just overwrite themā€¦

I recommend now, to use your snapshot and copy this pacnew files from the snapshot to the original locations and do this time a real Merge.

And yes, Merge (M-Key) option is buggy, just press V and Merge from there.

I also recommend to splitt this files, merge the half now and the other half in a few days or later after a restart, if you dont want to wait to see if you run into problems.

23

Well those all show ā€˜viewā€™ first ā€¦ maybe they did manage them before removal.

Despite the name, I never suggest using the ā€˜mergeā€™ function - ā€˜viewā€™ is the suggestion.

(which would open DIFFPROG and allow you to make edits)

24

From what i see there in the logs, i miss the line where it saidā€¦ that both files looks identical and ask to remove it.

Not that this should be the general case but i think that around ~40-60% of this pacnew files probably should be that way (Identical to remove). Depends on the individual settings from the average user.

That i miss this slogan at all, lead me to the conclusion, that Kurogane did a mistake there.

(M)erge AND (V)iew was identical anyways (from my understanding), i used M in the past and use V today, because M is buggy and is no longer working.

25

They are not.
Merge attempts to do the merge for you ā€˜automaticallyā€™ (which is why it is not recommended).

merge_file() {
        pacfile="$1"
        file="$2"

        package="$(pacman -Qoq "$file")" || return 1
        base_tar="$(base_cache_tar "$package")"

        if [[ -z $base_tar ]]; then
                msg2 "Unable to find a base package."
                return 1
        fi

        basename="$(basename "$file")"
        tempdir="$(mktemp -d --tmpdir "pacdiff-merge-$basename.XXX")"
        base="$(mktemp "$tempdir"/"$basename.base.XXX")"
        merged="$(mktemp "$tempdir"/"$basename.merged.XXX")"

        if ! bsdtar -xqOf "$base_tar" "${file#/}" >"$base"; then
                msg2 "Unable to extract the previous version of this file."
                return 1
        fi

        if $mergeprog "$file" "$base" "$pacfile" >"$merged"; then
                msg2 "Merged without conflicts."
        fi

        $diffprog "$file" "$merged"

        while :; do
                ask "Would you like to use the results of the merge? [y/n] "

                read -r c || return 1
                case $c in
                        y|Y) break ;;
                        n|N) return 1 ;;
                        *) msg2 "Invalid answer." ;;
                esac
        done

        if ! $SUDO cp -v "$merged" "$file"; then
                warning "Unable to write merged file to %s. Merged file is preserved at %s" "$file" "$merged"
                return 1
        fi
        $SUDO rm -rv "$pacfile" "$tempdir"
        return 0
}

Though as you can see from the code it is pretty sane about it and would present you with the files and ask about replacement, etc.
If your merge somehow worked differently ā€¦ Iā€™m not sure how or why ā€¦ maybe you were misinterpreting what was presented?
Merge would use DIFFPROG to show you the difference between the old file and the automerged one.

26

Meld does a decent job with this, where it states ā€œFiles are identical.ā€ I wouldnā€™t trust any ā€œauto-mergeā€ though, without making a backup of the file first.

27

Automerge would be something that i definitely never would trust or rely on.

But as i said in another Topic that i created 6month ago, that (M)erge lead to another command in the past, so we had this discussion already :wink:

28

well I did get it wrong and already reverted the changes but did not had the time to respond.

maybe I am also having a problem because I am using Steam with nearly 4 Drives on my Desktop

29

Well my Bad as Merge(Auto) did not work and it was not obvious for me when the Meld window opened that I should edit them there too

30

That is what is confusing me and every mistake could lead to an unbootable system

31

Or could be that for some files I just need to add the changes from pacnew files to the original?

32

Yes, indeed. You can also remove parts which are not in the .pacnew, if you are sure those parts are no longer needed (especially #commented lines).

If in doubt about a particular file, post it here with its .pacnew for comparison; Iā€™m happy to assist.

33

I tried looking into the manjaro wiki and arch wiki and the Manjaro forum howto but could not find something for pacnew files.

I was before Manjaro a Chakra Linux user and even then I did not knew about that part so probably about time to learn it so thanks for you all willingness to help :+1:

2 Likes
34

I am a bit busy right now so I will probably try again on the weekend

and yeah the parts with # are easier to handle but problem is where it is a small change

like for passwd.pacnew is:
root:x:0:0::/root:/usr/bin/bash

but passwd:

root:x:0:0::/root:/bin/bash
nobody:x:65534:65534:Nobody:/:/usr/bin/nologin
dbus:x:81:81:System Message Bus:/:/usr/bin/nologin
bin:x:1:1::/:/usr/bin/nologin
daemon:x:2:2::/:/usr/bin/nologin
mail:x:8:12::/var/spool/mail:/usr/bin/nologin
ftp:x:14:11::/srv/ftp:/usr/bin/nologin
http:x:33:33::/srv/http:/usr/bin/nologin
systemd-coredump:x:981:981:systemd Core Dumper:/:/usr/bin/nologin
systemd-network:x:980:980:systemd Network Management:/:/usr/bin/nologin
systemd-oom:x:979:979:systemd Userspace OOM Killer:/:/usr/bin/nologin
systemd-journal-remote:x:978:978:systemd Journal Remote:/:/usr/bin/nologin
systemd-resolve:x:977:977:systemd Resolver:/:/usr/bin/nologin
systemd-timesync:x:976:976:systemd Time Synchronization:/:/usr/bin/nologin
tss:x:975:975:tss user for tpm2:/:/usr/bin/nologin
uuidd:x:68:68::/:/usr/bin/nologin
dhcpcd:x:974:974:dhcpcd privilege separation:/:/usr/bin/nologin
dnsmasq:x:973:973:dnsmasq daemon:/:/usr/bin/nologin
rpc:x:32:32:Rpcbind Daemon:/var/lib/rpcbind:/usr/bin/nologin
rpcuser:x:34:34:RPC Service User:/var/lib/nfs:/usr/bin/nologin
avahi:x:972:972:Avahi mDNS/DNS-SD daemon:/:/usr/bin/nologin
cups:x:209:209:cups helper user:/:/usr/bin/nologin
flatpak:x:971:971:Flatpak system helper:/:/usr/bin/nologin
geoclue:x:970:970:Geoinformation service:/var/lib/geoclue:/usr/bin/nologin
git:x:969:969:git daemon user:/:/usr/bin/git-shell
nm-openconnect:x:968:968:NetworkManager OpenConnect:/:/usr/bin/nologin
nm-openvpn:x:967:967:NetworkManager OpenVPN:/:/usr/bin/nologin
ntp:x:87:87:Network Time Protocol:/var/lib/ntp:/bin/false
openvpn:x:966:966:OpenVPN:/:/usr/bin/nologin
polkitd:x:102:102:PolicyKit daemon:/:/usr/bin/nologin
rtkit:x:133:133:RealtimeKit:/proc:/usr/bin/nologin
saned:x:965:965:SANE daemon user:/:/usr/bin/nologin
sddm:x:964:964:Simple Desktop Display Manager:/var/lib/sddm:/usr/bin/nologin
usbmux:x:140:140:usbmux user:/:/usr/bin/nologin
dean:x:1000:1000:Dean :/home/dean:/bin/bash
systemd-journal-upload:x:961:961:systemd Journal Upload:/:/usr/bin/nologin
fwupd:x:960:960:Firmware update daemon:/var/lib/fwupd:/usr/bin/nologin
_talkd:x:959:959:User for legacy talkd server:/:/usr/bin/nologin
passim:x:958:958:Local Caching Server:/usr/share/empty:/usr/bin/nologin

if I mess that up then not even my password works in tty1

or that with the shalls

shalls.pacnew

# Pathnames of valid login shells.
# See shells(5) for details.

/bin/sh
/bin/bash
/bin/rbash
/usr/bin/sh
/usr/bin/bash
/usr/bin/rbash

shells

# Pathnames of valid login shells.
# See shells(5) for details.

/bin/sh
/bin/bash
/bin/zsh
/usr/bin/zsh
/usr/bin/git-shell
/usr/bin/bash
/bin/rbash
/usr/bin/rbash
/usr/bin/sh
/usr/bin/systemd-home-fallback-shell

it would be nice to have visual guides or how to with examples in the wiki or the forum or maybe I overlooked them so if you have link that would be helpful n

35

Those two files Iā€™d leave alone. You are correct that simply merging the first one means your login wouldnā€™t work; youā€™d have to chroot in and set the passwords again.

For shells; same. No reason to remove those entries in your existing file, at least that I can see.

36

This link was already given:

ā€¦and thereā€™s also this from the Arch Wiki:

Manjaro Search returned 50 results simply by searching for one key word pacnew:

Yes, thatā€™s what merging does; at least, in theory. Itā€™s best to see what needs to be merged beforehand, so that you can decide what should be merged.

But, be very careful. Good luck.

37

And as I showed there, and as one of the posts is eventually marked the solution ā€¦ the merge function always did the automerge thing (using $MERGEPROG) and only after that would use DIFFPROG to show you the old file and the automerged one. The m has always included the automerge - it is its function.
Some logic around how it did the automerge changed slightly ā€¦ but if you wanted to avoid some sort of automerge ā€¦ then you should never have been using m.

The suggestion is, was, and will continue to be - use view.
Then compare and ā€˜mergeā€™ by hand as needed.
This may not, indeed in my experience rarely does, produce an ā€˜identical fileā€™.
(You have an edited file, which is why you have the pacnew, for a reason usually. Custom options, etc.)

Back to the issue at hand ā€¦

Does not strike me as inherently incorrect.
This is likely what my actions and output would look like most of the time.
It all hinges of course on what edits were made during ā€˜viewā€™.
But if they were correct - this sequence of events is entirely normal and acceptable practice.

2 Likes
38

Of course I looked over them before but they are not that useful for users who for the fist time stumble open pacnew or pacsave files that they should edit themself

My bad I did not thought to use the search option to look for that and that did help to have some more examples to be more sure what I am doing and I did the merge now on my laptop probably a bit better

1 Like
39

Yeah I did notice on my laptop it does not need to be identical if it deletes my changes that I made myself as example I edited the grub file where I set swap file for hibernation

at pamac.conf this part there were basically only my added changes and in pacnew out commented or not there

and that I am a bit more secure what I am doing I will try that same on my desktop and report back on the weekend if ti fixes the original problem at all if not I will anyway be doing the reinstall with new drives

so thank you all for helping and having the patience for teaching me new stuff :+1:

3 Likes
40

UPDATE

Sorry that took a lot of longer because I was running out of space on my Root portion to make a Timeshift

(base) [dean@MeshifyC-Manjaro ~]$ sudo DIFFPROG=meld DIFFSEARCHPATH="/ /etc " MERGEPROG="git tlp.conf.pacnew -p" pacdiff
==> pacnew file found for /etc/bluetooth/main.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/bluetooth/main.conf.pacnew'
==> 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/shadow
:: (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/shadow.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/fonts/fonts.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/fonts/fonts.conf.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] 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] 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] r
removed '/etc/pam.d/kde.pacnew'
==> 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] r
removed '/etc/pacman.conf.pacnew'
==> pacnew file found for /etc/makepkg.conf.d/rust.conf
:: (V)iew, (M)erge, (S)kip, (R)emove pacnew, (O)verwrite with pacnew, (Q)uit: [v/m/s/r/o/q] v
  -> Files are identical, removing...
removed '/etc/makepkg.conf.d/rust.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] r
removed '/etc/pacman-mirrors.conf.pacnew'
==> pacnew file found for /etc/sane.d/canon_lide70.conf
:: (V)iew, (M)erge, (S)kip, (R)emove pacnew, (O)verwrite with pacnew, (Q)uit: [v/m/s/r/o/q] v
  -> Files are identical, removing...
removed '/etc/sane.d/canon_lide70.conf.pacnew'
==> pacnew file found for /etc/sane.d/escl.conf
:: (V)iew, (M)erge, (S)kip, (R)emove pacnew, (O)verwrite with pacnew, (Q)uit: [v/m/s/r/o/q] r
removed '/etc/sane.d/escl.conf.pacnew'
==> pacnew file found for /etc/pam.d/sddm
:: (V)iew, (M)erge, (S)kip, (R)emove pacnew, (O)verwrite with pacnew, (Q)uit: [v/m/s/r/o/q] v
  -> Files are identical, removing...
removed '/etc/pam.d/sddm.pacnew'
==> pacnew file found for /etc/systemd/homed.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/systemd/homed.conf.pacnew'
==> pacsave file found for /etc/texmf/web2c/fmtutil.cnf
:: (V)iew, (M)erge, (S)kip, (R)emove pacsave, (O)verwrite with pacsave, (Q)uit: [v/m/s/r/o/q] v
  -> Files are identical, removing...
removed '/etc/texmf/web2c/fmtutil.cnf.pacsave'

I did probably make one mistake with sane.d pressed r too fast without seeing what happened but probably not important in this case.

I have normal booting system but still Steam is not working hot how should some games can work some do not and recently I noticed I can not a add new drives to steam and when I remove one forget it.

Because I will be anyway reinstalling as soon as I get an bigger Nvme drive I would just like to know if I somehow by mistake removed something that was important for Steam?

and in both Steam Native and Steam Flatpack can not add new drives or it does not look how it should look when you are adding Drives in Steam because I tried Nobara Linux on my 500 GB Nvme drive and added Game-Date drive a 1 TB sata ssd and was normally able to add the drive and play some Doom Eternal on the same drive I was playing in Manjaro Linux