https://bugs.winehq.org/show_bug.cgi?id=55160
Bug ID: 55160
Summary: Loading Bay / Harry Potter Magic Awakened: Unable to
install
Product: Wine
Version: 8.11
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: bcrypt
Assignee: wine-bugs(a)winehq.org
Reporter: worble+winehq(a)worble.xyz
Distribution: ---
Created attachment 74728
--> https://bugs.winehq.org/attachment.cgi?id=74728
Wine Logs
After clicking "Install", a generic "Installation Failed" page appears.
Attached logs suggest '01b0:fixme:bcrypt:BCryptOpenAlgorithmProvider algorithm
L"RC4" not supported' could be the culprit?
The installer can be downloaded from this page:
https://www.harrypottermagicawakened.com/global/
Direct link:
https://api.loadingbay.com/app/v1/download_client/windows/mkt-hpma-official…
SHASUM: 3f3ff1a8d118975dfb03ce7cceab99ba499b13c0
Using wine-8.11 (Staging)
--
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=55124
Bug ID: 55124
Summary: Can't run Flutter SDK (cmd.exe doesn't support
redirecting stderr for a block)
Product: Wine
Version: 8.10
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: cmd
Assignee: wine-bugs(a)winehq.org
Reporter: alexhenrie24(a)gmail.com
Distribution: ---
`wine flutter.bat` goes into an infinite loop that prints this message over and
over:
Can't recognize '2 (' as an internal or external command, or batch script.
It's coming from these lines in internal/shared.bat:
2>NUL (
REM "3" is now stderr because of "2>NUL".
CALL :subroutine %* 2>&3 9> "%cache_dir%\flutter.bat.lock" || GOTO
acquire_lock
)
Wine's cmd.exe does support redirecting stdout for a block of code, for
example:
>NUL (
COPY flutter.bat flutter2.bat
)
But it does not support redirecting stderr in the same way.
--
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=55097
Bug ID: 55097
Summary: cmd.exe does not handle PATH with leading or
sequential semicolons
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: cmd
Assignee: wine-bugs(a)winehq.org
Reporter: loothelion(a)nvidia.com
Distribution: ---
Created attachment 74657
--> https://bugs.winehq.org/attachment.cgi?id=74657
Repro program for PATH separator bug
Wine's cmd.exe doesn't properly handle PATH values with:
- A leading semicolon
- Two sequential semicolons
Windows handles this fine, as shown in the attached test program. Simply
extract and then run test.bat from cmd.exe
Output looks like such in wine:
```
Z:\home\loothelion\repos\wine-path-bug>test.bat
"Expecting failure (no print)"
Can't recognize 'test.bat' as an internal or external command, or batch script.
"Expecting SUCCESS"
"PATH=Z:\home\loothelion\repos\wine-path-bug/a"
SUCCESS
"Expecting SUCCESS (exposes WINE bug)"
"PATH=;Z:\home\loothelion\repos\wine-path-bug/a"
"Expecting SUCCESS"
"PATH=D:/;Z:\home\loothelion\repos\wine-path-bug/a"
SUCCESS
"Expecting SUCCESS (exposes WINE bug)"
"PATH=D:/;;Z:\home\loothelion\repos\wine-path-bug/a"
```
I have a fix for this that I plan to send for review shortly, as well as a new
test case to protect against regressions.
--
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=54978
Bug ID: 54978
Summary: vbscript fails to compile Sub when End Sub on same
line
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: vbscript
Assignee: wine-bugs(a)winehq.org
Reporter: francisdb(a)gmail.com
Distribution: ---
Sub Sw35_UnHit()Controller.Switch(35)=0: End Sub
has to be changed to
Sub Sw35_UnHit()
Controller.Switch(35)=0
End Sub
to work
see also Bug 53873
--
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=49772
Bug ID: 49772
Summary: Memory safety issues in widl
Product: Wine
Version: 5.16
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: tools
Assignee: wine-bugs(a)winehq.org
Reporter: kolan_n(a)mail.ru
Distribution: ---
I have tried to compile some type libraries missing in MinGW-w64 and Wine and
ReactOS SDKs too (more precisely, sapiddk.idl) into headers from the files in
Windows SDK (used Windows 10 SDK).
MinGW-w64 widl has crashed without producing any output, just left some files
with garbled filenames (looks like a zero terminator got missing in a C
string).
So I have built wine widl. It has also crashed, but at least produced some
meaningful output.
--
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=7767
Michael Stefaniuc <mstefani(a)winehq.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |8.0.x
--
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=55101
Bug ID: 55101
Summary: DesignDoll Declaring An Error After Loading All
Component In Splash Screen
Product: Wine
Version: 8.10
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: zeroredgrave(a)gmail.com
Distribution: ---
Created attachment 74668
--> https://bugs.winehq.org/attachment.cgi?id=74668
After Loading Screen
DesignDoll Doesn't Load in Weird Way and I dunno what kind of Error is this.
--
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=55053
Bug ID: 55053
Summary: Prometheus exporter for Windows needs
DISPATCH_PROPERTYGET support in object_Invoke
Product: Wine
Version: 8.10
Hardware: x86-64
URL: https://github.com/prometheus-community/windows_export
er/releases/download/v0.22.0/windows_exporter-0.22.0-a
md64.exe
OS: Linux
Status: NEW
Keywords: download, patch, source
Severity: normal
Priority: P2
Component: wmi&wbemprox
Assignee: wine-bugs(a)winehq.org
Reporter: gijsvrm(a)gmail.com
Distribution: ---
Created attachment 74615
--> https://bugs.winehq.org/attachment.cgi?id=74615
hack
To test this:
1) Run windows_exporter-0.22.0-amd64.exe
2) Go to http://localhost:9182/ in your browser
3) Press the 'Metrics' button
4) An error page is shown
When pressing the 'Metrics' button, this fixme is spammed:
0188:fixme:wbemdisp:object_Invoke flags 0x2 not supported
This stems from the fact that wbemdisp:object_Invoke doesn't support
DISPATCH_PROPERTYGET on its own. The attached hack "fixes" the issue and
instead of the error page, you get a page with metrics.
Source of the program can be found here:
https://github.com/prometheus-community/windows_exporter
--
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=9378
Summary: CM: Shock Force 'Could not initialize graphics display'
Product: Wine
Version: 0.9.43.
Platform: PC
URL: http://www.battlefront.com/products/cmsf/downloads.html
OS/Version: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: wine-directx
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: mailing_list(a)orange.nl
After starting Combat Mission: Shock Force Demo it stops with the message:
'Could not initialize graphics display. REQUIRED 1024x768, 32-bit
color'.
The terminal output doesn't provide any clues:
wine 'CM Shock Force DEMO.exe'
ALSA lib conf.c:3939:(snd_config_expand) Unknown parameters 0
ALSA lib control.c:910:(snd_ctl_open_noupdate) Invalid CTL default:0
err:alsa:ALSA_CheckSetVolume Could not find 'PCM Playback Volume' element
err:alsa:ALSA_CheckSetVolume Could not find 'PCM Playback Volume' element
fixme:wave:ALSA_AddCaptureDevice Add support for DSCapture
ALSA lib seq_hw.c:457:(snd_seq_hw_open) open /dev/snd/seq failed: No such file
or directory
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.