March 2017 - Wine-Bugs - list.winehq.org

[Bug 37002] New: Plogue chipsound registration fails
by wine-bugs＠winehq.org Aug. 29, 2026

Aug. 29, 2026

http://bugs.winehq.org/show_bug.cgi?id=37002 Bug ID: 37002 Summary: Plogue chipsound registration fails Product: Wine Version: 1.7.23 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bique.alexandre(a)gmail.com Plogue Chipsound registration fails: fixme:process:GetProcessWorkingSetSize (0xffffffff,0x33e754,0x33e758): stub fixme:process:GetProcessWorkingSetSize (0xffffffff,0x33e754,0x33e758): stub fixme:ole:RemUnknown_QueryInterface No interface for iid {00000019-0000-0000-c000-000000000046} Here is a link to the software: http://www.plogue.com/products/chipsounds/ -- 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.

2 4

[Bug 32547] New: ShowMiiWads: Crashes when installing WADs
by wine-bugs＠winehq.org Aug. 29, 2026

Aug. 29, 2026

http://bugs.winehq.org/show_bug.cgi?id=32547 Bug #: 32547 Summary: ShowMiiWads: Crashes when installing WADs Product: Wine Version: 1.5.20 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: d.schwimer(a)hotmail.com Classification: Unclassified Created attachment 42952 --> http://bugs.winehq.org/attachment.cgi?id=42952 Wine's output following the crash Using a program called ShowMiiWads v1.4: http://wiibrew.org/wiki/ShowMiiWads The program is a sort of utility used to inject WAD files into a NAND backup of a Wii system. Steps to produce issue: 1. Created a "Common Key.bin" file using Tools > Create Common Key and typin '45e'. 2. Selected Options > Change NAND Backup Path, and navigated to the desired folder. 3. Selected View > ShowMiiNand. 4. Right-clicked an item from the list, selected "Install", then "File", then selected a WAD file. 5. Program crashes with attached output. -- 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.

2 6

[Bug 32363] New: Fonts are smoothed
by wine-bugs＠winehq.org Aug. 29, 2026

Aug. 29, 2026

http://bugs.winehq.org/show_bug.cgi?id=32363 Bug #: 32363 Summary: Fonts are smoothed Product: Wine Version: 1.5.18 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: sworddragon2(a)aol.com Classification: Unclassified After upgrading from Wine 1.5.17 to 1.5.18 the fonts are smoothed (even on a new profile). I have already looked at "HKEY_CURRENT_USER\\Control Panel\\Desktop\\FontSmoothing" but it is already set to 0. If it is important: My system uses the ttf-mscorefonts-installer package with some rules to look like the fonts of a Windows system. -- 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.

2 20

[Bug 39158] New: strange behaviour of WinForms components using MS .net
by wine-bugs＠winehq.org Aug. 29, 2026

Aug. 29, 2026

https://bugs.winehq.org/show_bug.cgi?id=39158 Bug ID: 39158 Summary: strange behaviour of WinForms components using MS .net Product: Wine Version: 1.7.50 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mayth(a)arcor.de Distribution: --- Created attachment 52192 --> https://bugs.winehq.org/attachment.cgi?id=52192 executable of the demo The bug was detected on a system as follows: * Linux Mint 17.2 64-bit * Wine 1.7.50 with a 32-bit environment * orginal Microsoft .net 4.0 framework installed in Wine (using winetricks) Attached is a simple .net program which is written in C# and consists of several small source files. The main windows of this program contains a component of type System.Windows.Forms.StatusStrip with property GripStyle=Visible. Moreover, the main window contains a component of type System.Windows.Forms.ToolTip which is connected with some other GUI component (which is a simple button in this demo). The compiled exe file is attached. If it is executed on a Windows system, the status strip shows a grip which can be used for resizing the window (additionally to the actual borders of the window). Moreover, the tooltip attached to the button works as expected. If the same exe file is executed on a Linux system as described above (i.e. Wine using the original MS .net 4.0 framework), the behaviour is different. The status strip does not show an additional grip. However, the position where the grip should be diplayed is sensible to mouse actions. But it does not cause resizing of the window but some strange resizing effect on the other GUI elements of the window (in this demo on the button). Moreover, the tooltip attached to the button steals the focus from the window (this is in particular a problem for text edit boxes as clicking on the box leads to the tool tip stealing the focus from the edit box, so you cannot really enter text...). By the way, the tool tip which is attached to the status strip element works fine (but this is not a connected element of type Forms.ToolTip but is implemented by the StatusStrip itself...). The same executable using the same .net framework behaves in different ways, depending on whether this is run on windows or on linux using wine. Therefore, the reason for the difference must be found within 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.

2 6

[Bug 39065] New: thread.c, line 403: Crash when attaching debugger (EXC_BAD_ACCESS, EXC_i386_GPFLT)
by wine-bugs＠winehq.org Aug. 29, 2026

Aug. 29, 2026

