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

[Bug 15556] New: Adobe Illustrator CS installer looks for Color directory in wrong place?
by wine-bugs＠winehq.org 29 Sep '15

29 Sep '15

http://bugs.winehq.org/show_bug.cgi?id=15556 Summary: Adobe Illustrator CS installer looks for Color directory in wrong place? Product: Wine Version: CVS/GIT Platform: Other OS/Version: other Status: NEW Keywords: download Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com http://bugs.winehq.org/show_bug.cgi?id=10002#c8 is a report from Anastasius about Illustrator CS's installer getting confused about where the Color directory lives. Here's what he said, with long traces removed: --- snip --- installer and the app/support tools don't get well with color profiles in mscms storage (the 'private' locations will work). With the current implementation of mscms api, the profiles are stored in "windows/system32/spool/drivers/color". This works as long as the mscms API is used to retrieve the directory where the profiles are stored. Unfortunately the CS installer stores the profiles *NOT* in "windows/system32/spool/drivers/color" but in the old 9X "windows/system32/Color/" location (creates the "Color" directory if not present). ... Illustrator and other support tools later retrieve the profiles location by using GetColorDirectoryA(). ... Nothing is found due to installer putting them in "old" directory and C++ exception is thrown. Not catastrophic for Illustrator because it searches additional 'private' profile locations but it adds additional noise. Other tools like the adobe gamma loader (from "C:\Program Files\Common Files\Adobe\Calibration\Adobe Gamma Loader.exe") won't even work due to that problem. To solve the profiles problem - supporting the "old" and "new" profile storage I suggest to use a symbolic link. E.g. wine should create a "windows/system32/Color/" symlink to "windows/system32/spool/drivers/color". That way older and new apps can access the profiles. With fresh ~./wine, precreation of "color" profile directory symlink and installation, the app and tools find the profiles: --- snip --- So, why is the installer doing this? Should we work around it with the symlink suggested by Anastasius? -- 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 6

[Bug 15332] New: Compiling on PC-BSD with -Werror fails in dlls/mscms/handle.c
by wine-bugs＠winehq.org 29 Sep '15

29 Sep '15

http://bugs.winehq.org/show_bug.cgi?id=15332 Summary: Compiling on PC-BSD with -Werror fails in dlls/mscms/handle.c Product: Wine Version: 1.1.4 Platform: PC OS/Version: FreeBSD Status: UNCONFIRMED Keywords: source Severity: enhancement Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com In today's installment of finding obscure bugs on weird setups, tried compiling on PC-BSD with: CFLAGS="-Werror" ./configure && make clean && make depend && make which works, all the way up to: gcc -c -I. -I. -I../../include -I../../include -D__WINESRC__ -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing -Wdeclaration-after-statement -Wwrite-strings -Wpointer-arith -I/usr/local/include -Werror -o handle.o handle.c In file included from mscms_priv.h:52, from handle.c:32: /usr/local/include/lcms.h:213:1: "HIWORD" redefined In file included from ../../include/wine/debug.h:25, from handle.c:22: ../../include/windef.h:301:1: this is the location of the previous definition *** Error code 1 Stop in /usr/home/pcbsd/wine-git/dlls/mscms. *** Error code 1 Stop in /usr/home/pcbsd/wine-git/dlls. *** Error code 1 Stop in /usr/home/pcbsd/wine-git. Marking as unconfirmed, since I'm not sure if Wine can work around this or not... -- 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 6

[Bug 6359] mscms compile error
by wine-bugs＠winehq.org 29 Sep '15

29 Sep '15

1 0

[Bug 7605] mscms compile error(in wine-git-2007-3-3 & lcms-2007-3-3)
by wine-bugs＠winehq.org 29 Sep '15

29 Sep '15

1 0

[Bug 17452] New: Lcms error crashes PowerPoint 2003
by wine-bugs＠winehq.org 29 Sep '15

29 Sep '15

http://bugs.winehq.org/show_bug.cgi?id=17452 Summary: Lcms error crashes PowerPoint 2003 Product: Wine Version: unspecified Platform: PC URL: http://download.microsoft.com/download/a/1/a/a1adc39b- 9827-4c7a-890b-91396aed2b86/ppviewer.exe OS/Version: Linux Status: NEW Keywords: download Severity: enhancement Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: fgouget(a)codeweavers.com The attached presentation causes PowerPoint 2003 to exit abruptly when you open it (or on startup if you put it on the command line). There's no bracktrace but there is this error message: lcms: Error #12288; Pointer error; probably corrupted file The same issue happen with PowerPoint Viewer 2003 too (if you can get it to install with Wine) so I'm adding the download keyword. -- 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 6

