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

[Bug 25325] New: Titan quest: missing models on with fglrx >= 10.10 (mobility radeon hd 5730)
by wine-bugs＠winehq.org Nov. 27, 2016

Nov. 27, 2016

http://bugs.winehq.org/show_bug.cgi?id=25325 Summary: Titan quest: missing models on with fglrx >= 10.10 (mobility radeon hd 5730) Product: Wine Version: 1.3.8 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3dx9 AssignedTo: wine-bugs(a)winehq.org ReportedBy: rechapita(a)hotmail.com CC: wine-bugs(a)winehq.org some models are missing from the screen, particulary character models, while using wine versions 1.2 to 1.3.8 and fglrx >= 10.10 (screenshot:http://img574.imageshack.us/img574/7813/tquest.jpg) reverting to fglrx 10.9 solves this problem don't know if its a wine or fglrx issue -- 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 36

[Bug 38768] New: Stronghold 2 hangs when started.
by wine-bugs＠winehq.org Nov. 25, 2016

Nov. 25, 2016

https://bugs.winehq.org/show_bug.cgi?id=38768 Bug ID: 38768 Summary: Stronghold 2 hangs when started. Product: Wine Version: 1.7.44 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: Robert.Zenz(a)bonsaimind.org Distribution: --- Created attachment 51702 --> https://bugs.winehq.org/attachment.cgi?id=51702 warn+all log When trying to start Stronghold 2, it simply hangs: 1. Start Stronghold 2 2. The configuration window opens, press Play 3. The configuration window closes, nothing happens 4. The process sits there consuming ~3-10% CPU, but no window appears ever I tested the Steam version and the one contained within the Stronghold Collection, both show the same behavior, as does Stronghold Legends. Stronghold 1 and Crusader work flawlessly. This was tested in a clean prefix (SH1 and SHC was tested in the same prefix afterwards). Attached is the output of warn+all, if you need any more logs drop me a note. The application was terminated with Ctrl+C after it hang. According to the log SH2 fails to create the configuration fail, however the permissions of the directory are okay. Also I tried to create the configuration file by hand (by simply using touch), Stronghold 2 would then fail with an error dialog that the application stopped working correctly. I guess that this is expected behavior as it most likely tries to load the (empty) configuration file and fails miserably to do so. Though, I can't say if it hangs because it can't create the configuration file or if it is something different. -- 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 36115] New: cabinet/fdi tests show some valgrind warnings
by wine-bugs＠winehq.org Nov. 25, 2016

Nov. 25, 2016