https://bugs.winehq.org/show_bug.cgi?id=39065 Bug ID: 39065 Summary: thread.c, line 403: Crash when attaching debugger (EXC_BAD_ACCESS, EXC_i386_GPFLT) Product: Wine Version: 1.7.49 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: philippe.groarke(a)gmail.com Created attachment 52035 --> https://bugs.winehq.org/attachment.cgi?id=52035 Variables pthread_join crashes when attaching debugger. This makes it impossible to debug anything. I am using lldb and/or xcode directly. Winedbg also crashes, but I cannot retrieve anything with it. I attached the state of local variables when it crashes (in exit_thread). I've also attached the variables of call_thread_func and start_thread. libsystem_pthread.dylib`pthread_join$UNIX2003: 0x9776dedc <+0>: pushl %ebp 0x9776dedd <+1>: movl %esp, %ebp 0x9776dedf <+3>: pushl %ebx 0x9776dee0 <+4>: pushl %edi 0x9776dee1 <+5>: pushl %esi 0x9776dee2 <+6>: subl $0x3c, %esp 0x9776dee5 <+9>: calll 0x9776deea ; <+14> 0x9776deea <+14>: popl %esi 0x9776deeb <+15>: movl 0x8(%ebp), %edi -> 0x9776deee <+18>: movl %gs:0x0, %ebx Small backtrace: #0 0x9776deee in pthread_join$UNIX2003 () #1 0x7bcb0358 in exit_thread at wine/dlls/ntdll/thread.c:403 #2 0x7bca0b65 in call_thread_func_wrapper () #3 0x7bca3f6b in call_thread_func at wine/dlls/ntdll/signal_i386.c:2732 #4 0x7bca0b22 in call_thread_entry_point () #5 0x7bcb0f6f in start_thread at wine/dlls/ntdll/thread.c:443 #6 0x97769e13 in _pthread_body () #7 0x97769d89 in _pthread_start () #8 0x97767e52 in thread_start () Could be many things, open for suggestions. -- 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.

2 15

[Bug 39044] New: Skyforge: In-game browser crash (possibly crypt/ntdll.FILE_CreateFile related).
by wine-bugs＠winehq.org Aug. 29, 2026

Aug. 29, 2026

https://bugs.winehq.org/show_bug.cgi?id=39044 Bug ID: 39044 Summary: Skyforge: In-game browser crash (possibly crypt/ntdll.FILE_CreateFile related). Product: Wine Version: 1.7.48 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: philippe.groarke(a)gmail.com Created attachment 52009 --> https://bugs.winehq.org/attachment.cgi?id=52009 Good backtrace Bug: In-game browser (called Aelinent) crashes on load. Repro: Go to community tab, click Aelinet, crash. (You may need to exit tab and repeat a few times). Attached is a backtrace. I would definitely appreciate some tips/ideas to further pin-point the crash, ty :) After spending a LONG time analyzing logs and trying different combinations of debugs, I believe it might be file creation, or crypt (file creation). These are wild guesses. Of interest: +tid,seh,relay --> 0088:Call KERNEL32.WriteFile(000014c8,d4e6e8a0,00000055,d5f2f310,00000000) ret=0489a01e 0088:Ret KERNEL32.WriteFile() retval=00000001 ret=0489a01e 0088:Call KERNEL32.ReleaseMutex(000014bc) ret=0489a033 0088:Ret KERNEL32.ReleaseMutex() retval=00000001 ret=0489a033 0088:Call KERNEL32.IsDebuggerPresent() ret=048c35c6 0088:Ret KERNEL32.IsDebuggerPresent() retval=00000000 ret=048c35c6 0088:trace:seh:raise_exception code=80000003 flags=0 addr=0x48c35e0 ip=048c35e1 tid=0088 0088:trace:seh:raise_exception eax=00000000 ebx=00000010 ecx=00000055 edx=00000000 esi=d5f2f480 edi=d5f2f478 0088:trace:seh:raise_exception ebp=d5f2f488 esp=d5f2f2fc cs=001b ds=0023 es=0023 fs=113f gs=000f flags=00000246 0088:trace:seh:call_stack_handlers calling handler at 0x7bc913a0 code=80000003 flags=0 More file creation, though it reports success... +tid,+seh,+ntdll,+mshtml,+wininet,+crypt,+cryptasn,+cryptdlg,+cryptdll,+cryptnet,+cryptui 008c:trace:ntdll:NtQueryInformationFile (0x14c8,0xc6fff270,0xc6fff260,0x00000008,0x00000014) 008c:trace:ntdll:NtSetInformationFile (0x14c8,0xc6fff270,0xc6fff268,0x00000008,0x0000000e) --> 008c:trace:ntdll:NtWriteFile (0x14c8,0x0,0x0,0x0,0xc6fff2b8,0xc77d3ae0,0x00000055,0x0,0x0)! 008c:trace:ntdll:NtWriteFile = SUCCESS (85) 008c:trace:seh:raise_exception code=80000003 flags=0 addr=0x48c35e0 ip=048c35e1 tid=008c 008c:trace:seh:raise_exception eax=00000000 ebx=00000010 ecx=00000001 edx=95e376d2 esi=c6fff480 edi=c6fff478 008c:trace:seh:raise_exception ebp=c6fff488 esp=c6fff2fc cs=001b ds=0023 es=0023 fs=1117 gs=000f flags=00000246 008c:trace:seh:call_stack_handlers calling handler at 0x7bc923c0 code=80000003 flags=0 ... wine: Unhandled exception 0x80000003 in thread 8c at address 0x48c35e0 (thread 008c), starting debugger... So If I go back a long time before these errors, looking at the crashed thread mainly, some interesting things show up. The last file created: 008c:trace:ntdll:FILE_CreateFile handle=0xc6ffebfc access=80000000 name=L"\\??\\C:\\users\\pgroarke\\Local Settings\\Temporary Internet Files\\Content.IE5\\CDJK03WH\\DigiCertHighAssuranceEVRootCA[0]" objattr=00000040 root=0x0 sec=0x0 io=0xc6ffec00 alloc_size=0x0 attr=00000080 sharing=00000001 disp=1 options=00000060 ea=0x0.0x00000000 Cause? There are special chars in there (STX ESC SOH ETX ENQ ACK): 008c:trace:crypt:Base64WithHeaderAndTrailerToBinaryA Can't find -----BEGIN in 0‚0‚0 *†H†÷ . Hope this helps narrow it down. I will continue digging. -- 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.

