March 2016 - Wine-bugs - list.winehq.org

[Bug 31978] New: LWA_COLORKEY support significantly slows down GOG installer verification progress bar
by wine-bugs＠winehq.org 05 Nov '18

05 Nov '18

http://bugs.winehq.org/show_bug.cgi?id=31978 Bug #: 31978 Summary: LWA_COLORKEY support significantly slows down GOG installer verification progress bar Product: Wine Version: 1.5.15 Platform: x86 OS/Version: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv AssignedTo: wine-bugs(a)winehq.org ReportedBy: jonas.bugzilla(a)gmail.com Classification: Unclassified Installers from gog.com always first verify their own integrity. During this period they display a custom progress bar, which makes use of the LWA_COLORKEY attribute. Prior to wine containing support for LWA_COLORKEY, this verification process was basically limited by the speed of the hard drive. Since that support has been added, the verification has become much slower, and furthermore the progress bar flickers a lot. I've bisected the cause to commit edea44f0ff995aadaaadb866a022832c16301e4a Author: Alexandre Julliard <julliard(a)winehq.org> Date: Wed Sep 12 16:00:18 2012 +0200 winex11: Add support for the LWA_COLORKEY layered window attribute. To reproduce: it should happen with any installer downloaded from gog.com. I tested with the freely available http://www.gog.com/en/gamecard/teenagent I'm using XQuartz 2.7.4 on Mac OS X 10.6.8. If you need any traces, let me know -- 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 5

[Bug 34391] New: PPSSPP Crash on opening
by wine-bugs＠winehq.org 05 Nov '18

05 Nov '18

http://bugs.winehq.org/show_bug.cgi?id=34391 Bug #: 34391 Summary: PPSSPP Crash on opening Product: Wine Version: 1.6 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: alaskancaveman(a)Live.com Classification: Unclassified Created attachment 45782 --> http://bugs.winehq.org/attachment.cgi?id=45782 Crash Log PPSSPP 9.1 x86 win http://www.ppsspp.org/ current setup ::: amd A6 HD6250G Cayman Linux Mint 15 Ubuntu Raring base 13.04 wine1.6 kernel 3.11rc7 mesa 9.3dev libg3dvl-mesa (gallium) mod: radeon.dpm=1 added kernel boot paramater mod: R600_DEBUG=SB etc/environment ::: the catalyst drivers 13.8b2 will allow 2 open but zero function beyond that without crash... (no 3.11 support yet for Catalyst) both gallium and Catalyst worked fine before 3.11 kernel upgrade from 3.8... which i did after mesa upgrade neither of the 2 mods make any difference on program crash 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 8

[Bug 27473] New: Wine Changing Window Decorations in Conflict with Window Managers
by wine-bugs＠winehq.org 05 Nov '18

05 Nov '18

http://bugs.winehq.org/show_bug.cgi?id=27473 Summary: Wine Changing Window Decorations in Conflict with Window Managers Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv AssignedTo: wine-bugs(a)winehq.org ReportedBy: swt(a)techie.net When running an application under Wine, if the window manager removes the window decorations, Wine restores them. For example, under Unity, when an application is maximized, the WM removes the window decorations as the title bar is merged with the Unity panel. When this happens with a Wine application, Unity removes the decorations, but Wine puts them back (sometimes only partially, leading to a confused experience where the decorations exist but are invisible). -- 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 35438] New: FBO backend doesn't work on some Intel iGPUs
by wine-bugs＠winehq.org 05 Nov '18

05 Nov '18

