https://bugs.kde.org/show_bug.cgi?id=425403
Patrick Silva changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=425403
Patrick Silva changed:
What|Removed |Added
Resolution|FIXED |---
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=425403
Nate Graham changed:
What|Removed |Added
Version Fixed In||5.23
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=425403
Aleix Pol changed:
What|Removed |Added
Latest Commit||https://invent.kde.org/plas
|
https://bugs.kde.org/show_bug.cgi?id=425403
Bug Janitor Service changed:
What|Removed |Added
Status|CONFIRMED |ASSIGNED
--- Comment #16 from Bug
https://bugs.kde.org/show_bug.cgi?id=425403
--- Comment #15 from Aleix Pol ---
Turns out I was quite wrong in my assessment.
On the bright side, it's fixed with the following MR.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=425403
--- Comment #14 from Nate Graham ---
Yeah that would probably be fine. KCMs opened in KCMshell are rare now anyway.
Hence the "LO minor" importance level, I guess. :)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=425403
--- Comment #13 from Aleix Pol ---
Feels like a big detour. As a general rule, kcms are opened with system
settings and we don't have a problem with that.
In fact, why is this not a problem for systemsettings? Would showing the
systemsettings icons
https://bugs.kde.org/show_bug.cgi?id=425403
--- Comment #12 from Nate Graham ---
Is there a good reason not to? I guess if we did that they would show up in
Kickoff etc, so maybe that's the reason. Is there a "hidden" flag or something
we could set to make that not happen, yet still let them be
https://bugs.kde.org/show_bug.cgi?id=425403
--- Comment #11 from Nicolas Fella ---
Those are not installed into /usr/share/applications though
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=425403
--- Comment #10 from Nate Graham ---
Don't KCMs already have .desktop files?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=425403
--- Comment #9 from Aleix Pol ---
we could have kcms install themselves as applications, then kwin would find it
I guess?
The way KWin figures out the icon is by getting a desktop file (e.g.
"firefox.desktop") then looking it up and using the Icon
https://bugs.kde.org/show_bug.cgi?id=425403
--- Comment #8 from Nate Graham ---
I believe you, but it kind of boggles my mind that such a thing is unfixable by
design. It would seem to point to a faulty design somewhere...
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=425403
--- Comment #7 from Aleix Pol ---
Well, the short answer (besides "no") is "it's not fixable under xdg-shell", as
what we use to display the icon is the desktop file.
Well we could make it show a random icon, surely not the kcm's.
--
You are
https://bugs.kde.org/show_bug.cgi?id=425403
--- Comment #6 from Nate Graham ---
It's not realistic to make QDialog::setWindowIcon() work on Wayland?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=425403
--- Comment #5 from Aleix Pol ---
Just don't use kcmshell5.
>From Plasma 5.23 there's plasma-open-settings which will launch system settings
(or plasma-settings if that's what you have) that works better on many levels.
This issue isn't realistically
https://bugs.kde.org/show_bug.cgi?id=425403
Nate Graham changed:
What|Removed |Added
Assignee|plasma-b...@kde.org |aleix...@kde.org
Component|general
17 matches
Mail list logo
