Any news on 6.2.4

[dth2]

Any news on KDE Plasma 6.0.4?

[Antonio_Marra]

I suppose you mean “Kde Plasma Desktop 6.2.4”.
6.2.4 was out on 26 November, but it isn’t available to upgrade on Kde Neon since now.
https://kde.org/it/announcements/plasma/6/6.2.4/
Are there problems with the update?

[dth2]

Sorry, yes I meant KDE Plasma 6.2.4

[happycthulhu]

I think with 6.2.2 there was a bit of a delay as well. It might be that the packages are just taking time to get together as peoples lives are a bit busier this time of year?

[moschlegbz]

Fedora 41 updated to KDE 6.2.4 back on Nov 27th so that’s at least one distro where you could try it

[Antonio_Marra]

I’m on KDE Neon 24.04, so I’m waiting for every minor release of Plasma to solve several little bug.
KDE Neon is usually fast to integrate new releases of Plasma, but strangely this time it has not.
Kudos to all the KDE Developers, the greatest desktop experience on Linux, in my own opinion.

[happycthulhu]

Well looks like it’s update time folks!

[jivask]

Most noticeable change is, that firefox does not use any more breeze cursor and menu fonts are also smaller than in plasma applications…

[happycthulhu]

Odd. I’m not seeing that at all. Firefox looks the same to me as it always has.

[jivask]

X11 or Wayland? I’m on Wayland. And only Firefox, for example Thunderbird is OK. Also the neon-user-20241210-2052.iso-s Firefox has the same problem.
Edit: Just tested in plasma-X11 - there is OK. So the problem is related to Firefox&Wayland…
Edit1: And you can’t blame Firefox, as the same Firefox version used system theme OK when in Plasma 6.2.3 or when booted the previous user iso: neon-user-20241201-0744.iso

[claydoh]

Well, we did get a new FF and kernel, as well as some Mesa driver updates, along with the new Plasma and Qt…

[jivask]

Kernel and Mesa updates came after the problem appeared. Probably the FF update came unnoticed for me then. I tried the FF from Mozillateam ppa (from November 27th) and it also suffered the same problem.

[Haley]

@Antonio_Marra

Are there problems with the update?

I definitely have issues with this update. Wayland session does not come up. Crashes straight. Have to fall back to an X-Session.

