Problem with new Linux default font for 2017.1

Answered

After installing, 2017.1, there default font looks different.  Went to settings/appearance and am still going with the default font (deja vu sans 13) but can't locate the previously used font.

Anyone else see this or could this be due to some update to my fedora system which was done at the same time?

19 comments

I've seen this on an Ubuntu 16.04 installation so it's not local to your Fedora environment.  The change from 2016 -> 2017 has introduced a default font change that looks pretty darned different.

2

I'm on Yakkety Yak (16.10), and no other font is offered than this DejaVu Sans 13. This is a serious readability and thus productivity issue for me!

1

Brought this up (but wasn't explicit) as the font renders very poorly and readability is an issue as Csaba mentions.  It's not just I feel like changing it for fun.

1

Anyone knows what was the old font (I wish I checked before) in the old 2016.x PyCharm in Linux, so once we can figure out how to set it to something else we cans et it back to that one?

0

Mh4, can you rename the topic, like "2017.1 Linux lame font" or something?

0

The same problem here (Ubuntu 16.04). The same font as in 2016 version, but rendering is really bad now

4

I just upgraded a few minutes ago, and immediately noticed the font change. My preferred font from PyCharm 2016.3, "DejaVu Sans Mono" is still selected in the font settings dialog. However, PyCharm is silently substituting "Monospaced" instead.

The problem seems to be specific to DejaVu Sans Mono. Other fonts seem to work fine in 2017.1. The older PyCharm is still working correctly. 

I even tried removing DejaVu Sans from the system fonts and putting copy in my local user fonts (~/.fonts) folder. That didn't help either. 

Other fonts in the IDE (labels, buttons) are different as well. I'm on Mint 17.3 (Ubuntu 14.04).

2

@Seth so the font "DejaVu Sans Mono" was what we saw in the older version, just cannot be resolved with the 2017. My bigger problem was that I couldn't even select anything else. Now fonts appeared in the drop-down, but non of them is as readable as "DejaVu Sans Mono" was, and on top of that my selection only affects mainly the editor. I want the console to be readable, etc. I wonder if this problem present in the IntelliJ IDEA as well.

0

It'd be great to see someone from JetBrains chime in here. Otherwise I'll write a proper support ticket soon.

4

Filed an issue https://youtrack.jetbrains.com/issue/PY-23363

My JDK BTW:

java version "1.8.0_121"
Java(TM) SE Runtime Environment (build 1.8.0_121-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode)

Looking at AskUbuntu and other place people advise various fonts. I just want the old font back, that worked.

 

1

How somebody in bugtracker said. For quick fix it just about replacing new jre folder in your Pycharm folder with the older one. Now I have the same rendered font as with old version

0

I experienced the same issue with Ubuntu 16.04, at the end I reverted back to the previous version, 2016.1.

With that version everything is fine. This is very annoying.

0

I also have reverted back to 2016.3. Fonts in 2017.1 are too ugly and I can't use it.  I think JetBrains has test his products more carefully before the release.

2

Installed 2017.1.1 and now I'm back to a different very thin, non-substantial font than I was last night. 

Jetbrains, what are the proper setting to get back to the original font?

2

9 years have past https://intellij-support.jetbrains.com/hc/en-us/community/posts/206824625-IDEA-linux-fonts

still same problem

still no reply from IDEA team

still eclipse looks and feels much better

still occasionally have to use idea because of "formatting standards" at work.

 

1

Indeed, very disappointing, to say the least.

Luckily, the only thing affected for me is the Error Console.

 

0

Hi Amel,

When do you have the error?

Have you tried the proposed by PyCharm solutions?

If problem is totally different from described in this post originally, I think it will be better to create another one for your problem.

0

Please sign in to leave a comment.