https://bugs.kde.org/show_bug.cgi?id=486699
Nate Graham changed:
What|Removed |Added
Version Fixed In||6.0.5
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=486699
--- Comment #12 from Nate Graham ---
Git commit 18adccdede9e659ce7a166787641f7a4d030b9f1 by Nate Graham.
Committed on 14/05/2024 at 18:52.
Pushed by ngraham into branch 'Plasma/6.0'.
kcm/fonts: use correct signal handlers for UI controls
Using the on[
https://bugs.kde.org/show_bug.cgi?id=486699
--- Comment #11 from Bug Janitor Service ---
A possibly relevant merge request was started @
https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/4321
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=486699
--- Comment #10 from Nate Graham ---
Git commit 6315e625c17227edf5b7b1e6b04fb70e8b384097 by Nate Graham.
Committed on 14/05/2024 at 18:35.
Pushed by ngraham into branch 'master'.
kcm/fonts: use correct signal handlers for UI controls
Using the on[Thin
https://bugs.kde.org/show_bug.cgi?id=486699
ratijas changed:
What|Removed |Added
CC||m...@ratijas.tk
--- Comment #9 from ratijas ---
Can'
https://bugs.kde.org/show_bug.cgi?id=486699
--- Comment #8 from Nate Graham ---
https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/4301 may fix
it. If you could test that, it would be lovely.
If you can't compile a patch locally, then even just changing the main.qml file
of the Font
https://bugs.kde.org/show_bug.cgi?id=486699
--- Comment #7 from littlefroggie...@gmail.com ---
(In reply to Nate Graham from comment #6)
> Do you have the ability to test a patch? I see an issue in the code that
> *may* explain this, but I can't be sure because I can't reproduce the issue
> myself
https://bugs.kde.org/show_bug.cgi?id=486699
--- Comment #6 from Nate Graham ---
Do you have the ability to test a patch? I see an issue in the code that *may*
explain this, but I can't be sure because I can't reproduce the issue myself.
--
You are receiving this mail because:
You are watching a
https://bugs.kde.org/show_bug.cgi?id=486699
--- Comment #5 from littlefroggie...@gmail.com ---
If I'm gonna guess it's just not reading the actual setting at all and showing
the checkbox as checked in the UI because for some reason that's the UI code's
(undefined) behavior when failing to read the
https://bugs.kde.org/show_bug.cgi?id=486699
--- Comment #4 from littlefroggie...@gmail.com ---
(In reply to Nate Graham from comment #3)
> That's unexpected. What happens when you click the "Defaults" button at the
> bottom of the page?
Clears the checkbox, this part is expected. And it enables t
https://bugs.kde.org/show_bug.cgi?id=486699
--- Comment #3 from Nate Graham ---
That's unexpected. What happens when you click the "Defaults" button at the
bottom of the page?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=486699
--- Comment #2 from littlefroggie...@gmail.com ---
(In reply to Nate Graham from comment #1)
> Are you saying that for you, when you first opened the Fonts page, the
> checkbox next to "Exclude fonts from anti-aliasing" was already checked?
> Because tha
https://bugs.kde.org/show_bug.cgi?id=486699
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org
Status|REPORTED
13 matches
Mail list logo