KDE Plasma Version: 6.2.4
KDE Frameworks Version: 6.8.0
Qt Version: 6.8.1
Kernel Version: 6.8.0-50-generic (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 7 7840HS w/ Radeon 780M Graphics
Memory: 54,7 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: Framework
Product Name: Laptop 16 (AMD Ryzen 7040 Series)
System Version: AG

[Antonio_Marra]

Yes, the update is finally here, but I’m in trouble as you.
Plasma session doesn’t come up after login, returning to the login screen.
X11 session comes up fine.
I’m also on AMD CPU (2600X) and AMD GPU (R480).
I cant’ found any solution up to now.

Have someone else the same problem and resolved it?

[jivask]

Thanks to guss77 for an idea what to try. Downgrading xdg-desktop-portal to 1.18.4-1 fixes the FF wrong cursor&font issue.

[happycthulhu]

Yeah it appears that I’m having issues as well with Wayland but X seems to be fine. I’m on an AMD CPU (3800x) and an Nvidia GTX 1060.

[uc5z9]

Does this fix cursor and font issues in other programs as well? LibreOffice and Logseq are having issues for me.

Some others with libreoffice as well:

Fonts in Libreoffice not displaying Normally

After doing some system updates today I’m finding on opening existing libre-office files they have a strange “fuzzy” appearance. Both the menu bar text and the document text is affected. On further checking it appears to apply to apply to all libre office programs, writer, calc, base etc. The only other application I have installed that is also affected is “home bank” The calc files were displaying “normally” on Sunday and the home bank file was fine yesterday. I’m pretty certain neither l…

[Haley]

@jivask

Thanks to [guss77] for an idea what to try. Downgrading xdg-desktop-portal to 1.18.4-1 fixes the FF wrong cursor&font issue.

Didn’t work here. Wayland session still does not come up.
Got loads of drkonqi messages showing up. Here a partial output, as too long.

déc. 12 09:51:55 jupiter systemd[21015]: drkonqi-coredump-launcher.socket: Too many incoming connections (16), dropping connection.
déc. 12 09:51:55 jupiter systemd[21015]: drkonqi-coredump-launcher.socket: Too many incoming connections (16), dropping connection.
déc. 12 09:51:55 jupiter systemd[21015]: drkonqi-coredump-launcher.socket: Too many incoming connections (16), dropping connection.
déc. 12 09:51:55 jupiter systemd[21015]: drkonqi-coredump-launcher.socket: Too many incoming connections (16), dropping connection.
déc. 12 09:51:55 jupiter systemd[21015]: drkonqi-coredump-launcher.socket: Too many incoming connections (16), dropping connection.
déc. 12 09:51:55 jupiter systemd[21015]: drkonqi-coredump-launcher.socket: Too many incoming connections (16), dropping connection.
déc. 12 09:51:55 jupiter systemd[21015]: drkonqi-coredump-launcher.socket: Too many incoming connections (16), dropping connection.
déc. 12 09:51:55 jupiter systemd[21015]: drkonqi-coredump-launcher.socket: Too many incoming connections (16), dropping connection.
déc. 12 09:51:55 jupiter systemd[21015]: drkonqi-coredump-launcher.socket: Too many incoming connections (16), dropping connection.
déc. 12 09:51:55 jupiter systemd[21015]: drkonqi-coredump-launcher.socket: Too many incoming connections (16), dropping connection.
déc. 12 09:51:55 jupiter systemd[21015]: drkonqi-coredump-launcher.socket: Too many incoming connections (16), dropping connection.
déc. 12 09:51:55 jupiter systemd[21015]: drkonqi-coredump-launcher.socket: Too many incoming connections (16), dropping connection.
déc. 12 09:51:53 jupiter dbus-daemon[21040]: [session uid=1000 pid=21040] Activated service 'org.kde.KSplash' failed: Process org.kde.KSplash exited with status 1
déc. 12 09:51:53 jupiter plasma_waitforname[21700]: org.kde.plasma.waitforname: WaitForName: Service was not registered within timeout
déc. 12 09:51:53 jupiter sudo[23279]: pam_unix(sudo:session): session closed for user root
déc. 12 09:51:53 jupiter drkonqi-coredump-launcher[23865]: Unable to find file for pid 3672 expected at "kcrash-metadata/baloo_file_extractor.6504e808bb184392aa10bfcfd356893d.3672.ini"
déc. 12 09:51:53 jupiter drkonqi-coredump-launcher[23862]: Unable to find file for pid 3627 expected at "kcrash-metadata/baloo_file_extractor.6504e808bb184392aa10bfcfd356893d.3627.ini"
déc. 12 09:51:53 jupiter drkonqi-coredump-launcher[23863]: Unable to find file for pid 3658 expected at "kcrash-metadata/baloo_file_extractor.6504e808bb184392aa10bfcfd356893d.3658.ini"
déc. 12 09:51:53 jupiter drkonqi-coredump-launcher[23859]: Unable to find file for pid 3611 expected at "kcrash-metadata/baloo_file_extractor.6504e808bb184392aa10bfcfd356893d.3611.ini"
déc. 12 09:51:53 jupiter drkonqi-coredump-launcher[23857]: Unable to find file for pid 3593 expected at "kcrash-metadata/baloo_file_extractor.6504e808bb184392aa10bfcfd356893d.3593.ini"
déc. 12 09:51:53 jupiter drkonqi-coredump-launcher[23856]: Unable to find file for pid 3578 expected at "kcrash-metadata/baloo_file_extractor.6504e808bb184392aa10bfcfd356893d.3578.ini"
déc. 12 09:51:53 jupiter drkonqi-coredump-launcher[23855]: Unable to find file for pid 3547 expected at "kcrash-metadata/baloo_file_extractor.6504e808bb184392aa10bfcfd356893d.3547.ini"
déc. 12 09:51:53 jupiter drkonqi-coredump-launcher[23854]: Unable to find file for pid 3531 expected at "kcrash-metadata/baloo_file_extractor.6504e808bb184392aa10bfcfd356893d.3531.ini"
déc. 12 09:51:53 jupiter systemd[21015]: Started drkonqi-coredump-launcher@31-21352-1000.service - Launch DrKonqi for a systemd-coredump crash (PID 21352/UID 1000).
déc. 12 09:51:53 jupiter drkonqi-coredump-launcher[23853]: Unable to find file for pid 3507 expected at "kcrash-metadata/baloo_file_extractor.6504e808bb184392aa10bfcfd356893d.3507.ini"
déc. 12 09:51:53 jupiter systemd[21015]: Started drkonqi-coredump-launcher@30-21352-1000.service - Launch DrKonqi for a systemd-coredump crash (PID 21352/UID 1000).
déc. 12 09:51:53 jupiter drkonqi-coredump-launcher[23851]: Unable to find file for pid 3491 expected at "kcrash-metadata/baloo_file_extractor.6504e808bb184392aa10bfcfd356893d.3491.ini"
déc. 12 09:51:53 jupiter systemd[21015]: Started drkonqi-coredump-launcher@29-21352-1000.service - Launch DrKonqi for a systemd-coredump crash (PID 21352/UID 1000).
déc. 12 09:51:53 jupiter drkonqi-coredump-launcher[23850]: Unable to find file for pid 3467 expected at "kcrash-metadata/baloo_file_extractor.6504e808bb184392aa10bfcfd356893d.3467.ini"

[jivask]

Did not notice anything wrong in Libreoffice, only Firefox had issues. I use libreoffice-plasma integration package.

[Antonio_Marra]

Very little update about Wayland crashing on login.

• I’ve tried, on the machine that doesn’t work after the update, to boot the latest Neon live iso image, containing Plasma 6.2.4, it works well (Wayland session, amdgpu);
• I’ve updated a Lenovo X380 Yoga Kde Neon install to Plasma 6.2.4 (Intel integrated GPU), it works well in Wayland after the update;
• I’ve updated a Dell XPS15 9500 with mixed Intel/Nvidia GPU KDE Neon to Plasma 6.2.4, it works well in Wayland after the update.

So I can suppose that the only machine that doesn’t work after the Plasma 6.2.4 update should have some “scares” due to some software installation or configuration editing, but I cannot determine which or why.
I’ve also installed all the updates submitted in the meanway, but without solving the problem: it works only on X11.
Any ideas?