https://bugs.winehq.org/show_bug.cgi?id=8051
--- Comment #188 from Alexandr Oleynikov <sashok.olen(a)gmail.com> ---
What kind of an update do you want exactly?
It doesn't look like Wine 9.0-rc1 had any changes related to software vertex
processing, so the bug stands as it is. And it's probably unlikely that this
will change, especially with DXVK now being the preferred backend for games
(which like I mentioned before fully implements this feature).
--
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=8051
--- Comment #187 from Chebanenko Igor <chebanenkoigor93(a)gmail.com> ---
Wine 9.0-rc1 was released. Any updates?
--
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.
https://bugs.winehq.org/show_bug.cgi?id=55548
Bug ID: 55548
Summary: kernel32:power - test_GetSystemPowerStatus() fails on
macOS
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Mac OS X
Status: NEW
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
kernel32:power - test_GetSystemPowerStatus() fails on macOS:
power.c:34: Test failed: expected TRUE
See https://test.winehq.org/data/patterns.html#kernel32:power
The failure is systematic and only happens macOS (see Remi's rbernon-macos-*
cloud test machines). It looks like the macOS implementation of
fill_battery_state() fails, presumably because of permission issues.
--
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=55965
Bug ID: 55965
Summary: Divide by zero error with Trackmania 2020 when loading
tracks [D3DMetal]
Product: Wine
Version: unspecified
Hardware: arm
OS: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: omgloldave(a)gmail.com
Created attachment 75555
--> https://bugs.winehq.org/attachment.cgi?id=75555
backtrace log of game crashing when loading into a game.
Hi all, bit at a loss on where exactly to report this. I'm trying here first
and if it's not a problem with wine itself, please tell me where to poke
exactly.
So Trackmania 2020 has a rather weird error when it comes to using Apples new
GPTK layer. The game works amazingly... in the editor. You can load tracks and
drive them (with pretty remarkable quality).
However, when you load a track or join a server, the game crashes with a divide
by zero error. Additionally, in the editor, some graphical elements are weird
(i.e, some trees are not rendering, weird blown out textures etc) and you can't
render the track (aka "calculate shadows").
Luckily TM2020 is free to play to recreate this. Just open the game and try to
load any track. You can also recreate the editor weirdness by using the scenery
blocks.
I have used Whisky, Crossover (where this error log comes from), PortingKit and
vanilla wine and each yields the same results with various versions (all
released within the last 4-5 months). There's a bug report on Whisky on this
issue that's flagged specifically as an issue with wine (also I posted a
comment with no response: https://github.com/Whisky-App/Whisky/issues/235). I
currently use Parallels to play (which works fine, of course using a different
method of emulation), but with the new GPTK update the performance increase is
apparently massive, so it would be nice to see this fixed.
I'm not going to make this harder by guessing, as I am not super technical with
Wine. However looking at the backtrace and just glancing at the error-log I
think the problem is down to Wine's interaction with GPTK/D3DMetal, or with
GPTK/D3D/Apple itself.
Weirdly, I don't *think* this is a WINE bug necessarily, TM2020 is my favourite
game, so more than anything I kinda want to know *where* exactly to report this
error in detail if not here. Plus I want someone far more well versed than me
to explain how to report this bug.
Is this an Apple issue or a WINE issue or a skill issue?
Thanks for your help and all your hard work!
--
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=47028
Bug ID: 47028
Summary: WinSCP hosts list missing indentation
Product: Wine
Version: 4.6
Hardware: x86-64
URL: http://winscp.net/download/winscp577.zip
OS: Mac OS X
Status: NEW
Keywords: download, source
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: gijsvrm(a)gmail.com
CC: jr98(a)gmx.net
Created attachment 64194
--> https://bugs.winehq.org/attachment.cgi?id=64194
terminal output, +message log, screenshots
On windows there is space between the edge of the box and the icons.
To reproduce, run WinSCP.exe and you can see the hosts list on the left.
Attached is a zip containing terminal output, a +message log and screenshots
for comparison.
--
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=54397
Bug ID: 54397
Summary: Wine does not populate prefixes with 32-bit dlls
Product: Wine
Version: 7.22
Hardware: x86-64
OS: FreeBSD
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: eralegrid(a)hotmail.com
Starting from Wine 7.22, Wine doesn't copy any 32-bit files into new prefixes.
For a 32-bit prefix, only system.reg/user.reg/user.reg and a bunch of empty
directories are created.
For a 64-bit prefix, things appear to be normal aside from
$WINEPREFIX/drive_c/windows/syswow64 being empty.
It seems this situation started with commit
d45de318748639cfd1e80a976b39f5e19213990f.
--
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=13778
Summary: Date and Time display
Product: Wine
Version: unspecified
Platform: Other
OS/Version: other
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: rx9tx(a)qrz.ru
Created an attachment (id=13813)
--> (http://bugs.winehq.org/attachment.cgi?id=13813)
wine window
The problem is that in a Windows application running in Wine the date and time
displayed as digit like 39591.6425810185 instead of May-23-2008, 15:25, see
pictures http://rx9tx.qrz.ru/wine.jpg and http://rx9tx.qrz.ru/windows.jpg .
Same about the frequency value 0000000000028.012100 in mHz (28.0121 mhz) is
shown like 298112000.0. I dont know what kind of database is used, but it has
the .isd extension, also .isf, .ism, .isl files are present.
Here's the excerption from the database with the data shown on the pics:
http://rx9tx.qrz.ru/log.txt
--
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=50338
Bug ID: 50338
Summary: Open/save dialog don't show current folder path.
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: comdlg32
Assignee: wine-bugs(a)winehq.org
Reporter: ltgustavsen(a)gmail.com
Distribution: ---
Created attachment 68924
--> https://bugs.winehq.org/attachment.cgi?id=68924
Screenshot from linux. Missing folder path.
Hello
The opening/save dialog in Picture Window 8 from dl-c.com doesn't work as
expected. There is no way to see which folder I’m in. The green back arrows on
the top don’t work when I open the default catalog. I have to start each time
in the left sidebar and browse to the correct directory. If I do so, the arrows
work.
I have attached some screenshots. And a debug file.
I have tested with wine-5.0.3 and wine-6.0-rc2
I have installed Picture Window this way
winetricks vcrun2019
wine msiexec /i Picture\ Window\ Pro.msi
--
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=44016
Bug ID: 44016
Summary: Improve path handling in Open and Save dialogs
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: comdlg32
Assignee: wine-bugs(a)winehq.org
Reporter: kolan_n(a)mail.ru
Distribution: ---
Current open and save dialogs have large usability issues.
1 When I paste a path of a folder into it to make it open that folder in itself
it doesn't work and writes an error.
2 I also expect this dialog to accept the absolute path in linux rootfs.
3 I also expect it to show a drop-down menu as in Windows.
--
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.