February 2016 - Wine-Bugs - list.winehq.org

[Bug 27349] New: SafeDisc v2.x API entry analyzer flags Wine's user32.dll as "bad" (too many exports with PIC loads in prolog code) (SimCity 4, ...)
by wine-bugs＠winehq.org March 8, 2019

March 8, 2019

http://bugs.winehq.org/show_bug.cgi?id=27349 Summary: SafeDisc v2.x API entry analyzer flags Wine's user32.dll as "bad" (too many exports with PIC loads in prolog code) (SimCity 4, ...) Product: Wine Version: 1.3.21 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: user32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: focht(a)gmx.net Hello, many games (and some apps) have dependency on "meta" bug 219 "Programs refuse to run because of safedisc copy-protection" which just bad (not even targeting specific version). I bought some games for few bucks just to have a look at some copy protections. Though I will probably never play them ;-) Collecting/tracking affected games/apps for this _specific_ issue here (applicable appdb entries should have bug 219 dependency removed in favor of this one). The root cause was already targeted by bug 10273 ("satisfy SafeDisc 2.x heuristic API analyzer by "adjusting" API exports/entry statistics of wine builtins (affects e.g. adobe photoshop)") ... That bug was closed a long time ago because it ought to work for various SD 2.x apps/games (unfortunately also depending on wine build environment/host gcc). I rejected the idea of reviving that bug and instead created a new one, targeting the affected core dll. Game: "SimCity 4" A quick scan with "ProtectionID" reveals: --- snip --- -=[ ProtectionID v0.6.4.0 JULY]=- (c) 2003-2010 CDKiLLER & TippeX Build 07/08/10-17:57:05 Ready... Scanning -> H:\.wine\drive_c\Program Files\Maxis\SimCity 4\Apps\SimCity 4.exe File Type : 32-Bit Exe (Subsystem : Win GUI / 2), Size : 7971630 (079A32Eh) Byte(s) [x] Warning - FileAlignment seems wrong.. no solution calculated (using NULL) -> File has 746286 (0B632Eh) bytes of appended data starting at offset 06E4000h [File Heuristics] -> Flag : 00000000000000000100000100000111 (0x00004107) [!] Safedisc v2/v3/v4 [unknown version] detected ! [i] Appended data contents.... ... [CompilerDetect] -> Visual C++ 6.0 - Scan Took : 0.262 Second(s) --- snip --- We can do better ... The string "BoG_" is well known for detection of SafeDisc versions. --- snip --- $:~/.wine/drive_c/Program Files/Maxis/SimCity 4/Apps$ xxd -g 4 SimCity\ 4.exe | grep "BoG_" -A 2 0006fd0: 00000000 426f475f 202a3930 2e302621 ....BoG_ *90.0&! 0006fe0: 21202059 793e0000 00000000 00000000 ! Yy>.......... 0006ff0: 00000000 02000000 50000000 0a000000 ........P....... --- snip --- 0x02000000 -> 2 0x50000000 -> 90 0x0a000000 -> 10 So this is SafeDisc v2.90.10 protection. By debugging this game I came to conclusion there is still a problem with the API entry statistics. $ wine --version wine-1.3.21-26-ge6ee2c1 $ gcc --version gcc version 4.4.5 (Ubuntu/Linaro 4.4.4-14ubuntu5) For the meaning of the table just read up some comments in bug 10273 kernel32 user32 gdi32 condition (cx < threshold) -------------------------------------------------------------------- c1: 0x43 0x55 0x50 0x5F c2: 0x23 *0x41 0x39 0x3C c3: 0x00 0x00 0x00 0x5A * = threshold exceeded -> bad Basically the majority of exported user32 API entries have PIC register load code within range of first 8 opcode bytes of entry which is treated as trampoline (= high c2 value). --- snip --- ... .text:0001D847 __i686_get_pc_thunk_bx proc near .text:0001D847 mov ebx, [esp+0] .text:0001D84A retn .text:0001D84A __i686_get_pc_thunk_bx endp ... API entry: .text:0003735C push ebp .text:0003735D mov ebp, esp .text:0003735F push ebx .text:00037360 sub esp, 34h .text:00037363 call __i686_get_pc_thunk_bx .text:00037368 add ebx, 0AEC8Ch ... --- snip --- Kernel32 gets the good looking stats because it forwards various stuff to ntdll, letting compiler produce different function prolog code (= not having PIC register load in first place). As already mentioned in the other bug, unimpl. stubs also help to improve stats because they have 8 NOPs on entry. I've tweaked user32 again a bit just to pass the threshold - there are various ugly methods one bad as the other ;-| A method without adding unimpl. stubs or stack protector code (unreliable because cookie code can be inserted _after_ PIC code) and keeping -fPIC is to convince the compiler to use the 6 byte opcode for reserving stack space, e.g. "subl $xxx, %esp" with a 32-bit immediate (0x81,0xEB,<32 bit immediate>). Good targets are stubs and functions that make use of FIXME/TRACE. There are lots of them that can be tweaked this way (= no performance penalty), improving entry stats. Result: games work out of the box without the need of No-CD patches. Regards -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.