https://bugs.winehq.org/show_bug.cgi?id=36115 Bug ID: 36115 Summary: cabinet/fdi tests show some valgrind warnings Product: Wine Version: 1.7.17 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Depends on: 36114 ==19974== Conditional jump or move depends on uninitialised value(s) ==19974== at 0x7BC907C4: __divdi3 (libgcc2.c:1234) ==19974== by 0x7BC882F3: RtlTimeToSecondsSince1970 (time.c:359) ==19974== by 0x7B8724E9: FileTimeToDosDateTime (time.c:1062) ==19974== by 0x4D69317: get_open_info (fdi.c:552) ==19974== by 0x4EB9739: FCIAddFile (fci.c:362) ==19974== by 0x4D699F7: add_file (fdi.c:572) ==19974== by 0x4D69AF1: create_cab_file (fdi.c:609) ==19974== by 0x4D6AC61: func_fdi (fdi.c:631) ==19974== by 0x4D64F87: main (test.h:584) ==19974== Uninitialised value was created by a stack allocation ==19974== at 0x4D6926C: get_open_info (fdi.c:536) ==19974== ==19974== Conditional jump or move depends on uninitialised value(s) ==19974== at 0x7BC907F4: __divdi3 (libgcc2.c:1028) ==19974== by 0x7BC882F3: RtlTimeToSecondsSince1970 (time.c:359) ==19974== by 0x7B8724E9: FileTimeToDosDateTime (time.c:1062) ==19974== by 0x4D69317: get_open_info (fdi.c:552) ==19974== by 0x4EB9739: FCIAddFile (fci.c:362) ==19974== by 0x4D699F7: add_file (fdi.c:572) ==19974== by 0x4D69AF1: create_cab_file (fdi.c:609) ==19974== by 0x4D6AC61: func_fdi (fdi.c:631) ==19974== by 0x4D64F87: main (test.h:584) ==19974== Uninitialised value was created by a stack allocation ==19974== at 0x4D6926C: get_open_info (fdi.c:536) ==19974== ==19974== Conditional jump or move depends on uninitialised value(s) ==19974== at 0x7BC88304: RtlTimeToSecondsSince1970 (time.c:360) ==19974== by 0x7B8724E9: FileTimeToDosDateTime (time.c:1062) ==19974== by 0x4D69317: get_open_info (fdi.c:552) ==19974== by 0x4EB9739: FCIAddFile (fci.c:362) ==19974== by 0x4D699F7: add_file (fdi.c:572) ==19974== by 0x4D69AF1: create_cab_file (fdi.c:609) ==19974== by 0x4D6AC61: func_fdi (fdi.c:631) ==19974== by 0x4D64F87: main (test.h:584) ==19974== Uninitialised value was created by a stack allocation ==19974== at 0x4D6926C: get_open_info (fdi.c:536) ==19974== fdi.c:555: Test failed: Failed to GetFileAttributes ==19974== Conditional jump or move depends on uninitialised value(s) ==19974== at 0x4EB9BFD: FCIAddFile (fci.c:201) ==19974== by 0x4D699F7: add_file (fdi.c:572) ==19974== by 0x4D69AF1: create_cab_file (fdi.c:609) ==19974== by 0x4D6AC61: func_fdi (fdi.c:631) ==19974== by 0x4D64F87: main (test.h:584) ==19974== Uninitialised value was created by a stack allocation ==19974== at 0x4EB94CC: FCIAddFile (fci.c:1423) ==19974== fdi.c:574: Test failed: Expected FCIAddFile to succeed fdi.c:546: Test failed: Failed to CreateFile Z:\home\austin\wine-git\dlls\cabinet\tests\testdir\c.txt fdi.c:549: Test failed: Expected GetFileInformationByHandle to succeed fdi.c:555: Test failed: Failed to GetFileAttributes ==19974== Conditional jump or move depends on uninitialised value(s) ==19974== at 0x4EB9BFD: FCIAddFile (fci.c:201) ==19974== by 0x4D699F7: add_file (fdi.c:572) ==19974== by 0x4D69AFE: create_cab_file (fdi.c:610) ==19974== by 0x4D6AC61: func_fdi (fdi.c:631) ==19974== by 0x4D64F87: main (test.h:584) ==19974== Uninitialised value was created by a stack allocation ==19974== at 0x4EB94CC: FCIAddFile (fci.c:1423) ==19974== fdi.c:574: Test failed: Expected FCIAddFile to succeed fdi.c:546: Test failed: Failed to CreateFile Z:\home\austin\wine-git\dlls\cabinet\tests\testdir\d.txt fdi.c:549: Test failed: Expected GetFileInformationByHandle to succeed fdi.c:555: Test failed: Failed to GetFileAttributes ==19974== Conditional jump or move depends on uninitialised value(s) ==19974== at 0x4EB9BFD: FCIAddFile (fci.c:201) ==19974== by 0x4D699F7: add_file (fdi.c:572) ==19974== by 0x4D69B0B: create_cab_file (fdi.c:611) ==19974== by 0x4D6AC61: func_fdi (fdi.c:631) ==19974== by 0x4D64F87: main (test.h:584) ==19974== Uninitialised value was created by a stack allocation ==19974== at 0x4EB94CC: FCIAddFile (fci.c:1423) ==19974== fdi.c:574: Test failed: Expected FCIAddFile to succeed fdi.c:614: Test failed: Failed to flush the cabinet fdi.c:678: Test failed: Expected 4, got 1 fdi.c:681: Test failed: Expected 182, got 84 make: *** [fdi.ok] Error 15 -- 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 35343] New: dialog windows are too large
by wine-bugs＠winehq.org Nov. 25, 2016

Nov. 25, 2016

http://bugs.winehq.org/show_bug.cgi?id=35343 Bug ID: 35343 Summary: dialog windows are too large Product: Wine Version: 1.7.10 Hardware: x86 OS: Linux Status: NEW Keywords: download, regression, source Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: madewokherd(a)gmail.com Classification: Unclassified Sometimes windows are created much larger than they should be. I've noticed this in an installer and also in wordpad's "exit without saving" confirmation dialog. Easiest way to reproduce: 1. Open wordpad. 2. Type some things. 3. Click the "x" button to close wordpad. 4. Click "Cancel" on the dialog. 5. Repeat steps 3 and 4 until the dialog appears larger than normal. I think this was not the case in 1.7.10 (will retest) and only really appeared in git today or yesterday. I will try to do a bisect. -- 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 30735] New: MS Office 2000 SR1 installs unusable
by wine-bugs＠winehq.org Nov. 23, 2016

