December 2017 - Wine-bugs - list.winehq.org

[Bug 42364] New: Very low texture resolution in Trackmania Nations Forever / United ( Regression)
by wine-bugs＠winehq.org 12 Feb '18

12 Feb '18

https://bugs.winehq.org/show_bug.cgi?id=42364 Bug ID: 42364 Summary: Very low texture resolution in Trackmania Nations Forever / United (Regression) Product: Wine Version: 2.0 Hardware: x86 URL: http://files.trackmaniaforever.com/tmnationsforever_se tup.exe OS: Linux Status: NEW Keywords: download, regression Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: michael(a)fds-team.de CC: joseph.kucia(a)gmail.com Regression SHA1: 90909951154e1d663bebc134263b4025eacbdabd Distribution: Debian Created attachment 57141 --> https://bugs.winehq.org/attachment.cgi?id=57141 ddraw log I tested Trackmania Nations Forever and noticed that many of the textures have a very low resolution. Even the small time display (top bar in main menu / in-game) seems blurred. Since I could not remember having such problems the last time I tested the application, I did a bisect and found the guilty commit: commit 90909951154e1d663bebc134263b4025eacbdabd Author: Józef Kucia <jkucia(a)codeweavers.com> Date: Mon Jan 2 10:44:38 2017 +0100 ddraw: Subtract framebuffer size from reported available video memory. Signed-off-by: Józef Kucia <jkucia(a)codeweavers.com> Signed-off-by: Henri Verbeet <hverbeet(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> The game uses ddraw only to detect the available memory while the actual drawing is done using d3d9. See attachment for a +ddraw log. The test was done on a Geforce GTX 660 with 2GB VRAM and 1280x1024 as desktop resolution. -- 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 6

[Bug 43379] New: valgrind shows an invalid read in dlls/ntdll/tests/file.c
by wine-bugs＠winehq.org 12 Feb '18

12 Feb '18

https://bugs.winehq.org/show_bug.cgi?id=43379 Bug ID: 43379 Summary: valgrind shows an invalid read in dlls/ntdll/tests/file.c Product: Wine Version: 2.12 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase, valgrind Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Distribution: --- ==30466== Invalid read of size 1 ==30466== at 0x7BCAD43B: virtual_check_buffer_for_write (virtual.c:1718) ==30466== by 0x7BC48F48: NtReadFile (file.c:854) ==30466== by 0x4A47FDE: test_read_write (file.c:3504) ==30466== by 0x4A4DEE9: func_file (file.c:4288) ==30466== by 0x4AA25B4: run_test (test.h:603) ==30466== by 0x4AA2A13: main (test.h:687) ==30466== Address 0xdeadbeef is on thread 1's stack ==30466== -- 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 43748] New: Dead or Alive Last Round ntdll crash on Wine newer than 1.8.7 under Linux , but not in OS X
by wine-bugs＠winehq.org 12 Feb '18

12 Feb '18

https://bugs.winehq.org/show_bug.cgi?id=43748 Bug ID: 43748 Summary: Dead or Alive Last Round ntdll crash on Wine newer than 1.8.7 under Linux, but not in OS X Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: tod.jackson(a)gmail.com Distribution: --- Created attachment 59244 --> https://bugs.winehq.org/attachment.cgi?id=59244 staging-2.17 console/debug output I got Dead or Alive Last Round (free on Steam) working without issues under OS X, with multiple Wine versions tested: 2.0.2, 2.13, 2.16-staging. However, under Linux, no version of Wine newer than 1.8.7 even proceeds beyond a brief white window. I attached a log with the default debug settings, please let me know what further to enable as I'm not sure what the issue is. -- 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 21

[Bug 44113] New: World of Tanks(WoT) crashes on AMD GPU the moment entering hangar starting version 0.9.20.1.3 of WoT
by wine-bugs＠winehq.org 12 Feb '18

12 Feb '18

https://bugs.winehq.org/show_bug.cgi?id=44113 Bug ID: 44113 Summary: World of Tanks(WoT) crashes on AMD GPU the moment entering hangar starting version 0.9.20.1.3 of WoT Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: HASH.DuOrden(a)gmail.com Distribution: --- Created attachment 59834 --> https://bugs.winehq.org/attachment.cgi?id=59834 wine ./WorldOfTanks.exe -clientGraphicsAPI d3d9 &>./WorldOfTanks.log Starting with WoT version 0.9.20.1.3 game now crashes right after entering the hangar. It happens only with AMD GPU, I have couple of PC's, one with AMD/ATI Radeon RX 460 and nVidia GeForce GTX 570, it works on nVidia but crashes on AMD/ATI. It happened without Me updating anything so I'm assuming it is something WarGaming changed some thing in the WoT. I am currently on Gentoo profile 13 and wine-staging-2.19, gentoo-sources-4.13.4. I tried with kernel versions gentoo-sources-4.13.4 to gentoo-sources-4.13.10 and wine-staging-2.19 to wine-staging-2.21 without any success, with staging enabled and not, with gcc-5.4.0. I've tried to re-download the game on clean prefix, WinXP and Win7 installing or not d3dx9_36, xact_jun2010, msvcp110/msvcr110, msvcp140/msvcr140, no change. Without sound or not. I am currently rebuilding my system with gcc-6.4.0, gcc version 5.4.0 was not a problem before, but now I simply do not know what to do! P.S.: All this is on RU region. -- 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 43734] New: Identical CUPS printers MUST have different DESCRIPTIONs to be available to wine
by wine-bugs＠winehq.org 11 Feb '18