1 30

[Bug 36977] New: Magic: The Gathering – Duels of the Planeswalkers 2015 crashes after few frames of intro sequence
by wine-bugs＠winehq.org March 7, 2019

March 7, 2019

http://bugs.winehq.org/show_bug.cgi?id=36977 Bug ID: 36977 Summary: Magic: The Gathering – Duels of the Planeswalkers 2015 crashes after few frames of intro sequence Product: Wine Version: 1.7.21 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: otigkd(a)gmail.com Created attachment 49100 --> http://bugs.winehq.org/attachment.cgi?id=49100 crash log os: Gentoo x86 installed trough steam. a few seconds of loding/intro is played, then crashes -- 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.

1 6

[Bug 35698] New: Nuance PDF Create! 5 installer (part of OmniPage 17) reports 'Error code: 154 - Get ServerPolicy failed' (IGroupPolicyObject, CLSID {ea502722-a23d-11d1-a7d3-0000f87571e3})
by wine-bugs＠winehq.org March 4, 2019

March 4, 2019

https://bugs.winehq.org/show_bug.cgi?id=35698 Bug ID: 35698 Summary: Nuance PDF Create! 5 installer (part of OmniPage 17) reports 'Error code: 154 - Get ServerPolicy failed' (IGroupPolicyObject, CLSID {ea502722-a23d-11d1-a7d3-0000f87571e3}) Product: Wine Version: 1.7.13 Hardware: x86 OS: Linux Status: NEW Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Hello folks, as the summary says. The failure seems non-critical and the message box can be dismissed. The sub-installer can be separately run for testing: --- snip --- $ pwd /mnt/iso/PDFCreate5/System32/PDFCreate $ WINEDEBUG=+tid,+seh,+relay,+ole,+variant wine ./setup.exe >> ~/Downloads/log2.txt 2>&1 ... 003f:Call ole32.CoCreateInstance(00b2e33c,00000000,00000001,00b2e324,00b2e334) ret=008d881a 003f:trace:ole:CoCreateInstance (rclsid={ea502722-a23d-11d1-a7d3-0000f87571e3}, pUnkOuter=(nil), dwClsContext=00000001, riid={ea502723-a23d-11d1-a7d3-0000f87571e3}, ppv=0xb2e334) 003f:trace:ole:CoGetClassObject CLSID: {ea502722-a23d-11d1-a7d3-0000f87571e3},IID: {00000001-0000-0000-c000-000000000046} 003f:Call KERNEL32.FindActCtxSectionGuid(00000001,00000000,00000004,00b2e33c,00b2e11c) ret=7eac14e4 003f:Ret KERNEL32.FindActCtxSectionGuid() retval=00000000 ret=7eac14e4 003f:Call ntdll.RtlInitUnicodeString(00b2e030,00b2e082 L"CLSID\\{EA502722-A23D-11D1-A7D3-0000F87571E3}") ret=7eabb537 003f:Ret ntdll.RtlInitUnicodeString() retval=00b2e030 ret=7eabb537 003f:Call ntdll.NtOpenKey(00b2e07c,00020019,00b2e038) ret=7eabb553 003f:Ret ntdll.NtOpenKey() retval=c0000034 ret=7eabb553 003f:Call ntdll.RtlNtStatusToDosError(c0000034) ret=7eabb55e 003f:Ret ntdll.RtlNtStatusToDosError() retval=00000002 ret=7eabb55e 003f:err:ole:CoGetClassObject class {ea502722-a23d-11d1-a7d3-0000f87571e3} not registered 003f:err:ole:CoGetClassObject no class object {ea502722-a23d-11d1-a7d3-0000f87571e3} could be created for context 0x1 003f:Ret ole32.CoCreateInstance() retval=80040154 ret=008d881a 003f:Call user32.MessageBoxA(00000000,00b2e1e8 "CoCreateInstance \n Error code: 154",00901348 "Get ServerPolicy failed",00000000) ret=008d8eee --- snip --- MSDN: http://msdn.microsoft.com/en-us/library/aa374235%28v=VS.85%29.aspx Here is a blog entry which talks about it, with some code example: http://magicmao.wordpress.com/2011/08/05/changing-group-policy-by-c-coding/ $ wine --version wine-1.7.13-118-g0eb6265 Regards -- 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.

