June 2026 - Wine-Bugs - list.winehq.org

[Bug 59929] New: Excessive CPU usage in winedevice.exe and wineserver process with high polling rate gamepads
by WineHQ Bugzilla June 28, 2026

June 28, 2026

http://bugs.winehq.org/show_bug.cgi?id=59929 Bug ID: 59929 Summary: Excessive CPU usage in winedevice.exe and wineserver process with high polling rate gamepads Product: Wine Version: 11.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: wineserver Assignee: wine-bugs(a)list.winehq.org Reporter: deus.exe93(a)gmail.com Distribution: --- Description: Playing games using gamepads with high polling rate joysticks (1KHz) will cause winedevice & wineserver to massively spike CPU usage How to reproduce: - Use any gamepads that are *equipped with 1KHz joysticks* (very common with Gamesir/Flydigi/8Bitdo that use HE/TMR joysticks) . - Open any game with Wine, and at the same time open any system monitoring tool. - Wiggle both right and left joysticks. Watch the CPU usage of `wineserver` & `winedevice` process spiking significantly as long as the joysticks are being used - The issue does not present when using gamepad with default low polling rate joysticks (125Hz) Tested Wine version : 11.0-11.11, 10.11-10.20 This problem might, or might not be similar to the one reported in this regarding mouse with high polling rate : https://bugs.winehq.org/show_bug.cgi?id=46976 however as far as current version of Wine in Arch repository (11.11-1.1) it's still present. The issue is exacerbated if the games that are being played are CPU intensive, since both are competing for CPU time. Which in turn causes noticeable input delays, and sometimes burst of queued inputs after that delay ends. Example of similar problems other people have been reporting : https://www.reddit.com/r/linux_gaming/comments/1srzbgm/8bitdoo_controller_l… https://www.reddit.com/r/Bazzite/comments/1svvq33/i_get_a_strange_cpu_usage… https://www.reddit.com/r/Fedora/comments/1rrvmic/games_stutter_and_have_inp… This is quite problematic for gamepads that do not provide the ability to change the default polling rate (like 8bitdo and Flydigi Vader 3 Pro that I used, and some Gamesir models). This issue does not affect native linux games. No significant CPU spikes on any process observed when using the high polling rate joysticks in them. -- 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 1

[Bug 44203] New: SlingPlayer 2 crashes under Wine Staging
by wine-bugs＠winehq.org June 28, 2026

June 28, 2026

https://bugs.winehq.org/show_bug.cgi?id=44203 Bug ID: 44203 Summary: SlingPlayer 2 crashes under Wine Staging Product: Wine-staging Version: 2.21 Hardware: x86 URL: http://download.slingmedia.com/player/pc/SlingPlayer_2 .0.4522_Setup-Global.exe OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: imwellcushtymelike(a)gmail.com CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: Ubuntu Created attachment 59971 --> https://bugs.winehq.org/attachment.cgi?id=59971 Wine Staging 2.21 console output Under Wine Staging 2.21, SlingPlayer 2.0 crashes in a way that it does not under vanilla Wine 3.0-rc2. I tried patching latest git with the dxva2 patches, as that seems to be the last thing mentioned in the log before the crash but when I did that it doesn't seem to be used: 0009:trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\dxva2.dll" at 0x7c020000: builtin 0009:trace:loaddll:free_modref Unloaded module L"C:\\windows\\system32\\dxva2.dll" : builtin I guess something needs setting in the registry or the likes. To get this far, the following overrides are needed: WINEARCH=win32 - Bug 35268 / Bug 35276 quartz - Bug 18556 wmp9 - Bug 28669 mf - Bug 44201 The application crashes on load so you do not need a Slingbox to test. 01:00.0 VGA compatible controller: NVIDIA Corporation NV34 [GeForce FX 5200] (rev a1) -- 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.

3 6

[Bug 40437] New: Smartdraw 2013 won't run, crashes.
by wine-bugs＠winehq.org June 28, 2026

June 28, 2026

