wine-bugs October 2017

wine-bugs@winehq.org

1 participants
7852 discussions

[Bug 41194] New: SetFileTime does not set timestamp on ntfs-3g mounts
by wine-bugs＠winehq.org 29 Aug '18

29 Aug '18

https://bugs.winehq.org/show_bug.cgi?id=41194 Bug ID: 41194 Summary: SetFileTime does not set timestamp on ntfs-3g mounts Product: Wine Version: 1.9.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: wine.severach(a)spamgourmet.com Distribution: --- To change file times: Total Commander Wine: Files, Change Attributes Double Commander: Files, Change Attributes Linux Shell: touch -r, touch -d, touch -t File time changes from TC are applied VFAT and ext mounts. File time changes from TC are ignored on NTFS mounts. Linux touch and Double Commander are able to change the file time on NTFS mounts. -- 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 35902] New: [EA Origin] Online login is currently unavailable
by wine-bugs＠winehq.org 27 Aug '18

27 Aug '18

http://bugs.winehq.org/show_bug.cgi?id=35902 Bug ID: 35902 Summary: [EA Origin] Online login is currently unavailable Product: Wine Version: 1.7.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: robert2505(a)gmail.com Created attachment 47943 --> http://bugs.winehq.org/attachment.cgi?id=47943 log from running origin up untill the login screen that displays the message Since the latest update (a few days ago), EA Origin displays the message "Online login is currently unavailable" It won't allow me to log in I'm running the latest wine, version 1.7.15 on archlinux x86_64. I've tried the following: -start over in a fresh prefix with WINEARCH=win32 -install Qt5 as described in the appdb entry -use winetricks to install vcrun2008 and vcrun2010 -recompiling wine, in case an update broke it -running it in a windows vm in case the server is actually down (it isn't) I don't recognise anything out of the ordinary in the log, other than the "CLSCTX_REMOTE_SERVER not supported" message. I'm not sure it wasn't there before, but it also displays in Steam and that works fine. -- 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 39

[Bug 28251] New: Shadows do not appear in Mafia II
by wine-bugs＠winehq.org 26 Aug '18

26 Aug '18

http://bugs.winehq.org/show_bug.cgi?id=28251 Summary: Shadows do not appear in Mafia II Product: Wine Version: 1.3.27 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: peanuthead_069(a)yahoo.com I'm not sure if it can be fixed via winetricks, but shadow maps don't show up ingame even if I tweak with the ingame settings. Also, the skydome texture occasionally flickers when I drive or move around. Nothing really that show-stopping, as I can play the game just fine, albeit with somewhat lower framerates. -- 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 24

[Bug 43794] New: While mouse warping is in use, a bounding box randomly traps the cursor.
by wine-bugs＠winehq.org 25 Aug '18

25 Aug '18

https://bugs.winehq.org/show_bug.cgi?id=43794 Bug ID: 43794 Summary: While mouse warping is in use, a bounding box randomly traps the cursor. Product: Wine Version: 2.4 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jlinkkai(a)gmail.com Distribution: --- I've not seen any reports of this, so it may have something to do with my setup. Whenever a program uses mouse warping, a bounding box may trap it at a random time. This is temporarily resolved by causing the window to lose focus. I first knew this bug to occur on 2.4, and it may have been earlier. I knew 2.0 to work perfectly in this regard, but Steam now crashes on that version and cannot test 2.1-2.3. I've created a video demonstrating situations where this occurs. Please request more info where needed. https://youtu.be/-Nzt6p8fYis -- 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 1

[Bug 19376] New: Suspend kwin's compositing when starting a 3D application
by wine-bugs＠winehq.org 24 Aug '18

24 Aug '18

