Bug 370530 - Compact switcher uses bad font rendering with startkde and kwin_x11
Summary: Compact switcher uses bad font rendering with startkde and kwin_x11
Status: RESOLVED WORKSFORME
Alias: None
Product: kwin
Classification: Plasma
Component: effects-tabbox (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2016-10-12 08:37 UTC by Luke-Jr
Modified: 2018-10-27 04:00 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Luke-Jr 2016-10-12 08:37:41 UTC
The font rendering in the Compact switcher by default makes it difficult to use. Entire columns are skipped, leaving characters like "l" (lowercase "L") and "j" entirely invisible. Restarting kwin from within the running KDE session fixes this problem. Restarting it from outside the session goes back to bad rendering.

See http://luke.dashjr.org/tmp/screenshots/snapshot149.png

Reproducible: Always
Comment 1 Martin Flöser 2016-10-12 08:47:10 UTC
Could you please explain what you mean with startkde and kwin_x11? How do you start things?
Comment 2 Luke-Jr 2016-10-12 08:51:38 UTC
Since I was unable to find any standard way to start KDE with startx, and I do not wish to use a DM, I added "startkde" to my ~/.xsession file, and that seems to get startx to work. So when I boot my PC, I now login to the VT and run "startx", which AIUI then calls "startkde" (which I assume starts kwin_x11 somehow). This results in the switcher with bad font rendering (top screenshot).

When debugging this issue, I was executing "kwin_x11 --replace" in Konsole (to get good font rendering as in the bottom screenshot) and back in my original VT (to go back to the bad font rendering; top ss).
Comment 3 Martin Flöser 2016-10-12 09:47:36 UTC
If you start through a DE, does it work correctly then?
Comment 4 Luke-Jr 2016-10-12 09:58:38 UTC
I'm not interested in installing a DM.
Comment 5 Martin Flöser 2016-10-12 13:29:36 UTC
please compare the environ of kwin started through startkde and the kwin started manually.
Comment 6 Luke-Jr 2016-10-12 16:32:30 UTC
--- env.original    2016-10-12 16:30:27.458085244 +0000
+++ env.konsole 2016-10-12 16:30:31.726105018 +0000
+COLORFGBG=15;0
+DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-MrapamK7gW,guid=4140cf83381320fe01f9896a57f089bd
+GS_LIB=/home/luke-jr/.fonts
+GTK2_RC_FILES=/etc/gtk-2.0/gtkrc:/home/luke-jr/.gtkrc-2.0:/home/luke-jr/.config/gtkrc-2.0
+GTK_RC_FILES=/etc/gtk/gtkrc:/home/luke-jr/.gtkrc:/home/luke-jr/.config/gtkrc
+KDE_FULL_SESSION=true
+KDE_MULTIHEAD=false
+KDE_SESSION_UID=1000
+KDE_SESSION_VERSION=5
+KONSOLE_DBUS_SERVICE=:1.64
+KONSOLE_DBUS_SESSION=/Sessions/127
+KONSOLE_DBUS_WINDOW=/Windows/94
+KONSOLE_PROFILE_NAME=Shell
+LANGUAGE=en_GB:en_US
+LC_MEASUREMENT=en_US.UTF-8
+LC_TIME=en_CA.UTF-8
+PROFILEHOME=
+SESSION_MANAGER=local/ishibashi:@/tmp/.ICE-unix/4398,unix/ishibashi:/tmp/.ICE-unix/4398
+SHELL_SESSION_ID=84328fa2b8714000a84c9751e9521569
-SHLVL=2
+SHLVL=6
+SSH_ASKPASS=/usr/bin/ksshaskpass
-STY=2341.X
-TERM=screen.linux
+TERM=xterm
+WINDOWID=16777856
+WINDOWPATH=7
+XAUTHORITY=/tmp/xauth-1000-_1
+XCURSOR_SIZE=0
+XCURSOR_THEME=Oxygen_Blue
+XDG_CURRENT_DESKTOP=KDE
Comment 7 Martin Flöser 2016-10-13 05:25:54 UTC
Interesting. That's kind of what I expected, but much more than I expected. The KWin started through startkde does not have any of the required environment variables set and is not part of the dbus session.

My guess is that kwin gets started before startkde. Can you check the parent process? It should be ksmserver.
Comment 8 Luke-Jr 2016-10-13 05:39:32 UTC
That was technically VT-launched vs Konsole-launched. Missed that you wanted specifically a new session, rather than simply a comparison between bad vs good.

I'll try to remember to grab the env and parent process next time I login (not often, probably several weeks from now).
Comment 9 Martin Flöser 2016-10-13 06:24:32 UTC
Ok, seems like you are a lucky user who can run the session for several weeks ;-)
Comment 10 Andrew Crouthamel 2018-09-26 22:06:43 UTC
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 set the bug status 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!
Comment 11 Andrew Crouthamel 2018-10-27 04:00:57 UTC
Dear Bug Submitter,

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!