https://bugs.winehq.org/show_bug.cgi?id=40437 Bug ID: 40437 Summary: Smartdraw 2013 won't run, crashes. Product: Wine Version: 1.9.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bbaker6212(a)gmail.com Distribution: --- Created attachment 54188 --> https://bugs.winehq.org/attachment.cgi?id=54188 wine crash dump file Nothing to say really. Trying to run it and it crashes right away. -- 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.

3 8

[Bug 37258] New: Editor via Wine (notepad) no Numlock numbers avaiable
by wine-bugs＠winehq.org June 28, 2026

June 28, 2026

https://bugs.winehq.org/show_bug.cgi?id=37258 Bug ID: 37258 Summary: Editor via Wine (notepad) no Numlock numbers avaiable Product: Wine Version: 1.6.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: info(a)mk-news.com Editor via Wine (notepad) no Numlock numbers avaiable testet with my own programm: "VK-LEFT" comes for key 4 on numeric Key if Numlock on or off Leafpad do it correct wine 1.6.2 via VNC4Server on LXDE-desktop -- 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 59768] New: IsoBuster 5.8 fails browsing isos
by WineHQ Bugzilla June 28, 2026

June 28, 2026

http://bugs.winehq.org/show_bug.cgi?id=59768 Bug ID: 59768 Summary: IsoBuster 5.8 fails browsing isos Product: Wine Version: 11.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: p.glizniewicz(a)gmail.com Distribution: --- Created attachment 80973 --> http://bugs.winehq.org/attachment.cgi?id=80973 Screenshot of the failure message IsoBuster 5.8 (https://appdb.winehq.org/objectManager.php?sClass=application&iId=1384) fails with "List capacity out of bounds (10)" when trying to browse most isos. I've asked the developer and confirmed, that the message comes from VCL (it's a C++Builder app), so this might be not IsoBuster specific. I've tested multiple versions of Wine, ranging from 7.0.9, through 9.0.1, 11.0 to 11.8, and it always fails in the same way. Also have tried switching compatibility from Windows 10 to Windows 7, and it didn't help. The app works fine on Windows, it's also not something new, it failed this way for all the 5.x versions I've tried. Here's an iso file that will trigger the error: https://archive.org/details/dmx-6-firec-1 . Just open it with IsoBuster and try to browse into the ISO filesystem in the left panel. -- 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 2

[Bug 59925] New: WPF (.NET 8) renders U+002D (HYPHEN-MINUS) as .notdef ("tofu") for some fonts under Wine — public DirectWrite is correct; defect is in WPF's font-fallback path
by WineHQ Bugzilla June 28, 2026

June 28, 2026

