Bug 412013 - Wrong typeset of numbers in tab inscription
Summary: Wrong typeset of numbers in tab inscription
Status: RESOLVED DOWNSTREAM
Alias: None
Product: krusader
Classification: Applications
Component: general (show other bugs)
Version: 2.6.0
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Krusader Bugs Distribution List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-09-18 11:19 UTC by Sergejevicz
Modified: 2020-05-16 11:45 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Screenshot of badly set inscription of path on tab containing corrupted digits typeset (25.85 KB, image/png)
2019-09-18 11:19 UTC, Sergejevicz 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Sergejevicz 2019-09-18 11:19:15 UTC 
Created attachment 122699 [details]
Screenshot of badly set inscription of path on tab containing corrupted digits typeset

SUMMARY
Wrong typeset of numbers in tab inscription

OBSERVED RESULT
In inscription containing path, appearing on tab, all numbers are set by light font with big spaces between digits.

EXPECTED RESULT
Used font should be the same for characters as well as digits.

SOFTWARE/OS VERSIONS
Linux openSUSE Leap 15.2
Comment 1 Sergejevicz 2019-09-18 13:02:01 UTC 
Observed in another places within openSUSE Leap 15. It may be system-wide problem.
Comment 2 Davide Gianforte 2020-05-03 04:59:32 UTC 
As in comment #1, it seems to be a problem with the system, is the problem still present?
Comment 3 Sergejevicz 2020-05-16 07:33:25 UTC 
The problem occurred in openSUSE Leap 15 with GNOME GUI. During the period till now, I reinstalled the system to KDE GUI. There the problem did not occur. Additionally I switched to GNOME GUI, without reinstallation. I use this set-up till now and the problem did not occur again so far. It may be caused by bug fix or possibly by manipulation with GUIs (can some features from KDE preserve after switching to GNOME...?).
Comment 4 Davide Gianforte 2020-05-16 11:45:27 UTC 
It's seems to be related to a package / configuration missing in a partial usage of KDE software, solved by the full installation. It could be resolved by updating dependencies for the package in the distro.