2 8

[Bug 38954] New: One barrel shotgun gets rendered with wrong orientation on Serious Sam HD: The Second Encounter
by wine-bugs＠winehq.org Aug. 29, 2026

Aug. 29, 2026

https://bugs.winehq.org/show_bug.cgi?id=38954 Bug ID: 38954 Summary: One barrel shotgun gets rendered with wrong orientation on Serious Sam HD: The Second Encounter Product: Wine Version: 1.7.46 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: winehq(a)iooioio.orion.uberspace.de Distribution: --- On Serious Sam HD: The Second Encounter one of the weapons gets rendered with a wrong orientation (see attachment). I haven't systematically checked them all but all the other weapons I've seen so far seem to render correctly. I'm using the proprietary nvidia drivers (352.21). -- 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.

2 8

[Bug 21539] New: Using "Bare Streams" console mode with SRCDS does not work.
by wine-bugs＠winehq.org Aug. 29, 2026

Aug. 29, 2026

http://bugs.winehq.org/show_bug.cgi?id=21539 Summary: Using "Bare Streams" console mode with SRCDS does not work. Product: Wine Version: 1.1.37 Platform: x86 URL: http://srcds.com OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: laurikoivunen(a)hotmail.com SRCDS ( Source Dedicated Server ) is designed to run both in GUI and CLI modes. However, when trying to run the server in pure console without X and using "bare streams" as described here ( http://www.winehq.org/docs/wineusr-guide/cui-programs ) I still receive the error: DISPLAY='' WINEDEBUG=+console wine srcds.exe -console ... trace:console:AllocConsole () err:curses:WCCURSES_InitBackend (n)curses was not found. err:wineconsole:WINECON_Init failed to init. This is probably due to srcds running in "hybrid" mode where it is marked as a GUI application, but uses AllocConsole to create a console hence resulting in a new console creation, which currently fails. As a workaround I stubbed AllocConsole and only returned TRUE. This allows the application to start and reach a point where it tries to read the console and where it then fails due to wine not being able to read from the console. Could you add an option for true "bare streams" and so that input would also work? ps: I know that there is a linux version of SRCDS but there are no linux binaries for the server I am trying to run. This bug forces a lot of server hosters run X on their servers to be able to run SRCDS in wine. The server is free to download and use. -- 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.

2 8

[Bug 34748] New: Integrate GVFS just like you have integrated CUPS
by wine-bugs＠winehq.org Aug. 29, 2026

Aug. 29, 2026

http://bugs.winehq.org/show_bug.cgi?id=34748 Bug #: 34748 Summary: Integrate GVFS just like you have integrated CUPS Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: netapi32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: n296869(a)rtrtr.com Classification: Unclassified Wine already integrates with CUPS to allow applications to print documents exactly as they do it in Windows. My proposal is to integrate Wine with GVFS to let applications automatically mount network shares. In Windows applications can access network shares by just specifying a path like "//server/share". But in Wine you first need to manually create a link to "~/.wine/dosdevices/unc/server/share", and only then all applications will be able to access this particular server. -- 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.

2 7

[Bug 35558] New: Rift crashes when VT switch > 60 sec
by wine-bugs＠winehq.org Aug. 29, 2026

Aug. 29, 2026

http://bugs.winehq.org/show_bug.cgi?id=35558 Bug ID: 35558 Summary: Rift crashes when VT switch > 60 sec Product: Wine Version: 1.7.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: rift-wine(a)yopmail.com Classification: Unclassified Created attachment 47482 --> http://bugs.winehq.org/attachment.cgi?id=47482 Standard Output Open Rift in a secondary X server. Switch to primary X server : if time passed on primary X server is greater than 60 seconds, Rift will crash on secondary X server. -- 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.

2 6