December 2015 - Wine-Bugs - list.winehq.org

[Bug 28436] New: Panzer Corps: Buttons unusable
by wine-bugs＠winehq.org Dec. 12, 2018

Dec. 12, 2018

http://bugs.winehq.org/show_bug.cgi?id=28436 Summary: Panzer Corps: Buttons unusable Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: slackers.mailbox(a)gmail.com Created an attachment (id=36449) --> (http://bugs.winehq.org/attachment.cgi?id=36449) Panzer Corps: unusable buttons Clicking on buttons like "next", "supply", etc. has the following results: The buttons are highlighted when you click at them, but there is no appropriate response from the game - for instance, clicking on supply doesn't supply the unit. Instead, there are no mouse clicks recognized anymore. By opening up the purchase menu (hotkey "b") and clicking on "cancel" the mouse is working fine again. So you are limited to play the game using hotkeys exclusively. -- 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.

1 8

[Bug 16968] New: environment variables not passed across to commands that are run with popen
by wine-bugs＠winehq.org Dec. 12, 2018

Dec. 12, 2018

http://bugs.winehq.org/show_bug.cgi?id=16968 Summary: environment variables not passed across to commands that are run with popen Product: Wine Version: unspecified Platform: Other OS/Version: other Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: lkcl(a)lkcl.net this is the python test from test_os.py, but it should work equally as well in straight c-code. the only reason this test _happened_ to be run at all is because i have msys installed. normally, under windows, this test would be entirely skipped. # Bug 1110478 def test_update2(self): if os.path.exists("/bin/sh"): os.environ.update(HELLO="World") value = os.popen("/bin/sh -c 'echo $HELLO'").read().strip() self.assertEquals(value, "World") -- 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.

1 10

[Bug 19176] New: err:ddeml:WDML_CreateString Unknown code page 437
by wine-bugs＠winehq.org Dec. 11, 2018

Dec. 11, 2018

http://bugs.winehq.org/show_bug.cgi?id=19176 Summary: err:ddeml:WDML_CreateString Unknown code page 437 Product: Wine Version: 1.1.25 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: perchrh-wine(a)pvv.org Created an attachment (id=22166) --> (http://bugs.winehq.org/attachment.cgi?id=22166) Output of WINEDEBUG=+ddeml The installer of "Mordor 1 The Depths of Dejenol" (demo and full version) fails and the message "err:ddeml:WDML_CreateString Unknown code page 437". This may or may not be the reason it crashes, but in any case it looks to be a shortcoming in Wine's ddeml.dll -- 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.

1 15

[Bug 25283] New: Unimplemented function urlmon.dll.410
by wine-bugs＠winehq.org Dec. 11, 2018

Dec. 11, 2018

http://bugs.winehq.org/show_bug.cgi?id=25283 Summary: Unimplemented function urlmon.dll.410 Product: Wine Version: 1.3.7 Platform: x86-64 URL: http://http://download.microsoft.com/download/C/C/0/CC 0BD555-33DD-411E-936B-73AC6F95AE11/IE8-WindowsXP-x86-E NU.exe OS/Version: Linux Status: NEW Keywords: download Severity: minor Priority: P2 Component: urlmon AssignedTo: wine-bugs(a)winehq.org ReportedBy: kennybobs(a)o2.co.uk IE8 for XP crashes out with unimplemented function urlmon.dll.410 once installed. winetricks urlmon doesn't help, but urlmon.dll from Windows XP does. Tested in wine-1.3.7-233-g9867c39. -- 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.

1 10

[Bug 35900] New: L.A. Noire 1.3 (Steam version) crashes during upload of WINED3DFMT_DXT1 volume texture
by wine-bugs＠winehq.org Dec. 10, 2018

Dec. 10, 2018

