KDE Developers Prepare For Christmas With More Bug Fixes & Qt 6 Porting

[phoronix]

Phoronix: KDE Developers Prepare For Christmas With More Bug Fixes & Qt 6 Porting

This week brought the second beta of KDE Plasma 6.0 along with KDE Gear and KDE Frameworks updates too. The holidays haven't resulted in KDE development slowing down too much with still a number of bug fixes being merged this week and other minor enhancements...

https://www.phoronix.com/news/KDE-Bug-Fixes-For-Christmas

[cl333r]

I imagine they don't fix Plasma 5 Wayland bugs anymore, e.g. firefox from a .tar.gz release has no icon, whereas on X11 the firefox icon is present. It seems anything that is not packaged has no icon (bears the wayland icon instead).

(Fedora 39)

[archkde]

I imagine they don't fix Plasma 5 Wayland bugs anymore, e.g. firefox from a .tar.gz release has no icon, whereas on X11 the firefox icon is present. It seems anything that is not packaged has no icon (bears the wayland icon instead).

(Fedora 39)

Fix your .desktop file and it will have the proper icon again.

[cl333r]

Fix your .desktop file and it will have the proper icon again.

What to fix? And why under X11 it works "unfixed"? Not to mention as I wrote previously I'm running a .tar.gz, there's no desktop file to begin with.

[eszlari]

What to fix? And why under X11 it works "unfixed"? Not to mention as I wrote previously I'm running a .tar.gz, there's no desktop file to begin with.

You can use the menu editor (kmenuedit) that comes with Plasma to create a desktop file.

[ssokolow]

What to fix? And why under X11 it works "unfixed"? Not to mention as I wrote previously I'm running a .tar.gz, there's no desktop file to begin with.

Under X11, Windows, and macOS, there's an API to allow an application to set its own icon at runtime. For Wayland, the icons come from the compositor looking for a matching installed .desktop file and there's currently an ongoing dispute over whether it's legitimate for applications to want to set their icons any other way and it's unclear how many compositors will be willing to implement the protocol extension for doing so if it gets accepted.

The claim is that the .desktop approach is to prevent phishing by putting icon-selection somewhere sandboxed applications can't alter it, which is LOL given that GNOME insists on everything using CSD where they can draw whatever the *honk* they want in their titlebars.

[cl333r]

.

That's a better answer than I ever expected, thanks.

[mrg666]

That's a better answer than I ever expected, thanks.

Do you have anything real to add now that you have been educated a bit?

[cl333r]

Do you have anything real to add now that you have been educated a bit?

Yes. Of course. Please hold your hand.

[Volta]

The claim is that the .desktop approach is to prevent phishing by putting icon-selection somewhere sandboxed applications can't alter it, which is LOL given that GNOME insists on everything using CSD where they can draw whatever the *honk* they want in their titlebars.

Sandboxed applications or third party ones? Are you claiming apps want to phish themselves?