https://bugs.winehq.org/show_bug.cgi?id=45916
Bug ID: 45916
Summary: x64dbg does not open executables, nothing happens
Product: Wine
Version: 3.16
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: msvcrt
Assignee: wine-bugs(a)winehq.org
Reporter: jimbo1qaz(a)gmail.com
Distribution: ---
When I File/Open or drag a .exe file into x32dbg (x64dbg 32-bit), the exe does
not load onto the graphs, and Ctrl+G doesn't work. I think the EXE is not
loaded by the debugger at all.
Fixed by ~/bin/winetricks vcrun2013 .
Wine 3.16 on Debian on Virtualbox.
--
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=25257
Summary: Enabling Virtual desktop by default cannot be turned
off for specific applications
Product: Wine
Version: 1.3.7
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: zzarko(a)gmail.com
My system is Ubuntu 10.10 and Wine is installed from Ubuntu Wine team's PPA.
Steps to reproduce the problem:
1. Select Default settings in Configure Wine/Applications tab and check
Graphics/Enable virtual desktop
2. Add an application (in my case, Subtitle Workshop) to Applications tab and
uncheck the same option for this application
3. Start the application -> application is started in virtual desktop, despite
the different setting for that application
--
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.
https://bugs.winehq.org/show_bug.cgi?id=53755
Bug ID: 53755
Summary: Missing setx.exe
Product: Wine
Version: 7.17
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: programs
Assignee: wine-bugs(a)winehq.org
Reporter: wine(a)thecybershadow.net
Distribution: ---
The Wwise installer tries to invoke setx.exe to configure a persistent
environment variable. The installer fails with the error message:
Installation failed. Error installing prerequisites: "Error: Can't set
enviromnent variables: Command failed: %windir%/system32/setx "WWISEROOT"
"C:\Program Files (x86)\Audiokinetic\Wwise 2021.1.0.7575" Can't recognize
'C:\windows/system32/setx "WWISEROOT" "C:\Program Files
(x86)\Audiokinetic\Wwise 2021.1.0.7575"' as an internal or external command, or
batch script. "
setx.exe seems to be a standard utility for configuring environment variables
to be set by default.
An online reference: https://ss64.com/nt/setx.html
--
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=52118
Bug ID: 52118
Summary: The 64-bit crypt32:store test crashes due to heap
corruption
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: crypt32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
The 64-bit crypt32:store crashes due to heap corruption:
crypt32:store:0224 done (-1073740940) in 0s
Test failed: crash (c0000374)
https://test.winehq.org/data/patterns.html#crypt32:store
The crashes only happen with the 64-bit build. They happen almost
systematically on the TestBot's w864 VM and cw-rx460. It looks like the same
crash happens on the TestBot's Windows 10 1507, 1607 and 2009 VMs.
At least on cw-rx460 the crash happens around the last CertCloseStore(store,
0); call in testRegStoreSavedCerts(). Adding traces changes the crash location
a bit.
Also the test tends to crash every other time. That suggest there is some
cleanup issue.
--
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=53273
Bug ID: 53273
Summary: user32:msg - test_PeekMessage2() sometimes fails on
Windows 10 1709+
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
user32:msg - test_PeekMessage2() sometimes fails on Windows 10 1709+:
msg.c:12835: 1st move event: 0200 1292b3 99 100
msg.c:12855: 2nd move event: 0200 1292b3 99 100
msg.c:12861: Test failed: message time not advanced: 1292b3 1292b3
msg.c:12862: Test failed: coords not changed: (99 100) (99 100)
msg.c:12873: 3rd move event: 0200 1292b3 99 100
msg.c:12879: Test failed: message time not advanced: 1292b3 1292b3
msg.c:12880: Test failed: coords not changed: (99 100) (99 100)
https://test.winehq.org/data/patterns.html#user32:msg
--
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=1398
hjlinq(a)gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hjlinq(a)gmail.com
--
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=53885
Bug ID: 53885
Summary: MT5; tooltip still showing instead it should already
went away
Product: Wine
Version: 7.20
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: haxpor(a)gmail.com
Distribution: ---
Created attachment 73427
--> https://bugs.winehq.org/attachment.cgi?id=73427
Tooltip still shows
Tested with both wine-stable and wine-devel.
Tooltip should hide already, but it still shows. Please see the attached image.
Such tooltip will show where the mouse cursor would be, so if I move my mouse
cursor to somewhere else (literally anywhere) it will show such tooltip there,
and keep hanging there.
Until I close the file I'm editing, it will hide. But issue will repeat itself.
--
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=50936
Bug ID: 50936
Summary: Several games (The suicide of Rachel Foster, Far lone
sails & Virginia) crashes after some times with vulkan
rendeder
Product: Wine
Version: 6.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: titan.costa(a)gmail.com
Distribution: ---
The suicide of Rachel Foster & Virginia just crashes. For Far lone sails it
becomes very slow before crashing.
No backtrace. The console output is pretty silent.
With the GL renderer, Virginia & Far lone sails just works fine and can be
finished from start to end without interruption.
I can't test GL renderer with The suicide of Rachel Foster due to bug
https://bugs.winehq.org/show_bug.cgi?id=50764 which makes the game unplayable.
Setup is wine-6.5-156-g2fcc1d0ecde + Ubuntu 20.10 + GTX1070 + nvidia driver
460.39.
--
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=53886
Bug ID: 53886
Summary: SendMessage(WM_GETTEXT) is implemented as Unicode
instead of Ansi.
Product: Wine
Version: 7.20
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: vcc_02(a)yahoo.com
Distribution: ---
SendMessage, with WM_GETTEXT returns Unicode, instead of ANSI when targeting
other applications. This leads to unusable content, for applications expecting
ANSI.
The Windows compatibility can be anything from Win7 to Win10. The behavior is
the same on Wine's virtual desktop vs. native Linux desktop.
Also, tested on Kubuntu 32-bit and 64-bit.
Test applications (source code available):
https://github.com/VCC02/CodeExamples/blob/main/SendMessage_WM_GETTEXT/FP/G…https://github.com/VCC02/CodeExamples/blob/main/SendMessage_WM_GETTEXT/FP/G…https://github.com/VCC02/CodeExamples/blob/main/SendMessage_WM_GETTEXT/Delp…
Looking at the provided applications..
The "Control Text" editbox should properly display the received text, but its
content is truncated by ASCII 0.
The "Control Text [no ASCII 0]" editbox is set to display the same text, but it
removes the ASCII 0 characters before displaying, so we can see the expected
content.
Below the "Control Text [no ASCII 0]" editbox, there is a hex representation of
the received string, which shows the ASCII 0 characters after every other
character, indicating UTF-16.
Targeting the same window as the app calling SendMessage(WM_GETTEXT), results
in the expecting content. It seems, that the Unicode content is for other
windows/controls, from other applications, not the one making the call.
There are three provided executables, all seem to behave the same (FreePascal
(CodeTyphon 7.9): 32-bit and 64-bit, and Delphi 2006: 32-bit). All of the three
are compiled with no Unicode support (i.e., they call the "A" versions of the
Windows API functions, e.g. SendMessageA).
On Wine 7.16 the app may crash after a few seconds. Newer versions of Wine are
stable (7.20).
Thank you
--
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=53864
Bug ID: 53864
Summary: MIR4 launcher not open in Windows Vista or early
Product: Wine
Version: 7.19
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: dwmapi
Assignee: wine-bugs(a)winehq.org
Reporter: blogmrcs(a)gmail.com
Distribution: ---
Created attachment 73395
--> https://bugs.winehq.org/attachment.cgi?id=73395
log generated while runing the game launcher
The launcher will not open if wine mode is Windows Vista and later like Win 7
and Win 10.
The launcher work fine in Windows XP mode, the main game run too, but the CEF3
component used for authentication will not.
In Windows vista mode and later, the launcher not work.
The main problem is between the game launcher only and dwm (dwmapi) at Windows
Vista mode and later.
--
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.