https://bugs.winehq.org/show_bug.cgi?id=35900 Bug ID: 35900 Summary: L.A. Noire 1.3 (Steam version) crashes during upload of WINED3DFMT_DXT1 volume texture Product: Wine Version: 1.7.15 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Hello folks, with bug 35112 fixed, it runs a bit farther - only to crash again. Prerequisite: 'winetricks -q dotnet35sp1' --- snip --- $ pwd /home/focht/wine-apps/wineprefix-steam/wineprefix/drive_c/Program Files/Steam $ WINEDEBUG=+tid,+seh,+loaddll,+process,+msvcrt,+d3d,+d3d9,+d3d_texture,+d3d_surface wine ./steam.exe -applaunch 110800 >>~/Downloads/log.txt 2>&1 ... 0041:trace:d3d:device_update_volume device 0x31b52f00, src_volume 0x34dc7ea0, dst_volume 0x34dc7c78. 0041:trace:d3d_surface:wined3d_volume_map volume 0x34dc7ea0, map_desc 0x3328c4, box (nil), flags 0x10. 0041:trace:d3d_surface:wined3d_volume_map Base memory pointer 0x34e1c8e0. 0041:trace:d3d_surface:wined3d_volume_get_pitch Returning row pitch 128, slice pitch 2048. 0041:trace:d3d_surface:wined3d_volume_map No box supplied - all is ok 0041:trace:d3d_surface:wined3d_volume_map Returning memory 0x34e1c8e0, row pitch 128, slice pitch 2048. 0041:trace:d3d:context_acquire device 0x31b52f00, target (nil). 0041:trace:d3d:context_enter Entering context 0x31b804f8, level 1. 0041:trace:d3d_texture:wined3d_texture_bind texture 0x34dc7b10, context 0x31b804f8, srgb 0. 0041:trace:d3d:context_bind_texture glBindTexture call ok /home/focht/projects/wine/wine.repo/src/dlls/wined3d/context.c / 2065 0041:trace:d3d_surface:wined3d_volume_load_location Volume 0x34dc7c78, loading WINED3D_LOCATION_TEXTURE_RGB, have WINED3D_LOCATION_TEXTURE_RGB. 0041:trace:d3d_surface:wined3d_volume_load_location Location(s) already up to date. 0041:trace:d3d_surface:wined3d_volume_upload_data volume 0x34dc7c78, context 0x31b804f8, level 0, format WINED3DFMT_DXT1 (0x31545844). 0041:trace:seh:raise_exception code=c0000005 flags=0 addr=0xf5b6cde9 ip=f5b6cde9 tid=0041 0041:trace:seh:raise_exception info[0]=00000000 0041:trace:seh:raise_exception info[1]=34e40000 0041:trace:seh:raise_exception eax=00000000 ebx=00000000 ecx=00000004 edx=00000000 esi=34e40000 edi=f18a1728 0041:trace:seh:raise_exception ebp=00000038 esp=0033231c cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00010202 0041:trace:seh:call_stack_handlers calling handler at 0x1048b64 code=c0000005 flags=0 0041:trace:seh:call_stack_handlers handler at 0x1048b64 returned 1 0041:trace:seh:call_stack_handlers calling handler at 0x1060f8d code=c0000005 flags=0 0041:trace:seh:call_stack_handlers handler at 0x1060f8d returned 1 0041:trace:seh:call_stack_handlers calling handler at 0x1068980 code=c0000005 flags=0 0041:trace:seh:call_stack_handlers handler at 0x1068980 returned 1 0041:trace:seh:call_stack_handlers calling handler at 0x10521c5 code=c0000005 flags=0 0041:trace:seh:call_stack_handlers handler at 0x10521c5 returned 1 0041:trace:seh:call_stack_handlers calling handler at 0xedc215 code=c0000005 flags=0 --- snip --- This is with the Nvidia binary driver: $ nvidia-smi +------------------------------------------------------+ | NVIDIA-SMI 4.304... Driver Version: 304.119 | |-------------------------------+----------------------+----------------------+ | GPU Name | Bus-Id Disp. | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | |===============================+======================+======================| | 0 GeForce GT 425M | 0000:01:00.0 N/A | N/A | | N/A 61C N/A N/A / N/A | 13% 128MB / 1023MB | N/A Default | +-------------------------------+----------------------+----------------------+ Interestingly, when I disable DXTC support (commenting out the "GL_EXT_texture_compression_s3tc" from gl_extension_map[] in dlls/wined3d/directx.c -> http://source.winehq.org/git/wine.git/blob/62f7ba2555c475a65ad6bf143780b24f…) it runs much farther: several splash/intros can be seen until it crashes again (probably due to disabling of DXTC support), after lots of: --- snip --- ... 0042:trace:d3d9:d3d9_device_CreateCubeTexture iface 0xfa0a540, edge_length 128, levels 8, usage 0, format 0x31545844, pool 0, texture 0x332d84, shared_handle (nil). 0042:trace:d3d_texture:wined3d_texture_create device 0xfd12f00, desc 0x332c68, level_count 8, surface_flags 0, parent 0x3524e438, parent_ops 0xf5f77e78, texture 0x3524e448. 0042:fixme:d3d:debug_d3dusage Unrecognized usage flag(s) 0x10000000 0042:trace:d3d_texture:wined3d_texture_init texture 0x3524e488, texture_ops 0xf5eab0b0, layer_count 6, level_count 8, resource_type WINED3D_RTYPE_CUBE_TEXTURE, format WINED3DFMT_DXT1, multisample_type 0, multisample_quality 0, usage 0, pool WINED3D_POOL_DEFAULT, width 128, height 128, depth 1, device 0xfd12f00, parent 0x3524e438, parent_ops 0xf5f77e78, resource_ops 0xf5eab0bc. 0042:warn:d3d_texture:wined3d_texture_init Failed to initialize resource, returning 0x8876086c 0042:warn:d3d_texture:cubetexture_init Failed to initialize texture, returning 0x8876086c 0042:warn:d3d_texture:wined3d_texture_create Failed to initialize texture, returning 0x8876086c. 0042:warn:d3d9:cubetexture_init Failed to create wined3d cube texture, hr 0x8876086c. 0042:warn:d3d9:d3d9_device_CreateCubeTexture Failed to initialize cube texture, hr 0x8876086c. 0042:trace:seh:raise_exception code=c0000005 flags=0 addr=0xd66b7e ip=00d66b7e tid=0042 0042:trace:seh:raise_exception info[0]=00000001 0042:trace:seh:raise_exception info[1]=00000014 0042:trace:seh:raise_exception eax=00000000 ebx=00000008 ecx=10998bf0 edx=00110064 esi=10998b70 edi=31545844 0042:trace:seh:raise_exception ebp=1169bd90 esp=00332db8 cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00010246 0042:trace:seh:call_stack_handlers calling handler at 0x1048bb6 code=c0000005 flags=0 --- snip --- There is also bug 29128 - IMHO messed up with various issues, unusable for problem analysis. $ wine --version wine-1.7.15-133-g62f7ba2 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.

