March 2013 - Wine-Bugs - list.winehq.org

[Bug 33090] New: Apache Flex SDK Installer: can not access file system.
by wine-bugs＠winehq.org March 15, 2013

March 15, 2013

http://bugs.winehq.org/show_bug.cgi?id=33090 Bug #: 33090 Summary: Apache Flex SDK Installer: can not access file system. Product: Wine Version: 1.4.1 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: silver_ghost(a)list.ru Classification: Unclassified Created attachment 43755 --> http://bugs.winehq.org/attachment.cgi?id=43755 screenshot of Apache Flex SDK Installer insallation log Apache Flex SDK Installer (https://flex.apache.org/installer.html) can not install Flex SDK. See attachment for Installer's log. -- 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 9548] New: pxtone: Can't save new project files (*.ptcop), or *.pttune
by wine-bugs＠winehq.org March 15, 2013

March 15, 2013

http://bugs.winehq.org/show_bug.cgi?id=9548 Summary: pxtone: Can't save new project files (*.ptcop), or *.pttune Product: Wine Version: 0.9.44. Platform: Other URL: http://hp.vector.co.jp/authors/VA022293/pxtone.html OS/Version: other Status: UNCONFIRMED Severity: trivial Priority: P2 Component: wine-files AssignedTo: wine-bugs(a)winehq.org ReportedBy: trick(a)icculus.org Using pxtone (v 0.8.3.3), everything seems to work perfectly, *except* for saving a new .ptcop project file (also some d3d warnings in the terminal, but those seem harmless). Exporting to .pttune also doesn't work. Attempting to save either of these results in a dialog box titled "error" containing the text "open file". Interestingly, exporting to new .wav files works fine. (Wild shot in the dark, but could this be related to the filename extension of both .ptcop and .pttune being more than 3 chars?) Ran with freshly generated ~/.wine, and changing the emulated Windows version has no effect. Loading existing .ptcop files work fine. Saving to existing .ptcop files also work fine. Thus, the problem is only saving to new .ptcop files (and .pttune files) that doesn't already exist in the file system. (This also works fine in real Windows.) Using pxtone v 0.8.3.3, available from this page: <http://hp.vector.co.jp/authors/VA022293/pxtone.html> Steps to reproduce (works every time): 1. Download pxtone: <http://homepage2.nifty.com/rochet/storage/pxtone_0833.zip> 2. Delete japanese.ico to enable english mode 3. Run the program, go to File->Save project or File->Save project as 4. Enter a new filename, click save 5. Watch error dialog pop up -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 15

[Bug 32520] New: Call from 0x7b83bcb2 to unimplemented function d3d11.dll.D3D11CreateDevice
by wine-bugs＠winehq.org March 15, 2013

March 15, 2013

http://bugs.winehq.org/show_bug.cgi?id=32520 Bug #: 32520 Summary: Call from 0x7b83bcb2 to unimplemented function d3d11.dll.D3D11CreateDevice Product: Wine Version: 1.5.20 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: Commander.Alchemy(a)gmail.com Classification: Unclassified Created attachment 42901 --> http://bugs.winehq.org/attachment.cgi?id=42901 Backtrace Like the summary tells, this needs to have an added stub. EVE-Online that uses dx9 somehow or for some reason calls for a dx11 function, maybe checking and reporting back to developers on how many dx11 cards are using their application. Issue is that the application crashes soon after that. -- 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 2082] DirectDraw games only showing black screen
by wine-bugs＠winehq.org March 15, 2013

March 15, 2013

http://bugs.winehq.org/show_bug.cgi?id=2082 --- Comment #112 from Manuel Soukup <linuxuser-sky(a)gmx.de> 2013-03-15 05:50:03 CDT --- My suggestion till this bug is fixed officially: Someone who can code, should code a patch that works with the current wine 1.5.25, or modify one of the earlier ones so it works with the 1.5.25 version and not a git version. then we write a appdb note how to - get and compile 1.5.25 wine with this patch locally installed maybe in the Diablo folder - describe how to start D1 with this version of patched wine. - Link this discussion so everybody can read why their is no easy fix We could run Diablo 1 again and as the patch is for an official version and not git this would work as long as wine does not delete the 1.5.25 version from the sourceforge servers, so quite long. I could do all of the above except coding the patch to work with wine 1.2.25 Thanks for consideration -- 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 0