http://bugs.winehq.org/show_bug.cgi?id=59925 Bug ID: 59925 Summary: WPF (.NET 8) renders U+002D (HYPHEN-MINUS) as .notdef ("tofu") for some fonts under Wine — public DirectWrite is correct; defect is in WPF's font-fallback path Product: Wine Version: 11.10 Hardware: x86-64 OS: MacOS Status: UNCONFIRMED Severity: normal Priority: P2 Component: dwrite Assignee: wine-bugs(a)list.winehq.org Reporter: robowens(a)me.com Under Wine, WPF (.NET 8) renders U+002D (HYPHEN-MINUS) as .notdef ("tofu") for some fonts (Segoe UI, Eurostile Next LT Pro) while rendering it correctly for others (Futura PT). Letters, digits and spaces always render. WPF itemizes the line and splits it at every hyphen, orphans the hyphen into its own run, and its font-fallback for that run fails to produce a glyph — the box is laid down without the hyphen ever being shaped. The public DirectWrite APIs are NOT broken for U+002D (see Negative controls below): IDWriteTextLayout, IDWriteFontFallback::MapCharacters, IDWriteFont::HasCharacter(0x2d) and IDWriteFontFace::GetGlyphIndices all resolve U+002D correctly for these exact fonts. The defect is in the font-fallback path WPF exercises under Wine (which the trace shows also drives gdi32 font-linking), not the public dwrite layout/shaping surface. Component may therefore belong to gdi32 rather than dwrite — triage's call. VERSIONS REPRODUCED Reproduced on BOTH vanilla wine-devel 11.10 and wine-staging 11.10 (Gcenx macOS builds, osx64 — same upstream release, differing only by the staging patchset). The +dwrite,+font trace signature is byte-identical on the two: line split at every hyphen, the hyphen orphaned into a run that never reaches GetGlyphs (zero L"-" runs), HasCharacter(0x2d) probed during fallback. So this is upstream Wine, not a staging artifact. PLATFORM macOS 26 / Darwin 25.5, x86-64 under Rosetta 2. .NET 8 WPF (Microsoft.WindowsDesktop.App 8.0.28), software rendering (HKCU\Software\Microsoft\Avalon.Graphics\DisableHWAcceleration=1). STEPS TO REPRODUCE 1. Build the attached WPF reproducer (Program.cs + repro.csproj) on any OS with a .NET SDK (EnableWindowsTargeting lets non-Windows hosts build net8.0-windows): dotnet publish -c Release -o out 2. Run under Wine: WINEPREFIX=/path/to/prefix \ DOTNET_EnableWriteXorExecute=0 LIBGL_ALWAYS_SOFTWARE=1 \ WINEDLLOVERRIDES="mshtml=d" \ wine out/HyphenRepro.exe (WPF needs software rendering under Wine — set HKCU\Software\Microsoft\Avalon.Graphics\DisableHWAcceleration=1 or the window paints black.) 3. The window draws "A-B-C NL-C4-1" in five font/style combinations. ACTUAL RESULT Each U+002D renders as the .notdef box for some fonts; letters/digits/spaces render fine. Font-dependent, not universal, not italic-specific (see attachment repro-output.png): [1] Segoe UI, normal -> hyphen tofu [2] Eurostile Next LT Pro, normal -> hyphen tofu [3] Eurostile Next LT Pro, italic (oblique-sim) -> hyphen tofu [4] Futura PT Book, italic -> renders correctly [5] Eurostile Next LT Pro (private collection) -> hyphen tofu That Segoe UI normal drops the hyphen while Futura renders it in the same window points at the font-fallback path, not the codepoint. EXPECTED RESULT The hyphen renders for every line (as on native Windows / native .NET). ON-SCREEN vs OFFSCREEN (RenderTargetBitmap) — backend isolation Run with --render (offscreen RenderTargetBitmap; no window, no winemac.drv surface) the reproducer drops ONLY the Segoe line; the Eurostile lines render their hyphen. Same machine, same Wine, same fonts, same text (see attachment repro-offscreen-render.png): Line / font On-screen window Offscreen RTB [1] Segoe normal tofu tofu [2] Eurostile normal tofu renders [3] Eurostile italic tofu renders [4] Futura italic renders renders [5] Eurostile (file) tofu renders This split is identical on vanilla wine-devel 11.10 and wine-staging 11.10. Two consequences: - The core defect is NOT in Wine's graphics/presentation backend. The Segoe U+002D tofu reproduces in the offscreen RTB path (WPF software MIL rasterizer to a bitmap, never touches winemac.drv) — so the hyphen-dropping lives in the platform-independent WPF text/font-fallback layer. - The extra Eurostile tofu is specific to the on-screen presentation path (GDI GetGlyphOutline route the trace shows), separate from the itemization defect that drops the hyphen for Segoe everywhere. ANALYSIS (WINEDEBUG=+dwrite,+font) - dwritetextanalyzer_GetGlyphs is called per run; WPF's itemization splits the line at every U+002D. For "[1] Segoe normal A-B-C NL-C4-1" the runs reaching GetGlyphs are L"...A", L"B", L"C NL", L"C4", L"1" — spaces stay inside a run, only hyphens break it. The split is identical on all five lines, including Futura (renders fine), so the split itself is not the bug. - The hyphen is orphaned into its own run that never reaches GetGlyphs — zero L"-" runs in the entire trace. The hyphen is never shaped; the box is laid down by WPF's fallback, not by dwrite glyph mapping. - dwritefont_HasCharacter(font, 0x2d, ...) is probed during fallback. The trace logs the probe inputs but not the boolean result, so it was tested directly (Negative controls): HasCharacter(0x2d) returns TRUE for these fonts. The failure is downstream of the coverage check, inside WPF's fallback bookkeeping under Wine. - The fonts contain the glyph: U+002D -> 'hyphen' is in every cmap subtable (verified with fontTools for Eurostile OTTO/CFF, Futura, Roboto) and at runtime by GetGlyphIndices (Eurostile->15, Futura->14, Tahoma->16). NEGATIVE CONTROLS (pure DirectWrite — why these localize the bug) Attachments repro_dwrite.cpp and repro_fallback.cpp drive the public DirectWrite APIs directly (no .NET/WPF/window) over the same "A-B-C NL-C4-1" and fonts (incl. the brand .otf loaded as a private/custom collection, as WPF loads them). All pass — none reproduces the bug: IDWriteTextLayout (system family) -> one unsplit run, shaped — OK IDWriteTextLayout (Eurostile/Futura from .otf) -> real glyph shaped — OK IDWriteFontFallback::MapCharacters -> maps '-' to Tahoma, has=yes — OK IDWriteFont::HasCharacter(0x2d) -> true — OK IDWriteFontFace::GetGlyphIndices(0x2d) -> real glyph id (15/14/16) — OK The public DirectWrite surface is correct for U+002D on these fonts. Combined with the WPF reproduction, the defect is in WPF/PresentationCore's font-fallback path under Wine (and the gdi32 font-linking it drives), not in dwrite's public layout/shaping APIs. CONFIRMED IN HOST APP (Q-SYS Designer 10.4.0) The same defect renders every hyphenated schematic component label (NL-C4-1, CX-Q..., Display-Amp) as boxes. A +dwrite,+font trace of the running Designer: - IDWriteFontFallback::MapCharacters calls = 0 — the Designer uses WPF/PresentationCore's OWN fallback, not the public dwrite fallback API. - ~45x dwritefont_HasCharacter(..., 0x2d, ...) iterating its candidate font list, plus ~29k GDI GetGlyphOutline calls; the orphaned hyphen never reaches GetGlyphs. - Brand fonts load from C:\windows\fonts (registered or not) — not a missing-/ private-font issue. Font-side workarounds do not fix the host app (tested against the live prefix): Wine's Replacements key is ignored by dwrite; a font file-swap has no effect; and registering the brand fonts fixes a plain WPF TextBlock but NOT the Designer (its schematic always routes the hyphen through the broken WPF-internal fallback regardless of registration). So this needs a Wine-side fix, not a font/config workaround. NOTES FOR TRIAGE - Public DirectWrite APIs verified correct for U+002D (Negative controls) — not a basic dwrite shaping/layout bug. Reproduction is WPF-only; defect is in the font-fallback path WPF drives under Wine (dwrite-internal and/or gdi32 font-linking). Component may need to move from dwrite to gdi32. - Upstream confirmed: reproduces on vanilla wine-devel 11.10, not just staging (identical trace signature). Not a staging-patch artifact. - Latest version tested = 11.10, the newest macOS binary available at filing (Gcenx wine-devel/staging packages); upstream 11.11 has no macOS package yet. The only font/glyph-adjacent change in wine-11.10..wine-11.11 (225 commits) is "win32u: Fixed incorrect glyph outline size" — likely unrelated to the WPF font-fallback itemization (the hyphen never reaches GetGlyphs), but a retest candidate. A retest on 11.11+ will follow once a macOS build ships. - Linux not yet tested: reporter is on Apple Silicon, where x86-64 Wine will not boot under Docker/qemu — Wine's anon_mmap_fixed page-alignment assertion fails against the host's 16 KB pages (qemu: uncaught target signal 6), a hard incompatibility, not a config issue. The reproducer is OS-portable (cross-builds via EnableWindowsTargeting, no macOS dependencies) and is expected to reproduce on Linux/X11. The offscreen RenderTargetBitmap reproduction already isolates the core case away from winemac.drv, which is the main thing a Linux run would show. - Per-font divergence has three tiers: Segoe tofus everywhere (on-screen and offscreen RTB); Eurostile tofus on-screen only; Futura never. All five lines itemize identically, so the divergence is in WPF's per-font fallback bookkeeping (and, for Eurostile, the on-screen glyph-rendering path), not the run split. ATTACHMENTS (added after filing) - Program.cs, repro.csproj — canonical WPF reproducer (no-arg = window; --render <out.png> = offscreen RTB). - repro-output.png — on-screen output (wine-staging 11.10, macOS). - repro-offscreen-render.png — offscreen --render output (vanilla wine-devel 11.10). - repro_dwrite.cpp, repro_fallback.cpp — pure-DirectWrite negative controls. -- 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 10