http://bugs.winehq.org/show_bug.cgi?id=35438 Bug ID: 35438 Summary: FBO backend doesn't work on some Intel iGPUs Product: Wine Version: 1.7.10 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: Zatloukal.Frantisek(a)gmail.com Classification: Unclassified The default backend (FBO) doesn't work on some Intel iGPUs(tested Gen3). Tested GPU: 00:02.0 VGA compatible controller: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller Tested OS: Fedora Rawhide, Ubuntu 12.04 Tested Mesa versions: 9.0, 10.0 Tested affected apps/games: Age of Mythology, ePSXE (I believe this affects most of DirectX 9.0 apps) Switching from fbo to backbuffer solves problems in both tested apps. If fbo is active, terminal log is spammed by: epsxe: fixme:d3d:context_check_fbo_status Location SFLAG_INTEXTURE (0x10000). fixme:d3d:context_check_fbo_status Color attachment 0: (0x1f9ad0) WINED3DFMT_B8G8R8X8_UNORM 1024x600 0 samples. err:d3d:context_bind_texture >>>>>>>>>>>>>>>>> GL_INVALID_FRAMEBUFFER_OPERATION (0x506) from glBindTexture @ context.c / 2031 fixme:d3d:context_check_fbo_status FBO status GL_FRAMEBUFFER_UNSUPPORTED (0x8cdd) aom: fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:buffer_internal_preload Too many declaration changes or converting dynamic buffer, stopping converting err:d3d:wined3d_debug_callback 0x2373e18: "GL_INVALID_ENUM in glLight(light=0x1140b8)". err:d3d:transform_view >>>>>>>>>>>>>>>>> GL_INVALID_ENUM (0x500) from glLightfv posn @ state.c / 3917 err:d3d:wined3d_debug_callback 0x2373e18: "GL_INVALID_ENUM in glLight(light=0x1140b8)". err:d3d:transform_view >>>>>>>>>>>>>>>>> GL_INVALID_ENUM (0x500) from glLightfv dirn @ state.c / 3919 -- 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 33087] New: After uninstall file associations to notepad still persist
by wine-bugs＠winehq.org 05 Nov '18

05 Nov '18

http://bugs.winehq.org/show_bug.cgi?id=33087 Bug #: 33087 Summary: After uninstall file associations to notepad still persist Product: Wine Version: unspecified Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: longsincedark(a)lavabit.com Classification: Unclassified After uninstalling wine I noticed that, although most traces had been removed, my file association list still included notepad for almost all text-type documents. I did manually remove the association for each, but it was a monotonous process. I would have expected the "uninstall" to remove all traces, except user created files &/or directories. This is not a bug on how WINE operates, and I will be re-installing. But it seems only appropriate that an "uninstall" is just that. Please consider, I used WinDONT's for many years and dealt with this problem of uninstall remnants. For most, it may be a minor or trivial issue. But some users, like myself, have qualms about software that leaves too many remnants after uninstalling. Keep up the fabulous work! -- 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 30256] New: Ancients of Ooga: very slow rendering in mid game
by wine-bugs＠winehq.org 05 Nov '18

05 Nov '18

http://bugs.winehq.org/show_bug.cgi?id=30256 Bug #: 30256 Summary: Ancients of Ooga: very slow rendering in mid game Product: Wine Version: 1.3.22 Platform: x86 OS/Version: Linux Status: NEW Keywords: regression Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: gyebro69(a)gmail.com CC: matteo.mystral(a)gmail.com Classification: Unclassified Regression SHA1: 002674e49d3343d2ad4670081276e38af867eefe Created attachment 39520 --> http://bugs.winehq.org/attachment.cgi?id=39520 terminal output Ancients of Ooga is an indie platformer, developed by NinjaBee. The demo version of the game is Steam-only: http://store.steampowered.com/app/91810/ The problem: performance is okay in the menus and during the intro video. As soon as the video ends and the game is loaded, framerate drops dramatically. While in the menus I get 50 fps, in mid-game I get 1-2 fps or less. This makes the game unplayable. The problem appeared in Wine-1.3.22 and is still present in 1.5.0. Actually, Wine-1.3.21 is the one and only version being capable of running the game normally. All previous versions fail to start the game correctly, and all later versions have the reported performance issue. When I start a new game I get 30 fps with 1.3.21, and 1-2 fps with 1.3.22. The result of the regression test: 002674e49d3343d2ad4670081276e38af867eefe is the first bad commit commit 002674e49d3343d2ad4670081276e38af867eefe Author: Matteo Bruni <mbruni(a)codeweavers.com> Date: Mon Jun 6 17:44:43 2011 +0200 wined3d: Fix glDrawBuffers() optimization. :040000 040000 afbbbb65e869d58ae00b56c627228bd6e9d2d1bb 71478cb542317c0b2e3c1dc2b8155a6ff4dcd44a M dlls The problem can be reproduced with the Steam demo version (the game needs native d3dx9_36.dll). Please let me know if you need a log with debug channels enabled. Fedora 16 Nvidia 250 / driver 290.10 X.Org X Server 1.11.4 -- 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 17

[Bug 30924] New: Uncapture Mouse in Fullscreen Windows
by wine-bugs＠winehq.org 05 Nov '18

05 Nov '18

