https://bugs.winehq.org/show_bug.cgi?id=50988
Bug ID: 50988
Summary: New ProcessBasicInformation() failure in
kernel32:process
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
kernel32:process has a new test failure which happens on all test
configurations from Vista to the latest Windows 10:
process.c:4206: Test failed: ProcessBasicInformation info modified
See: https://test.winehq.org/data/tests/kernel32:process.html
This failure was introduced by the following commit:
commit fdf6d7de2e77f0986b01532c4e1913602e006d6b
Author: Alexandre Julliard <julliard(a)winehq.org>
AuthorDate: Thu Mar 11 18:04:48 2021 +0100
Commit: Alexandre Julliard <julliard(a)winehq.org>
CommitDate: Thu Mar 11 18:10:42 2021 +0100
kernel32/tests: Add some tests for the behavior of queries on a dead
process.
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
--
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=49801
Bug ID: 49801
Summary: Freight Yard Manager: Crashes on start
Product: Wine
Version: 5.15
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: blue(a)blu3wolf.com
Distribution: ---
Created attachment 68114
--> https://bugs.winehq.org/attachment.cgi?id=68114
exception text
On running, Freight Yard Manager V5.9.17 (and all previous versions tested)
throws an unhandled System.InvalidProgramException: Invalid IL code. This does
not happen on any tested Windows system.
--
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=51216
Bug ID: 51216
Summary: In Wine riched20:txtsrv has a succeeding todo in the
ar-MA, he-IL and ja-JP locales
Product: Wine
Version: 6.8
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: richedit
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
In Wine riched20:txtsrv has a succeeding todo in the ar-MA, he-IL and ja-JP
locales:
https://test.winehq.org/data/patterns.html#riched20:txtsrv
txtsrv.c:807: Test succeeded inside todo block: got wrong width: 72, expected:
72 {+1}.
The succeeding todo was introduced in this commit:
commit e7b42deaf2a18e32313e2da02566905180986760
Author: Huw Davies <huw(a)codeweavers.com>
AuthorDate: Thu Mar 25 09:10:28 2021 +0000
riched20: Implement TxGetNaturalSize().
Signed-off-by: Huw Davies <huw(a)codeweavers.com>
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
References:
https://www.winehq.org/pipermail/wine-devel/2021-March/183576.htmlhttps://www.winehq.org/pipermail/wine-devel/2021-April/185835.html
>From that email:
| So I don't know how to avoid getting this failure in every
| nightly WineTest run.
|
| Is it a font problem?
| Making the todo conditional on the locale feels iffy.
| Same for skipping the test based on the locale. Fix the
| implementation some more so it works on all locales?
--
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=34734
Bug #: 34734
Summary: Dino Crisis 2 Demo website-like launcher doesn't run
the game (it doesn't respond to clicking)
Product: Wine
Version: 1.7.4
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: winebugs140(a)gmail.com
Classification: Unclassified
Created attachment 46311
--> http://bugs.winehq.org/attachment.cgi?id=46311
Dino Crisis 2 Demo Launcher Log
If you try to launch the game with it, nothing happens. Also, if you click on,
for example, 'Help' the content isn't displayed.
--
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=29011
Bug #: 29011
Summary: Non-standard serial baud rates are not reported
correctly.
Product: Wine
Version: 1.2.2
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: jstutch(a)googlemail.com
Classification: Unclassified
Running VCDS-Lite 1.1 (connects to car diagnostics), with a FTDI-based
USB-Serial cable, when a non-standard baud rate is set on the port (10.4Kbps I
think), and the rate is read back by the program, wine reports
"err:comm:get_baud_rate unknown speed 1000", and returns an error to the
program. This breaks the serial port in the program until it is reset.
Replacing the offending lines in dlls/ntdll/serial.c: get_baud_rate with
"sbr->BaudRate = speed; break;", removes the error, and the program operates
correctly, although this may not be the right way to do this.
This was noted running Ubuntu Maverick (10.10), kernel 2.6.35-25-generic.
Running wine from the Maverick ubuntu package, rebuilt from package source to
correct the error as above.
Thanks,
JStutch
--
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=2571
Sabbir <robinssgraphics(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |robinssgraphics(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=51211
Bug ID: 51211
Summary: BioShock 2 Remastered crashes when enabling/disabling
vertical sync
Product: Wine
Version: 6.9
Hardware: x86-64
OS: Linux
Status: NEW
Severity: minor
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
Distribution: ---
Created attachment 70084
--> https://bugs.winehq.org/attachment.cgi?id=70084
backtrace
Can be enabled manually with changing UseVSync=0 to 1 in [Engine.RenderConfig]
section of Bioshock2SP.ini file located in 'drive_c/users/user_name/Application
Data/BioshockHD/Bioshock2'
wine-6.9-248-g96030ce738a
--
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=10204
Summary: Incorrectly raised FD_WRITE socket event
Product: Wine
Version: 0.9.48.
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: wine-net
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: rraptorr(a)nails.eu.org
Created an attachment (id=8812)
--> (http://bugs.winehq.org/attachment.cgi?id=8812)
FD_WRITE event on socket test program
According to MSDN WSAEventSelect function description
(http://msdn2.microsoft.com/en-us/library/ms741576.aspx), FD_WRITE event should
be raised only once after: a) successful connection b) WSAEWOULDBLOCK error
while in nonblocking mode.
MSDN description:
"The FD_WRITE network event is handled slightly differently. An FD_WRITE
network event is recorded when a socket is first connected with
connect/WSAConnect or accepted with accept/WSAAccept, and then after a send
fails with WSAEWOULDBLOCK and buffer space becomes available. Therefore, an
application can assume that sends are possible starting from the first FD_WRITE
network event setting and lasting until a send returns WSAEWOULDBLOCK. After
such a failure the application will find out that sends are again possible when
an FD_WRITE network event is recorded and the associated event object is set."
Unfortunately, it seems that in Wine 0.9.48 (and a few earlier versions too)
this event is raised every time it is possible to write to the socket. I've
created a simple test program (FD_WRITE-test.c) that shows this problem. When
ran on Windows I get:
lNetworkEvents: 2
lNetworkEvents: 0
but when ran on Wine:
lNetworkEvents: 2
lNetworkEvents: 2
which means that FD_WRITE was raised twice and it shouldn't.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=12366
Summary: Acclaim Cashbook startup failure - recompile visual
basic
Product: Wine
Version: 0.9.58.
Platform: PC
URL: http://www.acclaim.co.nz/download.htm
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: pcpavnz(a)gmail.com
Install routine executes properly, but when trying to run the installed
program, an error message pops up with a message about having to recompile the
visual basic module. I suspect the message indicates the cashbook program is
what it thinks requires recompiling, not the environment it is running from,
but thought I'd submit it anyway because so many people want accounting
software packages to work inside Linux and wine is so close very now to getting
it right.
url provided in the report form is for the free 90 day trial download, which is
no different to a full version.
--
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=40639
Bug ID: 40639
Summary: Can't run a game with Wine
Product: Wine
Version: 1.9.9
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: rmbeer2(a)gmail.com
Distribution: ---
Testing with GTA San Andreas.
Running direct with ./wine cause a halt and stooped game in the memory, i only
can run normaly if i execute ./wineboot with a active desktop.
Not show nothing in the 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.