11 Feb '18

https://bugs.winehq.org/show_bug.cgi?id=43734 Bug ID: 43734 Summary: Identical CUPS printers MUST have different DESCRIPTIONs to be available to wine Product: Wine Version: 2.0.2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: spooler Assignee: wine-bugs(a)winehq.org Reporter: pfortin(a)pfortin.com Distribution: --- New installation of Linux Mageia 6 with wine 2.0.2. I have 2 identical printers -- 1 local and 1 remote. However, with... /etc/printcap: hpoj|HP Officejet Pro 8600:rm=prf.pfortin.com:rp=hpoj: PW|HP Officejet Pro 8600:rm=prf.pfortin.com:rp=PW: only the first printer was available to the applications. Changing the printer DESCRIPTIONs so that they are different: hpoj|HP Officejet Pro 8600 (PF):rm=prf.pfortin.com:rp=hpoj: PW|HP Officejet Pro 8600 (PW):rm=prf.pfortin.com:rp=PW: ^^^^ Applications can now see both printers. -- 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 34836] New: Jagged Alliance 2 1.x orginal cd version crash.
by wine-bugs＠winehq.org 10 Feb '18

10 Feb '18

http://bugs.winehq.org/show_bug.cgi?id=34836 Bug #: 34836 Summary: Jagged Alliance 2 1.x orginal cd version crash. Product: Wine Version: 1.7.5 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: lahtis(a)gmail.com Classification: Unclassified Created attachment 46440 --> http://bugs.winehq.org/attachment.cgi?id=46440 Backtrace wine 1.7.5 versions. Testing Jagged Alliance 2 original cd (2 cd's) 1x version. Game install correctly. But game crash when starting. I’m tested a latest wine 1.7.5 version. Im also tested a many old versions 1.0.1 etc.. And the end result is the same. Im added a latest 1.7.5 wine versions backtrace in attachments. -- 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 20

[Bug 37693] New: No color printing within applications
by wine-bugs＠winehq.org 09 Feb '18

09 Feb '18

https://bugs.winehq.org/show_bug.cgi?id=37693 Bug ID: 37693 Summary: No color printing within applications Product: Wine Version: 1.7.32 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: powersurge69(a)hotmail.com Distribution: --- I recently loaded Linux Mint 17 on my mother's computer and one of the programs that she likes to use is CreataCard 3. I loaded this program on her machine using PlayOnLinux and the latest version of Wine and the program almost runs perfectly. The only issue that it's having is that the cards are printing in grayscale on her color HP PSC1410 printer. The same thing happened when I installed Hallmark Card Studio on her machine. Her printer prints full color images just fine using other Linux programs. I tested it with another printer and got the same result. I even tried testing it with an older version of Linux Mint 13 and it still printed in grayscale so this leads me to believe that it's a Wine issue. I think this is the same issue that was reported in bug# 8428 that was abandoned. -- 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 19

[Bug 43837] New: LINE (Powered by Naver): Window flickers when maximized
by wine-bugs＠winehq.org 08 Feb '18

08 Feb '18

https://bugs.winehq.org/show_bug.cgi?id=43837 Bug ID: 43837 Summary: LINE (Powered by Naver): Window flickers when maximized Product: Wine Version: 2.18 Hardware: x86 URL: https://scdn.line-apps.com/client/win/new/LineInst.exe OS: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: cges30901(a)gmail.com Distribution: --- Created attachment 59388 --> https://bugs.winehq.org/attachment.cgi?id=59388 terminal output If I maximize any window of LINE, the window flickers. Unchecking "Allow the window manager to decorate the windows" in Graphics tab in winecfg is a workaround. -- 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

[Bug 15726] New: incorrect text background on listview in Paf 5.2
by wine-bugs＠winehq.org 08 Feb '18

08 Feb '18

http://bugs.winehq.org/show_bug.cgi?id=15726 Summary: incorrect text background on listview in Paf 5.2 Product: Wine Version: 1.1.6 Platform: PC URL: http://ftp.ldscatalog.com/PAF5AllLangs.exe OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: comctl32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: cjstimpson(a)utwire.net In Paf 5.2 In the dialog from Edit/Add -> Individual, the list view has white instead of transparent backgrounds for the following text on the left side: "PERSONAL:" "EVENTS:" "OTHER:". There's also these partial grey backgrounds that show up on the selected row that aren't supposed to be there. -- 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 12

[Bug 43784] New: Updating a 2.16 prefix to 2.17 causes Wine to hang forever updating the configuration.
by wine-bugs＠winehq.org 07 Feb '18

07 Feb '18

https://bugs.winehq.org/show_bug.cgi?id=43784 Bug ID: 43784 Summary: Updating a 2.16 prefix to 2.17 causes Wine to hang forever updating the configuration. Product: Wine Version: 2.17 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alexchandel(a)gmail.com Running winecfg (with wine 2.17) on a 2.16 prefix causes the "The Wine configuration in X is being updated, please wait..." dialog to appear. However, it never finishes, and the Activity Monitor reveals an unresponsive process using 58% CPU. Eventually, this message is printed: err:process:__wine_kernel_init boot event wait timed out and the winecfg window appears. However, the unresponsive process continues using 58% CPU and never exits, even when winecfg is closed. -- 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