https://bugs.winehq.org/show_bug.cgi?id=44836
Bug ID: 44836
Summary: Mod Organizer 2 crashes on
msvcp140.dll.?uncaught_exceptions@std@@YAHXZ (64-bit)
Product: Wine
Version: 3.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: msvcp
Assignee: wine-bugs(a)winehq.org
Reporter: labmailssadur(a)gmail.com
Distribution: ---
Created attachment 60881
--> https://bugs.winehq.org/attachment.cgi?id=60881
Console Output from initial launch of MO to crash
When trying to launch Mod Organizer 2, the application crashes with
"msvcp140.dll.?uncaught_exceptions@std@@YAHXZ" after launching the tutorial
dialogue (which does not display correctly).
Steps to reproduce:
1. Install Mod Organizer 2 (i.e. from
https://github.com/Modorganizer2/modorganizer/releases)
2. Install any Game supported by MO2.
3. Launch MO2 and point it to the game when asked to do so (otherwise MO2 will
exit before the crash can occur).
4. Watch the crash occur.
I am aware of Bug 44278, but it seems that the issue lies with the 64-bit
implementation of the function (see attachment).
Tested with TES4: Oblivion from GOG and TES5: Skyrim Special Edition from Steam
installed (in seperate Prefixes).
Further info:
Arch Linux, wine 3.4-2
64-bit prefix
--
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=44880
Bug ID: 44880
Summary: Latest dev build of Mod Organizer 2 fails to
initialize dlls
Product: Wine
Version: 3.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: labmailssadur(a)gmail.com
Distribution: ---
Created attachment 60947
--> https://bugs.winehq.org/attachment.cgi?id=60947
Console output of the crash.
The latest dev build of Mod Organizer 2 fails to launch and complains about
failing to initialize dlls (specifically usvfs_x64.dll).
Steps to reproduce:
1. Set up a fresh 64-bit prefix.
2. Download the dev build of MO2 (2.1.2dev6-Silarn-prerelease).
3. Try to launch it.
4. Watch it fail.
I am not allowed to link to the download, though it is available on the
ModOrganizerDevs Discord Channel (https://discord.gg/5tCqt6V) in the #builds
channel (make sure to pick the link titled as "Full Build", and not "PDBs").
Also, the problem does not occur in the release build (2.11).
--
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=40950
Bug ID: 40950
Summary: ProgramFiles(x86) environment variable is not created
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: programmerjake(a)gmail.com
Distribution: ---
the ProgramFiles(x86) environment variable is not created.
it should probably be set in
https://github.com/wine-mirror/wine/blob/master/dlls/kernel32/process.c#L571
--
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=37163
Bug ID: 37163
Summary: WiX Toolset installer doesn't open
Product: Wine
Version: 1.7.25
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: alexhenrie24(a)gmail.com
Created attachment 49394
--> https://bugs.winehq.org/attachment.cgi?id=49394
wix38-stderr
The WiX Toolset installer (version 3.8) hangs without opening any windows. The
console output is attached.
--
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=37251
Bug ID: 37251
Summary: WiX Toolset v3.8 installer doesn't open with Wine-Mono
Product: Wine
Version: 1.7.26
Hardware: x86
URL: https://wix.codeplex.com/releases/view/115492
OS: Linux
Status: NEW
Keywords: download, Installer, source
Severity: normal
Priority: P2
Component: mscoree
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
Created attachment 49539
--> https://bugs.winehq.org/attachment.cgi?id=49539
installer's log
With bug 37163 fixed, the installer still pops up a dialog complaining that it
needs Microsoft .Net.
I'll attach a screenshot/log.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=39254
Bug ID: 39254
Summary: Microsoft 365 Installer: Crashes on startup
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jamesmfox(a)live.com
Distribution: ---
Created attachment 52321
--> https://bugs.winehq.org/attachment.cgi?id=52321
backtrace of wine
Microsoft 365 office installer crashers on startup (Before anything kind of gui
is shown)
--
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=35390
Bug ID: 35390
Summary: Samsung_Magician_Setup_v4.0.exe fails to install
Product: Wine
Version: 1.7.8
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wmi&wbemprox
Assignee: wine-bugs(a)winehq.org
Reporter: vinschen(a)redhat.com
Classification: Unclassified
Created attachment 47217
--> https://bugs.winehq.org/attachment.cgi?id=47217
debug output of Samsung_Magician_Setup_v4.0.exe
Trying to install the Samsung Magician (an SSD tool)
fails to install. The first dialog asks for the installation
language, which I keep on the default "English", the next dialog
contains the following error message:
INSTALLATION CANNOT CONTINUE: "Windows Management Instrumentation"
service is disabled. Please enable and try again.
I attached a file with a log created like this:
WINEDEBUG=+msi,+wbemprox,+wmiutils,+service,+seh,+tid wine
Samsung_Magician_Setup_v4.0.exe >> foo.log 2>&1
If you need more input, I'm willing to provide it.
Thanks,
Corinna
--
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=35778
Bug ID: 35778
Summary: Samsung Magician v4.0 fails to install (widl emits
incorrect var type for IDispatch* defaultvalue)
Product: Wine
Version: 1.7.14
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: tools
Assignee: wine-bugs(a)winehq.org
Reporter: focht(a)gmx.net
Hello folks,
I split this off from bug 35390 because this looks like widl issue.
https://bugs.winehq.org/show_bug.cgi?id=35390#c7
--- quote ---
So next thing to check is vartype of default value for this parameter in native
typelib. If it's VT_DISPATCH|VT_BYREF, unlikely I think cause only NULL value
makes sense as a default, then widl is to blame, if it's stored at VT_PTR type
we need ITypeInfo code to deal with that. It's also possible that both parts
are broken.
--- quote ---
I downloaded native wbemdisp and registered it (regsvr32)
http://www.dlldump.com/download-dll-files_new.php/dllfiles/W/wbemdisp.dll/5…http://filemare.com/browse/62.99.77.70/WBEMDISP.TLB
With that part the installer goes further (succeeds) and trace log reveals the
defaultvalue type for IDispatch* is VT_DISPATCH (Wine's widl generates VT_PTR)
--- snip ---
$ WINEDEBUG=+tid,+seh,+tlb,+wbemprox,+wbemdisp,+ole,+variant wine
./Samsung_Magician_Setup_v4.0.exe >>log.txt 2>&1
...
002c:trace:ole:ITypeInfo_fnInvoke changing args
002c:trace:ole:dump_Variant 0x681db8->{VT_BSTR,(null)}
002c:trace:ole:dump_Variant 0x681da8->{VT_BSTR,L"root\\CIMV2"}
002c:trace:ole:dump_Variant 0x681d98->{VT_BSTR,(null)}
002c:trace:ole:dump_Variant 0x681d88->{VT_BSTR,(null)}
002c:trace:variant:VariantCopy (0x1684c8->(VT_EMPTY),0x15dce0->(VT_BSTR))
002c:trace:variant:VariantClear (0x1684c8->(VT_EMPTY))
002c:trace:variant:VariantCopy (0x1684d8->(VT_EMPTY),0x15dcf8->(VT_BSTR))
002c:trace:variant:VariantClear (0x1684d8->(VT_EMPTY))
002c:trace:variant:VariantCopy (0x1684e8->(VT_EMPTY),0x15dd10->(VT_I4))
002c:trace:variant:VariantClear (0x1684e8->(VT_EMPTY))
002c:trace:variant:VariantCopy (0x1684f8->(VT_EMPTY),0x15dd28->(VT_DISPATCH))
002c:trace:variant:VariantClear (0x1684f8->(VT_EMPTY))
002c:trace:ole:DispCallFunc (0x13f358, 28, 4, 10, 9, 0x1685cc, 0x1685a8,
0x33f610 (vt=10))
002c:trace:ole:DispCallFunc arg 0: type 8
002c:trace:ole:dump_Variant 0x681db8->{VT_BSTR,(null)}
002c:trace:ole:DispCallFunc arg 1: type 8
002c:trace:ole:dump_Variant 0x681da8->{VT_BSTR,L"root\\CIMV2"}
002c:trace:ole:DispCallFunc arg 2: type 8
002c:trace:ole:dump_Variant 0x681d98->{VT_BSTR,(null)}
002c:trace:ole:DispCallFunc arg 3: type 8
002c:trace:ole:dump_Variant 0x681d88->{VT_BSTR,(null)}
002c:trace:ole:DispCallFunc arg 4: type 8
002c:trace:ole:dump_Variant 0x1684c8->{VT_BSTR,L""}
002c:trace:ole:DispCallFunc arg 5: type 8
002c:trace:ole:dump_Variant 0x1684d8->{VT_BSTR,L""}
002c:trace:ole:DispCallFunc arg 6: type 3
002c:trace:ole:dump_Variant 0x1684e8->{VT_I4,0}
002c:trace:ole:DispCallFunc arg 7: type 9
002c:trace:ole:dump_Variant 0x1684f8->{VT_DISPATCH,(nil)}
002c:trace:ole:DispCallFunc arg 8: type 16393
002c:trace:ole:dump_Variant 0x168508->{VT_DISPATCH|VT_BYREF,0x33f600}
--- snip ---
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.