[Bug 19647] New: mscms: GetStandardColorSpaceProfileW() profile id handling incorrect (LCS_sRGB and LCS_WINDOWS_COLOR_SPACE)
by wine-bugs＠winehq.org 29 Sep '15

29 Sep '15

http://bugs.winehq.org/show_bug.cgi?id=19647 Summary: mscms: GetStandardColorSpaceProfileW() profile id handling incorrect (LCS_sRGB and LCS_WINDOWS_COLOR_SPACE) Product: Wine Version: 1.1.27 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: focht(a)gmx.net Hello, various .NET 3.x apps fail to init because GetStandardColorSpaceProfileW() doesn't work as expected. --- snip --- ... 0029:Call mscms.GetStandardColorSpaceProfileW(00000000,73524742,00185110,00184f08) ret=0036bf3f 0029:trace:mscms:GetStandardColorSpaceProfileW ( 0x73524742, 0x185110, 0x184f08 ) 0029:trace:mscms:GetColorDirectoryW ( 0x32d9c8, 0x32d9c4 ) 0029:Call KERNEL32.GetSystemDirectoryW(0032d784,00000100) ret=4340b8ff 0029:Ret KERNEL32.GetSystemDirectoryW() retval=00000013 ret=4340b8ff 0029:Call KERNEL32.lstrcatW(0032d784 L"C:\\windows\\system32",43411b40 L"\\spool\\drivers\\color") ret=4340b91a 0029:Ret KERNEL32.lstrcatW() retval=0032d784 ret=4340b91a 0029:Call KERNEL32.lstrlenW(0032d784 L"C:\\windows\\system32\\spool\\drivers\\color") ret=4340b92b 0029:Ret KERNEL32.lstrlenW() retval=00000027 ret=4340b92b 0029:Call KERNEL32.lstrcpyW(0032d9c8,0032d784 L"C:\\windows\\system32\\spool\\drivers\\color") ret=4340b958 0029:Ret KERNEL32.lstrcpyW() retval=0032d9c8 ret=4340b958 0029:Call KERNEL32.SetLastError(00000002) ret=4340c31a 0029:Ret KERNEL32.SetLastError() retval=00000002 ret=4340c31a 0029:Ret mscms.GetStandardColorSpaceProfileW() retval=00000000 ret=0036bf3f ... --- snip --- --- snip dlls/mscms/profile.c --- BOOL WINAPI GetStandardColorSpaceProfileW( PCWSTR machine, DWORD id, PWSTR profile, PDWORD size ) { static const WCHAR rgbprofilefile[] = { '\\','s','r','g','b',' ','c','o','l','o','r',' ', 's','p','a','c','e',' ','p','r','o','f','i','l','e','.','i','c','m',0 }; ... GetColorDirectoryW( machine, rgbprofile, &len ); switch (id) { case SPACE_RGB: /* 'RGB ' */ lstrcatW( rgbprofile, rgbprofilefile ); len = lstrlenW( rgbprofile ) * sizeof(WCHAR); if (*size < len || !profile) { *size = len; SetLastError( ERROR_MORE_DATA ); return FALSE; } lstrcpyW( profile, rgbprofile ); break; default: SetLastError( ERROR_FILE_NOT_FOUND ); return FALSE; } ... --- snip dlls/mscms/profile.c --- This doesn't look right. MSDN info: http://msdn.microsoft.com/en-us/library/dd372087.aspx --- quote --- dwProfileID Specifies the ID value of the standard color space for which to retrieve the profile. The only valid values for this parameter are LCS_sRGB and LCS_WINDOWS_COLOR_SPACE. --- quote --- You might also want to have a look at "Windows Metafile Format Specification": [MS-WMF] — v20090630 (afaik latest one): http://download.microsoft.com/download/9/5/E/95EF66AF-9026-4BB0-A41D-A4F818… --- quote --- 2.1.1.14 LogicalColorSpace Enumeration The LogicalColorSpace Enumeration specifies the type of color space. <14> typedef enum { LCS_CALIBRATED_RGB = 0x00000000, LCS_sRGB = 0x73524742, LCS_WINDOWS_COLOR_SPACE = 0x57696E20 } LogicalColorSpace; LCS_CALIBRATED_RGB: Color values are calibrated red green blue (RGB) values. LCS_sRGB: The value is an encoding of the ASCII characters "sRGB", and it indicates that the color values are sRGB values. LCS_WINDOWS_COLOR_SPACE: The value is an encoding of the ASCII characters "Win ", including the trailing space, and it indicates that the color values are Windows default color space values. --- quote --- Regards -- 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 6

[Bug 11532] New: Photoshop doesn't support custom monitor profiles
by wine-bugs＠winehq.org 29 Sep '15

29 Sep '15

