July 2016 - Wine-Bugs - list.winehq.org

[Bug 40012] New: Scrap Mechanic BETA 0.1.11: UI/HUD not visible/active ingame
by wine-bugs＠winehq.org Nov. 18, 2016

Nov. 18, 2016

https://bugs.winehq.org/show_bug.cgi?id=40012 Bug ID: 40012 Summary: Scrap Mechanic BETA 0.1.11: UI/HUD not visible/active ingame Product: Wine Version: 1.9.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: blehdableh(a)gmail.com Distribution: --- Created attachment 53458 --> https://bugs.winehq.org/attachment.cgi?id=53458 terminal output captured by script, includes steam starting up before Scrap Mechanic runs While entering the game world the UI/HUD display correctly for a moment, then disappear/become unresponsive for the rest of the game. Attempting to open the inventory or Esc menu causes nothing to appear, and the game/terminal logs complain that it cannot find the required UI files. -- 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 31028] New: Showing the architecture for needed packages
by wine-bugs＠winehq.org Nov. 17, 2016

Nov. 17, 2016

http://bugs.winehq.org/show_bug.cgi?id=31028 Bug #: 31028 Summary: Showing the architecture for needed packages Product: Wine Version: 1.5.7 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: sworddragon2(a)aol.com Classification: Unclassified As already sayed in bug #31027 Wine could show the architecture for which a package is needed. For example if Wine says that the Gecko package is missing it could show if this message is related to a 32 bit or 64 bit package. This would avoid duplicated messages which are confusing. -- 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 7

[Bug 18741] New: Wine printing output should be in .pdf rather than postscript
by wine-bugs＠winehq.org Nov. 13, 2016

Nov. 13, 2016

http://bugs.winehq.org/show_bug.cgi?id=18741 Summary: Wine printing output should be in .pdf rather than postscript Product: Wine Version: 1.1.22 Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: wineps.drv AssignedTo: wine-bugs(a)winehq.org ReportedBy: scott(a)open-vote.org Blocks: 5551,6416 The new CUPS standards from http://openprinting.org/ say that .pdf is the preferred printing format over postscript: https://lists.linux-foundation.org/pipermail/printing-architecture/2008/001… -- PDF as the Standard Print Job Format ------------------------------------ To improve the reliability of the printing process, especially for complex graphics, high color depths, and for jobs where pages get separated and reordered (2 pages per sheet, booklets, selected pages, ...) we are switching from PostScript to PDF as standard print job format. The server (printing system) side is nearly completely implemented in the form of new CUPS filters and file conversion rules. On the client (application) side it is needed that the applications generate the print jobs in PDF and not in Postscript. This would mean a change of the print job generation part of OpenOffice.org. As OpenOffice.org has an excellent "Export to PDF" function, there will not be needed much new code. One can use this functionality to generate print jobs, using PDF settings optimized for printing. This is not absolutely urgent, as CUPS can convert PostScript to PDF with a pstopdf filter, but applications which directly produce PDF have a better control over the graphical quality of the print job, and they even solve page management (2 on a sheet, booklets, selected pages, ...) problems on old PostScript-based servers, as a CUPS filter will generate PostScript from the incoming PDF then (pdftops) and this PostScript is much cleaner as the one coming from most applications. So I am asking you whether you can change OpenOffice.org to make the "Print" command emitting PDF instead of PostScript. To not break lagacy, non-PDF-capable environments, make this a configurable option. I am very grateful for any support from the OpenOffice.org side in terms of these OpenPrinting projects. They will improve the printing workflow a lot and will make many bugs and user complaints go away. -- We should do a similar thing in Wine -- 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 9

[Bug 30740] New: winedump should extend ordinal imports/exports with known names from our spec files
by wine-bugs＠winehq.org Nov. 13, 2016

Nov. 13, 2016

http://bugs.winehq.org/show_bug.cgi?id=30740 Bug #: 30740 Summary: winedump should extend ordinal imports/exports with known names from our spec files Product: Wine Version: 1.5.4 Platform: x86-64 OS/Version: Linux Status: NEW Severity: enhancement Priority: P2 Component: tools AssignedTo: wine-bugs(a)winehq.org ReportedBy: wine.dev(a)web.de Classification: Unclassified winedump in dump mode show ordinal imports/exports only as numbers, but we have names for many of them in our spec files. In addition to create *def files for all exports from spec files, we should create a database (set of c or h files) for all numbered export for every dll in Wine and add them to winedump. No idea, if this database is an improvement for other tools or dlls. (winedbg, dbghelp.dll as examples) -- By by ... Detlef -- 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 3

