27 червня 2021 р. 10:28:48 UTC, "Hakan Bayındır" <hakan@bayindir.org> написав(-ла):
Hi Vasyl,
First of all, thanks for all the hard work! I finally had time to install the
latest version you've sent. Unfortunately, the problem still persists. I have
the following packages installed related to kodi:
- kodi 2:19.1+dfsg2-2~local amd64
- kodi-bin 2:19.1+dfsg2-2~local amd64
- kodi-data 2:19.1+dfsg2-2~local all
- kodi-repository-kodi 2:19.1+dfsg2-2~local all
Note: I've just upgraded what is already installed using the files you've
sent, in order to keep the environment the same. Upgrading didn't pull in any
new dependencies.
When I start kodi without any locale changes, which is as follows for
reference:
LANG=tr_TR.UTF-8
LANGUAGE=en_US
LC_CTYPE="tr_TR.UTF-8"
LC_NUMERIC="tr_TR.UTF-8"
LC_TIME="tr_TR.UTF-8"
LC_COLLATE="tr_TR.UTF-8"
LC_MONETARY="tr_TR.UTF-8"
LC_MESSAGES="tr_TR.UTF-8"
LC_PAPER="tr_TR.UTF-8"
LC_NAME="tr_TR.UTF-8"
LC_ADDRESS="tr_TR.UTF-8"
LC_TELEPHONE="tr_TR.UTF-8"
LC_MEASUREMENT="tr_TR.UTF-8"
LC_IDENTIFICATION="tr_TR.UTF-8"
LC_ALL=
I get the same empty screens for movies, TV Shows, Settings and many more. I
have attached a screenshot of the problem.
Changing locale to en_US.UTF-8 for everything works around the problem like in
the previous versions. Since the problem is still reproducible, I was unable
to test further.
Will try to get more detailed logs and send them,
Best regards,
Hakan
On 26 Haziran 2021 Cumartesi 00:30:25 +03 Vasyl Gello wrote:
Hi Hakan!
Can you please test this build with workaround I mentioned?
https://fex.net/s/vbdtzs6
Please test video library, search, PVR, whatever you use. It might break
some things but let's see. --
Vasyl Gello
Certified SolidWorks Expert
Mob.:+380 (98) 465 66 77
E-Mail: vasek.gello@gmail.com
Skype: vasek.gello
호랑이는 죽어서 가죽을 남기고 사람은 죽어서 이름을 남긴다
25 червня 2021 р. 08:20:58 UTC, Vasyl Gello <vasek.gello@gmail.com>
написав(-ла):
Hi Hakan!
I’ll provide similar information to the official bugzilla today.
This means glibc is correct and my proposed fix for Kodi upstream (
https://github.com/xbmc/xbmc/pull/19905 ) is technically not…
Does it make sense to catch this edge case in the linked PR rather than
just fall back into non-UTF-8 C locale if "Turkish I" problem is detected?
--
Vasyl Gello
Certified SolidWorks Expert
Mob.:+380 (98) 465 66 77
E-Mail: vasek.gello@gmail.com
Skype: vasek.gello
호랑이는 죽어서 가죽을 남기고 사람은 죽어서 이름을 남긴다