1 4

[Bug 39011] New: Sierra Chart hangs when drawing polygon fill line type: gdi32.Polygon()
by wine-bugs＠winehq.org March 3, 2019

March 3, 2019

https://bugs.winehq.org/show_bug.cgi?id=39011 Bug ID: 39011 Summary: Sierra Chart hangs when drawing polygon fill line type: gdi32.Polygon() Product: Wine Version: 1.7.48 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdi32 Assignee: wine-bugs(a)winehq.org Reporter: spam(a)brettcave.net Distribution: --- Created attachment 51965 --> https://bugs.winehq.org/attachment.cgi?id=51965 v1.7.44 WINEDEBUG log segment with THREAD_DETACH errors Sierra Chart is a stock market, forex, and other market price graphing program. They use C/C++ and avoid java and .net. Normally it runs well under wine, but there is a long term issue that they've known about: Drawing chart lines with a polygon fill (Fill Top, Fill Bottom in the program) will hang wine for a minute or 2 but works fine under regular windows. This hanging will release and then hang again shortly after making the chart unusable. I'm using ubuntu 14.04 LTS with wine 1.7.44 from the ppa archive. I've also compiled 1.7.48 32bit using the lxc instructions. I was able to get the X11 socket running inside lxc after some work. Sierra Chart runs at full speed with it. My hardware for testing is a laptop, dual core 2.2ghz AMD K10e, Mobile Radeon HD 4250 using generic linux drivers, and 8g RAM. Sierra Chart isn't known to directly bang video hardware, so chip and driver shouldn't be an issue. This laptop can play 1080i mpeg2 off my DVR faster than normal, so it is capable enough to handle a chart. Both were tested with cleanly created wine prefixes. Sierra Chart is 32bit compiled and normally works fine with wine. I've been able to reproduce the bug by using the polygon fill line type and by scrolling the chart back and forth. If I change the line type to something plain, the freezing problem doesn't happen. The bug is harder to reproduce with debugging activated. It's probably allowing extra time for whatever is causing the hang to finish before it hangs. *** file: wine_SC_THREAD_DETACH.wine1.7.44.log.txt I've attached a small log file segment from ubuntu version 1.7.44: WINEDEBUG=+timestamp,+relay,+seh,+tid,+message,+msgbox,+dll,+loaddll It starts out with the gdi32 draw commands, has the freezing section in the middle, and then continues with the gdi32 draw commands. The problem is from time stamp 1306647.286 to 1306718.051. It's about 71 seconds total. There are a bunch of THREAD_DETACH entries in the log. Sierra Chart support says that graph drawing is not multi threaded and that they don't know what that is. The only other threads are when downloading real time price data updates and loading chart price data from disk. Note: the next 1.7.48 versions were run from inside the 32bit lxc build environment. One thing I noticed when testing with 1.7.48 is that my memory usage bar applet was jumping around a lot during a freeze. I didn't get exact figures but the range was over 3g. That's huge for a 32bit program. I wasn't watching for the first log. *** file: wine_SC_ConsoleLog_wine1.7.48.log.txt This is the regular shell console log. *** file: wine_SC_wine1.7.48.log.txt I've attached a second small log file segment from compiled version 1.7.48: WINEDEBUG=+timestamp,+relay,+seh,+tid,+message,+msgbox,+dll,+loaddll It starts out with the gdi32 draw commands, has a very small freezing section in the middle, and then continues with the regular gdi32 draw commands. The problem is from time stamp 1485052.556 to 1485124.153. It's about 71 seconds total. In this log I didn't see the THREAD_DETACH entries. It was small and clean with no errors reported. I don't know what to make of the difference between the 2 logs. I can see that there's a problem, but I don't have enough programming and debugging skills to understand what is going on. If this looks like a programming error in Sierra Chart, please give me something I can tell them that they won't brush off. ------------- Download Instructions. Download page: http://www.sierrachart.com/index.php?page=doc/SCInstallerList.php The page will list multiple versions ranging from current to past. The file to get is: SierraChartSetupNoCLR.exe The file date in the list: 2015/7/31 The "NoCLR" (No Common Language Runtime) doesn't use poorly supported windows functions and is wine friendly. This is the version Sierra Chart support normally recommends. sha1sum: 4454a0ef2e3a2bb525098ea5620f8d4bb23edb2a SierraChartSetupNoCLR.exe In a week or so, this current version will "probably" be named: 1280SierraChartSetupNoCLR.exe Help / About shows version number 1280. ------------ Account Setup Instructions. Sierra Chart has a free demo account for testing. Their install is almost entirely self contained to a directory and won't scatter files everywhere. Instructions are here: http://www.sierrachart.com/index.php?page=doc/setup.php Step 1: Download program. Since Sierra Chart support isn't going to do anything with this bug, the current version will very likely have it since this is an old bug of unknown age. If not using this link, use the download link above. Step 2: "Create Your Account" to get a free demo account. I recommend something alone the lines of "Wine Debug". They will know what that is. A support ticket will need to be opened to activate the account. They're very easy going with programmers. Just mention that you're someone from the wine debug team. If y'all want more than the 15 day trial, request it there. They will usually activate the account the same day. Support Link: http://www.sierrachart.com/index.php?page=doc/support.html#SCAccounts This is Section #2, instructions in the yellow box with the link. In the future if the trial account expires, open another support ticket, mention that you're with the wine debug team and need to run some more tests. They'll usually reactivate the account the same day. So long as you're actively programming or debugging and not using their product to trade for free, Sierra Chart support is very laid back about continuing accounts. Ignore the rest of the Sierra Chart account steps web page and follow my steps below to reproduce the bug once the demo account is activated. -------------- Steps to reproduce the bug. #create a new prefix WINEPREFIX=/home/user1/.wine3 winecfg Applications / Windows Version: Windows 7 #earlier tests have shown different windows versions don't matter. No library overrides. Turned off Graphics: Allow the window manager to decorate the windows. Sierra Chart has alert sounds, but they are irrelevant for the bug reproduction. "OK" to exit out of winecfg. #install Sierra Chart WINEPREFIX=/home/user1/.wine3 wine SierraChartSetupNoCLR.exe Accept defaults options and locations in the installer. Run when finished. Note: I recommend to run Sierra Chart in normal / non-debug mode the first time as the freezing bug is easier to reproduce. Enter user name and password. When the main window comes up, press "No" at the Data and Trade Service prompt to use demo mode defaults. Hit "Close Log" on "Message Log" to get it out of the way. Menu: File / Find Symbol Expand "Forex". I prefer to select "GBPUSD" as the symbol since it has good volume and is easily recognized. Hit the "Open Intraday Chart" button. Hit the "Close" button to get rid of the find screen. A full screen chart will open and download price data for a minute. Click once in the middle of the chart to select it. Press the keyboard down arrow 11 times. At the very bottom right corner will be a tiny green box with a number in it. Every time the down arrow gets hit, it will decrement and the chart will show more bars per screen. The bar should read "1". If it is red, hit the "End" key on the keyboard. Color doesn't matter much for this reproduction, though. Note: If the hanging problem below gets to be too severe to do anything, only press the down arrow several times to not compress the chart view as much. Maybe go down to "5" instead of "1". Quick side note before the hanging bug gets triggered: Menu: Help / About will show the build number / version number for verification. The latest installer file usually won't have a version number in the name. Menu: Analysis / Studies Hit "Add Custom Study" button at the bottom. Double click to expand "User Contributed Studies". Scroll down to "RSI Bands". Select it and hit "Add". It will show up on the right panel list. This study won't cause the bug alone. It is used to put an extra load on the graph. Hit "Add Custom Study" button again. Scroll down a little to "RSI w/Trend". Select it and hit "Add". It will show up on the right panel list. This study has the polygon fill that will trigger the freezing bug. Note for Bug Settings: Something to point out to come back to later... Select "RSI w/Trend" and hit the "Settings" button. Hit the "Subgraphs" tab at the top. At the top middle will be a "Draw Style" column. This is how the study line types are drawn on the graph. The bug versions will have "Trans. Fill Top" for "Fast MA" and "Trans. Fill Bottom" for "Medium MA". Selecting these two entries and changing them with the "Draw Style" drop down box to "Line" then "Solid" and "1" will allow them to not trigger the bug (but do that later). Changing the two entires to "Fill Top" and "Fill Bottom" will still trigger the bug regardless of transparency settings. For now, don't change the settings for the bug reproduction, but come back to this afterwards. Hit "Cancel" to get out of the settings screen. Hit "OK" on the "Chart Studies" window to get back to the main chart. New lines will be drawn on the screen from the two added studies. The graph "should" come back immediately, but sometimes it will trigger the hanging bug. Click on another virtual desktop and come back or click on a window below Sierra Chart to bring it forwards and then go back to Sierra Chart. If the screen doesn't redraw within a second or two, then the bug was triggered. It will take a minute or two for Sierra Chart to come back. Note that the CPU will be maxed out and RAM usage will be jumping around. To save these settings so far, Menu: File / Save All. Enter a brief chart book name for a file name at the bottom (like "test1"). Afterwards the chart book can be quickly reloaded by that name in the recent files list on the right side of the File menu. This will allow for skipping the "Menu: Analysis / Studies" steps on next program reload. ...That is if the hanging bug isn't triggered again... and again... and again... In wine debug mode, the hanging bug "usually won't" be triggered yet. To manually trigger the hanging bug, use the mouse to grab the horizontal scroll bar at the bottom of the screen and drag it back and forth. This will scroll the chart back and forth causing a lot of redraws. If Sierra Chart stops responding, click on another virtual desktop and come back or click on a window below Sierra Chart to bring it forwards and then go back to Sierra Chart. If the screen doesn't redraw within a second or two, then the bug was triggered. It will take a minute or two for Sierra Chart to come back. Note that the CPU will be maxed out and RAM usage will be jumping around. With the wine debug mode log it is hard to see where the bug was triggered. I use the "+timestamp" option and a stop watch/timer app to note the hang and resume times so they can be matched up later in the debug log. When dragging the chart horizontal scroll bar, they will be surrounted by gdi32 draw commands. In future tests, the Sierra Chart process may have to be killed. To restart it, I go into the drive_c/SierraChart folder and run SierraChart.exe. Sierra Chart will remember your login name and password. When the authentication window pops up, just leave it for a couple seconds and it will go away and the main chart will pop up. Now that the hanging bug has been experienced, the line type can be changed from the Note instructions above to see the comparison with a plain line. -- 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.