[Bug 37044] New: Freedom Fighters game has slow performance
by wine-bugs＠winehq.org Nov. 13, 2016

Nov. 13, 2016

http://bugs.winehq.org/show_bug.cgi?id=37044 Bug ID: 37044 Summary: Freedom Fighters game has slow performance Product: Wine Version: 1.7.22 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: subins2000(a)gmail.com The game starts and works, but the gameplay is slow. The intro, menu and gameplay is slow. -- 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 17329] New: Wine needs more userfriendly message when certain dlls are not registered/missing
by wine-bugs＠winehq.org Nov. 11, 2016

Nov. 11, 2016

http://bugs.winehq.org/show_bug.cgi?id=17329 Summary: Wine needs more userfriendly message when certain dlls are not registered/missing Product: Wine Version: 1.1.12 Platform: PC URL: http://www.whizlabs.com/download.php?prod=SCJP6.0.exe OS/Version: Linux Status: NEW Keywords: download Severity: enhancement Priority: P2 Component: ole32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: xerox_xerox2000(a)yahoo.co.uk Created an attachment (id=19352) --> (http://bugs.winehq.org/attachment.cgi?id=19352) an idea of how to generate more userfriendly message This bug's intention is to enhance user friendlyness, and hopefully less invalid bug reports, and more first time success experience for users. Take for example app from http://www.whizlabs.com/download.php?prod=SCJP6.0.exe (from some bug in bugzilla). The application fails with a run-time error, and some , for newbies, cryptic ole errors. I think it would enhance wine's userfriendlyness a big deal, if we would just put up a nice messagebox, with a message what the error means, and what should be done. I'll attach a (crappy) patch , just to give an idea how easy it would be to give users more clues how to get around the "bug". Just apply patch , and run the app above, and user will know he has to install wsh56. -- 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 40925] New: Flame in the Flood crashes with a Fatal error
by wine-bugs＠winehq.org Nov. 11, 2016

Nov. 11, 2016

https://bugs.winehq.org/show_bug.cgi?id=40925 Bug ID: 40925 Summary: Flame in the Flood crashes with a Fatal error Product: Wine Version: 1.9.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: blue-t(a)web.de Distribution: --- Created attachment 55034 --> https://bugs.winehq.org/attachment.cgi?id=55034 Log output Now that R16-Typeless is supported as of b53b717 the game no longer crashes with a fatal error in CreateTexture2D. The crash window now only talks about Fatal Error without any additional hints. -- 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 32

[Bug 17323] New: Superbase Dialogs are too wide
by wine-bugs＠winehq.org Nov. 11, 2016

Nov. 11, 2016

http://bugs.winehq.org/show_bug.cgi?id=17323 Summary: Superbase Dialogs are too wide Product: Wine Version: 1.1.14 Platform: PC-x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: harv(a)gmx.de Created an attachment (id=19348) --> (http://bugs.winehq.org/attachment.cgi?id=19348) Uppre is how it looks like in XP, lower part is same dialog in wine 1.1.14 Superbase (a Relational database management system) displays its internal dialogs way too wide. They don't even fit on the screen. See attachment. -- 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 34

[Bug 40110] New: d3d10core:device and d3d11:d3d11 regression
by wine-bugs＠winehq.org Nov. 11, 2016

Nov. 11, 2016