1 24

[Bug 37418] New: Unable to paste images from linux clipboard to Wine apps workspace (affects Photoshop, Powerpoint etc.)
by wine-bugs＠winehq.org Dec. 10, 2018

Dec. 10, 2018

https://bugs.winehq.org/show_bug.cgi?id=37418 Bug ID: 37418 Summary: Unable to paste images from linux clipboard to Wine apps workspace (affects Photoshop, Powerpoint etc.) Product: Wine Version: 1.7.29 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: fincer89(a)hotmail.com Distribution: --- Note: This is not the same bug than 7372 (https://bugs.winehq.org/show_bug.cgi?id=7372) as it deals mostly with text/html issue. Pasting a raster image from the clipboard or from a website (using native linux web browser like Firefox) to the Photoshop workspace doesn't work. The paste button stays greyed out, no matter of what. The workaround, which is basically saving the image to the computer and opening to the Photoshop, is a cumbersome, less user-friendly and time consuming method: you need to save the image file and look for it from a local directory structure and then open it. Much more complicated than just copying the image to the linux clipboard and paste it to the Photoshop, isn't it? Very desirable Wine implementation would be a support for copy-pasting images from native linux programs to Windows-based programs straightforwardly without extra tricky steps needed. This is marked as a bug because the image pasting function is one of the fundemental functions in the program and, at the moment of writing this bug report, it does not work as it should do. All comments and ideas are welcome. -- 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.

1 17

[Bug 17107] New: compiler warnings in server/fd.c on NetBSD
by wine-bugs＠winehq.org Dec. 10, 2018

Dec. 10, 2018

http://bugs.winehq.org/show_bug.cgi?id=17107 Summary: compiler warnings in server/fd.c on NetBSD Product: Wine Version: 1.1.13 Platform: PC OS/Version: NetBSD Status: NEW Keywords: download, source Severity: enhancement Priority: P2 Component: wineserver AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com fd.c: In function 'set_fd_epoll_events': fd.c:580: warning: assignment makes integer from pointer without a cast fd.c:581: warning: assignment makes integer from pointer without a cast Only appears on NetBSD, but not OpenBSD/FreeBSD. Vincent Povirk helped me investigate on IRC, and looks like the problem is that on FreeBSD, in /usr/include/sys/event.h you've got: struct kevent { uintptr_t ident; /* identifier for this event */ short filter; /* filter for event */ u_short flags; u_int fflags; intptr_t data; void *udata; /* opaque user data identifier */ }; But on NetBSD: struct kevent { uintptr_t ident; /* identifier for this event */ uint32_t filter; /* filter for event */ uint32_t flags; /* action flags for kqueue */ uint32_t fflags; /* filter flag value */ int64_t data; /* filter data value */ intptr_t udata; /* opaque user data identifier */ }; Note the difference in udata 'void *' vs 'intptr_t'. Relevant lines from the code: EV_SET( &ev[0], fd->unix_fd, EVFILT_READ, 0, NOTE_LOWAT, 1, (void *)user ); EV_SET( &ev[1], fd->unix_fd, EVFILT_WRITE, 0, NOTE_LOWAT, 1, (void *)user ); removing (void *) or changing it to intptr_t fixes the warning, but doesn't seem a proper fix. Probably needs an ifdef or typedef, but I'll leave that for someone else to decide. -- 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.