http://bugs.winehq.org/show_bug.cgi?id=19376 Summary: Suspend kwin's compositing when starting a 3D application Product: Wine Version: unspecified Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: kde(a)martin-graesslin.com KDE bug https://bugs.kde.org/show_bug.cgi?id=198744 illustrates that some graphics card drivers are still not able to support 3D applications in a composited environment correctly. This seems to be a stronger problem for wine applications (at least in the bug report). KWin supports suspending compositing via a dbus interface (http://websvn.kde.org/*checkout*/trunk/KDE/kdebase/workspace/kwin/org.kde.K…). You can basically check if compositing is active, suspend it when the app is started and resume when the app is closed. This is for example done by KDE's powermanagement daemon. As a shell script it looks like that: composited='qdbus org.kde.kwin /KWin compositingActive' if $composited; then qdbus org.kde.kwin /KWin toggleCompositing; fi wine blablabla if $composited; then qdbus org.kde.kwin /KWin toggleCompositing; fi I basically wish with this enhancement report that you add support for suspending KWin's compositing on an application basis in wine. It shouldn't be for every app and it shouldn't be activated in general but the user should have the possibility to just say that one specified app should suspend compositing. -- 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 24

[Bug 42016] New: texture map covering whole screen (Driver San Francisco)
by wine-bugs＠winehq.org 24 Aug '18

24 Aug '18

https://bugs.winehq.org/show_bug.cgi?id=42016 Bug ID: 42016 Summary: texture map covering whole screen (Driver San Francisco) Product: Wine Version: 1.9.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: o.dierick(a)piezo-forte.be Distribution: --- Created attachment 56461 --> https://bugs.winehq.org/attachment.cgi?id=56461 controls option menu screen shot bug visible Some kind of texture map covers the whole screen when driving, making the game unplayable. The same texture covers the whole screen in the controls option menu (see attached screen shot). It looks like the game want to show an icon from a texture map, but the whole texture map is drawn instead. The log and screenshot are from a 3840x1024 triple-monitor setup, but the issue is the same on a 1920x1080 widescreen setup. Found on wine 1.9.22, still present on wine 2.0-rc2. -- 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 11

[Bug 41696] New: Trials Fusion requires DXGI_FORMAT_R32G8X24_TYPELESS support
by wine-bugs＠winehq.org 24 Aug '18

24 Aug '18

https://bugs.winehq.org/show_bug.cgi?id=41696 Bug ID: 41696 Summary: Trials Fusion requires DXGI_FORMAT_R32G8X24_TYPELESS support Product: Wine Version: 1.9.22 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: leslie_alistair(a)hotmail.com Distribution: --- Trying to run the Steam version of the Trial Fusion, results in a crash. Snippet of the log at the point of the crash. 01ce:trace:d3d11:d3d11_device_CreateTexture2D iface 0x4ca43d0, desc 0x991e408, data (nil), texture 0x22767b50. 01ce:trace:d3d:wined3d_texture_create device 0x4cae168, desc 0x991e348, layer_count 1, level_count 1, flags 0, data (nil ), parent 0x10d9f818, parent_ops 0x7df6bcac, texture 0x10d9f830. 01ce:trace:d3d:wined3d_texture_init texture 0x10d9f870, texture_ops 0x7e213740, layer_count 1, level_count 1, resource_t ype WINED3D_RTYPE_TEXTURE_2D, format WINED3DFMT_R32G8X24_TYPELESS, multisample_type 0, multisample_quality 0, usage WINE D3DUSAGE_DEPTHSTENCIL | WINED3DUSAGE_TEXTURE, pool WINED3D_POOL_DEFAULT, width 320, height 256, depth 1, flags 0, device 0x4cae168, parent 0x10d9f818, parent_ops 0x7df6bcac, resource_ops 0x7e213728. 01ce:trace:d3d:wined3d_format_calculate_pitch Returning row pitch 2560, slice pitch 655360. 01ce:warn:d3d:resource_init Format WINED3DFMT_R32G8X24_TYPELESS cannot be used for depth/stencil buffers. 01ce:warn:d3d:resource_init Format WINED3DFMT_R32G8X24_TYPELESS cannot be used for depth/stencil buffers. 01ce:warn:d3d:resource_init Format WINED3DFMT_R32G8X24_TYPELESS cannot be used for depth/stencil buffers. 01ce:warn:d3d:resource_init Did not find a suitable GL resource type for resource type WINED3D_RTYPE_TEXTURE_2D. 01ce:warn:d3d:wined3d_texture_init Failed to initialize resource, returning 0x8876086c 01ce:warn:d3d:wined3d_texture_init Failed to initialize resource, returning 0x8876086c 01ce:warn:d3d:texture_init Failed to initialize texture, returning 0x8876086c. 01ce:warn:d3d:wined3d_texture_create Failed to initialize texture, returning 0x8876086c. 01ce:warn:d3d11:d3d_texture2d_init Failed to create wined3d texture, hr 0x8876086c. 01ce:warn:d3d11:d3d_texture2d_create Failed to initialize texture, hr 0x80070057. 01ce:trace:d3d11:d3d11_device_CreateDepthStencilView iface 0x4ca43d0, resource (nil), desc 0x991e5dc, view 0x241a63f0. -- 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 43127] New: wine crashes when trying to launch Gwent
by wine-bugs＠winehq.org 23 Aug '18

