Some Nvidia cards donât work with the current 460.80 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.
GDM does not start (black screen when booting gnome edition)
Log into your system via tty and depending on your use of Plymouth or bootsplash-systemd choose a option from this post
Update seems o.k. - no error messages, reboot⊠then blackscreen.
Try to boot older kernel, same issue. Terminal session with Ctrl-Alt-F2 not possible⊠black is black
Next I will try to go back with livestick and timeshift - hopefully - it is first time for me.
Perhaps NVIDIA error (GTX 1080)?
System 2 with AMD-GPU (Ryzen 4650G) update seems without problems (nearly same config and apps).
Michael
Oh, I see @philm above⊠4k not mine, but 3840x1600 and DP. Perhaps here is Screen-Output on HDMI?
What is to do?
Hi there.
When trying to update via the GUI I got an error message about conflicting files.
plasma-workspace: /usr/share/locale/ta/LC_MESSAGES/kcm_autostart.mo already exists in filesystem (owned by plasma-desktop-primex)
I found a post from three days ago where someone on the testing branch had the same error and it seemed to have been resolved by replacing plasma-desktop-primex with regular plasma-desktop so thatâs what I tried.
Iâm quite new to this whole Linux thing so Iâm probably missing something but a few issues come up that I canât seem to find solutions for.
After updating it prompts me to reboot, but when I try to do so the screen blurs out and nothing more happens. I ended up opening up Yakuake and entering âshutdown nowâ.
After starting up the computer again, my plasma seems to be broken. No desktop background (just completely black and canât right click on it). No task bar or start menu. alt+ space doesnât work yet if I move my mouse to the top left corner of the screen I get the activity switcher as usual. I have restored my previous system twice via Timeshift and tried the update again but with no different result.
Any suggestions or help would be very appreciated.
And so, I tried updating as random crashes in AMD still persist, but when opening Pamac no update was available yet. I refreshed the database, and nothing. Finally I shut down the computer and there seems to be a regression (at least in GNOME), because the system took a good few minutes to shut down (which had not happened in a while).
Due to these problems, I no longer use my laptop as much as I used to, because I spend more time here in the forums than in my actual system. When activating automatic updates in Pamac, are they applied alone, or are they simply downloaded? Since now I am tired to check which version I am in and I do not know if this error is from now, although it had not happened to me since I manually updated the last stable update. I will hope this stabilizes soon.
System seems functional after restore last snapshot with timeshift - but timeshift shows that errors occurs - error message
âIf system not boots, try another snapshotâ⊠mmh, it boots⊠I wait and lookâŠ
but @philm, what is the right way, if the prop. driver are needed and why is such a shit in stable?
The last working Nvidia driver with Display Port support was 460.73.01. Then a new version came out, which backports stuff from 465 series. Current 460.80. Seems like the âfixesâ for some Display Port issues created a regression. People with issues on the Nvidia driver may report to Nvidia with some constructive feedback and step by step guides so they can reproduce it.
I encountered this error: [ 78%] Linking CXX shared library ../bin/libKF5GuiAddons.so [ 78%] Built target KF5GuiAddons make: *** [Makefile:136: all] Error 2 ==> ERROR: A failure occurred in build(). Aborting... error making: kguiaddons-git
Trying to switch to extra/kguiaddons results in: looking for conflicting packages... kguiaddons and kguiaddons-git are in conflict. Remove kguiaddons-git? [y/N] y error: failed to prepare transaction (could not satisfy dependencies) removing kguiaddons-git breaks dependency 'kguiaddons-git' required by kconfigwidgets-git
Same story if I try to replace kconfigwidgets-git with extra/kconfigwidgets, which leads to: removing kconfigwidgets-git breaks dependency 'kconfigwidgets-git' required by kiconthemes-git;
which in turn leads to: removing kiconthemes-git breaks dependency 'kiconthemes-git' required by ktextwidgets-git :: removing kiconthemes-git breaks dependency 'kiconthemes-git' required by kwallet-git
This results in having no panel, no window borders, no desktop, no icons anywhere. Iâm not sure what to try next.
Seems youâre having some KDE-git packages for some reason. We dropped them as we have [kde-unstable] repo. You might want to scan your install and replace them with regular packages @jdcard