http://bugs.winehq.org/show_bug.cgi?id=30924 Bug #: 30924 Summary: Uncapture Mouse in Fullscreen Windows Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: songandsilence27(a)gmail.com Classification: Unclassified In winecfg, there is an option, under the Graphics tab to automatically capture the mouse in fullscreen windows. When using the emulated virtual desktop, certain programs freezing, crashing, etc., can cause the mouse to stay within the emulated virtual desktop. Killing wine or wineserver causes the mouse to stay within the confines of the virtual desktop, rendering the (actual, X11) desktop useless. The Virtual desktop window will grey out, becoming unresponsive to any and all input meant to close it, including keystrokes such as ALT+F4 and clicking the "close" button. Opening a X11-managed window (e.g., a terminal emulator) inside of the window area will allow keyboard input, and depending on placement, can free the mouse from the virtual desktop window, however, mouse clicks are not functioning in other X11 windows, panels, etc. Killing and restarting the X server via CTRL+ALT+Bksp or switching to a second Virtual Console (e.g., tty2) and issuing "pkill X; startx" will temporarily solve the issue (unless the offending program is run and freezes/crashes again). There should be a key combination to release the mouse back to the X11 desktop environment. -- 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 5

[Bug 37831] New: Wine 1.7.33 incompatible with AMD Catalyst 14.12 "Omega"
by wine-bugs＠winehq.org 05 Nov '18

05 Nov '18

https://bugs.winehq.org/show_bug.cgi?id=37831 Bug ID: 37831 Summary: Wine 1.7.33 incompatible with AMD Catalyst 14.12 "Omega" Product: Wine Version: 1.7.33 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: castarco(a)gmail.com Distribution: --- I don't know if the bug is in the AMD Catalyst package or in the Wine package (I think it's a package bug, not a software bug): There is a conflicting package with catalyst (fglrx-core_14.501-0ubuntu1_amd64) which is a dependency on Wine (in Ubuntu): ocl-icd-libopencl1 . -- 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 27706] New: [integration] Menu entries generated by wine when installing apps are not compatible with Linux Mint menu
by wine-bugs＠winehq.org 05 Nov '18

05 Nov '18

http://bugs.winehq.org/show_bug.cgi?id=27706 Summary: [integration] Menu entries generated by wine when installing apps are not compatible with Linux Mint menu Product: Wine Version: 1.3.23 Platform: All OS/Version: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: programs AssignedTo: wine-bugs(a)winehq.org ReportedBy: wine(a)rodrigosilva.com The command wine generates for menu entries are like this (example): env WINEPREFIX="/home/rodrigo/.wine" wine C:\\windows\\command\\start.exe /Unix /home/sb/.wine/dosdevices/c:/users/sb/Start\ Menu/Programs/Microsoft\ Office/Microsoft\ Office\ Word\ 2007.lnk For some reason they dont work in Linux Mint's main menu (bad parser in mintmenu?). While this can be considered Mint's fault, its MUCH easier for wine to solve this, but just double-quoting the last parameter (the path to .lnk file) and removing escaping-backslashes from it: So the abve example would turn into this: env WINEPREFIX="/home/sb/.wine" wine C:\\windows\\command\\start.exe /Unix "/home/sb/.wine/dosdevices/c:/users/sb/Start Menu/Programs/Microsoft Office/Microsoft Office Word 2007.lnk" Its an easy fix that wouldnt break anything for other distros, and would make Mint work out-of-the-box, So I would be glad to see this "fixed" References: http://bugs.launchpad.net/mintmenu/+bug/714848 http://forums.linuxmint.com/viewtopic.php?f=47&t=57536 -- 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 12

[Bug 24392] New: Mass Effect 2: Lair of the Shadow Broker: Skycar chase scene renders nothing
by wine-bugs＠winehq.org 05 Nov '18

05 Nov '18

http://bugs.winehq.org/show_bug.cgi?id=24392 Summary: Mass Effect 2: Lair of the Shadow Broker: Skycar chase scene renders nothing Product: Wine Version: unspecified Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: megatog615(a)gmail.com After Shepard and Liara(and your choice of team member) enter the Skycar, a loading screen appears. After the loading screen, a mini game starts where you drive the skycar, presumably to catch Vasir(I haven't been able to see it yet due to this bug). The problem is, the game is rendering a blank image. The only other things that I can see are the UI and the game's darker edges film effect(the circular banding around the edges in the screenshot). -- 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 27