Nov. 23, 2016

http://bugs.winehq.org/show_bug.cgi?id=30735 Bug #: 30735 Summary: MS Office 2000 SR1 installs unusable Product: Wine Version: 1.5.4 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msi AssignedTo: wine-bugs(a)winehq.org ReportedBy: ubrammer(a)t-online.de Classification: Unclassified Installation of Office 2000 SR1 at wine 1.5.4 works with a success message. But the programs excel and word die silently latest after the first mousemovement. Further digging in reveals: Installing MS office 2000 SR1 does not install due to bug http://bugs.winehq.org/show_bug.cgi?id=29335 . This bug can be avoided bei copying the contents of the system-folder into windows/system32 and also installing mfc42 with winetricks. Using the above workaround gave the following: The installer crashes from wine-1.3.7 up to 1.5.3 with another bug. The crash was fixed in wine 1.5.4 by http://bugs.winehq.org/show_bug.cgi?id=30571 but the fix did not solve the unusable installation of office 2000. The first bad commit regarding bug 30571 is commit 19a2d144b563f23dacfb127b94948b0f0f89b003 Author: Hans Leidekker <hans(a)codeweavers.com> Date: Fri Nov 12 15:05:55 2010 +0100 msi: Don't rebuild the target path for files from global assembly components. Reverting this commit results in a good install until commit:2a59f016dbe716aaefec9ab94d47d7b8172d0b5b Author: Alexandre Julliard <julliard(a)winehq.org> Date: Tue Dec 20 11:42:45 2011 +0100 mountmgr: Add dynamic devices support using UDisks. Wine with this commit compiled in, give an unusable office 2000 installation. A Wine version before this commit give a good office 2000 installation. A wineprefix with a good installation is usable in later versions of wine, which will not give a good installation. I could not revert commit 2a59f016dbe716aaefec9ab94d47d7b8172d0b5b on top of wine 1.5.4. So I made logs of the install with the bisected version. -- 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 25

[Bug 37021] New: Wine anti-aliasing not working
by wine-bugs＠winehq.org Nov. 22, 2016

Nov. 22, 2016

http://bugs.winehq.org/show_bug.cgi?id=37021 Bug ID: 37021 Summary: Wine anti-aliasing not working Product: Wine Version: 1.7.22 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: fonts Assignee: wine-bugs(a)winehq.org Reporter: theauro(a)gmail.com Anti-aliasing stopped working in wine. I followed the registry fix in the following link: http://bugs.winehq.org/attachment.cgi?id=18411 Also tried to enable it in winetricks without any luck. I am using Lubuntu 14.04 (which I converted from Ubuntu 14.04) -- 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 37117] New: PVS-Studio Error: Shifting a negative number
by wine-bugs＠winehq.org Nov. 22, 2016

Nov. 22, 2016

https://bugs.winehq.org/show_bug.cgi?id=37117 Bug ID: 37117 Summary: PVS-Studio Error: Shifting a negative number Product: Wine Version: 1.7.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lukebenes(a)hotmail.com PVS-Studio Error: V610 Undefined behavior. Check the shift operator '<<. The left operand '(LONGLONG) - 1' is negative. propvar.c 127 ... if (*res >= ((LONGLONG)1 << (dest_bits-1)) || *res < ((LONGLONG)-1 << (dest_bits-1))) return HRESULT_FROM_WIN32(ERROR_ARITHMETIC_OVERFLOW); ... The LONGLONG type is declared as 'typedef signed __int64 LONGLONG;', i.e. it is a signed type. According to the new standard, shifting negative numbers leads to undefined or unspecified behavior. To find out why such code still may work and how to fix it best, see the article Wade not in unknown waters - part three. details on the V610 error here: http://www.viva64.com/en/d/0225/ -- 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 36803] New: Translate documentation
by wine-bugs＠winehq.org Nov. 20, 2016

Nov. 20, 2016

http://bugs.winehq.org/show_bug.cgi?id=36803 Bug ID: 36803 Summary: Translate documentation Product: WineHQ.org Version: unspecified Hardware: Other OS: other Status: UNCONFIRMED Severity: normal Priority: P2 Component: www-unknown Assignee: wine-bugs(a)winehq.org Reporter: patsev.anton(a)gmail.com Dear developers. Did you do an opportunity of translation of documentation? For example, as is done in https://translations.launchpad.net/ -- 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 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. 14, 2016

Nov. 14, 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