http://bugs.winehq.org/show_bug.cgi?id=26549
Summary: GomezPEER fails to set processor priority
Product: Wine
Version: 1.3.16
Platform: x86-64
URL: http://lastmile.gomez.com/PEERInstall.exe
OS/Version: Linux
Status: NEW
Keywords: download
Severity: minor
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: kennybobs(a)o2.co.uk
GomezPEER sets its background process (an instance of java.exe) to the lowest
(idle) priority in Windows. It fails to do so under Linux. Does Wine lack the
ability to set process priorities, perhaps?
Apologies if a similar bug is already open but I could not find one.
On newer systems this is not a problem, but on older system the PEER can
consume 100% CPU while processing. The app is designed so that performance of
the PC is not affected, which of course it isn't under Windows (save the usual
Windows-related problems) but it is under Wine.
I'm not sure if I/O priority is also set.
The following does not work as a workaround:
$nice -n19 wine ~/blah/GomezPEER.exe
because this then sets all the Wine components to -n19 and can badly affect the
performance of other apps running under Wine.
Instead, the workaround I use is:
$wineserver -p15
$nice -n19 wine ~/blah/GomezPEER.exe
This way the wineserver remains at normal priority. winedevice.exe in this
case still receives -n19 priority, however.
Console log:
fixme:win:EnumDisplayDevicesW ((null),0,0x73a83c,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),1,0x73a83c,0x00000000), stub!
fixme:ddraw:DirectDrawEnumerateExA flags 0x00000001 not handled
fixme:win:EnumDisplayDevicesW ((null),0,0x74b69c,0x00000000), stub!
fixme:font:WineEngCreateFontInstance Untranslated charset 255
fixme:time:GetSystemTimes (0xd9ee5a0,0xd9ee5b0,0xd9ee5a8): Stub!
fixme:time:GetSystemTimes (0xd9ee5a0,0xd9ee5b0,0xd9ee5a8): Stub!
--
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=53976
Bug ID: 53976
Summary: ntoskrnl.exe:ntoskrnl - test_pnp_devices() fails on
Windows 7
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: ntoskrnl
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
ntoskrnl.exe:ntoskrnl - test_pnp_devices() fails on Windows 7:
ntoskrnl.c:1637: Test failed: got flags 0x400
See https://test.winehq.org/data/patterns.html#ntoskrnl.exe:ntoskrnl
This failure was first detected by the TestBot in MR!1398:
https://gitlab.winehq.org/wine/wine/-/merge_requests/1398
Which then got merged:
commit f801ac97fbcbef5618eadf1fb922a2d0f0873c4d
Author: Zebediah Figura <zfigura(a)codeweavers.com>
Date: Wed Nov 16 19:53:54 2022 -0600
ntoskrnl: Set SPDRP_CONFIGFLAGS in install_device_driver().
--
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=52964
Bug ID: 52964
Summary: kernel32:locale - test_CompareStringA() fails on Wine
in Hindi
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:locale - test_CompareStringA() fails on Wine in Hindi:
locale.c:1929: Test failed: expected CSTR_LESS_THAN, got 2
locale.c:1931: Test failed: expected CSTR_GREATER_THAN, got 2
https://test.winehq.org/data/patterns.html#kernel32:locale
This test had very similar failures on Windows with the Hindi + UTF-8
configuration (see bug 52869). But while the failures on Windows have been
fixed, the ones in Wine persist.
A bisect indicates they started with the commit below (before the matching
Windows failures got fixed):
commit 8993e15cfa5b77ac2487239354ffe63bbc5e562d
Author: Alexandre Julliard <julliard(a)winehq.org>
Date: Mon Apr 11 17:21:47 2022 +0200
kernelbase: Support UTF-7/8 codepages in get_codepage_table().
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=53990
Bug ID: 53990
Summary: Serious Sam 2 crashes with OpenGL renderer
Product: Wine
Version: 7.22
Hardware: x86-64
URL: https://archive.org/details/SeriousSam2NewDemo
OS: Linux
Status: NEW
Keywords: download, regression
Severity: normal
Priority: P2
Component: opengl
Assignee: wine-bugs(a)winehq.org
Reporter: gyebro69(a)gmail.com
CC: rbernon(a)codeweavers.com
Regression SHA1: 50ab0f8f7123fa82ce7268cbe26303dec4f76680
Distribution: ---
Created attachment 73574
--> https://bugs.winehq.org/attachment.cgi?id=73574
terminal output
When using the OpenGl renderer the game crashes after the loading screen with
an error message: "The application has malfunctioned and it will now close."
The game quits afterwards.
The problem is present since
commit 50ab0f8f7123fa82ce7268cbe26303dec4f76680
Author: Rémi Bernon <rbernon(a)codeweavers.com>
Date: Mon Nov 7 16:34:20 2022 +0100
opengl32: Use manual win32 thunks for glMapBuffer (et al.).
To reproduce the problem with the demo version:
1. install the demo.
2. run Sam2.exe at least once so that the configuration file Sam2.ini is
properly created (by default the game is set up to use the Direct3D renderer).
3. exit the game and open Sam2.ini, located in '..Serious Sam 2
Demo/Content/SeriousSam2'. Look for the option 'gfx_iAPI = 2' under section
[Engine] and change it to 'gfx_iAPI = 1' to utilize the OpenGL renderer.
4. Start the demo again, start a new game, select difficulty etc. The
pre-rendered cutscenes work properly, the crash happens when loading the first
level.
Serious Sam 2 - New Demo.exe (371M)
md5sum: 1cd1aca3a854279a26483095d556c8bc
Wine-7.22
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: NVIDIA GeForce GT 730/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 470.141.03
OpenGL core profile shading language version string: 4.60 NVIDIA
--
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=53912
Bug ID: 53912
Summary: Static initialization in Winelibs may hang the loader
as of Wine 7.21
Product: Wine
Version: 7.21
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winelib
Assignee: wine-bugs(a)winehq.org
Reporter: mail(a)robbertvanderhelm.nl
Distribution: ---
Static initialization in Winelibs may cause the loader to stall as of Wine
7.21.
Compiling the below file using `wineg++ -o main main.cpp -m64 -mwindows` and
then running `./main.exe` will hang indefinitely. I noticed that this happens
with LoadCursor(). Other functions may be affected similarly.
#include <windows.h>
static const HCURSOR arrow_cursor = LoadCursor(nullptr, IDC_ARROW);
int main(int argc, char* argv[]) {
return 0;
}
--
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=53884
Bug ID: 53884
Summary: Project Ignis: EDOPro corrupted textures on resizing
Product: Wine
Version: 7.20
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: edoardo762(a)gmail.com
Distribution: ---
Created attachment 73421
--> https://bugs.winehq.org/attachment.cgi?id=73421
Corrupted textures
I'm the lead developer of this application
(https://projectignis.github.io/download.html), and seldom i test the windows
build on wine to see if it plays nicely.
The program uses the Irrlicht engine that uses directx9 as its default windows
backend.
Today i tried running the program after updating wine to 7.20, and i discovered
that now textures get corrupted when resizing the window (see attached image)
(when the window is resized, the program generates all the textures with the
new size).
I checked older wine versions, and wine 7.19 is the version where this issue
appears for the first time, and it's still present in the version 7.20.
--
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=52394
Bug ID: 52394
Summary: "Control panel" -> "Add/Remove Programs" in builtin
wine explorer is not working
Product: Wine
Version: 7.0-rc5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: galdralag(a)bk.ru
Distribution: ---
After clicking on "Add/Remove Programs" in "Control panel" nothing happens.
Earlier (a few months ago) it was working.
In control panel 3 items and clicking on any shows nothing.
--
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=46538
Bug ID: 46538
Summary: Unreal Tournament (UT99): mouse clicks in main menu
work only once (regression)
Product: Wine
Version: 4.0
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: nowic(a)wenner.ch
Distribution: ---
Created attachment 63395
--> https://bugs.winehq.org/attachment.cgi?id=63395
Commandline output
The main menu drop downs only works the first time using the mouse. After the
first click only navigation using the keyboard works which is quite annoying.
I remember that this worked without issues in a previous version of wine.
Probably wine < 3.0.
GPU: GeForce 940MX
--
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=54000
Bug ID: 54000
Summary: user32:win - test_mouse_input() gets an unexpected
0x60 message on Windows 11
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:win - test_mouse_input() gets an unexpected 0x60 message on Windows 11:
win.c:4513: Test failed: hwnd 0000000000C6043C message 0060
win.c:4519: Test failed: message 0060 available
See https://test.winehq.org/data/patterns.html#user32:win
I could not find the what the 0x60 message corresponds to but, according to the
tests, it is specific to Windows 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=53911
Bug ID: 53911
Summary: DC++ is no longer able to retrieve file list from
another user.
Product: Wine
Version: 6.12
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winsock
Assignee: wine-bugs(a)winehq.org
Reporter: dee3shee7aeno4(a)mailinator.com
Distribution: ---
Since following commit DC++ is no longer able to retrieve the file list
from another user:
commit 8312539efe18533f6e2b35882d12e9d1bcbefa0d
Author: Zebediah Figura <z.figura12(a)gmail.com>
Date: Fri Jun 25 20:21:08 2021 -0500
ws2_32: Use IOCTL_AFD_WINE_GET_SO_RCVBUF.
Signed-off-by: Zebediah Figura <z.figura12(a)gmail.com>
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
It looks like the application retrieves the buffer size
via a call to getsockopt(SO_RCVBUF), but unfortunately
receives a size of zero since the above commit.
The commit seems to not call getsockopt in the DC++ process any longer,
instead it returns the value from a wineserver call.
Wine-gdb> bt
#0 WS_getsockopt (s=<optimized out>, level=<optimized out>, optname=<optimized
out>, optval=0x3f2fba8 "", optlen=<optimized out>) at
wine/dlls/ws2_32/socket.c:2571
#1 0x0000000000667c7f in <lambda()>::operator() (__closure=<synthetic
pointer>) at dcpp/Socket.cpp:510
#2 dcpp::(anonymous
namespace)::check<dcpp::Socket::getSocketOptInt(int)::<lambda()> >
(blockOk=false, f=...) at dcpp/Socket.cpp:52
#3 dcpp::Socket::getSocketOptInt (this=0x29d6fc0, option=option@entry=4098) at
dcpp/Socket.cpp:510
#4 0x00000000005bd3aa in dcpp::BufferedSocket::threadAccept
(this=this@entry=0x29d8820) at dcpp/BufferedSocket.cpp:179
#5 0x00000000005c4418 in dcpp::BufferedSocket::checkEvents
(this=this@entry=0x29d8820) at dcpp/BufferedSocket.cpp:463
#6 0x00000000005c48e8 in dcpp::BufferedSocket::run (this=0x29d8820) at
dcpp/BufferedSocket.cpp:498
#7 0x000000000098c3da in dcpp::Thread::starter (p=<optimized out>) at
dcpp/Thread.h:107
https://sourceforge.net/p/dcplusplus/code/ci/default/tree/dcpp/Socket.cpp#l…https://sourceforge.net/p/dcplusplus/code/ci/default/tree/dcpp/BufferedSock…
The wineserver sock->rcvbuf gets initialized here:
(gdb) bt
#0 create_socket () at wine/server/file.h:240
#1 0x0000555946fd7619 in accept_socket (sock=0x555949c36cc0) at
wine/server/sock.c:1618
#2 0x0000555946fd9c9e in sock_ioctl (fd=<optimized out>, code=<optimized out>,
async=0x555949c3fb40) at wine/server/sock.c:2016
#3 0x0000555946fb4481 in req_ioctl (req=0x555949c371c8, reply=0x7ffcfd2ec140)
at wine/server/fd.c:2794
#4 0x0000555946fd39cb in call_req_handler (thread=<optimized out>) at
wine/server/request.c:312
#5 0x0000555946fdcd10 in thread_poll_event (fd=<optimized out>,
event=<optimized out>) at wine/server/thread.c:388
#6 0x0000555946fb1c67 in main_loop_epoll () at wine/server/fd.c:525
#7 0x0000555946fb1ece in main_loop () at wine/server/fd.c:985
#8 0x0000555946fa3a80 in main ()
And following change makes DC++ work again with
wine-7.21, unsure if this is correct:
--- a/server/sock.c
+++ b/server/sock.c
@@ -1998,6 +1998,7 @@ static struct sock *accept_socket( struct sock *sock )
acceptsock->window = sock->window;
acceptsock->message = sock->message;
acceptsock->connect_time = current_time;
+ acceptsock->rcvbuf = sock->rcvbuf;
if (sock->event) acceptsock->event = (struct event *)grab_object(
sock->event );
--
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.