1 5

[Bug 27374] New: FAR: Alt-tab will cause "alt" key to be left as pressed when returning to console window (regression)
by wine-bugs＠winehq.org Dec. 9, 2018

Dec. 9, 2018

http://bugs.winehq.org/show_bug.cgi?id=27374 Summary: FAR: Alt-tab will cause "alt" key to be left as pressed when returning to console window (regression) Product: Wine Version: 1.3.21 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: singularita(a)gmail.com When I updated wine I noticed that when I alt-tabbed out of console window with opensource FAR (http://www.farmanager.com/opensource.php?l=en) file manager (run via "wineconsole.exe --backend=user") and then either alt-tabbed back or changed focus using mouse, Alt key was stuck as pressed (therefore pressing F10 resulted in program receiving Alt+F10, arrow down resulted in Alt+arrow down, etc ...). Pressing and releasing the Alt key after alt-tabbing back fixes the issuem, though it is slightly annoying. This does not happen before, in good versions when alt-tabbed back, alt returned to normal and pressing a key would result in program receiving just that key. I've verified that the bug is still present in current head of master in git and I've run the regression test to find the commit that introduced this bug: Result of regression test: bc4afb078677095468d4ee8f9a15c18cbb47bbbf is the first bad commit commit bc4afb078677095468d4ee8f9a15c18cbb47bbbf Author: Alexandre Julliard <julliard(a)winehq.org> Date: Tue Mar 1 11:54:55 2011 +0100 server: Don't pass a thread id to send_hardware_message, determine it from the window. :040000 040000 4e7ac89f77a4ddc31fd947151c34d0acadc5dcc0 a3d857abf43a1eed9fcb6837ea006ac00d80a1a7 M dlls :040000 040000 7247b4b93aca9c98394638ccd0c48a788133a8cd 45aed0fb1bc86b403af16666b3fa5963c2abaf7d M include :040000 040000 469f40ddbdca23554a397c5122a78e09a13e2c75 f118b4fd2fb23ecbde100798c68b3221fe5ec2fc M server -- 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.

1 13

[Bug 28810] New: d3dx9_36/tests/mesh.ok: D3DXLoadMeshTest fails under valgrind
by wine-bugs＠winehq.org Dec. 7, 2018

Dec. 7, 2018

http://bugs.winehq.org/show_bug.cgi?id=28810 Bug #: 28810 Summary: d3dx9_36/tests/mesh.ok: D3DXLoadMeshTest fails under valgrind Product: Wine Version: 1.3.30 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3dx9 AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com CC: wine-bugs(a)winehq.org Classification: Unclassified Under Valgrind, "make mesh.ok" fails with mesh.c:2333: Test failed: Vertex[7]: Expected diffuse b3ffffff, got b2ffffff mesh.c:2333: Test failed: Vertex[11]: Expected diffuse b3ffffff, got b2ffffff mesh.c:2333: Test failed: Vertex[18]: Expected diffuse b3ffffff, got b2ffffff mesh.c:2406: Test failed: Vertex[7]: Expected diffuse b3ffffff, got b2ffffff mesh.c:2406: Test failed: Vertex[11]: Expected diffuse b3ffffff, got b2ffffff mesh.c:2406: Test failed: Vertex[18]: Expected diffuse b3ffffff, got b2ffffff This is on my i5 laptop, nvidia GeForce GTS 360M, NVIDIA 280.13. The test passes without valgrind. -- 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.

1 18

[Bug 37863] New: Halo only works using Nvidia graphics
by wine-bugs＠winehq.org Dec. 7, 2018

Dec. 7, 2018

https://bugs.winehq.org/show_bug.cgi?id=37863 Bug ID: 37863 Summary: Halo only works using Nvidia graphics Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: vroom.henderson(a)gmail.com Distribution: --- Using GPUs other than Nvidia (confirmed with Intel and AMD), Halo will launch but will just display a black screen. The music and menu sounds work correctly when the arrow keys are pressed giving evidence that other than the graphics component, the game is still actually running. When the game is placed in "Safe Mode" the screen is all black except for some flashing vertices in the lower right quadrant of the screen. The terminal also outputs the following error repeatedly: fixme:d3d:process_vertices_strided Didn't expect the destination to have a normal -- 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.

1 16