[Bug 9901] New: GetMonitorInfo returns wrong work area
by wine-bugs＠winehq.org June 28, 2026

June 28, 2026

http://bugs.winehq.org/show_bug.cgi?id=9901 Summary: GetMonitorInfo returns wrong work area Product: Wine Version: CVS/GIT Platform: Other OS/Version: other Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-x11driver AssignedTo: wine-bugs(a)winehq.org ReportedBy: lich(a)math.spbu.ru GetMontorInfo always returns rcWork equal to rcMonitor, but it must take panels and taskbars into account. The only solution I can see is to use SystemParametersInfo(SPI_SETWORKAREA) during initialization time, but I do not know how to deal with different monitors. P.S. It is needed to properly implement maximum dimensions of console window. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

3 31

[Bug 58532] New: error in solidworks 2023
by WineHQ Bugzilla June 28, 2026

June 28, 2026

http://bugs.winehq.org/show_bug.cgi?id=58532 Bug ID: 58532 Summary: error in solidworks 2023 Product: Wine Version: 10.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: grandrodri3(a)gmail.com Distribution: --- Created attachment 79015 --> http://bugs.winehq.org/attachment.cgi?id=79015 edrawings first error Hey, hi, how are you? Here's an error from an old friend, SolidWorks. I tried version 2023, and Edrawings gives two programming errors. I'm uploading them now to see if anything can be done about them. The viewer works without any problems. This was initially done without IE8. Let's see if it works without uninstalling the one that comes with Wine. Oh, the DLLs that were installed: dotnet48 vcrun2019 d3dcompiler_47 corefonts msxml6 Visual C++ 2010 and 2012 were installed, the ones that came with SolidWorks 2023, and they installed without any problems. Could you please check? Best 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.

