Was this really an “update”? Check any of several other threads as to why this is inappropriate and tend to break things.
If you actually performed a “sudo zypper dist-upgrade”, then make sure that you are only using openSUSE signed tumbleweed/repo/oss and non-oss repositories. The only reliable alien repository is Packman.
The only unusual thing about this update was that an earlier update a couple of months ago completely messed up WiFi; I couldn’t connect to anything, so I backed out the whole update. I didn’t get to do another update until a few days ago.
Please use the code Tags (the # icon above the forum edit pane) to display commands and their output.
Repositories #1 and #3 seem to be duplicates, and are mostly redundant nowadays.
I would change the Workspace Themes and Application Style settings. The artwork changed recently, and I found some configurations that were not working properly responde to being changed, applied, and changed back again.
I’ve spent a while hunting around the themes and settings for anything that might affect this. Also, I mentioned in my original post that I created a new user to check the default set-up and that also gets the huge fonts and borders - so I suspect it’s not a simple personal configuration issue.
If I could find where these values are set, I could probably fix this but I haven’t been able to.
This is how sddm.conf looks now: (blank lines removed)
# Cursor theme used in the greeter
# Current theme name
# The lowest virtual terminal number that will be used.
# Path to a script to execute when starting the display server
The X11 section didn’t exist before I just added it.
This update has fixed the logon screen which I hadn’t mentioned before but which was also presented in very large text. Nothing else seems to have improved.
XFCE? LXQT? E2? Plasma? Mate? Cinnamon? More than one?
xrdb -query | grep dpi
returned blank? Sometimes it’s expected, sometimes it’s not. In your case, returning blank might be part of the problem. If Plasma, you can make it 96 or 120 in systemsettings (personal settings/configure desktop) > fonts > force fonts dpi. In other DEs, Xft.dpi, which xrdb tested for, can be set directly in ~/.Xresources, e.g.:
What size is your 1920x1080 screen?
If Firefox or Thunderbird are the primary complaint, Xft.dpi might do what you want, or you might need or want to use one of their hidden preferences that can be changed in about:config, layout.css.devPixelsPerPx most likely. It defaults IIRC to -1.0. You might want 1.0, 1.1, 1.25 or possibly more.
Sorry. I didn’t understand the question. It’s Plasma
xrdb -query | grep dpi
returned blank? Sometimes it’s expected, sometimes it’s not. In your case, returning blank might be part of the problem. If Plasma, you can make it 96 or 120 in systemsettings (personal settings/configure desktop) > fonts > force fonts dpi.
That’s cracked it!
Forcing fonts dpi to 96 has restored sanity to my desktop. Many thanks.
I looked at this a few times while trying to fix this and it was already set to 96dpi but when I went there just now it was unset. Very bizarre.
Thanks to everyone who came to help. I’m happy now.
I don’t know how to find the actual TW version number but these are the dates I did the updates - taken from /var/log/zypp/history. I assume it’s pretty easy to find which version that would have been.
There would have been one after the April update but it wrecked WiFi so I backed it out. I didn’t have time to figure it out then and needed it working.
Same exact thing happened to me. I rolled back the update to fix it. Good to know there’s a fix if it happens again, but I’ve been extremely reluctant to update after this happened. This is the 2nd update that has broken things for me. The first time Plasma was COMPLETELY unusable. That time, I submitted a bug report and it was completely ignored, so I had to resort to a complete reinstall. I don’t see a whole lot of support when things go wrong with Tumbleweed, so I feel like perhaps it’s time for me to abandon this distro and switch to something that has better support.
A couple of things: That your bugreport has not ( yet ) been replied to is not the way it should be. Defintely not, and it’s not the normal way things go around Tumbleweed. But … talking about updates and Tumbleweed and KDE always triggers something:
How did you update ? Per KDE updater applet? YaST? None of these should be used on Tw, only
is supported. And nothing else.
To eleborate: Tw is released over and over again, as a whole distro. This means downgrades, architecture changes etc can be part of the upgrade. Neither YaST, nor the KDE updater can handle this, and it can lead to a mix of KDE packages from different builds.
And about support for Tw: check these forums, and you’ll see that support is there, with a relatively high percentage of solved issues ( we don’t mark as solved, but still ).
Thanks for your reply! I agree that bug reports shouldn’t be ignored! Even if someone just comments “this isn’t on our end” or something like that, then we’d at least know that someone is out there and paying attention.
I just ran the update and the same thing happened. I went in and ticked the box to force fonts DPI to 96, but the splash screen still has the gigantic font. This fix is just a band-aid because whatever is causing the problem is still going on.
Changes in desktop settings are personal. They have no applicability to the login manager. If the forcing is needed for the greeter, do it either through greeter settings, or globally in /etc/X11. Did you read comment 10?
What exactly is the “splash screen” that has the “gigantic font”? Most splashes have no text, just bling to pass the time until loading completes.