[Bug 2082] DirectDraw games only showing black screen
by wine-bugs＠winehq.org March 15, 2013

March 15, 2013

http://bugs.winehq.org/show_bug.cgi?id=2082 --- Comment #111 from Ben Klein <shacklein(a)gmail.com> 2013-03-15 02:51:42 CDT --- (In reply to comment #110) > wine is not dead, but the project is run in a way that does not put priority in > actually getting applications to run and continue running for the users. > The goals of us users and of most of the developers are just not aligned. False. The goal is to produce a Win32/Win64 implementation for Unix-like systems that allows native Windows applications to run without modification. Bigger, newer games work very well (or better) than Diablo and Worms Armageddon. Please read my post above outlining the difficulties in fixing this particular bug. There are other bugs that cannot be fixed (in the forseeable future) due to architectural differences between Windows and Unix-likes. > My wild guess is that since most of the project is in the hands of a company > that makes money out of "last mile" support, it would make little commercial > sense to put effort in prioritizing applications and regressions. That is indeed wild. You actually have it the wrong way around: Codeweavers uses Wine as a base for their Crossover products (e.g. Crossover Office, Crossover Games). They include hacks that don't pass the rigorous scrutiny of Wine developers to get applications to work that wouldn't otherwise work in Wine. Codeweavers devs are also actively involved in maintaining Wine upstream, as they have a vested interest in ensuring maximum compatibility with the latest Windows software. > See my little rant at Bugzilla is not the place for rants. BACK ON TOPIC: You're welcome to attempt your own fixes or workarounds for this bug and post your results here. -- 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 0

[Bug 2082] DirectDraw games only showing black screen
by wine-bugs＠winehq.org March 15, 2013

March 15, 2013

http://bugs.winehq.org/show_bug.cgi?id=2082 --- Comment #110 from Claudio <sick_soul(a)yahoo.it> 2013-03-15 02:40:54 CDT --- > As to the Wine development and the question on why a 9 year old bug (!) is > marked as NEW: It appears Wine is dead. No matter what they claim, action speak > more than words. Does anyone know of a Wine fork by someone who actually gives > a fuck? > > Johannes wine is not dead, but the project is run in a way that does not put priority in actually getting applications to run and continue running for the users. The goals of us users and of most of the developers are just not aligned. My wild guess is that since most of the project is in the hands of a company that makes money out of "last mile" support, it would make little commercial sense to put effort in prioritizing applications and regressions. See my little rant at http://bugs.winehq.org/show_bug.cgi?id=8854 I was thinking about forking wine a few times in the past, since I had to keep patching it in multiple areas to get my stuff working, and I have recognized the project as dysfunctional a long time ago. However it is a huge task, one that would absorb most of the energies of anyone attempting it, and one that requires multiple talented people for different areas (3D graphics in particular but there are many other complex areas). It seems more realistic to keep stacking, updating and rebasing those out of tree patches, until someone actually does fork wine, but I doubt it will happen, even more because the project becomes less and less important every day, as the importance of the windows PC wanes. -- 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 0

[Bug 2082] DirectDraw games only showing black screen
by wine-bugs＠winehq.org March 14, 2013

March 14, 2013

http://bugs.winehq.org/show_bug.cgi?id=2082 --- Comment #109 from Murray Colpman <muzerakascooby(a)gmail.com> 2013-03-14 18:26:39 CDT --- (In reply to comment #106) > Could you maybe elaborate on how that can be achieved? What do you mean by > "ingame minimisation"? Would be happy to try out your suggestion. Well, the maintainers for the game added an option to change the SetCooperativeLevel call to pass the desktop window as the parameter. This breaks ingame minimisation because the only way to minimise ingame due to other weirdness with the game itself is to set the desktop window as the currently active window. > It may be worthwhile posting the other workarounds here anyway. They may be > useful to users or developers looking at the problem. I believe Windows 8 essentially has a registry key to enable old ddraw behaviour/emulation/something special at least, which is what this workaround does (sets that key). Here's the reg file: Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers] "C:\\Team17\\Worms Armageddon\\WA.exe"="$ DWM8And16BitMitigation Layer_ForceDirectDrawEmulation" So, if Windows has a registry workaround, wine might benefit one too ;) Weirdly enough, WA has implemented new renderers recently - DirectDraw 32-bit (previous was 8-bit), Direct3D 7, Direct3D 9 with CPU palette conversion, and Direct3D 9 with Shader palette conversion. The weird thing is, these also exhibit a black screen in wine, and there appears to be no workaround (apart from DirectDraw 32-bit which has the same workaround as the old 8-bit renderer, that is the SetCooperativeLevel thing described above). I don't know if this is the same bug - if there's some legacy function in DirectDraw that enables the same sort of behaviour - or something completely unrelated, but they do definitely work in Win8. I could have sworn there used to be some debug output that looks related but I can't find it now (the only seemingly-relevant line is fixme:d3d:wined3d_get_adapter_raster_status wined3d 0x14f8e0, adapter_idx 0, raster_status 0x33ef40 semi-stub!). However, I digress, this probably belongs in a new bug. -- 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 0