2 4

[Bug 45244] New: MapleStory: screen freezes with certain audio files
by wine-bugs＠winehq.org June 28, 2026

June 28, 2026

https://bugs.winehq.org/show_bug.cgi?id=45244 Bug ID: 45244 Summary: MapleStory: screen freezes with certain audio files Product: Wine Version: 3.8 Hardware: Other OS: Mac OS X Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alpha.s3r(a)gmail.com Created attachment 61485 --> https://bugs.winehq.org/attachment.cgi?id=61485 Trimmed bug report. Frame Sync failed repeated indefinitely (but file size was 125 MB), so I erased most of those lines. Wine screen freezes when playing certain audio files. It seems to be either non-MPEG2 files or audio files that don't conform to 24k bps or 22050 Hz (any audio under this classification seems to be fine). The specific audio file that was used to replicate the crash was: MPEG 2.5 / 8k bps / 8000 Hz. I've tested out other Wine versions, and Wine Stable 3.0 has the same error, along Wine Staging 3.6, 3.7, 3.8. However, if you use Wine 2.22 or Wine 1.4.1, the app runs fine and doesn't freeze at these sound effects. -- 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.

3 10

[Bug 53013] New: Maplestory crashes after several minutes of gameplay
by WineHQ Bugzilla June 28, 2026

June 28, 2026