23 Aug '18

https://bugs.winehq.org/show_bug.cgi?id=43127 Bug ID: 43127 Summary: wine crashes when trying to launch Gwent Product: Wine Version: 2.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: unduthegun(a)gmail.com Distribution: --- Created attachment 58330 --> https://bugs.winehq.org/attachment.cgi?id=58330 log Wine crashes with a stack overflow when trying to launch it; this didn't happen with 2.8. I'm on Manjaro, I've tried several flavours of wine 2.9 and they all crash when trying to run it. -- 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

[Bug 24951] New: Call of Duty / UO: Jerky freelook
by wine-bugs＠winehq.org 22 Aug '18

22 Aug '18

http://bugs.winehq.org/show_bug.cgi?id=24951 Summary: Call of Duty / UO: Jerky freelook Product: Wine Version: 1.3.6 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: gav616(a)gmail.com At the main menu: When the cursor is moveed around it 'seems' to be at a very low framerate and it jerks about. In-game: When freelooking around, the game seems to stay at the correct rate but the mouse movements are jerked and misinterpreted. It looks like the FPS is dropping to 5 when the jerks occur, but the FPS remains constant through the jerks. Audio is not effected. -- 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 40336] New: Freelancer: Background Texture for in-game "NavMap" spreads across entire screen (Intel only)
by wine-bugs＠winehq.org 21 Aug '18

21 Aug '18

https://bugs.winehq.org/show_bug.cgi?id=40336 Bug ID: 40336 Summary: Freelancer: Background Texture for in-game "NavMap" spreads across entire screen (Intel only) Product: Wine Version: 1.9.5 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: adam(a)aphirst.karoo.co.uk Distribution: --- Created attachment 54005 --> https://bugs.winehq.org/attachment.cgi?id=54005 Example of erroneous behaviour This is essentially a repost of Bug #494 on the Wine-Staging tracker, as it turns out that it is not unique to the -staging builds. https://bugs.wine-staging.com/show_bug.cgi?id=494 ----- A feature of the HUD in this game is the "NavMap", a navigation map which overlays onto the current gameplay and displays a map either of the current star-system, or of the whole galactic sector, and with some additional relevant information. This HUD, like the other gameplay menu-elements, is supposed to simply overlay onto the screen, being transparent/translucent on the outside. Indeed, one can also interact with some game/menu elements outside said window even if it is currently displayed. However, the observed behaviour (attached) for the "NavMap" is that the background texture for the "map" portion, a texture of a star-scape, is instead displayed across the entire screen. The user can still interact with the (now invisible!) objects behind the texture. Some text in the NavMap window is also obscured. This behaviour occurs on a clean install of the game, with the official 1.1 patch, and with Jason's Extended Patch 1.20; also on just the Demo version of the game. http://dl.4players.de/f1/freelancer/freelancer_demo.exe --- I am currently running Wine-Staging 1.9.5 but the bug has been present since at least as early as 1.7.48. Intel i5-3540M with HD4000 graphics, 16GB RAM. Arch Linux x86_64, Linux 4.3.6 (but at least as far back as 4.1.4). Intel driver 2.99.917+579+g74cd4d0 (but at least as far back as 2.99.917+381+g5772556) --- Michael Müller from the Wine-Staging tracker tested this on other graphics hardware/stacks and came to the conclusion that the issue is only present on Intel+Mesa. -- 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

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 October 2017