1 7

[Bug 38066] New: Memento Mori (Numen: Contest of Heroes): mouse buttons don't work (needs native dinput8)
by wine-bugs＠winehq.org March 3, 2019

March 3, 2019

https://bugs.winehq.org/show_bug.cgi?id=38066 Bug ID: 38066 Summary: Memento Mori (Numen: Contest of Heroes): mouse buttons don't work (needs native dinput8) Product: Wine Version: 1.7.36 Hardware: x86 URL: http://www.4players.de/4players.php/download_info/Down loads/Download/50673/Memento_Mori/Deutsche_Demo.html OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: directx-dinput Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com Distribution: --- Created attachment 50710 --> https://bugs.winehq.org/attachment.cgi?id=50710 terminal output Keyboard is working in the game because I can skip the intro videos by pressing <Esc> and I can move the mouse pointer when the menu appears. Mouse buttons however are not registered thus I can't select a menu option. 'winetricks dinput8' is a workaround. I know of another game from the same publisher that also needs native dinput8 otherwise mouse buttons don't work: Numen: Contest of Heroes. To test the demo you need to install native d3dx9_36 and Windows Media Player 9 or 10. wine-1.7.36-28-ga679cae Fedora 21 XOrg 1.16.3 XFCE 4.10 Memento_Mori_DEMO_setup_GERMAN.exe md5sum: 8eda283807d43ad2a058c397efde7725 -- 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.

