SUSE's KDE updates for 9.0 and annoyingly large fonts
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This has been driving me nuts for a long time, but I can't seem to get to the bottom of it. After performing SUSE's KDE updates for 9.0 (the official updates, not the supplementary packages), khtml fonts are annoyingly huge. This makes Konqueror and Kmail terrible to look at on my 1024x768 laptop screen. This is also the case on other machines around here. I can make the fonts larger, but they will not go smaller than 12 point. Has anybody else seen this? - -- James Oakley Engineering - SolutionInc Ltd. joakley@solutioninc.com http://www.solutioninc.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/wkJC+FOexA3koIgRAoCXAJ9qOutz148Ciwl3+cNW2EXVxKqM/gCfZvW5 hHI/JGze+eigBU+9i3aCG3I= =2Wkp -----END PGP SIGNATURE-----
On Monday 24 November 2003 18:39, James Oakley wrote:
This has been driving me nuts for a long time, but I can't seem to get to the bottom of it.
After performing SUSE's KDE updates for 9.0 (the official updates, not the supplementary packages), khtml fonts are annoyingly huge. This makes Konqueror and Kmail terrible to look at on my 1024x768 laptop screen. This is also the case on other machines around here.
I can make the fonts larger, but they will not go smaller than 12 point.
Has anybody else seen this?
-- James Oakley Engineering - SolutionInc Ltd. joakley@solutioninc.com http://www.solutioninc.com
Maybe its related to the display size as its configured in XF86Config? Rendering is related to the screen resolution and the physical size of the display..I'm not I'm not an expert by any stretch ....just something.. Background: My 19" monitor was not recognized by Sax2 and I had always 'cheated' and picked a smaller screen..to get safe 'mode lines' (understood that afterwards) and had too large fonts, so I manually added the physical size of the display, should be in millimeters: to give X that 'extra push'.. Section "Monitor" DisplaySize 360 270 jk -- Suse Linux 9.0 | 2.4.21-121-smp4G | KDE 3.1.4 | XFree86 v4.3.0.1
This has been driving me nuts for a long time, but I can't seem to get to
On Monday 24 November 2003 11:39 am, James Oakley wrote: the
bottom of it.
After performing SUSE's KDE updates for 9.0 (the official updates, not the supplementary packages), khtml fonts are annoyingly huge. This makes Konqueror and Kmail terrible to look at on my 1024x768 laptop screen. This is also the case on other machines around here.
I can make the fonts larger, but they will not go smaller than 12 point.
Has anybody else seen this?
-- James Oakley
Yes I have in 8.2 Pro. In 9.0 that quit happening to me so far. I have no idea how it started in 8.2 and I have no idea how it doesn't happen in 9.0. I can go down to like 6 pt and it is that small. One thing to check is the screen size for your monitor in /etc/X11/XF86Config, Section "Monitor", DisplaySize 360 270 is what mine says. That's in mm not inches :o) Stan
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday 24 November 2003 07:51 pm, Stan Glasoe wrote:
After performing SUSE's KDE updates for 9.0 (the official updates, not the supplementary packages), khtml fonts are annoyingly huge. This makes Konqueror and Kmail terrible to look at on my 1024x768 laptop screen.
Yes I have in 8.2 Pro. In 9.0 that quit happening to me so far. I have no idea how it started in 8.2 and I have no idea how it doesn't happen in 9.0. I can go down to like 6 pt and it is that small.
Amazingly, it had nothing to do with the KDE updates. In the same KDE session, I updated my Gnome packages to James Ogley's releases. I thought nothing of it. Why would a Gnome package affect KDE in any way? The ULB control-center2 RPM causes this. I inspected the RPM, but I couldn't find out why. - -- James Oakley Engineering - SolutionInc Ltd. joakley@solutioninc.com http://www.solutioninc.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/xLfu+FOexA3koIgRArkQAKCH9VDANwlelddhuxMDmTcf2WXRSwCfUePB jZUwHS0/p/GdSmBr4cnJ7kI= =9a9j -----END PGP SIGNATURE-----
The ULB control-center2 RPM causes this. I inspected the RPM, but I couldn't find out why.
From the release notes with it on the site:
This is an updated version of the GNOME2 control centre. It also adds gnome-settings-daemon to the default KDE autostart folder, so that GTK applications are themed correctly under KDE. Please Note: Some people have experienced problems with their KDE desktop after installing this package. usr local bin cannot reproduce these problems, they may be related to having gnome-settings-daemon in your personal Autostart folder as well as the system one. If you have problems, you can revert to the version on the SuSE CDs, using the --oldpackage option to RPM. -- James Ogley, Webmaster, Rubber Turnip james@rubberturnip.org.uk http://www.rubberturnip.org.uk Jabber: riggwelter@myjabber.net Using Free Software since 1994, running GNU/Linux (SuSE 9.0) GNOME updates for SuSE: http://www.usr-local-bin.org
On Wednesday 26 November 2003 2:25 pm, James Oakley wrote:
Amazingly, it had nothing to do with the KDE updates. In the same KDE session, I updated my Gnome packages to James Ogley's releases. I thought nothing of it. Why would a Gnome package affect KDE in any way?
Indeed. Sjoerd Hiemstra posted a fix that worked for him, which was to turn off anti-aliasing in both the KDE Control Center and qtconfig. This doesn't work for me - if I have the gnome-settings-daemon running, I need to choose between anti-aliased fonts in KDE that are two sizes too big, or fonts that are the right size, but are not anti-aliased. Moreover, even though some Gnomish apps like Synaptic will respect gnome-control-center's font setting, others like GIMP don't - I presumably have to fiddle about with some other gnome1 control center for them. So I'm just putting up with crap fonts in Gnome apps. I think there is something broken in Gnome, but in a sufficiently esoteric place that it only shows up on some setups. For instance, when I opened gnome-control-center simply to do some more tests before posting this, and clicked the screensaver icon, it told me that there was no screensaver app running. This in spite of the fact that I have had Gnome random screensavers on this box for at least 3 months - the equivalent pane in KDE CC is completely empty, so that's the only place they could have come from. I didn't ask for them (although some of them are very nice), but they somehow inserted themselves as part of the install of a Gnome2 package. So how come Gnome didn't know about them? Definitely some dodgy code somewhere. -- Best wishes Kevin Donnelly www.kyfieithu.co.uk - Meddalwedd Rydd yn Gymraeg
participants (5)
-
Jaan Kold -
James Oakley -
James Ogley -
Kevin Donnelly -
Stan Glasoe