http://bugs.winehq.org/show_bug.cgi?id=11532 Summary: Photoshop doesn't support custom monitor profiles Product: Wine Version: CVS/GIT Platform: Other OS/Version: other Status: NEW Severity: normal Priority: P2 Component: gdi32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com Roland Geflitter wrote on wine-users: "I'm running a test with Wine 0.9.51 on SuSe 9.1 and Photoshop CS (1) and everything works perfectly (even working with big files of 1 GB and launching Image Ready) BUT: How do I use a CUSTOM Monitor Profile with Photoshop and Wine ? There seems to be no way to assign a monitor profile to the Wine system (as in Windows "control panel"), Photoshop just uses "sRGB ... 2.1" (a substitute for the missing monitor profile of the OS, Wine). I tried to look for a trick to assign another monitor profile to Photoshop, but Photoshop will only take a profile of the OS. That's a pity, because generating an accurate monitor profile under Linux (with an Eye-One spectrometer and Argyllcms) would be possible. Am I wrong - is there a workaround for assigning the monitor profile to Photoshop?" http://msdn2.microsoft.com/en-us/library/ms797852.aspx describes monitor profiles, and says they're enabled by calling a gdi32 function like SetICMMode(). Wine's implementation of that function is currently a no-op. Also, it looks like Photoshop installs a control panel, Adobe Gamma.cpl, see http://www.adobe.com/cfusion/knowledgebase/index.cfm?id=321608 It's possible he's looking for that, and not finding it because we don't have any sort of a GUI to locate control panel applets yet. -- 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 32

[Bug 35289] New: Star Wars - The Force Unleashed: launcher crash at start
by wine-bugs＠winehq.org 29 Sep '15

29 Sep '15

http://bugs.winehq.org/show_bug.cgi?id=35289 Bug ID: 35289 Summary: Star Wars - The Force Unleashed: launcher crash at start Product: Wine Version: 1.7.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: legluondunet(a)free.fr Classification: Unclassified Created attachment 47066 --> http://bugs.winehq.org/attachment.cgi?id=47066 Star Wars The Force Unleashed launcher crash log Hello, Star Wars - The Force Unleashed: launcher crashes at start. If I'm right, it is a .net launcher; so I installed dotnet 2 and 3,5 with winetricks but without success, the launcher still crash. Even If I could start the game without launcher, only the launcher could permit you to configure graphics, keyboard and gamepad options. There is no option menu in the game. I joined you the crash log. -- 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 35818] New: mscms/profile tests fail on Fedora
by wine-bugs＠winehq.org 29 Sep '15

29 Sep '15

https://bugs.winehq.org/show_bug.cgi?id=35818 Bug ID: 35818 Summary: mscms/profile tests fail on Fedora Product: Wine Version: 1.7.14 Hardware: x86 URL: https://test.winehq.org/data/77bd74fa2515e8babb6cda265 3a12adad65191dc/linux_ae-fedora64/mscms:profile.html 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 I've noticed that mscms/profile fails consistently on my machine: profile.c:675: Test succeeded inside todo block: EnumColorProfilesA() failed (18) profile.c:689: Test succeeded inside todo block: EnumColorProfilesA() failed (18) profile.c:729: Test succeeded inside todo block: EnumColorProfilesW() failed (18) profile.c:742: Test succeeded inside todo block: EnumColorProfilesW() failed (18) and looking at test.winehq.org, it also fails on Alasdair Sinclair's fedora machine. -- 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 32671] New: wine: Unhandeled stack overflow by PhotoLine32
by wine-bugs＠winehq.org 29 Sep '15

29 Sep '15

http://bugs.winehq.org/show_bug.cgi?id=32671 Bug #: 32671 Summary: wine: Unhandeled stack overflow by PhotoLine32 Product: Wine Version: 1.4.1 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: mroek(a)yahoo.com Classification: Unclassified Lenovo all-in-One B320 Ubuntu 12.04 WINE 1.4.1 Photoline32 gebnerate the following error (alll available PhotoLine32 Versions): wine: Unhandled stack overflow at address 0x6d7478 (thread 0009), starting debugger... err:seh:setup_exception_record stack overflow 1056 bytes in thread 0009 eip 7bc5c244 esp 00230f10 stack 0x230000-0x231000-0x330000 After trying to start Photoline, I can observe in the process list: winedevice.exe, wineserver and PhotoLine.exe appear shortly in the listing of running processes but then disdappear again. Other WIN programs (e.g. LTSpice) are running smoothly under WINE! During installation of PhotoLine32 there is no error shown. I reinstalled WINE 1.4.1, I installed the latest 1.5 version -> same effect. I reinstalled Photoline32, -> same effect I had the same PhotoLine32 under WINE 1.4.1. and same Ubuntu running smoothly on another PC. Regards Michael -- 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