1 7

[Bug 35320] New: wine crash in MSVCRT__mbstowcs_l regarding locale, & other minor locale related problems
by wine-bugs＠winehq.org March 3, 2019

March 3, 2019

http://bugs.winehq.org/show_bug.cgi?id=35320 Bug ID: 35320 Summary: wine crash in MSVCRT__mbstowcs_l regarding locale, & other minor locale related problems Product: Wine Version: 1.7.10 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msvcrt Assignee: wine-bugs(a)winehq.org Reporter: htl10(a)users.sourceforge.net Classification: Unclassified Created attachment 47106 --> http://bugs.winehq.org/attachment.cgi?id=47106 The file needed to cause the crash. from r project (http://www.r-project.org/) http://cran.ma.imperial.ac.uk/bin/windows/base/R-2.15.3-win.exe After installing, running: ./wine ~/.wine/drive_c/Program\ Files/R/R-2.15.3/bin/R.exe Then, at the R console prompt, type (having put the attached file at /tmp/1.R): Sys.setlocale("LC_CTYPE", "Chinese") source('z:/tmp/1.R', encoding='UTF8') wine immediately crashes with: -------------------------------------- wine: Unhandled page fault on read access to 0x00000000 at address 0x7eda29af (thread 0030), starting debugger... ... Backtrace: =>0 0x7eda29af MSVCRT__mbstowcs_l+0x5f(wcstr=<couldn't compute location>, mbstr=<couldn't compute location>, count=<couldn't compute location>, locale=<couldn't compute location>) [/home/Nobak-Hin-Tak/tmp-git/wine/dlls/msvcrt/mbcs.c:2140] in msvcrt (0x0440a168) 1 0x7eda2b06 MSVCRT_mbstowcs+0x35(wcstr="as a &Metafile CTRL+W", mbstr=0x0(nil), count=0x64) [/home/Nobak-Hin-Tak/tmp-git/wine/dlls/msvcrt/mbcs.c:2161] in msvcrt (0x0440a198) 2 0x6355b525 in rgraphapp (+0x1b524) (0x00030046) 0x7eda29af MSVCRT__mbstowcs_l+0x5f [/home/Nobak-Hin-Tak/tmp-git/wine/dlls/msvcrt/mbcs.c:2140] in msvcrt: movzbl 0x0(%eax),%eax 2140 if(mbstr[size] == '\0') ... ---------------------------------------- I assume this info in the backtrace should be enough to address the crash. FYI, the slightly unusual procedure is because under R under Vista in an English locale doesn't like to plot graphs with non-latin annotations/texts. The above procedure when used under Vista on British English windows would result in R displaying an almost empty plot with a chinese title. Native R on linux does not need the setlocale part to plot utf8-based texts. Also R on Vista accepts 'Sys.setlocale("LC_CTYPE", "Chinese_China.950")'. I only realized that trying to set traditional chinese [950] in a simplified chinese region [china] is wrong when it is rejected on linux; but R on Vista accepts this. ------------ Warning message: In Sys.setlocale("LC_CTYPE", "Chinese_China.950") : OS reports request to set locale to "Chinese_China.950" cannot be honored ------------ When R is running on Vista, it reports the locale as "English_United Kingdom.1252". But under Linux (in en_GB.utf8 locale), R warns of ----------- During startup - Warning messages: 1: Setting LC_TIME=en_GB.utf8 failed 2: Setting LC_MONETARY=en_GB.utf8 failed ----------- So three locale related issue: - a crash in msvcrt - R under Vista accepts "Chinese_China.950" but R under wine does not. - there are locale-related warning messages from R on start up when running under wine. -- 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.

