Dear all,
Same here , like others (AdamJenson), I had a sound issue on my Manjaro, after the update.
I was able to “fix” it , by opening pavucontrol and changing the settings (Configuration tab + Output Devices). But it is not perfect (as before the update): because I need to choose between the config for headphones or the config for speakers: Meaning I cannot easily switch from one to another.
From what I can see , this update has impacted my sink & port.
More details below where there is a diff between speakers & headphones configuration
Far more likely reason for ~/.profile not being loaded if you’re an Xfce user is this change to LightDM. Previously it was loading ~/.profile and other files
for file in "/etc/profile" "$HOME/.profile" "/etc/xprofile" "$HOME/.xprofile"; do
if [ -f "$file" ]; then
echo "Loading profile from $file";
. "$file"
fi
done
Now it doesn’t do that, and neither bash or zsh will load ~/.profile by default (bash will load it only if there is no ~/.bash_profile or ~/.bash_login, or if it’s launched with name sh or with --posix option).
So yes, if you were relying on previous LightDM behaviour and still need ~/.profile to be sourced then you now have to do that from either ~/.bash_profile or ~/.zprofile as appropriate for your chosen shell.
Since you got a snapshot from this pacnew file you can easy delete it.
If you have also merged other and older pacnew files, you may could fix your bug… its only a possibility.
But not from this brand new .pacnew file… both config files are fine “at the moment”… but we merge it for the future, if/when a developer rely on this newer settings at some day or not… nobody knows.
Thats why this changes right now are only optional… you can’t know what happends and how much it depends at a certain time, to have this settings updated.
You just fixing possible bugs that maybe will show up in future… minority report style, don’t get arrested by Tom Cruise
Yeah, I just type pacdiff -s. You already sent the instructions to use meld, right?
Do I need to use that, or doing that manually on the file it’s ok?
Right… If I remember correctly, I don’t have any other pacnew files…
I suspect that this bug it’s something on Xorg or Gnome itself. Because already on the login screen I feel the delay on some things (like press enter to start typing the password on login screen. In system, pause a song have the same problem).
Someone told me a year ago, that Meld doing a better job to keep the file rights/access present after Merging. You need to do it manually, always. The question is only, in which viewer/editor you gonna do it.
Its not meld thats better at permissions.
Its pacdiff -s, whatever the editor of choice.
As it creates temporary directory, and uses sudoedit, meaning acts on temporary files and then uses sudo afterwards to apply changes. meld is regarded well for being a GUI that supports in-line merging and editing.
(tools like kdiff3 only allow full replacements, vimdiff is unwieldy, etc)
But the point is to use pacdiff which is the tool for finding the offending pacnew/pacsave/etc’s, as well as the appropriate tools and formulated functions for editing and preserving files. (skip, save, backup, view, sudoedit as mentioned, etc)
A snippet for the extra curious:
Summary
diffprog_fn() {
if [[ -n "$SUDO" ]]; then
SUDO_EDITOR="$diffprog" sudoedit "$@"
else
$diffprog "$@"
fi
}
view_diff() {
pacfile="$1"
file="$2"
package="$(pacman -Qoq "$file")" || return 1
base_tar="$(base_cache_tar "$package")"
two_way_diff() {
diffprog_fn "$pacfile" "$file"
}
three_way_diff() {
diffprog_fn "$pacfile" "$base" "$file"
}
unset tempdir
if (( ! THREE_WAY_DIFF )); then
two_way_diff
elif [[ -z $base_tar ]]; then
msg2 "Unable to find a base package. falling back to 2-way diff."
two_way_diff
else
basename="$(basename "$file")"
tempdir="$(mktemp -d --tmpdir "pacdiff-diff-$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. falling back to 2-way diff."
two_way_diff
else
three_way_diff
fi
fi
ret=1
if cmp -s "$pacfile" "$file"; then
msg2 "Files are identical, removing..."
$SUDO rm -v "$pacfile"
ret=0
fi
$SUDO rm -rf "$tempdir"
return $ret
}
When you have several (older) pacnew files, because you never maintained your .pacnew files yet. And you need still help with them, you better create your own Topic.
In a Announcements Topic should mainly this discussed which is in direct relation to this Stable update and older pacnew files are no part of it… or is this a new file?
Btw. your screenshot not showing which one is pacnew and which is the old version. The simple answer, without any details… for sure you should manually merge, but how exactly… is another question and required more overview/details.
To me that looks like an old installation, since zsh has been default for a while now as far as I know. So I’d assume .pacnew merges haven’t been tended to in a while.
@GaaSantAna I’d merge that manually (right to left); but do heed advice on starting your own thread if you haven’t done so already, for any further issues on this.