[Bug 2082] DirectDraw games only showing black screen
by wine-bugs＠winehq.org March 14, 2013

March 14, 2013

http://bugs.winehq.org/show_bug.cgi?id=2082 Vincent Povirk <madewokherd(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|madewokherd(a)gmail.com | -- 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 0

[Bug 2082] DirectDraw games only showing black screen
by wine-bugs＠winehq.org March 14, 2013

March 14, 2013

http://bugs.winehq.org/show_bug.cgi?id=2082 --- Comment #108 from Ben Klein <shacklein(a)gmail.com> 2013-03-14 18:14:32 CDT --- (In reply to comment #101) > (In reply to comment #100) > > But i still fail to understand how a bug that was reported in year 2004 has its > > status named NEW. > > I have been asking myself the same kind of questions. But it's the wine > project, they are beyond our logic. Wine does not typically use the ASSIGNED status in bugzilla. It's only in cases where there is a single, definitive developer responsible for that component. http://bugs.winehq.org/buglist.cgi?query_format=advanced&order=Importance&l… (In reply to comment #104) > (In reply to comment #103) > > By configuring general translucency settings for dialogs to something like 50% > > I could see the game's directdraw area(?) trough the covering dialog-window. > > > > I settled for 50% because when I need to undo the workaround, it's not nice to > > work with completely transparent dialogues. (And for diablo it only matters > > while navigating the menu. YMMV for other games.) > > Interestingly enough, this is pretty much the same workaround people came up > with for getting Worms Armageddon to work in Windows 8. I don't think that's a > coincidence. (However, there are now better workarounds that have been > discovered but they look Windows-specific). It may be worthwhile posting the other workarounds here anyway. They may be useful to users or developers looking at the problem. > I also don't believe this would work in a virtual desktop There's no obvious reason why it shouldn't. Please test it. (In reply to comment #106) > As to the Wine development and the question on why a 9 year old bug (!) is > marked as NEW: It appears Wine is dead. No matter what they claim, action speak > more than words. Does anyone know of a Wine fork by someone who actually gives > a #$%&? Mind your language. This bug is more complicated than it seems on the face of it. It's an incongruence between the way Windows draws its windows and the way X11 draws its windows, caused essentially by a bug in native Windows. Implementing the "hacks" to get it fixed presents two major problems: 1) It would definitely break other programs (solved by making it an app-specific registry flag) 2) It's simply the "wrong way" to do it The truth is apps affected by this bug are incorrectly using the desktop window, triggering the bug that makes them display on native Windows. Wine's current behaviour is the technically "correct" way; Windows 8 reportedly suffers from the same problem running these apps. That's not to say that this bug can't be fixed; it's just a highly complicated and very low priority issue. There are only four apps reported to suffer from this bug. http://appdb.winehq.org/viewbugs.php?bug_id=2082 As much as I'd love to see it get fixed, for the one people are most vocal about (Diablo) it's a minor issue that does not effect main gameplay (the menu scheme can be memorised/transcribed from a Windows system if you so wish), and the second most popular app (Worms Armageddon) has received an official patch that includes a workaround. -- 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 0

[Bug 2082] DirectDraw games only showing black screen
by wine-bugs＠winehq.org March 14, 2013

March 14, 2013

http://bugs.winehq.org/show_bug.cgi?id=2082 --- Comment #107 from Dan Kegel <dank(a)kegel.com> 2013-03-14 18:05:00 CDT --- Wine's still very much under active development. Just because your favorite bug hasn't been fixed doesn't mean a project is dead. See also comments 35-39 above. -- 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 0