Re: [kde] QtCurve customizations do not apply to GTK applications after update to 4.9.1
Marcelo Magno T. Sales posted on Sat, 15 Sep 2012 21:05:13 -0300 as excerpted: > I've just updated KDE to 4.9.1 and now GTK applications do not look like > KDE applications anymore. > I use QtCurve with a number of customizations and have configured it to > be used for GTK applications in System Settings -> Appearance -> GTK > Appearance. Before the update, the GTK applications displayed menus, > widgets, buttons, etc. just like the ones in KDE applications, with all > the customizations I had applied to QtCurve. > However, after the update, GTK applications look like they are using > Oxygen. I think that is the default appearance of QtCurve and that my > customizations are being ignored for GTK applications. > Any hint on how to make GTK applications look like KDE applications > again (other than removing my QtCurve customizations to make KDE > applications use the oxygen-like style, of course :) ) I don't use qtcurve, but I've had the same thing happen occasionally to my kde color options, where I've checked the checkbox that applies the same colors to "non-kde" apps (tho AFAIK all it applies them to is gtk- based apps, and to non-kde qt apps of course, I know it doesn't seem to apply them to generic X apps or to tk based apps). In the case of the kde color option, it was a simple matter of toggling the option to apply to non-kde-apps off, hitting apply, then toggling it back on and hitting apply again. This sort of reapply the options to make them work again technique was very common on MS at least back in the 9x era before MS pushed me off their platform with eXPrivacy, but it's not generally needed as often on Linux, possibly because Linux tends to be more stable than at least 9x MS used to be (I've no current experience with MS since I couldn't even run it now, given I couldn't agree to the EULA giving me permission to do so). I believe what happened is that somehow the variable that kde set to tell the gtk apps what kde-authored gtkrc to use, somehow got unset, so the gtk apps returned to defaults. Toggling the option off and back on (with applies in between) caused kde to reset the variable and/or recreate the file it pointed to, and gtk apps started after that came up with the kde colors I had configured. I run pretty much every newest kde that comes out, including the beta and rc pre-releases, so I've done a lot of kde upgrades since the late 4.2 era when I first switched from kde3, and I've only had gtk apps lose their kde color settings about twice in those now nearing four years, and I'm not /sure/ it was due to an upgrade in /those/ cases, so it definitely doesn't happen with /every/ upgrade, but I /have/ seen it about twice, so it /does/ happen, and each time, a quick toggle/apply/ toggle/apply to that setting reset things appropriately. So hopefully there's something similar you can toggle in qt-curve, and hopefully it has a similar effect. =:^) -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
Re: [kde] krunner: broken font rendering
Nikos Chantziaras posted on Sun, 16 Sep 2012 01:52:31 +0300 as excerpted: > It seems that krunner displays fonts in a somewhat broken manner, > including "System Activity" (which is launched by krunner.) > > To demonstrate, here's a screenshot of "System Activity" through > krunner: > >http://i46.tinypic.com/2n7ktnq.png > > Look at how "Shared Mem" is rendered, for example. If I'm seeing the same problem you are, it's called font "kerning", the way letter spacing is adjusted to account for shape in variable-spaced fonts. For example, the capital letters VA when appearing together look too far apart unless the top of the V overhangs the bottom of the A. http://en.wikipedia.org/wiki/Kerning Especially on discreet-pixel displays such as LCD monitors and dot-matrix printers but to a lessor extent on blur-pixel displays such as CRTs and inkjet printers, a related-effect (but different technology, and it works in 2D, not just horizontal spacing) is hinting, aka grid-fitting. There's also anti-aliasing and (on color LCDs) sub-pixel rendering. http://en.wikipedia.org/wiki/Hinting http://en.wikipedia.org/wiki/Spatial_anti-aliasing http://en.wikipedia.org/wiki/Subpixel_rendering Some people are way more sensitive to these than others. I'd have not noticed the problem without your mention thereof as I'm not particularly sensitive to it. You, OTOH, must be quite sensitive to it in ordered for it to bother you enough to be worth posting about. Here's an XKCD comic that expresses it quite well. (As always with XKCD, be sure and hover for the alt-text as it generally expresses another level of the joke, and if you miss it, you miss half the fun! =;^) http://xkcd.com/1015/ You're the guy on the left, "ARGH!" I'm the guy on the right, "What?" I'm sure the sign bugs you, like the guy on the left, to no end. I see it when I look for it, but ordinarily (as, just walking down the street and seeing it, as presented in the comic), I'd just read it, oblivious to the distress it's causing others, and think nothing of it, much like the guy on the right. > And here's the same process list display, but through "System Monitor": > >http://i50.tinypic.com/r23saq.png > > Notice how "System Monitor" has correct font display. I found out that > I can trigger the same bug in System Monitor if I launch it with: > >ksysguard -graphicssystem native > > Then it looks like this: > >http://i45.tinypic.com/vwq53k.png > > Look for example at how the word "Table" (in "Process Table") is > rendered compared to the previous screenshot. > > Another application that has the same problem is KSnapshot. And indeed, > if I launch it manually with: > >ksnapshot -graphicssystem raster > > then the problem goes away. > > In System Settings, in the Desktop Effects section's "Advanced" tab, I > have "Raster" set as the "Qt graphics system". My Linux distro (Gentoo) > also has this set in the environment: > >QT_GRAPHICSSYSTEM=raster > > So why is this happening? How can I make krunner (and KSnapshot) use > the raster engine by default and not have broken font rendering? The problem as you're seeing it almost certainly has to do with the graphics system, the combination of hardware, drivers, and rendering method and graphics acceleration options chosen. Switching between qt- raster and qt-native (there's also qt-opengl mode, as you're on gentoo as I am, try eselect qtgraphicssystem list, but opengl mode really IS experimental, and last time I tried it resulted in a kde/qt display so bugged out it was pretty much unusable) switches acceleration and rendering methods, with obviously one method using different kerning, or more likely hinting, than the other. Actually, probably the one activates freetype's autohinting mode, while the other bypasses it, using either no hinting or a different hinting method. On the raster vs native qt-graphics-system question, I don't know. If both gentoo/eselect/environment and kde's advanced desktop effects tab are set to raster and you're still getting, presumably, native -- that is, if you're still seeing a difference between how they're run normally and what happens if you run them with the -graphicssystem raster switch, I'd say you've likely hit a bug. How are you starting kde, from a text login using startx (with kde4 set as the xsession), or from *DM (graphical/x-based login, kdm, xdm, gdm, etc), and if from *DM, which one? A first guess would be that you're either using a *DM and it's somehow missing the environment setting that would select raster, or alternatively, that you're using a text login with startx, and that it's missing the hook that would set raster. Either way, you need to ensure that the var is actually being set in the environment kde's actually getting. To see what environment kde's actually getting, try running this from krunner: env > $HOME/kde.env You can then open (or simply cat, in konsole) that
[kde] QtCurve customizations do not apply to GTK applications after update to 4.9.1
Hello, I've just updated KDE to 4.9.1 and now GTK applications do not look like KDE applications anymore. I use QtCurve with a number of customizations and have configured it to be used for GTK applications in System Settings -> Appearance -> GTK Appearance. Before the update, the GTK applications displayed menus, widgets, buttons, etc. just like the ones in KDE applications, with all the customizations I had applied to QtCurve. However, after the update, GTK applications look like they are using Oxygen. I think that is the default appearance of QtCurve and that my customizations are being ignored for GTK applications. Any hint on how to make GTK applications look like KDE applications again (other than removing my QtCurve customizations to make KDE applications use the oxygen-like style, of course :) ) Thanks, Marcelo ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
[kde] krunner: broken font rendering
It seems that krunner displays fonts in a somewhat broken manner, including "System Activity" (which is launched by krunner.) To demonstrate, here's a screenshot of "System Activity" through krunner: http://i46.tinypic.com/2n7ktnq.png Look at how "Shared Mem" is rendered, for example. And here's the same process list display, but through "System Monitor": http://i50.tinypic.com/r23saq.png Notice how "System Monitor" has correct font display. I found out that I can trigger the same bug in System Monitor if I launch it with: ksysguard -graphicssystem native Then it looks like this: http://i45.tinypic.com/vwq53k.png Look for example at how the word "Table" (in "Process Table") is rendered compared to the previous screenshot. Another application that has the same problem is KSnapshot. And indeed, if I launch it manually with: ksnapshot -graphicssystem raster then the problem goes away. In System Settings, in the Desktop Effects section's "Advanced" tab, I have "Raster" set as the "Qt graphics system". My Linux distro (Gentoo) also has this set in the environment: QT_GRAPHICSSYSTEM=raster So why is this happening? How can I make krunner (and KSnapshot) use the raster engine by default and not have broken font rendering? ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
Re: [kde] KDE Desktop effects
Bogus Zaba posted on Fri, 14 Sep 2012 19:59:15 +0100 as excerpted: > I am not desperate to have all possible eye-candy operating, but I know > that my system is capable of reasonable performance with regard to stuff > like box-switching etc because it has worked before. > > The system has an nvidia GeForce 7300 card and I am using the nvidia > (proprietary) driver. The KDE is 4.5.5 under Slackware 13.37 which is > the best I can run under Slack 13.37 without making some other > significant system changes. > > Recently KDE allows me to use only the XRender compositing type which > provides a jerky experience if desktop effects are turned on. If I try > and switch to OpenGL I get "Failed to activate desktop effects using the > given config options" and it reverts to jerky Xrender. I have > re-installed the nvidia driver and am sure it is working OK because the > nvidia Server settings utility does what is expected (provides a cursor > shadow for example). This utility also reports all sorts of OpenGL > parameters and so it looks like OpenGL should work OK. Why is KDE not > playing nicely? What kernel version? What xorg-server version? Did you upgrade those since it worked properly? What about your nvidia driver? If the rest of your system is as old as the now two years old kde 4.5 (tho 4.5.5 isn't quite that old... November/December), but you tried upgrading either the kernel or the video driver (or xorg-server, but that's less likely to be upgraded on its own I'd guess), they're probably expecting something newer. Of course if you upgrade your kernel, you need to rebuild your servantware drivers against the new kernel, but failing to do that usually results in not being able to get into X at all (or at least it did back shortly after the turn of the century when I last ran nVidia graphics, something I've stayed away from since due to their lack of cooperation with the FLOSS community), so /that/ shouldn't be the problem. Just to confirm. There's an app called glxgears. You can run it and see the gears still? If so, you have at least /minimal/ glx (glx = (open)gl-X). If not, your glx is broken. And on the same (third/advanced) tab of the desktop effects applet, IDR if kde 4.5 had it or if it was added later, but if you have a checkbox for opengl shaders, try unchecking that. Older hardware/software didn't work well with that. Also, along about the kde 4.5 era, kwin was blacklisting certain combinations of hardware and drivers due to problems they've since worked out. It's possible that whatever you're running is or was blacklisted. Check kwinrc (probably in ~/.kde/share/config/). You may wish to try renaming that file (with kde not running of course) and starting kde/kwin to have it recreated "clean". Finally, what window decoration are you running? Some of those, particularly the customizations available on kdelook.org, etc. (as opposed to those shipped by kde), have been known to trigger various issues. KDE's native oxygen decoration is one of the more challenging of the native/shipped decorations, so you might try one of the others. (Personally, I've run the kde2 decoration since... well... kde2, without the issues I sometimes see others mentioning for other decorations. But it's also not quite as featureful. YMMV.) -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
