Just “moved” changes inside Meld from left to right, saved updated original file and afterwards .pacnew got automatically removed (I did it through Pacdiff & Meld provided by Welcome app)
1 Like
Will be my approach as well. 
If you are having issues running Wyaland with an Nvidia GPU, check to make sure you have all the needed settings for Wayland.
- In the
/etc/environmentfile:
a. For Systems with just an Nvidia Card:
#
# This file is parsed by pam_env module
#
# Syntax: simple "KEY=VAL" pairs on separate lines
#
#This is so QT applications run properly
QT_QPA_PLATFORMTHEME="wayland;xcb"
# This is here to make nvidia play nice. Open Source your drivers.
QT_QPA_PLATFORMTHEME="wayland;xcb"
GBM_BACKEND=nvidia-drm
__GLX_VENDOR_LIBRARY_NAME=nvidia
ENABLE_VKBASALT=1
LIBVA_DRIVER_NAME=nvidia
# just in case you loose the hardware cursor
WLR_NO_HARDWARE_CURSORS=1
b. If you have an Optimus Laptop
#
# This file is parsed by pam_env module
#
# Syntax: simple "KEY=VAL" pairs on separate lines
#
#This is so QT applications run properly
QT_QPA_PLATFORMTHEME="wayland;xcb"
# This is here to make nvidia play nice. Open Source your drivers.
GBM_BACKEND=nvidia-drm
DRI_PRIME=pci-0000_01_00_0
__VK_LAYER_NV_optimus=NVIDIA_only
__GLX_VENDOR_LIBRARY_NAME=nvidia
ENABLE_VKBASALT=1
LIBVA_DRIVER_NAME=nvidia
__NV_PRIME_RENDER_OFFLOAD=1
# just in case you loose the hardware cursor
WLR_NO_HARDWARE_CURSORS=1
- Make sure you have the proper Modules being loaded in either
mkinitcpio.confor your drop in file indracut.conf.d
nvidia nvidia_modeset nvidia_uvm nvidia_drm
- Finally, make sure you have the Direct Render Manager (DRM) set to use Nvidia. In
/etc/default/grubmake sure you have the following in theGRUB_CMDLINE_LINUX_DEFAULT=line.
nvidia-drm.modeset=1
Using the above settings, I have not had any issues running Wayland with the Nvidia Optimus setup on my Laptop. If after trying out Wayland using your Nvidia card, you want to go back to using X11, you do not need to remove these settings. X11 will ignore them because it uses a different set of configuration files. I have successfully gone back and forth between X11 and Wayland without any issues.
4 Likes
Okay, so I used this and ended up with a few issues. Oddly, prior to running this, all of my existing themes, settings, etc. worked fine after updating to Plasma 6. After running that, it all went downhill and I’ve spent the past 90 minutes trying to fix it (when I really should be working 
)!!
I think I have most of it repaired now 
but have a few issues.
SDDM is telling me that
org.kde.plasma.core
org.kde.plasma.extras
org.kde.plasma.components
are not installed. I’ve done a little searching around and cannot figure out how to get them back. I’ve manually reinstalled plasma-desktop plasma-meta libplasma and they’re still missing.
I also created a new user and still the same problem.
Any thoughts or recommendations?
1 Like
If you use meta packages, you need to be really careful when removing orphans. For example, removing plasma-meta and then removing orphans will remove the entirety of plasma.
What sddm theme are you using?
1 Like
I’m using Breeze at the moment.
As far as I can tell, I never uninstalled plasma-meta with the orphan removal. Regardless, I have reinstalled it.
Any other thoughts?
For what it’s worth I think I figured it out. Thankfully, it had nothing to do with removing the orphans.
Through some searching, I discovered that a custom theme I’d been using was incorrectly ported to Plasma 6 that was searching for outdated libraries, prior to those that I listed above were moved to libplasma.
From what I figured out, I made a stupid copy/pasta and created some issues with my Breeze sddm directory. After forcing a reinstall of that, it’s all fine. In the meantime, I found a custom sddm theme that was correctly ported.