1 13

[Bug 40160] New: cant install mobogenie
by wine-bugs＠winehq.org March 3, 2019

March 3, 2019

https://bugs.winehq.org/show_bug.cgi?id=40160 Bug ID: 40160 Summary: cant install mobogenie Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: madscientistkustomz(a)gmx.com Distribution: --- Created attachment 53662 --> https://bugs.winehq.org/attachment.cgi?id=53662 trace log problem installing MOBOGENIE for ubuntu -- 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.

1 9

[Bug 40208] New: Steup installation of CEGID BUISINESS LINE failed.
by wine-bugs＠winehq.org March 3, 2019

March 3, 2019

https://bugs.winehq.org/show_bug.cgi?id=40208 Bug ID: 40208 Summary: Steup installation of CEGID BUISINESS LINE failed. Product: Wine Version: 1.9.4 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: msi Assignee: wine-bugs(a)winehq.org Reporter: christian.briard(a)gmx.com Distribution: --- Created attachment 53723 --> https://bugs.winehq.org/attachment.cgi?id=53723 MSI log Executing an installation of CEGID BUISINESS LINE failed with a log text (see attached files). "Install: C:\windows\System32\msiexec.exe /q /i "Z:\home\cbriard\CBL\PRODUCTS\AIDEBL.MSI" INSTALLDIR="C:\Program Files\Cegid\Cegid Business Line\" /norestart Install : 1603 - C:\windows\System32\msiexec.exe - Erreur en exécution du programme" Here enclosed a trace file to. Any idea of what is going wrong ? Christian. -- 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.

