https://bugs.winehq.org/show_bug.cgi?id=55475
Bug ID: 55475
Summary: Respondus LockDown Browser crashes on launch,
KERNEL32.dll.DiscardVirtualMemory not implemented
Product: Wine
Version: 8.0.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: micah.haber(a)gmail.com
Distribution: ---
Created attachment 75037
--> https://bugs.winehq.org/attachment.cgi?id=75037
Unhandled exception: unimplemented function KERNEL32.dll.DiscardVirtualMemory
called in 32-bit code (0x7bc2bbf0)
Installed in Windows 10 environment.
--
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=54177
Bug ID: 54177
Summary: vbscript fails to compile sub call when argument
expression contains multiplication
Product: Wine
Version: 7.21
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: vbscript
Assignee: wine-bugs(a)winehq.org
Reporter: jsm174(a)gmail.com
Distribution: ---
While working on the port of Visual Pinball, we found a script with code
similar to the following that fails to compile:
Public Sub AddTimer(aDelay, aMessage)
End Sub
Dim ii
ii = 1
AddTimer (ii-1)*200, "Message"
If the expression is wrapped in parenthesis, it compiles successfully:
AddTimer ((ii-1)*200), "Message"
--
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=28659
Bug #: 28659
Summary: rpcrt4/server test crashes on 32-bit FreeBSD9
Product: Wine
Version: 1.3.30
Platform: x86
OS/Version: FreeBSD
Status: NEW
Keywords: download, source, testcase
Severity: normal
Priority: P2
Component: rpc
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: austinenglish(a)gmail.com
Classification: Unclassified
Created attachment 36831
--> http://bugs.winehq.org/attachment.cgi?id=36831
backtrace
The rpcrt4/rpc test fails as well, but that may be related to missing ntlm_auth
(which I haven't found how to satisfy on FreeBSD). The server test shows that
same error, but also crashes, so something nastier is going on.
Backtrace attached.
--
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=52720
Bug ID: 52720
Summary: cmd.exe:batch times out in Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: cmd
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
cmd.exe:batch started timing out in Wine on 2022-03-17:
batch.c:427: running TEST_CMDLINE.CMD test...
cmd.exe:batch:040c done (258) in 120s
Test failed: timed out
https://test.winehq.org/data/patterns.html#cmd.exe:batch
Unfortunately I was unable to find a change in Wine that would be the cause for
the timeout: in my tests cmd.exe:batch still times out when run from older Wine
versions.
* Based on the WineTest logs cmd.exe:batch was taking about 50 seconds up to
2022-03-16. But the next day that run time more than doubled to about 118 - 170
seconds, causing it to time out most of the time.
* Reverting the Wine source to the 2022-03-16 head, rebuilding from scratch and
recreating the wineprefix did not help: cmd.exe:batch still times out.
* No package upgrades were performed on that date. Plus this regression
happened simultaneously on multiple machines with different upgrade schedules.
* WINETEST_TIME=1 indicates that almost all of the time is spent running
TEST_BUILTINS.CMD:
batch.c:427:0.149 running TEST_BUILTINS.CMD test...
batch.c:136:158.289 Test succeeded
^^^ The first ok() call after WaitForSingleObject() is in the map_file() called
after run_test()
* Running the test manually it looked like the "--- for /R" "Plain directory
enumeration" part of test_builtins.cmd was enumerating all of the computer's
directories, starting with /bin, /boot, /etc, ... That would certainly take a
long time but that run crashed after about 1 minute so this may be unrelated.
--
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=53095
Bug ID: 53095
Summary: system:NtUserChangeDisplaySettings Changing
L"\\\\.\\DISPLAY1" display settings returned -2
Product: Wine
Version: 7.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: zizka(a)seznam.cz
Distribution: ---
Created attachment 72524
--> https://bugs.winehq.org/attachment.cgi?id=72524
1) Wine 7.0 crash; 2) Attempts to run with the Wine bundled by the vendor
(i-deal Games)
App: "Jagged Alliance 2 - Wildfire" from Steam
Wine 7.0
Ubuntu 2022.04
I am trying to make Jagged Alliance run.
The Wine distributed with Jagged Alliance seems not to work, because it has 36
byte long libwine.so and Wine doesn't even start. See the "JA 2 dist Wine log"
below.
So I tried with Wine 7.0 (current stable), and it failed with:
system:NtUserChangeDisplaySettings Changing L"\\\\.\\DISPLAY1" display
settings returned -2
Along that, the system switched to fullscreen, with the whole screen black.
On a second run, Wine crashed - see the 1st part of the attached text.
I will try to contact the company and ask if they could figure out.
But in the meantime, I think this is a valid bug on an old Win32 game which
could be present on some others. Thanks to anyone who takes a look.
--
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=22904
Summary: Register URL protocol handlers under Linux
Product: Wine
Version: unspecified
Platform: All
OS/Version: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: programs
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: kempe.marcus(a)gmail.com
winemenubuilder is able to automatically register file type associations and
build menus under Linux, when triggered by an application under wine.
It would be great if the same thing were true for protocol handlers, so that
these would become registered in much the same way as when using gconftool in
gnome:
gconftool -s /desktop/gnome/url-handlers/spotify/command 'wine
c:\\spotify\\spotify.exe %s' --type String
gconftool-2 -s /desktop/gnome/url-handlers/spotify/enabled --type Boolean true
Would this be possible, hard, or maybe not a good idea?
--
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.
http://bugs.winehq.org/show_bug.cgi?id=16214
Summary: Copy command does not work as expected
Product: Wine
Version: 1.0.1
Platform: Other
OS/Version: other
Status: NEW
Severity: enhancement
Priority: P2
Component: dos
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: scott(a)open-vote.org
>From Launchpad: https://bugs.edge.launchpad.net/ubuntu/+source/wine/+bug/272921
In Windows, the COPY command run in a command prompt allows users to
concatenate files by using a plus ("+") operator, for example:
copy file1+file2 outfile
In wine's cmd.exe, it seems to read file1+file2 as a single path and therefore
outputs a "Path Not Found". Also, it does not recognize the "con" keyword used
to represent stdout/stdin. Therefore another method of concatenating files:
copy file1 outfile
copy file2 con >> outfile
does not work either.
My Ubuntu version is 8.04, AMD64 architecture, though I have seen the same
issue on the x86 version as well.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=20474
Summary: Wine can't be built with GCC in C99 mode
Product: Wine
Version: unspecified
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: build-env
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: yann(a)droneaud.fr
For multiple reason, wine can't be built by GCC in C99 mode ( --std=c99 ).
In particular, wine rely on GCC behavor regarding to extern inline.
It produces errors regarding asm construct conflicting with extern
inline symbols.
It produces errors with multiple defination of inline function in object files.
According to this, it seems that wine is not compatible with C99, but rely a
lot on GCC specific behavor.
See also bug #20306
--
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=53216
Bug ID: 53216
Summary: d3d11:d3d11 - test_depth_bias() fails in the TestBot
VMs
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
d3d11:d3d11 - test_depth_bias() fails in the TestBot VMs:
d3d11.c:28093: Test failed: Got depth 4.99374978e-003, expected
4.99999994e-003.
d3d11.c:28093: Test failed: Got depth 4.99374978e-003, expected
4.99999994e-003.
d3d11.c:28093: Test failed: Got depth 2.50997487e-003, expected
2.50999994e-003.
d3d11.c:28093: Test failed: Got depth 7.48750009e-003, expected
7.49999994e-003.
d3d11.c:28093: Test failed: Got depth 7.48750009e-003, expected
7.49999994e-003.
d3d11.c:28093: Test failed: Got depth 2.50997487e-003, expected
2.50999994e-003.
d3d11.c:28093: Test failed: Got depth 1.24749998e-002, expected
1.24999999e-002.
d3d11.c:28093: Test failed: Got depth 1.24749998e-002, expected
1.24999999e-002.
d3d11.c:28093: Test failed: Got depth 2.50997487e-003, expected
2.50999994e-003.
d3d11.c:28093: Test failed: Got depth 6.40899956e-001, expected
6.42500000e-001.
d3d11.c:28093: Test failed: Got depth 6.40899956e-001, expected
6.42500000e-001.
d3d11.c:28093: Test failed: Got depth 2.50997487e-003, expected
2.50999994e-003.
d3d11.c:28093: Test failed: Got depth 2.50997487e-003, expected
2.50999994e-003.
d3d11.c:28093: Test failed: Got depth 2.50997487e-003, expected
2.50999994e-003.
d3d11.c:27965: Test marked todo: Got 0xffffff00, expected 0x00ffffff at (0, 0,
0), sub-resource 0.
d3d11.c:28101: Test failed: Got value 0x14745 (4.99373704e-003), expected
0x147ae (4.99999553e-003).
d3d11.c:28101: Test failed: Got value 0x14745 (4.99373704e-003), expected
0x147ae (4.99999553e-003).
d3d11.c:28101: Test failed: Got value 0x8528f (3.25097461e-002), expected
0x85293 (3.25099845e-002).
d3d11.c:28101: Test failed: Got value 0x1eab3 (7.48747632e-003), expected
0x1eb85 (7.49999329e-003).
d3d11.c:28101: Test failed: Got value 0x1eab3 (7.48747632e-003), expected
0x1eb85 (7.49999329e-003).
d3d11.c:28101: Test failed: Got value 0x8528f (3.25097461e-002), expected
0x85293 (3.25099845e-002).
d3d11.c:28101: Test failed: Got value 0x33190 (1.24750145e-002), expected
0x33333 (1.24999888e-002).
d3d11.c:28101: Test failed: Got value 0x33190 (1.24750145e-002), expected
0x33333 (1.24999888e-002).
d3d11.c:28101: Test failed: Got value 0x8528f (3.25097461e-002), expected
0x85293 (3.25099845e-002).
d3d11.c:28101: Test failed: Got value 0xa41204 (6.40899935e-001), expected
0xa47ae1 (6.42500022e-001).
d3d11.c:28101: Test failed: Got value 0xa41204 (6.40899935e-001), expected
0xa47ae1 (6.42500022e-001).
d3d11.c:28101: Test failed: Got value 0x8528f (3.25097461e-002), expected
0x85293 (3.25099845e-002).
d3d11.c:28101: Test failed: Got value 0x8528f (3.25097461e-002), expected
0x85293 (3.25099845e-002).
d3d11.c:28101: Test failed: Got value 0x8528f (3.25097461e-002), expected
0x85293 (3.25099845e-002).
d3d11.c:28110: Test failed: Got value 0x28e (9.97940032e-003), expected 0x290
(1.00099184e-002).
d3d11.c:28110: Test failed: Got value 0x28e (9.97940032e-003), expected 0x290
(1.00099184e-002).
d3d11.c:28110: Test failed: Got value 0x331 (1.24666209e-002), expected 0x334
(1.25123980e-002).
d3d11.c:28110: Test failed: Got value 0x331 (1.24666209e-002), expected 0x334
(1.25123980e-002).
d3d11.c:28110: Test failed: Got value 0x476 (1.74258030e-002), expected 0x47b
(1.75020981e-002).
d3d11.c:28110: Test failed: Got value 0x476 (1.74258030e-002), expected 0x47b
(1.75020981e-002).
d3d11.c:28110: Test failed: Got value 0xa411 (6.40894179e-001), expected 0xa47a
(6.42496376e-001).
d3d11.c:28110: Test failed: Got value 0xa411 (6.40894179e-001), expected 0xa47a
(6.42496376e-001).
https://test.winehq.org/data/patterns.html#d3d11:d3d11
These failures:
* Don't happen on Debian 11 + Intel / KDE
* Happen on Debian 11 + QXL + single-monitor
* Happen on Debian 11 + QXL + multi-monitor
* Don't happen on Debian Testing + QXL + multi-monitor
So they are probably caused by some bug in the Debian 11 QXL support.
Note that despite being systematic these failures could cause false positives
due to the test multi-threading (see bug 53212).
--
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.