https://bugs.winehq.org/show_bug.cgi?id=58078
Bug ID: 58078
Summary: StarCraft Remastered: game is not started with
wine-10.5
Product: Wine-staging
Version: 10.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dimich.dmb(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
The game is not started with wine-10.5
StarCraft.exe process is running and consuming 100% of one CPU core. No video
mode changed, no game window created.
Battle.net launcher is displaying StartCraft as "Playing Now".
After downgrading wine to 10.4 the game starts and works fine.
StartCraft: v1.23.10.13515
OS: Arch Linux
Kernel v6.14.1
GPU: Nvidia, proprietary driver v570.133.07
--
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=58458
Bug ID: 58458
Summary: Wolfenstein: The Old Blood (Wolfenstein: The New
Order) fails to start with EGL opengl backend
Product: Wine
Version: 10.11
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: gyebro69(a)gmail.com
CC: rbernon(a)codeweavers.com
Distribution: ArchLinux
Created attachment 78909
--> http://bugs.winehq.org/attachment.cgi?id=78909
terminal output
When the new EGl Opengl backend is enabled the game plays the intro videos but
stops with an error before the main menu could be loaded.
The game console shows an error:
FATAL ERROR: idPixelUnpackBuffer::AllocBufferObject: failed
The next installment in the series (Wolfenstein II: The New Colossus) starts
properly with UseEGL=Y. All these games are using the Vulkan renderer.
wine-10.11-88-g730f65e737a
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 575.64.03
--
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=55151
Bug ID: 55151
Summary: PC crashes after endlessly eating up memory
Product: Wine
Version: 8.11
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: cmd
Assignee: wine-bugs(a)winehq.org
Reporter: axis6404(a)proton.me
Distribution: ---
example script (selfdel.bat):
:REP
del "selfdel.bat"
if exist "selfdel.bat" goto REP
wine selfdel.bat (An infinite loop occurs. Until it eats up all the memory and
the PC stops.)
The koeiuc.bat in Steam games made by Koei eats up all the memory and crashes
the PC.
--
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=58439
Bug ID: 58439
Summary: REGRESSION: trying to edit a text field immediately
causes the previous content to be completely erased
Product: Wine
Version: 10.9
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: scallegari(a)arces.unibo.it
Distribution: ---
Hi, I am recently experimenting a regression and even if I cannot say in which
version it was introduced, I am almost sure it is not the last one (but before)
and that it is indeed a regression (a few month ago the behavior was
different).
I am working with a software called LTspice (that is closed source but free,
which surely helps repro) and available from
https://www.analog.com/en/resources/design-tools-and-calculators/ltspice-si….
Incidentally, the developers of this code have traditionally been wine-friendly
(even if they do not offer a linux version of their code, neither they provide
support for running it in wine, they have tried to ensure that it could be used
with wine).
This software is a circuit simulator with a schematic capture component. You
can pick and place components and edit the values of their parameters using
some dialog boxes. Often there are multiple things that can be tuned and the
dialog box is arranged as a sort of a table, where some cells are editable.
In order to adjust things, until some simulation results are satisfactory, it
is common to modify some parameters multiple times and in doing so it is good
to be able to edit the previous value.
Unfortunately, in recent times it has become impossible to do so when running
the software with wine. As soon as you try to modify a value, the value
disappears and you remain with an empty field to be filled from scratch.
--
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=58602
Bug ID: 58602
Summary: Screen Issue in Colin McRae Rally 2
Product: Wine
Version: 10.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winex11.drv
Assignee: wine-bugs(a)winehq.org
Reporter: marcinzw(a)gmail.com
Regression SHA1: ae487930f8d3811a7434dc2cbb561982c894f5ba
Distribution: ---
The screen issue in Colin McRae Rally 2, originally reported in Bug #58488, is
still happening in Wine 10.13. After the intro video plays, the screen just
stays frozen when running the game in “Emulate a virtual desktop” mode – you
can still hear the sound, but nothing shows up. The patch I posted in Bug
#58488 still fixes it, though.
--- a/dlls/winex11.drv/opengl.c
+++ b/dlls/winex11.drv/opengl.c
@@ -1462,7 +1462,7 @@ static BOOL x11drv_surface_swap( struct opengl_drawable
*base )
if (pglXWaitForSbcOML) pglXWaitForSbcOML( gdi_display, gl->drawable,
target_sbc, &ust, &msc, &sbc );
}
- if (InterlockedCompareExchange( &base->client->offscreen, 0, 0 ))
+ //if (InterlockedCompareExchange( &base->client->offscreen, 0, 0 ))
{
if (!pglXWaitForSbcOML) XFlush( gdi_display );
client_surface_present( base->client, gl->hdc );
--
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=58534
Bug ID: 58534
Summary: Grand Theft Auto: Vice City intros play with a black
screen
Product: Wine
Version: 10.10
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: regression
Severity: normal
Priority: P2
Component: win32u
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
CC: rbernon(a)codeweavers.com
Regression SHA1: e5e2fd0a5209b0d07233d294e0ace5f1e41dfed5
Distribution: ---
State of df00a5c097cd9cb292952f5307ee96d96fbc58b4 works good.
--
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=49195
Bug ID: 49195
Summary: Multiple 4k demoscene OpenGL demos crash on startup
(failure to lookup atom 0xC019 'static' from global
atom tables)
Product: Wine
Version: 5.8
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: focht(a)gmx.net
Distribution: ---
Hello folks,
extracted from bug 48898
My comment: https://bugs.winehq.org/show_bug.cgi?id=48898#c12
--- quote ---
To me it looks like bug 18490 ("Multiple games fail to set pixel format on D3D
device context created on desktop window (Empire: Total War, Napoleon: Total
War, Utopia City)") but for GL device context on the desktop window.
According to online information it's not allowed to do any rendering using this
context but enough to call functions like glGetString() etc.
Maybe some of the Wine graphics folks could weigh in with an opinion if this
limitation is already known / tracked in a bug?
--- quote ---
Henri's answer: https://bugs.winehq.org/show_bug.cgi?id=48898#c13
--- quote ---
I'm not aware of an existing bug report for this issue, no. It does strike me
as similar to bug 36506 though, and it would not particularly surprise me if
wglGetProcAddress() is supposed to return results consistent with
GL_EXTENSIONS/GL_VERSION here, even without a current GL context.
I seem to recall having established in the context of bug 18490 that creating a
GL context (or more specifically, setting a pixel format) on the desktop window
is indeed supposed to fail. In any case, this seems like of of those bugs that
would benefit from tests to establish what's supposed to happen.
--- quote ---
Turns out this was a side-effect of an earlier problem.
It was not supposed to be GetDC(NULL) (Desktop window).
--- snip ---
$ WINEDEBUG=+seh,+relay,+server,+class,+win,+msg wine ./End\ of\ time\ 720p.exe
>>log.txt 2>&1
...
0024:Call user32.ChangeDisplaySettingsA(00421288,00000004) ret=004200da
...
0024: get_desktop_window( force=0 )
0024: get_desktop_window() = 0 { top_window=00010020, msg_window=00010026 }
...
0024:Ret user32.ChangeDisplaySettingsA() retval=00000000 ret=004200da
0024:Call
KERNEL32.CreateThread(00000000,00000000,004201ca,004304e8,00000000,00000000)
ret=004200ee
...
0024:Ret KERNEL32.CreateThread() retval=00000080 ret=004200ee
00bc: *fd* 17 <- 38
00bc: init_thread( unix_pid=3683, unix_tid=3729, debug_level=1, teb=7ffd4000,
entry=004201ca, reply_fd=15, wait_fd=17, cpu=x86 )
0024:Call
user32.CreateWindowExA(00000000,0000c019,00000000,91000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000)
ret=004200f4
0024:trace:win:WIN_CreateWindowEx (null) #c019 ex=00000000 style=91000000 0,0
0x0 parent=(nil) menu=(nil) inst=(nil) params=(nil)
00bc: init_thread() = 0 { pid=0020, tid=00bc, server_start=1d62d3b280579be
(-2.9701360), info_size=0, version=603, all_cpus=00000003, suspend=0 }
0024:trace:win:dump_window_styles style: WS_POPUP WS_VISIBLE WS_MAXIMIZE
0024:trace:win:dump_window_styles exstyle:
...
00bc:Starting thread proc 0x4201ca (arg=0x4304e8)
...
0024: create_window( parent=00010020, owner=00000000, atom=c019,
instance=00000000, dpi=96, awareness=2, class=L"" )
0024: create_window() = INVALID_HANDLE { handle=00000000, parent=00000000,
owner=00000000, extra=0, class_ptr=00000000, dpi=0, awareness=0 }
0024:warn:win:create_window_handle error 6 creating window
0024:trace:class:GetClassInfoExW (nil) #c019 0x1518f9e0
0024:trace:class:CLASS_FindClass #c019 0x7e910000 -> not found
0024:Ret user32.CreateWindowExA() retval=00000000 ret=004200f4
--- snip ---
The failing window creation resulted in NULL handle which got passed to
user32.GetDC():
--- snip ---
0024:Call user32.GetDC(00000000) ret=004200fb
0024:trace:win:GetDCEx hwnd 0x10020, hrgnClip (nil), flags 00000003
...
0024: get_visible_region( window=00010020, flags=00000013 )
0024: get_visible_region() = 0 { top_win=00010020, top_rect={-1920,0;-1919,1},
win_rect={0,0;3200,1080}, paint_flags=00000001, total_size=16,
region={{-1920,0;1280,1080}} }
0024:Call
winex11.drv.GetDC(00030039,00010020,00010020,1518fde0,1518fdf0,00000013)
ret=7e97bd3e
0024:Ret winex11.drv.GetDC() retval=00000001 ret=7e97bd3e
0024:trace:win:GetDCEx (0x10020,(nil),0x13): returning 0x30039 (updated)
0024:Ret user32.GetDC() retval=00030039 ret=004200fb
--- snip ---
Well, the rest of the OpenGL story is known and the current behaviour makes
sense.
Back to the actual problem...
The creation of the window which ought the be used for OpenGL context/rendering
fails because atom 0xc019 can't be found/resolved.
I should have looked more carefully at the trace log and the demo disassembly.
--- snip ---
...
004200B6 | xor esi,esi |
004200B8 | push esi |
004200B9 | push esi |
004200BA | push esi |
004200BB | push esi |
004200BC | push esi |
004200BD | push esi |
004200BE | push esi |
004200BF | push esi |
004200C0 | push esi |
004200C1 | push 91000000 |
004200C6 | push esi |
004200C7 | push C019 | global atom!
004200CC | push esi |
004200CD | push 4 |
004200CF | push end of time 720p.421288 |
004200D4 | call dword ptr ds:[<&user32.ChangeDisplaySettingsA>] |
004200DA | push esi |
004200DB | push esi |
004200DC | push end of time 720p.4304E8 |
004200E1 | push end of time 720p.4201CA |
004200E6 | push esi |
004200E7 | push esi |
004200E8 | call dword ptr ds:[<&KERNEL32.CreateThread>] |
004200EE | call dword ptr ds:[<&user32.CreateWindowExA>] | fails
004200F4 | push eax |
004200F5 | call dword ptr ds:[<&user32.GetDC>] |
004200FB | mov edi,eax |
004200FD | mov dword ptr ds:[3AB08EC],eax |
00420102 | push esi |
00420103 | push edi |
00420104 | push esi |
00420105 | push end of time 720p.42125C |
0042010A | push edi |
0042010B | call dword ptr ds:[<&gdi32.ChoosePixelFormat>] |
00420111 | push eax |
00420112 | push edi |
00420113 | call dword ptr ds:[<&gdi32.SetPixelFormat>] |
00420119 | call dword ptr ds:[<&opengl32.wglCreateContext>] |
0042011F | push eax |
00420120 | push edi |
00420121 | call dword ptr ds:[<&opengl32.wglMakeCurrent>] |
00420127 | call dword ptr ds:[<&user32.ShowCursor>] |
0042012D | call end of time 720p.4202CC |
--- snip ---
The demoscene guys are crazy and fight for each saved byte ;-)
Courtesy of: http://www.pouet.net/topic.php?which=9894
--- quote ---
I was able to get 4 bytes off of a test 1k intro (Peach GLSL Shader of Japan)
by replacing the "edit" string with 0xC018, making it 1006 bytes instead of
1010. Nice.
...and then I got it down to 1004 bytes, because now "test eax, eax" compressed
better than "test ax, ax", which used to compress better sometime before this
newest change. ;) This 1k intro business is crazy, you'd really need some kind
of brute-force code masher that tries all possible combinations of code that
perform the same thing.
--- quote ---
--- quote ---
That´s mine since 2009 using DirectX9...someone told me using "static" instead
of "edit" would be better back then in some other thread...was iq if i remember
correctly.
The ATOM for "static" is 0xC019 btw, but be warned: it added 7 bytes here in my
first test, opposed to chopping off 4 bytes in case of "edit".
--- quote ---
--- quote ---
Oh, shit...i did the test the wrong way around...meaning the ATOM actually
chopped off 7 bytes in case of "static" vs. "0xC019" :/ :D
Yay, thanks for the nice trick, man! :)
--- quote ---
Also relevant, shows dump of global and typical local atom tables:
https://github.com/lungetech/ICAS/blob/master/logs/volatility/win32/output/…
Wine source:
https://source.winehq.org/git/wine.git/blob/9e26bc811656ad8eb901bffa5528b9c…
--- snip ---
407 /***********************************************************************
408 * CLASS_FindClass
409 *
410 * Return a pointer to the class.
411 */
412 static CLASS *CLASS_FindClass( LPCWSTR name, HINSTANCE hinstance )
413 {
414 static const WCHAR comctl32W[] =
{'c','o','m','c','t','l','3','2','.','d','l','l',0};
415 struct list *ptr;
416 ATOM atom = get_int_atom_value( name );
417
418 GetDesktopWindow(); /* create the desktop window to trigger builtin
class registration */
419
420 if (!name) return NULL;
421
422 name = CLASS_GetVersionedName( name, NULL, NULL, TRUE );
423
424 for (;;)
425 {
426 USER_Lock();
427
428 LIST_FOR_EACH( ptr, &class_list )
429 {
430 CLASS *class = LIST_ENTRY( ptr, CLASS, entry );
431 if (atom)
432 {
433 if (class->atomName != atom) continue;
434 }
435 else
436 {
437 if (strcmpiW( class->name, name )) continue;
438 }
439 if (!class->local || class->hInstance == hinstance)
440 {
441 TRACE("%s %p -> %p\n", debugstr_w(name), hinstance,
class);
442 return class;
443 }
444 }
445 USER_Unlock();
446
447 if (atom) break;
448 if (!is_comctl32_class( name )) break;
449 if (GetModuleHandleW( comctl32W )) break;
450 if (!LoadLibraryW( comctl32W )) break;
451 TRACE( "%s retrying after loading comctl32\n", debugstr_w(name) );
452 }
453
454 TRACE("%s %p -> not found\n", debugstr_w(name), hinstance);
455 return NULL;
456 }
--- snip ---
https://source.winehq.org/git/wine.git/blob/9e26bc811656ad8eb901bffa5528b9c…
$ sha1sum atz-end_of_time.zip
3a4ce3fd92e2fdd1a4533ee67d4809d3f2184f6b atz-end_of_time.zip
$ du -sh atz-end_of_time.zip
3.3M atz-end_of_time.zip
$ wine --version
wine-5.8-173-g9e26bc8116
Regards
--
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=58582
Bug ID: 58582
Summary: Rainmeter 4.5.23: crashes on X11 after refreshing
default skin Clock.ini
Product: Wine
Version: unspecified
Hardware: x86-64
URL: https://github.com/rainmeter/rainmeter/
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: win32u
Assignee: wine-bugs(a)winehq.org
Reporter: castelei(a)yahoo.com
Regression SHA1: 980a2e3c65bee1422adbe06fead768669835e3e1
Distribution: ---
Created attachment 79106
--> http://bugs.winehq.org/attachment.cgi?id=79106
WINEDEBUG=+synchronous,+seh Rainmeter 4.5.23
Reproduction:
1) Click on the Rainmeter icon on the system tray to open the 'Manage
Rainmeter' window.
2) Click on the 'Active skins' drop-down list and select
illustro\Clock\Clock.ini
3) Click the 'Refresh' button to the right.
This X11 error prints as the application crashes if run without +synchronous:
X Error of failed request: BadMatch (invalid parameter attributes)
Major opcode of failed request: 139 (RENDER)
Minor opcode of failed request: 4 (RenderCreatePicture)
Serial number of failed request: 15285
Current serial number in output stream: 15292
Found this regression on a merged patch newer than 10.12 (the newest
development release at this time) while working on an unrelated bug.
--
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=57806
Bug ID: 57806
Summary: visual and response lags in Guitar Pro v8.1.3 (build
121)
Product: Wine
Version: 9.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: acidbong(a)tilde.club
Distribution: ---
Created attachment 78013
--> https://bugs.winehq.org/attachment.cgi?id=78013
Guitar Pro in Wine-9.20
I've been using Wine-staging for running Guitar Pro on Linux (Gentoo, then
NixOS), and it's been smooth until 9.20 -> 9.22 update
(https://github.com/NixOS/nixpkgs/pull/359908, nixpkgs maintainers skipped
v9.21). Then visual lags (constant, as if the program runs at 5 FPS) started to
happen. Welp, they aren't solely visual, responsiveness also suffers. Audio,
however, doesn't lag and is still smooth.
The lag is also present on Wine10.
Regression also confirmed on Wine-development v9.22 and with a demo version of
the program and on different PCs (first on an Intel-based laptop (Core
i3-7100), then on an AMD-based one (AMD Ryzen 5 5500U)), both with integrated
GPUs.
Camera recording (not screen capture, because `simplescreenrecorder` (haven't
tried other tools) for some reason reduced these lags): https://0x0.st/8KNw.mp4
Logs are attached below.
--
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=38142
Bug ID: 38142
Summary: Approach fields box only show 3/4 of one line
Product: Wine
Version: 1.7.36
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ToddAndMargo(a)zoho.com
Distribution: ---
Created attachment 50869
--> https://bugs.winehq.org/attachment.cgi?id=50869
Field Box
Hi All,
Wine 1.7.36 and Smart Suite N9.8.0208.1200.
Would you guys please fix this for me. It is driving me NUTS!
In the "Find Assistant" the Fields box only shows about 3/4 on one line. It
makes it impossible to file the other lines in the box.
I will attach a screen shot
Many thanks,
-T
--
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.