October 2022 - Wine-Bugs - list.winehq.org

[Bug 53719] Startopia crashes while loading

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=53719 Béla Gyebrószki <gyebro69(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #3 from Béla Gyebrószki <gyebro69(a)gmail.com> --- Fixed in Wine-Staging 7.19. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

Oct. 17, 2022

[Bug 45273] Chessbase 11 cannot draw arrows

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=45273 --- Comment #9 from Bartosz <gang65(a)poczta.onet.pl> --- More information about missing library is available at: https://learn.microsoft.com/en-us/cpp/c-runtime-library/reference/strlwr-s-… -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

Oct. 17, 2022

[Bug 45273] Chessbase 11 cannot draw arrows

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=45273 --- Comment #8 from Bartosz <gang65(a)poczta.onet.pl> --- After running ChessBase/CBaseReader14, I got crash caused by unimplemented function: 00a0:fixme:imm:ImeSetActiveContext (0000000000010026, 0): stub 00a0:fixme:imm:ImmReleaseContext (0000000000010020, 0000000000010026): stub 0024:fixme:reg:RegQueryInfoKeyA security argument not supported. wine: Call from 7B0411F5 to unimplemented function ucrtbase.dll._mbslwr_s_l, aborting wine: Unimplemented function ucrtbase.dll._mbslwr_s_l called at address 7B0411F5 (thread 0024), starting debugger... 0110:fixme:imm:ImeSetActiveContext (00010090, 1): stub 0110:fixme:imm:ImmReleaseContext (0001009E, 00010090): stub -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

Oct. 17, 2022

[Bug 50281] fsync patch for wine 6.0-rc1 (without staging)

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=50281 --- Comment #19 from roidal(a)googlemail.com --- (In reply to Zeb Figura from comment #18) > The current hope is to obviate esync with a new Linux kernel driver capable > of performantly emulating NT synchronization primitives. What is the actual approach to that? I was able to find an old mail to ntsync/winesync but sadly nothing about it's progress. Is it still in developement? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

Oct. 17, 2022

[Bug 53770] [ nls cause BUG ] local.nls should must be update (./wine/nls/local.nls )

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=53770 --- Comment #14 from 399989567(a)qq.com --- Created attachment 73305 --> https://bugs.winehq.org/attachment.cgi?id=73305 WINEDEBUG=+nls,+locale WINEDEBUG=+nls,+locale -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

Oct. 17, 2022

[Bug 53770] [ nls cause BUG ] local.nls should must be update (./wine/nls/local.nls )

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=53770 --- Comment #13 from 399989567(a)qq.com --- (In reply to Nikolay Sivov from comment #12) > (In reply to 399989567 from comment #9) > > Created attachment 73303 [details] > > The new locale.nle by SvenL > > > > Update the locale.nls to solve the Chinese default number problem. > > Updated binary file is not useful. Please attach the log I just asked for > instead. (In reply to Nikolay Sivov from comment #10) > First we'll need to validate that the change is correct. What is the exact > locale name you're using? I'm not totally sure how to check that easily, but > you could run your application like this: > > WINEDEBUG=+nls,+locale wine <application.exe> &> /tmp/log.txt > > and attach resulting file here. Hopefully it will show used locale name > somewhere in the log. Wait for me to open the computer to produce log files for you. —————————————— ① Actually, I was using DingTalk when I found a bug in the program, the time was displayed as "〇〇:〇〇:《>" during voice call, when LANG=zh_CN.UTF-8. Problem picture: https://imgse.com/i/xDQICq But on my English virtual machine, the time is displayed correctly here, like "00:00:12" —— ② I felt that this phenomenon was very strange, so I thought about this issue from several angles. When I investigated the registry, I exported all the registries of both Chinese and English environments, and then used "git diff", I found that there are two table entries in these two registries that are different, that is: > HKEY_USERS\S-1-5-21-0-0-0-1000\Control Panel\International\sNativeDigits English env -> sNativeDigits = 0123456789 Chinese env -> sNativeDigits = 〇一二三四五六七八九 Where "〇" is the "〇" in "〇〇:〇〇:《>" in my error picture above. So in the Chinese environment, I'm directly set the sNativeDigits = 0123456789,this problem disappears. So I presume that the time display API reads the value of sNativeDigits 。 —— ③ Next I opened the Chinese version of the window10 registry, I found the value of sNativeDigits in window10(Chinese env) also is 0123456789 but not is 〇一二三四五六七八九. Then,I took another look at wine's source code and found that the value of sNativeDigits is passed through the function "get_locale_info" ↓ > /* get locale information from the locale.nls file */ > static int get_locale_info( const NLS_LOCALE_DATA *locale, LCID lcid, LCTYPE type,WCHAR *buffer, int len ) > { > ..... > case LOCALE_SNATIVEDIGITS: > if ((ret = locale_return_reg_string( &entry_snativedigits, type, buffer, len )) != -1) return ret; > ..... > } I'm sure this data is read from locale.nls, and I'm also sure that under windows10（Chinese） sNativeDigits = 0123456789 ———————————— On a side note, there is actually a bug here, as you can see in my error picture, the time is displayed as "〇〇:〇〇:《>",The actual display should be "〇〇:〇〇:一二"。 This is not correct, the "一" is displayed as "《",But I haven't found out which API is called here, so I'm sorry I didn't find the cause of the problem. Is it related to the byte length of Chinese characters? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

Oct. 17, 2022

[Bug 53770] [ nls cause BUG ] local.nls should must be update (./wine/nls/local.nls )

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=53770 --- Comment #12 from Nikolay Sivov <bunglehead(a)gmail.com> --- (In reply to 399989567 from comment #9) > Created attachment 73303 [details] > The new locale.nle by SvenL > > Update the locale.nls to solve the Chinese default number problem. Updated binary file is not useful. Please attach the log I just asked for instead. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

Oct. 17, 2022

[Bug 53770] [ nls cause BUG ] local.nls should must be update (./wine/nls/local.nls )

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=53770 399989567(a)qq.com changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #73303|0 |1 is obsolete| | --- Comment #11 from 399989567(a)qq.com --- Created attachment 73304 --> https://bugs.winehq.org/attachment.cgi?id=73304 The new locale.nle by SvenL Update the locale.nls to solve the Chinese default number problem -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

Oct. 17, 2022

[Bug 53770] [ nls cause BUG ] local.nls should must be update (./wine/nls/local.nls )

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=53770 --- Comment #10 from Nikolay Sivov <bunglehead(a)gmail.com> --- First we'll need to validate that the change is correct. What is the exact locale name you're using? I'm not totally sure how to check that easily, but you could run your application like this: WINEDEBUG=+nls,+locale wine <application.exe> &> /tmp/log.txt and attach resulting file here. Hopefully it will show used locale name somewhere in the log. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

Oct. 17, 2022

[Bug 53770] [ nls cause BUG ] local.nls should must be update (./wine/nls/local.nls )

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=53770 399989567(a)qq.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |399989567(a)qq.com --- Comment #9 from 399989567(a)qq.com --- Created attachment 73303 --> https://bugs.winehq.org/attachment.cgi?id=73303 The new locale.nle by SvenL Update the locale.nls to solve the Chinese default number problem. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

Oct. 17, 2022