My guess is that it has something to do with plasma 6.4.X only having a wayland session unless the x11 user’s also know to install the x11 session package as well. It was mentioned somewhere that this transition was going to mark a release/iso.
Looks like plasma 6.4 is only in unstable (Branch compare for Manjaro), so you could swap branches to get those packages faster and assist with bug finding for the rest of us patient Stable users.
Well Plasma 6.0 already defaulted to Wayland.
Well 6.4.5 will be released in September according to KDE
But seriously Philip answered this question in a different thread
Hmm, seems people with Nvidia drivers have a problem. Which kernel series are used and possible affected?
I have 6.12, I had the latest patch version before update.
I have the same issue mentioned by @Krevetochka, though some messages are different, but I don’t think they are related to this issue.
I can log in to tty, so the boot seems correct. As the previous cases @angel and @Krevetochka
yeah, I also used the 6.12 kernel from manjaro when the update failed
Seems nvidia-open packages for linux612, and linux612-rt were not rebuilt. Now updated.
Does that mean that we have to update again using sudo pacman -Syu?
it says nvidia-open, it doesn’t apply to propietary drivers right?
Simply check the list. Normally each kernel series needs an update of nvidia and nvidia-open packages. For 6.12 series we missed the open ones.
Well, I updated and it told that it was changing such package. The Pc is working now and boots directly to the sddm.
Thanks for the help.
Ah I see, I totally missed this. Thanks for the heads up and the link. 
Hi everybody,
Old nvidia card (GForce GT 620 with open-source driver). Plasma desktop.
Problem with wayland and kernel 6.16 or 6.12. Boot is okay but my PC freezes after entering password at the connexion screen (graphical interface is reached). Keyboard and mouse are inactive and I cannot access to a tty.
Seems to be a problem with wayland and recent kernels because it works with X11.
Kernel 6.1 boots fine with either wayland or X11.
Thanks for help.
Updated without any problems using kernel 6.17.0-rc3 with intel meteor lake processor. Everything seems to be working fine.
I voted no issues but it seems like I have some brief network drops. A site can’t be reached or something stops loading but on refresh it works again.
I didn’t have this problem before upgrade so I will assume it is related.
Update went fine, but virtualbox GUI core dumps, see also: https://bbs.archlinux.org/viewtopic.php?id=307652
Every kernel version that is still maintained seems to be affected by network connection drops including LTS version. So once you upgrade there is nowhere to fall back. My laptop has this network instability problem. That’s why I ignored kernel packages in my desktop.
Added
IgnorePkg = linux616 linux616-headers
to /etc/pacman.conf for now until fixed kernel versions are out.
6.16.1 is reported to be last stable kernel.
Stable kernels and also LTS kernels get patches backported from the development kernels. So if you face any problem, please try the RC kernels, which is the 6.17 series currently @karmux, as those might ship fixes like net: ipv4: fix regression in local-broadcast routes already… Also tell us which exact network chipset you are using, so we can look for reported regressions.
I’m eagerly awaiting the upgrade to plasma 6.4. Since the last plasma update (a few stable updates ago) sleep has been totally broken on my machine. I had to mask plasma-powerdevil.service. Apparently the underlying bug is fixed in Plasma 6.4 but I don’t want to deal with the potential instability of unstable. For now I just don’t have sleep on my machine.
My card is Intel Wi-Fi 6 AX201, I don’t know how to find exact chipset, I will try RC kernel and see if it makes a difference
Same network problem with
inxi -Fxxxrz
Network:
Device-1: Intel Ethernet I219-V vendor: ASUSTeK driver: e1000e v: kernel
port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15b8 class-ID: 0200
IF: enp0s31f6 state: up speed: 1000 Mbps duplex: full mac: <filter>
I’ve gone back to Linux 6.6.102 which seems to be still free of that regression (backported to .103).
I don’t know if it was intended to let it lag one bugfix behind 6.12, but it was a good thing.
6.17 RC did not help with the network problem, but 6.6.102 as @Marsa suggested seems to work
Network:
Device-1: Intel Wi-Fi 6 AX201 driver: iwlwifi v: kernel bus-ID: 00:14.3
chip-ID: 8086:a0f0 class-ID: 0280
IF: wlp0s20f3 state: up mac: <filter>