http://bugs.winehq.org/show_bug.cgi?id=58733
Bug ID: 58733
Summary: widl gives a segmentation fault.
Product: Wine
Version: 10.15
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: programs
Assignee: wine-bugs(a)winehq.org
Reporter: xerox.xerox2000x(a)gmail.com
Distribution: Debian
I tried this command:
~/wine/tools/widl/widl -I ~/wine/include/ -L ~/wine/dlls/stdole2.tlb/
~/wine/include/msinkaut.idl
Result: Segmentation fault
This command works for other idl files like wbemdisp.idl
I found a hack to work around the crash is to make the 4 methods in msinkaut
that contain IDataObject static; might be a pointer to the cause of the bug?
diff --git a/include/msinkaut.idl b/include/msinkaut.idl
index 743dec82a40..0bc6d5c79d5 100644
--- a/include/msinkaut.idl
+++ b/include/msinkaut.idl
@@ -656,20 +656,20 @@ cpp_quote("#endif /* _WINGDI_ */")
[in] VARIANT PacketData,
[in] VARIANT PacketDescription,
[out, retval] IInkStrokeDisp **Stroke);
- HRESULT ClipboardCopyWithRectangle(
+ static HRESULT ClipboardCopyWithRectangle(
[in] IInkRectangle *Rectangle,
[in] InkClipboardFormats ClipboardFormats,
[in] InkClipboardModes ClipboardModes,
[out, retval] IDataObject **DataObject);
- HRESULT ClipboardCopy(
+ static HRESULT ClipboardCopy(
[in] IInkStrokes *strokes,
[in] InkClipboardFormats ClipboardFormats,
[in] InkClipboardModes ClipboardModes,
[out, retval] IDataObject **DataObject);
- HRESULT CanPaste(
+ static HRESULT CanPaste(
[in] IDataObject *DataObject,
[out, retval] VARIANT_BOOL *CanPaste);
- HRESULT ClipboardPaste(
+ static HRESULT ClipboardPaste(
[in] long x,
[in] long y,
[in, unique] IDataObject *DataObject,
--
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.
http://bugs.winehq.org/show_bug.cgi?id=58696
Bug ID: 58696
Summary: Profi cash 12 (32-Bit German Banking Software) crashes
during starting among Linux Mint
Product: WineHQ.org
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: www-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: michael.howland(a)kabelbw.de
Distribution: ---
Created attachment 79293
--> http://bugs.winehq.org/attachment.cgi?id=79293
Wine debugger mistake details
Profi cash version 12 is a 32-Bit German Banking Software.
It is crashing during starting in a Wine 9.0 box among Linux Mint.
Wine tricks is also installed.
I think the mistakes have to do with Microsofts .Net Runtime environment.
I could install the above mentioned software without a mistake message under
Wine 9.0.
.Net package is also installed.
The previous main Version of Profi cash was version 11.
Profi cash version 11 runs in a Wine 9.0 box on the same computer.
The only two things which are not doing is printing and working with a
reiner sct (smartcard reader) via USB. But I can live with that.
I think the reason is, that Wine is just a box for a Windows program and not a
complete Windows environment. If so, that would be fine.
By the way Profi cash Version 11 needs no .Net Runtime environment to run.
The development of Version 11 is terminated. New features and amendments by law
or regulations will be only technically implemented in Version 12.
Hope someone can help me.
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.
http://bugs.winehq.org/show_bug.cgi?id=58566
Bug ID: 58566
Summary: Maxis games (Simcity2000, SimCopter, StreetsofSimCity)
do not work anymore because smackw32.dll won't load,
no matter how much it's pasted all over the file
system. WoW64 (yes I know you'll just ignore this bug
as won't fix: that's how opensource is now)
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: chaosesqueteam(a)sogetthis.com
Distribution: ---
This dll doesn't work on WoW: it's in the game dir, and I put it in
systemwow64, system32, and system. Doesn't work. No maxis games can run. (also
note: the 16 bit installer doesn't work at all since you don't allow 16 bit
apps in wow64 mode, only 32, so all of the games everyone is using wine for
can't be installed the normal way anymore since they use 16 bit installer
binaries)
0640:err:environ:init_peb starting L"F:\\WIN95\\SC2K\\SIMCITY.EXE" in
experimental wow64 mode
0640:fixme:wow:wow64_NtSetLdtEntries 1107 0488323f 0000f335 0000 00000000
00000000: stub
0640:err:module:loader_init "smackw32.dll" failed to initialize, aborting
0640:err:module:loader_init Initializing dlls for
L"F:\\WIN95\\SC2K\\SIMCITY.EXE" failed, status c0000005
Ok so I'll be banned now for reporting a bug
>WOW64: WONT FIX!!!
>MAXIS 16 bit installer! WONT FIX
>32 bit dll though and you got around the installer
>WONT FIX AND BANNED!!!
Opensource really sucks these days.
I liked it when I was coding with my friends 20 years ago.
This culture of bullshit didn't exist then, and ultra professionalism.
We are hackers.
Not professional software engineers.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=58613
Bug ID: 58613
Summary: wine cannot run WinAuth at all - no GUI, instant crash
Product: Wine
Version: 10.13
Hardware: aarch64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: owokkgccs0s8os0gk4o4gsk8wss0w0ww(a)ai.notifier.in
Distribution: ---
https://github.com/winauth/winauth
1. "wine /path/to/WinAuth.exe"
--
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.
http://bugs.winehq.org/show_bug.cgi?id=58583
Bug ID: 58583
Summary: msvcp140: Multiple modern applications using C++
Concurrency crash in CONCRT140.dll on startup
Product: Wine
Version: 10.12
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: msvcp
Assignee: wine-bugs(a)winehq.org
Reporter: waser(a)waser.tech
Distribution: ---
Created attachment 79107
--> http://bugs.winehq.org/attachment.cgi?id=79107
The game's own crash log from its `_appdata_ixray_/logs` directory.
This report details a consistent, immediate startup crash in `CONCRT140.dll`
affecting modern S.T.A.L.K.E.R. engine forks. These engines are based on the
open-source **Open X-Ray 1.6**, which itself works flawlessly under Wine.
The crash only appears in these newer, more advanced forks which leverage the
MSVC concurrency runtime for performance. This strongly indicates the issue
lies within Wine's implementation of these APIs, not a bug in the engines
themselves. This is effectively a regression, as the baseline engine works
while the newer, concurrency-enabled versions do not.
**Existing Related Bugs:**
This issue appears to be a new, highly reproducible test case for known
problems in Wine's concurrency support. We are filing this as a new report due
to the unique test case and the specific failure point (constructor vs.
destructor), but it is likely caused by the same underlying issues as:
- **Bug 52899:** Notes that `CONCRT140.dll` requires `CreateEventExW` from
`kernel32`. This is the most likely root cause.
- **Bug 41749:** Shows a crash in the destructor for
`Concurrency::details::_TaskCollection`. Our crash occurs in the *constructor*
of this same object, demonstrating a different failing code path.
Our report provides two clear methods to reproduce this crash, including one
that is fully free and requires no commercial software.
---
### **Primary Reproduction Steps (IX-Ray on S.T.A.L.K.E.R.: Call of Pripyat)**
*(Steps 1-5 as in previous draft)*
6. **Run the Game with Debug Logging:** Launch the game using its main
executable with full debug channels enabled.
```bash
WINEDEBUG=+all wine Stalker-COP.exe &> stalker_cop_crash_all.log
WINEDEBUG=+seh,+loaddll wine Stalker-COP.exe &> stalker_cop_crash_seh.log
```
7. **Result:** The process will crash immediately. The game's own crash log
(in `_appdata_ixray_/logs`) and the attached Wine debug logs will show a fatal
error in `CONCRT140.dll`.
---
### **Alternative Reproduction Steps (AOEngine on S.T.A.L.K.E.R. Anomaly)**
*(As in previous draft, but with the same logging commands)*
---
**Expected Behavior:**
The game launcher should appear, and the game should launch to the main menu
successfully, as it does on Windows and as the baseline Open X-Ray 1.6 engine
does under Wine.
**Logs:**
Three files will be attached for the primary reproduction case:
1. `stalker_cop_crash_seh.log`: A small log with `+seh,+loaddll` for quick
initial review.
2. `stalker_cop_crash_all.log.bz2`: The complete `+all` debug log, compressed
with bzip2 due to its large size.
3. `ixray-2025.08.10-02.37.21-waser.log`: The game's own crash log from its
`_appdata_ixray_/logs` directory.
**References:**
- **IX-Ray GitHub (Open Source Engine):**
https://github.com/ixray-team/ixray-1.6-stcop
- **GE-Proton Issue #197 (Full History):**
https://github.com/GloriousEggroll/proton-ge-custom/issues/197
--
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.
https://bugs.winehq.org/show_bug.cgi?id=57744
Bug ID: 57744
Summary: Custom? 7z self extracting archive for autocad is
broken
Product: Wine
Version: 10.0-rc6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: francisco278herrera(a)gmail.com
Distribution: ---
Created attachment 77944
--> https://bugs.winehq.org/attachment.cgi?id=77944
dlls that aren't extracted
I tried installing autocad 2025 from the autodesk website
https://www.autodesk.com/products/autocad/overview?term=1-YEAR&tab=subscrip…
the installer at first fails to open. it seems to be a custom? 7z self
extracting archive that is broken so some dlls within it are not extracted and
the installer does not run. i have attached the full terminal output with the
dlls.
so i opened the exe using gnome file roller and copied those dlls to wine's
system32 folder. then the installer runs and gets stuck at 3%, but that is
another bug.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=58569
Bug ID: 58569
Summary: 32 bit video dll "smackw32" does not load under WoW64
for some reason (mac OSX, 64 bit only) (sorry, wine
works fine elsewhere, only hit this on macOSX)
Product: Wine
Version: 10.12
Hardware: x86-64
OS: MacOS
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: chaosesqueteam(a)sogetthis.com
The widely used video codec DLL smackw32.dll, which is used by Maxis games and
other things from the fun era of PC videogaming, doesn't load for some reason
under WoW64 on MacOSX 64-bit only (ie: past 10.15 etc).
Other 32 bit apps work fine (notepad++ 32 bit compile, simcity 3000 executable
works fine, etc).
No idea why this one 32 bit dll doesn't work, but it doesn't
Reporting as it's a 32 bit item that isn't loading under WoW64: (not 16 bit
issue as mistaken for).
0640:fixme:wow:wow64_NtSetLdtEntries 1107 0488323f 0000f335 0000 00000000
00000000: stub
0640:err:module:loader_init "smackw32.dll" failed to initialize, aborting
(Note: happens on 32 bit compiled apps like: Streets of Sim .exe ,
simcopter.exe, and network enabled simcity 2000.exe (2SCN), which is 32 bit).
I tried the smackw32.dll included on the CDs, and put them in different places:
system64wow, system32, and then system.
It is also in existance alongside the exes. So every possibility was tried.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=56881
Bug ID: 56881
Summary: BloodRayne unable to run in wow, but able to run under
none wow build
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: l12436.tw(a)gmail.com
Distribution: ---
Created attachment 76692
--> https://bugs.winehq.org/attachment.cgi?id=76692
Log with WINEDEBUG=+server,relay
the game seems and anti-cheat in it.
Game is unable to run under wow build of wine
but success run under none wow build
OS is ubuntu 20.04
wine is latest master.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=58709
Bug ID: 58709
Summary: upgrade to 10.15 results in garbled fullscreen in
Limelight Lemonade Jam
Product: Wine
Version: 10.15
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: pernegger(a)gmail.com
Distribution: ---
Created attachment 79308
--> http://bugs.winehq.org/attachment.cgi?id=79308
terminal output for 10.12–10.15
[Ubuntu 22.04, WINE packages from winehq.org repo]
I've been playing the trial version of Limelight Lemonade Jam, which is
available for free from
https://sample9.dmm.co.jp/digital/pcgame/yuzu_0012/yuzu_0012t.zip, using WINE
10.12. No issues.
Warning! The full game is NSFW, it's possible the trial has NSFW content as
well; but if so, it doesn't come up for quite a while.
WINE got upgraded to 10.15 just now, and the game doesn't launch correctly any
more, the display is messed up, see screenshot.
So I tested 10.12–10.15, each run with a fresh prefix, and it's reproducible:
- 10.12: OK
- 10.13: OK
- 10.14: OK
- 10.15: BROKEN
Full disclosure, I've set the game to fullscreen and enabled the suspend/resume
function, i.e. it'll bypass the main menu on launch and resume the game
directly. Judging by the sound, the game loads fine even on 10.15, AFAICT it
still reacts to keyboard input correctly, it's just the display that's messed
up.
It's likely that this affects other games using the KiriKiri engine as well.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=58665
Bug ID: 58665
Summary: cmd incorrectly wraps text containing ANSI escape
sequences
Product: Wine
Version: 10.14
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: cmd
Assignee: wine-bugs(a)winehq.org
Reporter: forestix(a)gaga.casa
Distribution: ---
Created attachment 79250
--> http://bugs.winehq.org/attachment.cgi?id=79250
reproducer: should print 3 lines; wine prints 4 lines
Wine's cmd.exe prematurely inserts line breaks when a program's output contains
non-printable ANSI escape sequences, such as those used to change colors.
It looks as though Wine is counting not only the printable characters in the
program's output, but also the non-printable ones, and using the total to
decide where to insert a line break. Text that fits entirely on one line in a
real Windows console is sometimes broken midway through the line, or followed
by a blank line that should not be there, when run in an xterm using Wine.
I am attaching a batch file that reproduces the problem. It should print 3
lines. The second line is identical to the others with the addition of some
non-printable escape sequences. These characters should either occupy no width
in the terminal (making the line length match the others) or be rendered as
visible placeholder characters (as older Windows versions do). To see Wine
handling it incorrectly, run it in an 80-column xterm or a similar terminal.
Ideally, the output should look like this, with the head of line 2 in red:
79 chars _123456789_123456789_123456789_123456789_123456789_123456789_123456789
79 chars _123456789_123456789_123456789_123456789_123456789_123456789_123456789
79 chars _123456789_123456789_123456789_123456789_123456789_123456789_123456789
In wine, the output looks like this:
79 chars _123456789_123456789_123456789_123456789_123456789_123456789_123456789
79 chars _123456789_123456789_123456789_123456789_123456789_123456789_12
3456789
79 chars _123456789_123456789_123456789_123456789_123456789_123456789_123456789
Bug 49780 is related, but IMHO does not excuse this behavior. Regardless of
whether virtual terminal sequences are supported, Wine should either print a
character or not count it toward the length of a line when deciding where to
wrap it.
--
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.