| Summary: | Anti-aliasing setting not written to /etc/sddm.conf.d/kde_settings.conf during a sync | ||
|---|---|---|---|
| Product: | [Applications] systemsettings | Reporter: | Lua <lv215bd5> |
| Component: | kcm_sddm | Assignee: | David Edmundson <kde> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | filipfila.kde, kde, nate, plasma-bugs-null |
| Priority: | NOR | ||
| Version First Reported In: | 5.22.0 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
Font aliasing
Font aliasing 2nd picture |
||
|
Description
Lua
2021-06-06 18:29:05 UTC
Created attachment 139042 [details]
Font aliasing
This gets synced by the settings synchronization feature in the SDDM KCM. You need to use that to get the login screen to use the settings from your user account. Created attachment 139170 [details]
Font aliasing 2nd picture
Unfortunately that didn't work. I even rebooted the system, but nothing.
Can you please paste the contents of /etc/sddm.conf.d/kde_settings.conf? This file doesn't exist: $ cat /etc/sddm.conf.d/kde_settings.conf cat: /etc/sddm.conf.d/kde_settings.conf: No such file or directory That means either you didn't sync the settings, or the sync didn't work. Can you confirm whether you did the sync in the SDDM page? Yes, I synchronized the settings more than one time. Ok, I tried one more time and now the sync happened, but the aliasing is still the same. [General] Numlock=on [Theme] CursorTheme=breeze_cursors Font=Noto Sans,10,-1,0,50,0,0,0,0,0 Lua, you seem to be talking about the lock screen and not the login screen. SDDM and its KCM handle the login screen. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |