wine-bugs March 2016

wine-bugs@winehq.org

1 participants
7491 discussions

[Bug 3548] .lnk file is created on the desktop together with the program icon...
by wine-bugs＠winehq.org 19 Mar '16

19 Mar '16

https://bugs.winehq.org/show_bug.cgi?id=3548 --- Comment #54 from gat <gatlinsullivan(a)yahoo.com> --- This is _NOT_ still present in Wine 1.9.5 with Fedora 23 using Nightingale 1.12.1 (getnightingale.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 0

[Bug 3548] .lnk file is created on the desktop together with the program icon...
by wine-bugs＠winehq.org 19 Mar '16

19 Mar '16

https://bugs.winehq.org/show_bug.cgi?id=3548 --- Comment #53 from gat <gatlinsullivan(a)yahoo.com> --- This is _NOT_ still present in Wine 1.9.5 with Fedora 23 using Notepad++ 6.9. Will somebody please test this for me? I tried this with a virtual desktop and without a virtual desktop and could not reproduce this again. It could be a change in Notepad++, though. -- 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 0

[Bug 39718] New: d3d9.dll trick for Fallout 3 no longer working in Steam
by wine-bugs＠winehq.org 18 Mar '16

18 Mar '16

https://bugs.winehq.org/show_bug.cgi?id=39718 Bug ID: 39718 Summary: d3d9.dll trick for Fallout 3 no longer working in Steam Product: Wine Version: 1.7.55 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: b.adamski(a)mac.com Created attachment 52967 --> https://bugs.winehq.org/attachment.cgi?id=52967 Crash Log File In order to get Fallout 3 work with Intel graphic boards, a modified d3d9.dll file needs to be installed in the game directory: /Program Files/Bethesda Softworks/Fallout 3/d3d9.dll for the standalone version of Fallout 3. /Program Files/Steam/SteamApps/common/Fallout 3 goty/d3d9.dll or /Program Files/Steam/SteamApps/common/Fallout 3/d3d9.dll for the Steam version of Fallout 3. In addition the modified d3d9.dll file needs to get registered in winecfg. Add "d3d9 (native, builtin)" in the 'Libraries' tab. The trick worked perfectly fine until Steam released an update on August 19th 2015. With the new Steam version the trick does no longer work. Fallout 3 crashes when starting a new game or loading a save game. Please find the crash log attached. This is a different crash then the typical "new game crash" that the d3d9 trick is supposed to solve. There seems no impact from OS X or Wine engine updates. The standalone version of Fallout 3 is not affected, the trick still works absolutely fine here. I did not find any similar reports about Fallout 3 in Steam on Wine under Linux or natively in Steam on Windows. You can download the standalone wrapper version for OS X here: http://portingteam.com/files/file/8182-fallout-3-goty/ You can download the Steam wrapper version for OS X here: http://portingteam.com/files/file/8213-fallout-3-and-fallout-new-vegas-on-s… You find a forum discussion about the problem here: http://portingteam.com/topic/10637-fallout-3-d3d9dll-trick-for-intel-gpus-n… -- 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 41

[Bug 40287] New: When I try to install steam with Wine, it works. Then I try to run steam, and steam just breaks. I can click things on it, but they are just blank buttons.
by wine-bugs＠winehq.org 18 Mar '16

18 Mar '16

https://bugs.winehq.org/show_bug.cgi?id=40287 Bug ID: 40287 Summary: When I try to install steam with Wine, it works. Then I try to run steam, and steam just breaks. I can click things on it, but they are just blank buttons. Product: Wine Version: unspecified Hardware: aarch64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: shadowvortex400(a)gmail.com Distribution: --- Created attachment 53928 --> https://bugs.winehq.org/attachment.cgi?id=53928 Backtrace Read summary -- 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 40253] New: regression: Can't remove fonts: is a directory (--with-wine64, shared wow64)
by wine-bugs＠winehq.org 18 Mar '16

18 Mar '16

https://bugs.winehq.org/show_bug.cgi?id=40253 Bug ID: 40253 Summary: regression: Can't remove fonts: is a directory (--with-wine64, shared wow64) Product: Wine Version: 1.9.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: build-env Assignee: wine-bugs(a)winehq.org Reporter: o.dierick(a)piezo-forte.be Distribution: --- I've updated my git tree with 1.9.5 and now I have this error while compiling 32bit Wine with the --with-wine64 option (in a shared wow64 setup): ---begin make output--- ... rm -f fonts && ln -s ../1.9.5_wow_64/fonts fonts rm: impossible de supprimer « fonts »: est un dossier make: *** [fonts] Erreur 1 ... ---end make output--- It says fonts is a directory and can't be removed. I do out-of-tree builds. The 32bit directory doesn't exists when I run configure. After running configure, the 32bit build tree is there and contains a fonts directory with a single Makefile in it. I had no such error with Wine 1.9.4 and I don't have it when compiling stand-alone 32bit Wine or the 64bit shared wow part. I did a regression test and found this commit to be the culprit: ---begin git bisect output--- dcc16c7cac1cbf93096b072fe2f7b32ad08d1fa5 is the first bad commit commit dcc16c7cac1cbf93096b072fe2f7b32ad08d1fa5 Author: Alexandre Julliard <julliard at winehq.org> Date: Mon Feb 29 15:06:42 2016 +0900 makefiles: Don't generate global rules in disabled directories. Signed-off-by: Alexandre Julliard <julliard at winehq.org> ... ---end git bisect output--- -- 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 37949] New: eLicenser Control Center needs msvcr80.dll.__CxxExceptionFilter
by wine-bugs＠winehq.org 18 Mar '16

18 Mar '16

https://bugs.winehq.org/show_bug.cgi?id=37949 Bug ID: 37949 Summary: eLicenser Control Center needs msvcr80.dll.__CxxExceptionFilter Product: Wine Version: 1.7.34 Hardware: x86 URL: https://web.archive.org/web/20130226012410/http://down load.elicenser.net/downloads/Archive/eLC_6.0.2.7036/eL icenserControlSetup.exe OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: 00cpxxx(a)gmail.com Distribution: --- To reproduce: 1) winetricks -q dotnet20 2) download and install the application 3) run c:/Program Files/Syncrosoft/LCC/eLCC.exe 4) press "Enter Activation Code" 5) hold a keyboard key until after all mask input is completed. wine: Call from 0x7b83b705 to unimplemented function msvcr80.dll.__CxxExceptionFilter, aborting I see bug 34841 for msvcr90 and bug 35657 for msvcr110 so I understand that each dll should have its own bug. If this is not true the bug can be closed as duplicate. -- 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 39239] New: ole32:compobj fails if privileges not high enough
by wine-bugs＠winehq.org 18 Mar '16

18 Mar '16

https://bugs.winehq.org/show_bug.cgi?id=39239 Bug ID: 39239 Summary: ole32:compobj fails if privileges not high enough Product: Wine Version: unspecified Hardware: x86 OS: Windows Status: NEW Severity: normal Priority: P2 Component: ole32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com The following errors systematically happen when running the test without elevated privileges on a Windows 7 box such as the fg-win7u64-1spie9adm and fg-win7u64-1spie9usr WineTest boxes. compobj.c:1269: Test failed: RegCreateKeyEx returned 5 compobj.c:1272: Test failed: RegCreateKeyEx returned 6 compobj.c:1274: Test failed: RegSetValueEx returned 6 compobj.c:1278: Test failed: CoGetPSClsid failed with error 0x80040155 compobj.c:1279: Test failed: got clsid {00000000-0000-0000-0000-000000000000} compobj.c:1282: Test failed: RegDeleteKeyEx returned 6 compobj.c:1285: Test failed: RegDeleteKeyEx returned 2 The error code (ERROR_ACCESS_DENIED) clearly indicates a permissions issue. The tests regression was introduced by the following commit: commit fae8d9db5f3dcbec198d1a4cde6c9cfe8684b5cf Author: Akihiro Sagawa <sagawa.aki(a)gmail.com> Date: Tue Jul 15 19:34:38 2014 +0900 ole32/tests: Add CoGetPSClsid WOW64 registry tests. -- 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 40115] New: ole32:compobj regression (privilege issue)
by wine-bugs＠winehq.org 18 Mar '16

18 Mar '16

https://bugs.winehq.org/show_bug.cgi?id=40115 Bug ID: 40115 Summary: ole32:compobj regression (privilege issue) Product: Wine Version: 1.9.3 Hardware: x86 OS: Windows Status: NEW Severity: normal Priority: P2 Component: ole32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com The commit below introduces 25 new failures when it is run without elevated privileges such as on the fg-win7u64-1spie9adm and fg-win7u64-1spie9usr VMs. New failures: compobj.c:2308: Test failed: failed to create a key 5, error 1008 compobj.c:2311: Test failed: got 6, error 1008 compobj.c:2314: Test failed: got 6, error 1008 compobj.c:2322: Test failed: got 6, error 1008 compobj.c:2325: Test failed: got 6, error 1008 compobj.c:2322: Test failed: got 6, error 1008 compobj.c:2325: Test failed: got 6, error 1008 compobj.c:2322: Test failed: got 6, error 1008 compobj.c:2325: Test failed: got 6, error 1008 compobj.c:2322: Test failed: got 6, error 1008 compobj.c:2325: Test failed: got 6, error 1008 compobj.c:2322: Test failed: got 6, error 1008 compobj.c:2325: Test failed: got 6, error 1008 compobj.c:2331: Test failed: got 0x80040154 compobj.c:2332: Test failed: got (null) compobj.c:2337: Test failed: got 0x80040154 compobj.c:2338: Test failed: got (null) compobj.c:2343: Test failed: got 0x80040154 compobj.c:2344: Test failed: got (null) compobj.c:2349: Test failed: got 0x80040154 compobj.c:2350: Test failed: got (null) compobj.c:2355: Test failed: got 0x80040154 compobj.c:2356: Test failed: got (null) compobj.c:2361: Test failed: got 0x80040154 compobj.c:2362: Test failed: got (null) ole32:compobj results on test.winehq.org: https://test.winehq.org/data/tests/ole32:compobj.html commit 8fe18a16f7f5e0326d2fe6ab32ef2aad947b343d Author: Nikolay Sivov <nsivov(a)codeweavers.com> Date: Wed Dec 30 23:48:38 2015 +0300 ole32: Properly implement OleRegGetUserType(). Signed-off-by: Nikolay Sivov <nsivov(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 22533] New: Half Life: loading screen rendering is wrong
by wine-bugs＠winehq.org 18 Mar '16

18 Mar '16

http://bugs.winehq.org/show_bug.cgi?id=22533 Summary: Half Life: loading screen rendering is wrong Product: Wine Version: 1.1.43 Platform: x86-64 OS/Version: Linux Status: NEW Severity: minor Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com Created an attachment (id=27624) --> (http://bugs.winehq.org/attachment.cgi?id=27624) screenshot See attached screenshot. Terminal output is minimal: fixme:win:EnumDisplayDevicesW ((null),0,0x32e298,0x00000000), stub! fixme:x11drv:X11DRV_desktop_SetCurrentMode Cannot change screen BPP from 32 to 16 fixme:mci:MCI_Break (0102) vkey 001B stub ALSA lib ../../../src/pcm/pcm.c:7234:(snd_pcm_recover) underrun occured fixme:mci:MCI_Break (0102) vkey 001B stub ALSA lib ../../../src/pcm/pcm.c:7234:(snd_pcm_recover) underrun occured fixme:win:LockWindowUpdate (0x30052), partial stub! fixme:win:LockWindowUpdate ((nil)), partial stub! fixme:win:LockWindowUpdate (0x30052), partial stub! fixme:win:LockWindowUpdate ((nil)), partial stub! -- 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 29

[Bug 39674] New: 3Dmark03, 05, 06 not started "Systen Info Error" (double regression)
by wine-bugs＠winehq.org 18 Mar '16

18 Mar '16

https://bugs.winehq.org/show_bug.cgi?id=39674 Bug ID: 39674 Summary: 3Dmark03, 05, 06 not started "Systen Info Error" (double regression) Product: Wine Version: 1.7.55 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: isakov-sl(a)bk.ru Created attachment 52897 --> https://bugs.winehq.org/attachment.cgi?id=52897 how the stop looks Since wine-1.7.55 the Futuremark applications 3DMark03, 3DMark05, 3DMark06 stop working with messages "System Info error" or "unhandled exception". With wine 1.7.54 they are working. Regression test give the follow ~~~ quote ~~~ $ git bisect bad f91a7b2cfe5b44fea333ed70b9fc38a509b7798a is the first bad commit commit f91a7b2cfe5b44fea333ed70b9fc38a509b7798a Author: Austin English <austinenglish(a)gmail.com> Date: Wed Nov 4 10:46:50 2015 -0800 fltmgr.sys: Add FltInitializePushLock stub. Signed-off-by: Austin English <austinenglish(a)gmail.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> :040000 040000 9a8f22f1f54f0af7b77216ea29b6360699eacb7e 5185e955c2cb2fe5ca9fa65034af095a9137d23a M dlls :040000 040000 a04028464398c6fceebbbe76e03446a3c2b8cb35 637e2081747c7c533f27d2a0f4ab1258d53bf9fa M include ~~~ quote ~~~ Meanwhile there is double regression as I notice in bug 36548. First regression was 1.7.54 working 1.7.54-140-7fbf33f hang at start. This regression reported and bisecting in 36548. commit 8cc5b07e9d0aedffd4251d2e8942cb8368920bf8 Second regression 1.7.54-134-gd4664c1 works but hang on exit 1.7.55 not working with the message. See attached screenshot. This regression I bisecting here. Strange to see this commit as regression. Analysis. Then I found a key difference in logs. Working log contains: ---- fixme:process:GetLogicalProcessorInformationEx (65535,0x9f6048,0x8beb54): stub ---- Non-working ---- fixme:process:GetLogicalProcessorInformationEx (65535,0x0,0x5203e8): stub ---- Note: second argument is ZERO. 3DMark application works in conjunction with Futuremarks SystemInfo (called by OLE?) and I may propose the SystemInfo calls the function but in second case it will not allocate buffer for CPU info. BOOL WINAPI GetLogicalProcessorInformationEx(LOGICAL_PROCESSOR_RELATIONSHIP relationship, PSYSTEM_LOGICAL_PROCESSOR_INFORMATION_EX buffer, PDWORD pBufLen) Why? Because there are new stubs? This procedure should return false if no buffer? Or this procedure should allocate this buffer? -- 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 40

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs March 2016