Some Nvidia cards don’t work with the current 465.31 drivers when used with Display Port and/or 4k Monitors. More about the issue at the Nvidia Developer Forum. We recommend to switch to Nouveau driver as needed. If you however need the Nvidia driver, you can get the PKGBUILDs of the 460.73.01 version and build your driver locally with makepkg or use the pre-compiled packages: nvida-utils, dkms and lib32 + precompiled .
Older Issues
OS prober does not run and add other operating systems
Please click the â–ş at the beginning of this line to view this solution
To restore, please execute: echo GRUB_DISABLE_OS_PROBER=false|sudo tee -a /etc/default/grub && sudo update-grub
We recommend to switch over to Nouveau drivers if your card is mentioned here and the feature you need is not in red TO DOhere for your particular card.
If you however still need proprietary drivers, you may want to execute the following to ensure all parts of the nVidia drivers get installed properly:
sudo mhwd -a pci nonfree 0300
If proprietary drivers don't fix everything, please click the â–ş at the beginning of this line to view more info
For AMD GPU users having a black screen with kernel 5.10
Please click the â–ş at the beginning of this line to view more info
Due to a bug in the AMD drivers, please try the following first:
For GRUB:
Open a terminal or a TTY
Open /etc/default/grub in your favourite CLI editor (nano vi, emacs`)
Find the line: GRUB_CMDLINE_LINUX_DEFAULT="
Add amdgpu.dc=0
Save
Execute sudo update-grub and reboot
For systemd-boot:
Open a terminal or a TTY
Open /boot/loader/entries/manjarolinux5.10.conf in your favourite CLI editor (nano vi, emacs`)
Add amdgpu.dc=0 to the end of the line options
Save & reboot
For rEFInd:
Open a terminal or a TTY
Open /boot/refind_linux.conf in your favourite CLI editor (nano vi, emacs`)
Find the line: "Boot using default options" "root=
Add amdgpu.dc=0
Save & reboot
Possible 2 Min delay on shutdown with Gnome
Please click the â–ş at the beginning of this line to view more info
If you got the problem with shutdown delay (about 2min) on Gnome, here is a workaround:
Edit /usr/lib/systemd/user/gnome-session-restart-dbus.service in your favourite editor as root and add Slice=-.slice as a line all by itself like this:
You get [PKGNAME] warning: directory permissions differ on [Directory name]
followed by:
Filesystem: NNN package MMM
Please click the â–ş at the beginning of this line to view this solution
The solution:
sudo chmod MMM DirectoryName
Where obviously MMM is the second number you see (the correct one)
The explanation:
Your package expects the security permissions to be MMM but your system is set to NNN. This is just a warning (today) but to ensure you remain up-to-date with the latest and greatest security rules it’s advised to execute the above command.
Systemd error message: .slice: Failed to migrate controller cgroups
If you have a similar error message like this:
systemd[1004]: -.slice: Failed to migrate controller cgroups from /user.slice/user-1000.slice/user@1000.service, ignoring: Permission denied
… you may need to add this Grub parameter to your /etc/default/grub file in line GRUB_CMDLINE_LINUX_DEFAULT: systemd.unified_cgroup_hierarchy=true. To update your grub menu, call: sudo update-grub. For more information on that issue, see also Arch Forum.
Python 3.9 Requires Rebuilds
Instructions for quickly and easily rebuilding affected AUR packages:
# Install yay
sudo pacman -S --needed --noconfirm yay
# Rebuild AUR python packages
yay -S --noconfirm $(pacman -Qqo "/usr/lib/python3.8/site-packages")
The libtraceevent package prior to version 5.9-1 was missing a soname link. This has been fixed in 5.9-1, so the upgrade will need to overwrite the untracked files created by ldconfig. If you get any of these errors
libtraceevent: /usr/lib/libtraceevent.so.1 exists in filesystem
PAM and PAMBASE got updated, which might prevent you from login
Due to updates from pambase and pam you might take care about any .pacnew files in /etc/pam.d as for example pam_tally, pam_tally2 and pam_cracklib got deprecated. Read in the ArchWiki about managing those files.
Typical issue:
For recovery, it is enough to boot with kernel option “systemd.unit=rescue.target”, then proceed into /etc/pam.d and merge “system-auth” and “system-auth.pacnew”
System takes a long time to boot
If you’ve got errors like Failed to start Network Manager Wait Online. you can try removing systemd from passwd and group in /etc/nsswitch.conf as described here Update: If you can see the line dbus-daemon[1453]: [system] Connection has not authenticated soon enough, closing it (auth_timeout=30000ms, elapsed: 45146ms)
in in your dbus log ( journalctl -b -u dbus ), the new/better workaround is to switch cups from service to socket as described here: systemctl disable cups.service systemctl enable cups.socket
I think I’ve some font problems
With the update of fontconfig some major rules how fonts get applied changed. Make sure that your system has ttf-dejavu installed. A more in depth explanation can be found here.
Gnome-shell-extension-pop-shell is currently incompatible with wayland
… and causes the system to freeze when the first window is tiled and can render it unbootable. Solution is a hard reset and disabling either pop shell or wayland. If the system becomes unbootable, use a live USB to edit /etc/gdm/custom.conf to disable wayland and reboot.
Please RTFT (Read This Fine Thread) first before reporting the same issues over and over again!
I think the SigLevel = Required DatabaseOptional in the [options] section makes the four occurences of SigLevel = PackageRequired in the repository sections superfluous.
EDIT: Noticed additional package updates pushed to testing. Reverted to snapshot and retested - no more issue. Thank you
Original problem report
Ran into the following:
pamac:
$ sudo pamac update
[sudo] password for user:
Preparing...
Synchronizing package databases...
Resolving dependencies...
Warning: cannot resolve "libalpm.so>=13", a dependency of "libpamac"
Warning: cannot resolve "libpamac>=11.0", a dependency of "pamac-cli"
Warning: cannot resolve "libalpm.so>=13", a dependency of "libpamac"
Warning: cannot resolve "libalpm.so>=13", a dependency of "libpamac"
Warning: cannot resolve "libpamac>=11.0", a dependency of "pamac-cli"
Warning: cannot resolve "pamac-cli=10.1.3-3", a dependency of "pamac-gtk"
Warning: cannot resolve "libalpm.so>=13", a dependency of "libpamac"
Warning: cannot resolve "libpamac>=11.0", a dependency of "pamac-gtk"
Error: Failed to prepare transaction:
could not satisfy dependencies:
- unable to satisfy dependency 'libalpm.so>=13' required by libpamac
- unable to satisfy dependency 'libpamac>=11.0' required by pamac-cli
- unable to satisfy dependency 'pamac-cli=10.1.3-3' required by pamac-gtk
pacman:
$ sudo pacman -Syu
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
multilib is up to date
:: Starting full system upgrade...
:: Replace pamac-common with extra/libpamac? [Y/n] y
resolving dependencies...
warning: cannot resolve "libalpm.so>=13", a dependency of "libpamac"
warning: cannot resolve "libpamac>=11.0", a dependency of "pamac-cli"
warning: cannot resolve "libalpm.so>=13", a dependency of "libpamac"
warning: cannot resolve "libalpm.so>=13", a dependency of "libpamac"
warning: cannot resolve "libpamac>=11.0", a dependency of "pamac-cli"
warning: cannot resolve "pamac-cli=10.1.3-3", a dependency of "pamac-gtk"
warning: cannot resolve "libalpm.so>=13", a dependency of "libpamac"
warning: cannot resolve "libpamac>=11.0", a dependency of "pamac-gtk"
:: The following packages cannot be upgraded due to unresolvable dependencies:
pamac-cli libpamac pamac-gtk
:: Do you want to skip the above packages for this upgrade? [y/N] y
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: installing alsa-lib (1.2.5.1-3) breaks dependency 'alsa-lib=1.2.5' required by lib32-alsa-lib
In order to update at all, I had to remove quite a few packages (including all of pamac and manjaro-steam):
As for manjaro, after this update, everything is so far
in order. However, I have two bugs in KDE/Plasma.
bug: Discover shows an update in the taskbar even though
everything is up to date. So the same as in the last update with pamac.
2nd bug: The activation button of the energy saving mode is inverted.
When the button is activated, the energy saving mode is switched off. And vice versa.
If I have time, I will have a look at kde/plasma and report the bugs, if nobody has done it yet.
@XRaTiX
Yes, that’s what I mean. So no bug !
One wonders, why always these senseless changes ?
I have read your appendix, wherein the reason for the change is explained. So i can understand now .
But the description behind the button “Inhibit automatic sleep and screen locking”.
is not displayed for me at all. This may be due to the German display. Otherwise it would have been clearer.
yeah, though the former was already in the [options] that’s why I was wondering, how the latter was kept for so long Well I guess it deserved a… “clean up” .
I’m seeing a new graphical bug on Manjaro with (but perhaps not related to) KDE Plasma, particularly with my multi-monitor setup.
On the unlock screen (note, not the initial sign in, that’s fine.), both screens’ login displays are shoved up to the top of half one the leftmost display, on top of one another. This also only occurs after displays have already been automatically shut off (screen timeout, in other words). The placement of the login screens is similar to a bug I’ve always had where the initial splash screen for one of the monitors is placed too high and gets cut off.
For the record, my displays are different resolutions, with the leftmost one being 1080p and the right one being 1440p (I only have two). They are aligned in software such that their bottoms line up. So these issues definitely come from the computer trying to place the display(s) at the top left point of the Xorg screen (perhaps this is X11’s doing? I don’t really know, I still don’t fully understand exactly what is handled by the display server and what is handled by the window manager.)
I’m not very experienced with the forum, so if I messed up or need to provide more info, just let me know, I’m more than happy to do it.
Edit: I’m using Nvidia proprietary drivers, if it matters. Left display is HDMI, right is DP.
Edit 2: This was hidden. Perhaps I didn’t make it clear enough that the login thing happened directly as a result of this update. Or maybe I don’t understand what kind of bugs I’m supposed to report here. Either way, if this gets hidden again, I’d really appreciate an explanation if this gets hidden again so I can better participate in the future.
I have an RTX 260. When trying to load into a plasma Wayland session using the non-free driver, the login fails. Previously it would crash my device. So that is good! When trying to log in using the free driver, I can get to the desktop, but it freezes. The top 1/8th of my display was just a black bar even on x11 until I switched back to the non-free driver.
Well I guess it deserved a… “clean up” .