| Summary: | Global scale 100% large icons and fonts | ||
|---|---|---|---|
| Product: | [Plasma] KScreen | Reporter: | gareginra |
| Component: | common | Assignee: | kscreen-bugs-null <kscreen-bugs-null> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | normal | CC: | kde, nate, uhhadd |
| Priority: | NOR | ||
| Version First Reported In: | 5.26.5 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
Screenshot of 100% Global scale
kdeglobals |
||
|
Description
gareginra
2023-01-08 23:39:31 UTC
And are you using X11 or Wayland? Have you manually changed the "Force Font DPI" setting"? Can you attach a screenshot that shows the problem after going to 100% scale and rebooting? Created attachment 155171 [details]
Screenshot of 100% Global scale
I am using X11. The 'Force font DPI' changes automatically with scaling, otherwise it is default.
How bizarre. Can you attach your ~/.config/kdeglobals file? Created attachment 155201 [details]
kdeglobals
So, I checked it out as well. Apparently, what happens when I change Global scale to 100% is 'ScaleFactor' line (182) gets deleted. However, I tried setting it manually to 1 and it worked fine. No large icons, everything is perfect (at least at first glance). Before that I tried it only through System Settings.
Interesting. I wonder if you have a kdeglobals file elsewhere with a bad ScaleFactor line in it that the system is falling back to when you remove your local override for that line.
Can you paste the output of:
sudo find / -type f -name kdeglobals -exec grep -H 'ScaleFactor=' {} \;
(In reply to Nate Graham from comment #5) > Interesting. I wonder if you have a kdeglobals file elsewhere with a bad > ScaleFactor line in it that the system is falling back to when you remove > your local override for that line. > > Can you paste the output of: > > sudo find / -type f -name kdeglobals -exec grep -H 'ScaleFactor=' {} \; With all settings I've used it shows this. If there was no ScaleFactor in kdeglobals, that line would be absent in the result. find: ‘/run/user/1000/gvfs’: Permission denied /home/*username*/.config/kdeglobals:ScaleFactor=1 find: ‘/proc/617/net’: Invalid argument find: ‘/proc/618/task/618/net’: Invalid argument find: ‘/proc/618/net’: Invalid argument find: ‘/proc/619/task/619/net’: Invalid argument find: ‘/proc/619/net’: Invalid argument find: ‘/proc/620/task/620/net’: Invalid argument find: ‘/proc/620/net’: Invalid argument Well I'm awfully confused then. Thanks for checking. Any ideas, David? Another thing worthy of mentioning, my Xorg starts after login. Before this bug I had a problem where my desktop wouldn't load properly on start. I was greeted with a black screen and could only launch anything via Alt+F2, but I could fix it by applying the Global Theme again in System Settings every time. It was annoying, but I don't reboot that much. Also, some windows would freeze after excessive use, which I believe had to do with that bug. Then it got fixed with an update, and I believe for a while everything was alright. There was some sound driver problem earlier, but my friend helped me fix that. All bugs appeared after and due to updates. Oh, this is probably the problem. On X11, scaling changes aren't live; the app needs to be restarted after it's changed. If Xorg is starting after the scaling environment variables get set, this is not gonna work properly, yeah. I would recommend debugging whatever is causing Xorg to launch too late. Perhaps ask Arch folks for help. |