https://bugs.winehq.org/show_bug.cgi?id=7767
--- Comment #12 from joaopa <jeremielapuree(a)yahoo.fr> ---
Does the bug still occur with wine-5.15?
Unable to find a download to test by myself.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=4785
joaopa <jeremielapuree(a)yahoo.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jeremielapuree(a)yahoo.fr
--- Comment #14 from joaopa <jeremielapuree(a)yahoo.fr> ---
Bug still occur with wine-5.15. Download link is burst. Here is a working one.
https://web.archive.org/web/20120528122233if_/http://www.t4000.freeserve.co…
Can an administrator put the link at URL place?
--
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.
https://bugs.winehq.org/show_bug.cgi?id=1151
joaopa <jeremielapuree(a)yahoo.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jeremielapuree(a)yahoo.fr
--- Comment #27 from joaopa <jeremielapuree(a)yahoo.fr> ---
Bug still occurs with wine-5.15 with OEM_FIXED_FONT.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=49648
Bug ID: 49648
Summary: Still Life hangs when player starts moving
Product: Wine
Version: 5.13
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: regression
Severity: normal
Priority: P2
Component: directx-dsound
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
CC: z.figura12(a)gmail.com
Regression SHA1: ac528a492b719f6a8759d919710ca733f5acf167
Distribution: ---
err:ntdll:RtlpWaitForCriticalSection section 011294B4 "?" wait timed out in
thread 00d4, blocked by 0024, retrying (60 sec)
--
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.
https://bugs.winehq.org/show_bug.cgi?id=49698
Bug ID: 49698
Summary: Unwinding with a PE based ntdll.dll fails in some
cases
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: martin(a)martin.st
Distribution: ---
Created attachment 67943
--> https://bugs.winehq.org/attachment.cgi?id=67943
Testcase
If ntdll is built as a PE, some unwinding cases (that, as far as I understand,
unwind through ntdll itself) fail, where the testcases succeed if wine is built
with --without-mingw.
The attached testcase that fails is built from
https://github.com/microsoft/compiler-tests/blob/master/eh/ehthrow.cxx with "cl
ehthrow.cxx -Feehthrow-msvc-x64.exe -EHsc -O2" using MSVC 19.24.28314 for x64.
FWIW, in a non-PE build, this testcase also regressed earlier, in
887332f9c7bf0d75f53f88a9739b77b12463d636 "ntdll: Fix KiUserExceptionDispatcher
ABI on x86_64.", but was fixed again by
12dba1b2ae50099de4cd857f867ebcaefe6852d8 "ntdll: Fix PE unwind info for %rsi,
%rdi in KiUserExceptionDispatcher." I think.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=49631
Bug ID: 49631
Summary: Wine does not fill in Vulkan device LUID property when
running in Virtual Desktop
Product: Wine
Version: 5.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winevulkan
Assignee: wine-bugs(a)winehq.org
Reporter: sashok.olen(a)gmail.com
Distribution: ArchLinux
Hi. Previously, this game has an issue with Vulkan backend not being selectable
in the video settings, even in normal fullscreen mode, but in recent versions
this issue was resolved by Wine exposing Vulkan device LUID property.
However, it doesn't seem to work when the game is running in Virtual Desktop
mode, it just reverts to its DX11 backend, which suggests there is a bug with
LUID property when Wine is in virtual desktop mode.
I've additionally tested this with standalone vkd3d-proton and it also reports
that it can't find LUID property when in virtual desktop.
I could attach a log for WWZ but I honestly see no need as there seems to be
absolutely nothing Vulkan related in the output and you can reproduce the issue
with standalone (Windows DLL) Vkd3d-Proton as well.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=37913
Bug ID: 37913
Summary: Inconsistent rounding behaviour for sprintf
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: msvcp
Assignee: wine-bugs(a)winehq.org
Reporter: christopherwuy(a)gmail.com
Distribution: ---
sample source code and output demonstrating the problem:
#include <iostream>
#include <stdio.h>
using namespace std;
int main()
{
double a;
a = 3.5;
char *tmp = new char(100);
char fmt[18] = " is %.0f";
sprintf(tmp, fmt, a);
cout<<endl<<a<<tmp<<endl<<endl;
a = -4.5;
sprintf(tmp, fmt, a);
cout<<endl<<a<<tmp<<endl<<endl;
a = -0.5;
sprintf(tmp, fmt, a);
cout<<endl<<a<<tmp<<endl<<endl;
a = 2597.625;
printf("%.3f", a);
sprintf(tmp, " is %.2lf", a);
cout<<tmp<<endl<<endl;
}
This code running by wine 's Output is:
3.5 is 4
-4.5 is -4
-0.5 is -0
2597.625 is 2597.62
while windows' output is:
3.5 is 4
-4.5 is -5
-0.5 is -1
2597.625 is 2597.63
It indicated that Wine's sprintf used rounding rule which is Round half to
even, while windows used Round half away from zero.
You can find a detailed discussion of 'similar bug' form
https://sourceware.org/bugzilla/show_bug.cgi?id=4943
--
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.
http://bugs.winehq.org/show_bug.cgi?id=24320
Summary: Unexpected DetectEnvStatus.exe crash with Cisco Quick
VPN Client (QVPN 1.4.1.2)
Product: Wine
Version: unspecified
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: ethanfharris(a)gmail.com
Cisco QVPN v1.4.1.2 does not work under Wine. QVPN is used to establish an
IPSec Virtual Private Network tunnel from a client computer to a Cisco
Router/Gateway to facilitate secure communication over the internet.
There appear to be 3 errors when running the Cisco QVPN application under Wine:
(a) an apparent crash / closure of DetectEnvStatus.exe
(b) a failure to resolve a DDNS domain name, and
(c) QVPN is not able to ping the gateway router, and all data transfer over the
VPN fails.
In all cases a popup box appears (see attached screenshot) indicating that
DectectEnvStatus.exe has a serious problem and has closed.
If anyone wants to debug this, I can supply a copy of QVPN, and I can set up a
temporary guest account on my WRVS4400N small business router for testing
purposes. QVPN works fine under Windows Vista SP2, and works fine on a Ununtu
10.04LTS host with a Vista guest running under Oracle VirtualBox. So the QVPN
application itself is OK, and the problem is related somehow to Wine or various
underlying services.
On the attached screenshot the DetectEnvStatus popup appears immediately when I
attempt to connect the VPN. If I use the IP address of the gateway router I am
connecting to in lieu of the DDNS domain name, QVPN will create the VPN, but
the tunnel verification ping test fails and the tunnel will not transmit data,
which is why the "remote gateway not responding" message also appears on the
screenshot. If I specify the DDNS domain name of the remote gateway router,
the VPN tunnel is not established (not shown), suggesting a dynamic DNS
name-to-IP address resolution related problem in Wine.
Any help would be appreciated.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=46994
Bug ID: 46994
Summary: Firefox preferences
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: wvpsvm(a)openmailbox.org
Distribution: ---
Firefox preferences is not accessible.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=44200
Bug ID: 44200
Summary: Quake Champions Instant Crash To Desktop (Steam)
Product: Wine
Version: 2.21
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: 7oxicshadow(a)googlemail.com
Distribution: ---
Created attachment 59969
--> https://bugs.winehq.org/attachment.cgi?id=59969
QC crash dump
I have been playing Quake Champions in Wine with no problems for the past few
months but unfortunately there was a patch released in December that broke
compatibility.
If you open the game, a black window opens and just before the intro would
start to play the game crashes back to desktop. This issue is/was present for a
large number of real windows 7 users as well.
A solution was posted on the Quake Champions forum which has fixed the problem
for %95 of the community.
1. Make sure that Win 7 SP1 is installed
2. Install the following (specific) windows update:
https://www.microsoft.com/en-us/download/details.aspx?id=36805
Does anyone know what this update does, Is there anyway to install it on Wine?
There is no useful debug information as it crashes silently but I have attached
a crashdump.dmp file. I am unsure if the format is propitiatory or not.
I have tested both 2.21 and 2.21 staging as both were working fine before the
patch.
The following link contains an image of a decoded crash dump:
https://bethesda.net/community/topic/148801/quake-champions-failed-to-launc…
The general consensus is that it is something related to game overlays as the
issue has been linked to plays.tv and a number of graphics card software
overlays
--
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.