1 15

[Bug 38402] New: glDebugMessageCallback is broken
by wine-bugs＠winehq.org March 3, 2019

March 3, 2019

https://bugs.winehq.org/show_bug.cgi?id=38402 Bug ID: 38402 Summary: glDebugMessageCallback is broken Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: opengl Assignee: wine-bugs(a)winehq.org Reporter: chris.kcat(a)gmail.com Distribution: --- According to the KHR_debug extension spec, the function glDebugMessageCallback takes a function pointer callback with the type: typedef void (APIENTRY *GLDEBUGPROC)(GLenum source, GLenum type, GLuint id, GLenum severity, GLsizei length, const GLchar* message, const void* userParam); https://www.opengl.org/registry/specs/KHR/debug.txt In particular, it notes that the function callback uses the same calling convention as the other GL functions. The problem is that on Windows, GL uses the stdcall calling convention, while on Linux it uses cdecl. Wine's glDebugMessageCallback thunk passes the callback through as-is, so the system's libGL tries to call an stdcall function as though it was cdecl, causing it to crash upon returning. Another problem is that the spec says: "When DEBUG_OUTPUT_SYNCHRONOUS is disabled, the driver is optionally allowed to concurrently call the debug callback routine from potentially multiple threads, including threads that the context that generated the message is not currently bound to." meaning the callback can be called on threads other than the one OpenGL is being used on. This is a problem because it may be called on one or more internal driver threads that were not created using the Windows API, and if the callback function tries to do anything that relies on Windows-related thread information, it won't be there. -- 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.

1 20

[Bug 39051] New: TabbedTextOut() incorrect output on tab character
by wine-bugs＠winehq.org March 3, 2019

March 3, 2019

https://bugs.winehq.org/show_bug.cgi?id=39051 Bug ID: 39051 Summary: TabbedTextOut() incorrect output on tab character Product: Wine Version: 1.7.29 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: wine(a)goabq.org Distribution: --- Created attachment 52021 --> https://bugs.winehq.org/attachment.cgi?id=52021 testcase (tto.exe) and files to build it Tab characters do not output correctly when they are output one at a time. This is much worse using a memory device context than a screen device context. Attached is a testcase. It outputs text to a window using 2 different methods. Clicking in the client area toggles the method. When iterating over each character, TabbedTextOut() produces apparently garbage from the previous line instead of filling the rectangle appropriately as windows does. When drawing the line in a single call, the behavior is as expected. Spaces do not suffer from this problem (illustrated also by the testcase). -- 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.

1 19