February 2019 - Wine-bugs - list.winehq.org

[Bug 45826] New: Doom 2016 - Rendering issues
by wine-bugs＠winehq.org 31 Mar '19

31 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=45826 Bug ID: 45826 Summary: Doom 2016 - Rendering issues Product: Wine-staging Version: 3.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ahmed.com(a)aol.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 62283 --> https://bugs.winehq.org/attachment.cgi?id=62283 wine error log I can't run Doom 2016 with Mesa 18.1.7 or Mesa 18.1.8, so I tried Mesa 18.2.0-1 and the game started but it look so weird, and I can hear the menu sounds but I can't see the menu. System information: Operating system: Manjaro KDE GPU: AMD HD 8750M Driver: Mesa 18.2.0-1 Wine version: 3.15 staging-nine -- 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 30

[Bug 46224] New: ddraw-Create-rendering-targets-in-video-memory patch got borked between 3.19 and 3.20
by wine-bugs＠winehq.org 31 Mar '19

31 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=46224 Bug ID: 46224 Summary: ddraw-Create-rendering-targets-in-video-memory patch got borked between 3.19 and 3.20 Product: Wine-staging Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: sashok.olen(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Testing application - The Sims Complete Collection With 3.19, the game launches just fine, and I get `0009:fixme:ddraw:ddraw_surface_create Application wants to create rendering target in system memory, using video memory instead` fixmes in the terminal output, and the game starts. In 3.20, the game aborts the launch, and I don't get the fixmes. I suspect this rebase might have broke it: https://github.com/wine-staging/wine-staging/commit/a423a7087ff2dad6f2def0c… -- 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 12

[Bug 41107] New: Total Commander 8.52a Final has VERY slow folder icons rendering
by wine-bugs＠winehq.org 31 Mar '19

31 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=41107 Bug ID: 41107 Summary: Total Commander 8.52a Final has VERY slow folder icons rendering Product: Wine Version: 1.9.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: shell32 Assignee: wine-bugs(a)winehq.org Reporter: katsunori.kumatani(a)gmail.com Distribution: --- Created attachment 55313 --> https://bugs.winehq.org/attachment.cgi?id=55313 Terminal Output, not very useful Using the 32-bit version of Total Commander 8.52a Final (latest non-beta), when drawing/rendering the icons for folders, it is VERY slow. Download the 32-bit version here: http://totalcmd2.s3.amazonaws.com/tcmd852ax32.exe After installing and launching it, please do the following to reproduce: 1) Maximize the Window to have more folders on screen. 2) Near the top-left, to the right of the green "Refresh" button, click on the "Source: Only file names" button, this enables more folders visible at once to show the slow effect more. 3) Go/navigate to a folder which has around 200 folders, such as Z:\usr\share (depends on your Linux distro), it doesn't matter, just make sure it has a lot of folders to see how painfully slow it is. This problem of course is not present in Windows. Terminal output has been attached, however I don't think it has any useful information because [b]Total Commander version 7 exhibits almost the same terminal output, but IT IS NOT SLOW like 8.52a![/b] In fact it is almost instant when rendering folder icons, which look the exact same. If you turn off folder icons in Preferences, it is fast, so I know that they are the culprit, 100%. Btw, the version 9 beta does not seem to have this problem because it uses the system's folder icons (which are blue on my system) instead of internal. The internal ones are yellow. I hope you can track down and fix this bug with this information. -- 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 26

[Bug 45278] New: Vietcong: invisible objects (staging 3.9)
by wine-bugs＠winehq.org 31 Mar '19

31 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=45278 Bug ID: 45278 Summary: Vietcong: invisible objects (staging 3.9) Product: Wine-staging Version: 3.9 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: havran.jan(a)email.cz CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: ArchLinux Created attachment 61538 --> https://bugs.winehq.org/attachment.cgi?id=61538 Wine staging 3.9 rendering issues in Vietcong Wine-staging 3.9 has an issue with rendering objects in Vietcong - some parts of soldier models are invisible (see attachment). This problem does not exist in Wine-testing and all other Wine-staging versions (so its only Wine-staging 3.9 issue). Reproducible in Vietcong full [1] and demo [2] versions. See notes in AppDB how to run the game. Tested SW Kernel 4.16.11 Mesa 18.0.4 Tested HW Processor: Intel(R) Core(TM) i5-4210M CPU @ 2.60GHz GPU 1: Intel HD Graphics 4600 GPU 2: AMD Radeon R7 M265 PS: Different Vietcong rendering bug occured also in Wine-staging 3.3, but it has been fixed: bug #44712 PPS: Also note that some missions will crash without stagged "wined3d-Indexed_Vertex_Blending" patch, see bug #39057 or #9337 [1] https://appdb.winehq.org/objectManager.php?sClass=version&iId=8864 [2] https://appdb.winehq.org/objectManager.php?sClass=version&iId=35621 -- 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

[Bug 46733] New: IDirect3DTexture9_LockRect failed inside ID3DXFontImpl_DrawTextW with OblivionReloaded
by wine-bugs＠winehq.org 31 Mar '19

31 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=46733 Bug ID: 46733 Summary: IDirect3DTexture9_LockRect failed inside ID3DXFontImpl_DrawTextW with OblivionReloaded Product: Wine-staging Version: 4.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lorenzofer(a)live.it CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 63724 --> https://bugs.winehq.org/attachment.cgi?id=63724 +d3dx,+d3d9,+d3d log Hi, While testing OblivionReloaded (a patcher/extender for TES4:Oblivion), I discovered that in some place where there was supposed to be a rendered text, wasn't. One of these place is the options menu (by default it came up with the key O). Digging inside OR sourcecode, I saw that it use DrawTextA from ID3DXFont. However the functions was silently failing and there wasn't any message from the log. I put some TRACE messages inside the functions and discovered that was failing in IDirect3DTexture9_LockRect. After getting a +d3dx,+d3d9,+d3d log I got: 0046:warn:d3d:wined3d_resource_map Resource does not have MAP_W access. on a Texture created by the DrawTextW function. Now, I don't have aviable other games that use the DrawText functions,and were reported working. But considering where is failing, it's possible that a change (in wine or another staging patch) broke this patch en passant? The attachment uploader is crying when trying to upload the compressed log. Will retry tomorrow. -- 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 39424] New: CodeCharge Studio 5.2 Does Not Load
by wine-bugs＠winehq.org 31 Mar '19

31 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=39424 Bug ID: 39424 Summary: CodeCharge Studio 5.2 Does Not Load Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: api-ms-win-* Assignee: wine-bugs(a)winehq.org Reporter: tmp(a)pc-homepage.com Distribution: --- Created attachment 52538 --> https://bugs.winehq.org/attachment.cgi?id=52538 Error dump file Installation of CodeCharge Studio 5.2 gave errors but it seemed to install. However, it will not run. -- 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 9

[Bug 42844] New: Mouse not captured in fullscreen game ( Resident Evil Revelations)
by wine-bugs＠winehq.org 31 Mar '19

31 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=42844 Bug ID: 42844 Summary: Mouse not captured in fullscreen game (Resident Evil Revelations) Product: Wine Version: 2.4 Hardware: x86-64 OS: FreeBSD Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: adrien_fernandes2(a)hotmail.com I am using FreeBSD 12.0-CURRENT #0 r316750: Thu Apr 13 08:03:28 UTC 2017 amd64 Wine staging 2.4 i386 I set my cleaned prefix with "capture the mouse" checked and "virtual desktop" checked and set to 1920x1080. The problem is that when I'm playing, it's correctly in fullscreen 1920x1080, I don't see the bottom bar with "start" button and Steam icon in the tray BUT I can click it even without to see it. So when playing, it will sometimes happen that your cursor reaches the "Resident Evil Revelations" application in the bar then when you click it, it will simply minimize the game. It shouldn't happen since I checked the "capture mouse" thing in winecfg so I think there's a problem with the capture of the mouse in Resident Evil Revelations. -- 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 1

[Bug 44426] New: EssentialPim Portable 7.6.1 Free - Note editing component broken
by wine-bugs＠winehq.org 31 Mar '19

31 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=44426 Bug ID: 44426 Summary: EssentialPim Portable 7.6.1 Free - Note editing component broken Product: Wine Version: 3.0-rc6 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: rebe(a)gmx.net Distribution: --- In the notes tab. When entering new text in the notes field the text jumps to the end of the editing widget. This happens regularly in wine, esp. after several enter strokes. Example: you add 12345 to the top. three times "enter" and then type "333". As a result you see the 333 text together with the existing text at the bottom of the window and a large space betweeb 12345 and 333 when scrolling. When you type a backspace everything is at the right place again. The jumping occurs regularly when typing. Apparently a font for the white spaces between the two text elements gets assigned a giant font size, as between the upper text and the bottom text seems to be just a single char which you can show it as a line cursor. -- 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 4

[Bug 41643] New: Star Wars: The Old Republic' s Integrated Screenshot Tool Makes Blank Images
by wine-bugs＠winehq.org 31 Mar '19

31 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=41643 Bug ID: 41643 Summary: Star Wars: The Old Republic's Integrated Screenshot Tool Makes Blank Images Product: Wine Version: 1.9.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: visserthree(a)gmail.com Distribution: --- The game has a built-in screenshot tool, bound by default to printscreen. Under Wine, this produces screenshots with no data in them. OS: Debian 8 Video card: GTX 770, driver 367.44 Winetricks: d3dx9 Other: the swtor_fix.exe from the Appdb page Winecfg settings: Windowed desktop Windowmanager-managed windows SWTOR graphics settings: Vsync on or off Fullscreen or Fullscreen Windowed 60 Hz refresh rate (on a 75 Hz monitor) Using an X11 screenshot tool like scrot will produce an image with data in it. -- 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 2

[Bug 40616] New: Program Error "caused by a problem, or deficiency in Wine"
by wine-bugs＠winehq.org 30 Mar '19

30 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=40616 Bug ID: 40616 Summary: Program Error "caused by a problem, or deficiency in Wine" Product: Wine Version: 1.6.1 Hardware: Other OS: Mac OS X Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: colemangriffin7(a)gmail.com Created attachment 54475 --> https://bugs.winehq.org/attachment.cgi?id=54475 Plain Text Document, 4,922 bytes(8 KB on disk), open with TextEdit(default) Fore you to get the whole picture, let me first describe the computer I'm using. -Macbook (13-inch, Mid 2010) -Processor 2.4 GHz Intel Core 2 Duo -Memory 2GB 1067 MHz DDR3 using OS X El Capitan version 10.11.4 Because I'm using a mac, and I wanted to play windows games, and found out to use wine. The game i wanted to play is called "Dawn of Discovery Gold". Its platform is Windows Vista / XP, and file size is 4.49 GB. This was a download bought through Amazon. When using wine, everything went well setting up, the problem occurred when attempting to play the game. A small window would popup titled "Program Error" and the following text reads, "The program Dawn_of_Discovery_Gold_Downloader_2.exe has encountered a serious problem and needs to close. We are sorry for the inconvenience." And below another line of text reads, "This can be caused by a problem in the program or a deficiency in Wine..." Then below are two options to click, "Show Details" and "Close" In the "Show Details", a window opens titled as "Program Error Details" and is filled with codes. On the bottom is a line of text that reads, "If this problem is not present under Windows and has not been reported yet, you can save the detailed information to a file using "Save As" button, then file a bug report and attach that file to the report." The attachment is details of the program error. Thank you for your time looking through this report, if you've found a solution or have suggestions, please email me at colemangriffin7(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.

1 3