https://bugs.winehq.org/show_bug.cgi?id=40110 Bug ID: 40110 Summary: d3d10core:device and d3d11:d3d11 regression Product: Wine Version: 1.9.3 Hardware: x86 OS: Windows Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Since the commits below, my fg-acer64 test machine is getting new failures on Windows 8, in both 32 and 64 bits. fg-acer64 is an Acer laptop with an i5-3317U processor and HD Graphics 4000 integrated graphics. d3d10core:device failures: device.c:4858: Test failed: Got unexpected color 0xff0000ff at (0, 0), expected 0xffffffff. device.c:4858: Test failed: Got unexpected color 0xff00ffff at (1, 0), expected 0xff000000. device.c:4858: Test failed: Got unexpected color 0xff00ff00 at (2, 0), expected 0xff000000. device.c:4858: Test failed: Got unexpected color 0xffffff00 at (3, 0), expected 0xff000000. device.c:4858: Test failed: Got unexpected color 0xffff0000 at (0, 1), expected 0xffffff00. device.c:4858: Test failed: Got unexpected color 0xffff00ff at (1, 1), expected 0xff0000ff. device.c:4858: Test failed: Got unexpected color 0xff000000 at (2, 1), expected 0xff00ffff. device.c:4858: Test failed: Got unexpected color 0xff7f7f7f at (3, 1), expected 0x00000000. device.c:4858: Test failed: Got unexpected color 0xffffffff at (0, 2), expected 0xff7f7f7f. device.c:4858: Test failed: Got unexpected color 0xffffffff at (1, 2), expected 0xffff0000. device.c:4858: Test failed: Got unexpected color 0xffffffff at (2, 2), expected 0xffff00ff. device.c:4858: Test failed: Got unexpected color 0xff000000 at (3, 2), expected 0xff7f7f7f. device.c:4858: Test failed: Got unexpected color 0xff000000 at (1, 3), expected 0xffffffff. device.c:4858: Test failed: Got unexpected color 0xff000000 at (3, 3), expected 0x00000000. d3d11:d3d11 failures: d3d11.c:4508: Test failed: Got unexpected color 0xff0000ff at (0, 0), expected 0xffffffff. d3d11.c:4508: Test failed: Got unexpected color 0xff00ffff at (1, 0), expected 0xff000000. d3d11.c:4508: Test failed: Got unexpected color 0xff00ff00 at (2, 0), expected 0xff000000. d3d11.c:4508: Test failed: Got unexpected color 0xffffff00 at (3, 0), expected 0xff000000. d3d11.c:4508: Test failed: Got unexpected color 0xffff0000 at (0, 1), expected 0xffffff00. d3d11.c:4508: Test failed: Got unexpected color 0xffff00ff at (1, 1), expected 0xff0000ff. d3d11.c:4508: Test failed: Got unexpected color 0xff000000 at (2, 1), expected 0xff00ffff. d3d11.c:4508: Test failed: Got unexpected color 0xff7f7f7f at (3, 1), expected 0x00000000. d3d11.c:4508: Test failed: Got unexpected color 0xffffffff at (0, 2), expected 0xff7f7f7f. d3d11.c:4508: Test failed: Got unexpected color 0xffffffff at (1, 2), expected 0xffff0000. d3d11.c:4508: Test failed: Got unexpected color 0xffffffff at (2, 2), expected 0xffff00ff. d3d11.c:4508: Test failed: Got unexpected color 0xff000000 at (3, 2), expected 0xff7f7f7f. d3d11.c:4508: Test failed: Got unexpected color 0xff000000 at (1, 3), expected 0xffffffff. d3d11.c:4508: Test failed: Got unexpected color 0xff000000 at (3, 3), expected 0x00000000. The results on test.winehq.org: https://test.winehq.org/data/tests/d3d10core:device.html https://test.winehq.org/data/tests/d3d11:d3d11.html commit 50a8d3f6d2c0bce11aefa94a0b7fa53951d0defe Author: Józef Kucia <jkucia(a)codeweavers.com> Date: Tue Jan 19 22:28:12 2016 +0100 d3d10core/tests: Port test_copy_subresource_region() from d3d11. 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> commit c161543c8678125b00972282208035ad710ff648 Author: Józef Kucia <jkucia(a)codeweavers.com> Date: Tue Jan 19 22:28:11 2016 +0100 d3d11/tests: Add test for ID3D11DeviceContext::CopySubresourceRegion(). Based on test_update_subresource(). 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> -- 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 7

[Bug 35397] New: Endless Steam Client Update even after fresh install
by wine-bugs＠winehq.org Nov. 11, 2016

Nov. 11, 2016

http://bugs.winehq.org/show_bug.cgi?id=35397 Bug ID: 35397 Summary: Endless Steam Client Update even after fresh install Product: Wine Version: unspecified Hardware: x86-64 OS: FreeBSD Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lehmannwer(a)gmail.com Classification: Unclassified $ wine --version wine-1.7.10 $ FreeBSD (x64) 9.1 Geforce 8600 GT nvidia-driver-319.32 Even after complete deletion of the Steam folder and a fresh install of the SteamSetup.exe file, when setup seems complete, it downloads about 104 MB of updates and starts an update process which never ends. I thought that this problem had been fixed with version 1.7.8. The Steam client used to work on this machine last year with version 1.4, so it can't be a hardware related problem. -- 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 28