https://bugs.winehq.org/show_bug.cgi?id=53013 Bug ID: 53013 Summary: Maplestory crashes after several minutes of gameplay Product: Wine Version: 7.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: mazuz.eyal(a)gmail.com Distribution: --- Created attachment 72381 --> https://bugs.winehq.org/attachment.cgi?id=72381 last part of the wine debug info when maplestory crash Maplestory now works when downloading through the Nexon launcher, it logs into the game and even into the world, but after a few minutes of playing (it is mostly random, but not more than 5 minutes). The game freezes for a bit then crashes, where the last output in the console from wine is 0bec:fixme:keyboard:X11DRV_MapVirtualKeyEx keyboard layout 0x10001000 is not supported 0bec:fixme:key:X11DRV_ToUnicodeEx keyboard layout 0x10001000 is not supported 0bec:fixme:keyboard:X11DRV_MapVirtualKeyEx keyboard layout 0x10001000 is not supported 0bec:fixme:keyboard:X11DRV_MapVirtualKeyEx keyboard layout 0x10001000 is not supported 0bec:fixme:keyboard:X11DRV_MapVirtualKeyEx keyboard layout 0x10001000 is not supported 0bec:fixme:key:X11DRV_ToUnicodeEx keyboard layout 0x10001000 is not supported 0bec:fixme:keyboard:X11DRV_MapVirtualKeyEx keyboard layout 0x10001000 is not supported 0bec:fixme:keyboard:X11DRV_MapVirtualKeyEx keyboard layout 0x10001000 is not supported 0bec:fixme:keyboard:X11DRV_MapVirtualKeyEx keyboard layout 0x10001000 is not supported 0bec:fixme:key:X11DRV_ToUnicodeEx keyboard layout 0x10001000 is not supported 0bec:fixme:keyboard:X11DRV_MapVirtualKeyEx keyboard layout 0x10001000 is not supported 0bec:fixme:keyboard:X11DRV_MapVirtualKeyEx keyboard layout 0x10001000 is not supported 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:virtual:NtQueryVirtualMemory (0x128,(nil),info_class=1,0x10280390,65536,(nil)) Unknown information class 0208:fixme:virtual:NtQueryVirtualMemory (0x128,(nil),info_class=1,0x10280390,65536,(nil)) Unknown information class 0208:fixme:virtual:NtQueryVirtualMemory (0x128,(nil),info_class=1,0x17cc0390,65536,(nil)) Unknown information class 0208:fixme:virtual:NtQueryVirtualMemory (0x128,(nil),info_class=1,0x17cc0390,65536,(nil)) Unknown information class 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0208:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 018c:fixme:winsock:setsockopt Unknown IPPROTO_TCP optname 0x00000003 0208:fixme:virtual:NtQueryVirtualMemory (0x128,(nil),info_class=1,0x10280390,65536,(nil)) Unknown information class 0208:fixme:virtual:NtQueryVirtualMemory (0x128,(nil),info_class=1,0x10280390,65536,(nil)) Unknown information class 0208:fixme:virtual:NtQueryVirtualMemory (0x128,(nil),info_class=1,0x17cc0390,65536,(nil)) Unknown information class 0208:fixme:virtual:NtQueryVirtualMemory (0x128,(nil),info_class=1,0x17cc0390,65536,(nil)) Unknown information class 0208:fixme:virtual:NtQueryVirtualMemory (0x128,(nil),info_class=1,0x10280390,65536,(nil)) Unknown information class 0208:fixme:virtual:NtQueryVirtualMemory (0x128,(nil),info_class=1,0x10280390,65536,(nil)) Unknown information class 01a0:fixme:userenv:UnregisterGPNotification 00000000000005B4 01a0:fixme:userenv:UnregisterGPNotification 00000000000005B8 0254:fixme:iphlpapi:CancelIPChangeNotify (overlapped 000003A6EB1CD5C8): stub 023c:fixme:ver:GetCurrentPackageId (000000000011FDA0 0000000000000000): stub 0164:fixme:wtsapi:WTSUnRegisterSessionNotification Stub 0000000000030178 0164:fixme:iphlpapi:CancelIPChangeNotify (overlapped 000001F0A11E2908): stub 0270:err:ole:CoUninitialize Mismatched CoUninitialize 05b8:fixme:winsock:setsockopt Ignoring SO_RANDOMIZE_PORT attaching the last lines of the log when using WINEDEBUG=warn+all it's only the last lines cause I can't for some reason run the Nexon launcher using redirect operators to write to files (e.g. WINEDEBUG=warn+all wine nexon_launcher.exe > wine.error.log), so the log is the output saved from the console. The log corresponds to the time when the game crashed -- 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 14