Bug 19091 - konsole fonts are tiny
Summary: konsole fonts are tiny
Status: REOPENED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: KDE maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 17523
  Show dependency treegraph
 
Reported: 2016-07-29 16:37 CEST by David Walser
Modified: 2024-03-03 17:05 CET (History)
4 users (show)

See Also:
Source RPM: konsole-16.04.3-1.mga6.src.rpm
CVE:
Status comment:


Attachments

Description David Walser 2016-07-29 16:37:55 CEST
After upgrading from Mageia 5, konsole fonts are tiny.  They're probably half the height they were in Mageia 5.
Comment 1 Rémi Verschelde 2016-07-29 16:39:38 CEST
I can confirm the issue, and I think it's related to the fontconfig regression (bug 18488).
Comment 2 Rémi Verschelde 2016-07-29 16:40:40 CEST
(In reply to Rémi Verschelde from comment #1)
> I can confirm the issue, and I think it's related to the fontconfig
> regression (bug 18488).

Not 100% sure though, it's been a long time since I moved to Cauldron, and I don't really remember when I started having this specific issue (but AFAIR the fonts were fine when I migrated in January).
David Walser 2016-07-30 03:21:29 CEST

Blocks: (none) => 17523

Samuel Verschelde 2016-08-25 16:23:07 CEST

Assignee: mageia => kde

Comment 3 Nicolas Lécureuil 2017-01-24 09:47:49 CET
is it still valid with last sta2 isos ?

CC: (none) => mageia

Comment 4 Rémi Verschelde 2017-01-24 10:01:13 CET
In my everyday usage the fonts look good, but I think I made a custom konsole theme back then. This is probably something that needs to be tested in a new user/with a default config.
Comment 5 Nicolas Lécureuil 2017-03-14 17:25:12 CET
is it still valid with plasma 5.8.6 ?
Comment 6 David Walser 2017-06-26 00:44:12 CEST
Sorry for the delay.  It's still valid, but I guess probably not a big deal.
Comment 7 Yann Ciret 2018-02-07 17:33:09 CET
Hello,

for me this bug was fixed before mageia 6 release. So it can be closed.
David, can you confirm it is fixed on your side?

Regards
Yann

CC: (none) => mageia

Comment 8 David Walser 2018-02-07 21:43:40 CET
It wasn't fixed when I last checked right before the Mageia 6 release.  I haven't looked at my VM in a while, but I'll take a look at it eventually.
Comment 9 David Walser 2018-02-10 23:22:22 CET
I asked the QA team in the meeting Thursday and the team leader said that nothing had changed on this front.
Comment 10 Aurelien Oudelet 2020-10-29 16:07:35 CET
Hi, thanks for reporting this bug.
We are sorry, but we no longer maintains this version of Mageia. Please upgrade to the latest version and reopen this bug against that version if this bug exists there.
As a result we are setting this bug to RESOLVED:OLD

Also, this was tested with konsole-20.08.2-1.mga8.src.rpm under Cauldron (8) and Mageia 7.

Konsole has integrated profile that uses Monospace police at 10.0 size, which is pretty readable.

CC: (none) => ouaurelien
Status: NEW => RESOLVED
Resolution: (none) => OLD

Comment 11 David Walser 2020-10-29 16:30:14 CET
Re-opening for now.  I haven't played with my test VMs in years but hope to before Mageia 8, so I'll see where this stands, but from my host which is finally on Mageia 7, it looks like this may still be valid.  I'll have to compare in my VM if it's actually the same as what I reported here for Mageia 6, as well as how Mageia 8 looks.

Status: RESOLVED => REOPENED
Resolution: OLD => (none)

Comment 12 David Walser 2021-07-03 21:05:37 CEST
Finally upgraded my VM for the first time in over three years, and nothing has changed for this bug.
Comment 13 sturmvogel 2024-01-07 22:56:57 CET
Konsole has a menu entry to change the font size with a mouseclick (enlarge, shrink, reset to default) or key combo (Ctrl++, Ctrl+-, Ctrl+Alt+=).

As it easy to change the font size via the two methods above, is there still any actual issue present or can this bug finaly closed as OLD?
Comment 14 David Walser 2024-01-07 23:34:55 CET
Fixing it isn't that simple as I recall.  Even if you do that it wouldn't look right.
Comment 15 David GEIGER 2024-03-03 17:05:56 CET
So probably open a new bug upstream at https://bugs.kde.org/ would be much the best solution!

CC: (none) => geiger.david68210


Note You need to log in before you can comment on or make changes to this bug.