https://bugs.winehq.org/show_bug.cgi?id=56002
Bug ID: 56002
Summary: Adaptive sync results in transient halved refresh rate
with winewayland
Product: Wine
Version: 9.0-rc1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: shtetldik(a)gmail.com
Distribution: ---
Component: winewayland.drv
When running Cyberpunk 2077 using winewayland (vkd3d-proton/dxvk's dxgi set up
in the prefix with Wine 9.0-rc1 + esync), there is a transient issue when
monitor's refresh rate drops to half of the game framerate instead of matching
it as adaptive sync should do.
DE: KDE Plasma 5.27.9.
I measure game framerate with MangoHud and monitor's refresh rate with
on-screen OSD. With winex11 they match, with winewayland they match most of the
time, but sometimes refresh rate is halved. So for example the game would have
128 fps and OSD will show 64 Hz.
Since it only happens with winewayland, there must be something specific going
on with it.
KWin developers suggested it could have something to do with some additional
subsurfaces preventing direct scanout for example.
--
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=49767
Bug ID: 49767
Summary: All resources deleted during update Logos Bible
Software
Product: Wine
Version: 5.16
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: johnpgoodman(a)gmail.com
Distribution: ---
Created attachment 68072
--> https://bugs.winehq.org/attachment.cgi?id=68072
Console output from during update
Updates result in data wipe.
Logos stores all resources, eg. ebooks, videos etc in a subdir like
drive_c/users/$username/Local Settings/Application
Data/Logos/Data/$uniqueid/ResourceManager/
When an update to Logos Bible Software becomes available there is a
notification in the app. The update will usually install ok however on wine the
Resources are all wiped. The user is now stuck with a massive download eg.
40gb+. On Windows the resources are always still there after an update.
It's as if the msi somehow overwrites the directory rather than merging with
it?
I've attached a console log updating from 8.15.0.0004 to 8.16.0.0002 - in this
case the update also did not relaunch the newly updated app but simply kept
running. At this point I checked and confirmed all resources were wiped. Once
quit and reloaded it was clear the update had completed but it began to
download everything again.
--
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=45151
Bug ID: 45151
Summary: patches: 'git send-email' through Zoho SMTP causes
patch queue to go berserk
Product: WineHQ.org
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: www-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: kyle.auble(a)zoho.com
Distribution: ---
Created attachment 61339
--> https://bugs.winehq.org/attachment.cgi?id=61339
I'm starting to get embarrassed
So I'll probably just start using my Gmail account for submissions to Wine
anyways, but I've been having problems sending patches through Zoho.
I've followed the instructions on
https://wiki.winehq.org/Submitting_Patches
and when running 'git send-email', there are no issues on my computer. I'm
prompted for my SMTP password, git does its thing, and I've received an "OK /
250" return code every time.
Small, one-off patches seem to make it through fine, but beyond that, then the
wine-devel or the patch-list doesn't get them. Furthermore, Zoho delivers me a
message saying that wine-devel can't be reached and that they'll keep retrying
the delivery. And they do, which is where I think part of the problem might be
coming from.
---
In the first case, I tried sending a series of 7 patches. The first patch was a
very short text change, the next five were larger batch substitutions on
different strings, and the last one was a relatively short binary patch to
delete five images.
The first patch made it through pretty quickly, but the rest never showed up.
To make things more confusing, I received Zoho notices that patches 5-7
couldn't reach the list and would be retried, but nothing about 2-4. Then a few
hours later, the mailing list confirmed that patch 7 had made it through fine,
but no sign of the middle 5.
Since I had no notification from wine-devel or Zoho for patches 2-4, I tried
resending patch 2 a couple times. Everything besides patches 1 & 7 seemed to
just be falling into a black-hole though... until the next morning, every last
patch I had sent (including the repeats of patch 2) was on both wine-devel and
the patch-list, showing the original send dates, as if they had been there all
along.
---
In the second case, I had three large binary patches for deleting old images
that have since been moved onto the wiki. I tried sending them one-at-a-time,
'git send-email' gave me an OK / 250, and they never made it to the list. This
time Zoho sent me a notice saying that there was a fatal error with
wine-devel's address, specifically
"ResponseCode 421, Read timed out"
The notice said they would keep retrying the delivery for 4 days, but then I
didn't hear anything... until all of a sudden, today I see this on the patch
queue (screenshot attached). I know I didn't resend either of these patches,
much less 17 times. Weirdly enough, the wine-devel mailing list seems to
understand what's going on a little better and only shows the message once.
---
The one other pattern I have noticed is that it almost seems like the mailing
list is clocking out for business hours. The first was on a Wed evening, but it
wasn't until the next morning that everything suddenly appeared. The second
time, I tried sending in my patches before Friday evening, but there was still
no sign of them when I checked yesterday (Sun). Sure enough, they're all there
today though.
TL/DR: I know very little about how mail protocols work, and it could very well
be on my mail service's end, but it almost seems like the mailing-list is
actually receiving the emails. It then puts them in quarantine outside of
normal work-hours, which doesn't seem like a problem in isolation. Somehow the
sender is getting "delivery failed" codes though, and I only seem to get
delivery receipts sporadically, despite turning on delivery receipts in my
pipermail settings for wine-devel.
--
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=56051
Bug ID: 56051
Summary: Clickteam Fusion Application Bug
Product: Wine
Version: 8.21
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: coopacademy2020(a)gmail.com
Distribution: ---
On Wine Staging 8.21, Clickteam Fusion-made applications with things that are
activated by hovering your mouse over the bottom of the screen (for example,
FNaF games) tend to get triggered without the user allowing the game to do so.
This also happens on every version of Windows, including Windows 11, Windows
10, etc.
--
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=55799
Bug ID: 55799
Summary: ws2_32: setsockopt flag IP_RECVIF unimplemented
Product: Wine
Version: 6.0.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winsock
Assignee: wine-bugs(a)winehq.org
Reporter: Littlefighter1996(a)googlemail.com
Distribution: ---
Created attachment 75287
--> https://bugs.winehq.org/attachment.cgi?id=75287
UDP Receive Program
Some applications require IP_RECVIF to be set in order to identify the source
(IP Address and Interface) from which a message has been received.
This flag is not implemented,
leading to either termination of the program or unexpected behavior.
--
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=43443
Bug ID: 43443
Summary: mouse pointer/focusing issues with wine 2.11.1
Product: Wine
Version: 2.11
Hardware: x86
URL: https://bugzilla.redhat.com/show_bug.cgi?id=1468889
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: winebugs(a)evolution-hosting.eu
Distribution: Fedora
Description of problem:
Since wine got updated to 2.11-1 this morning, i had trouble with the mouse
pointer in "Runes of Magic" .
The pointer got invisible/stuck/both randomly when moving it on and off the
monitor ( dual monitor here ) where ROM was running, wenn moving the char
around with WASD controls. This was disturbing and made "dangerouse" gameplay
next to impossible, i.o.w. i couldn't risk dangerouse actions in game, because
it was uncertain if i could control the game while doing it.
After downgrading, it works again flawless ( said that in context with ROM,
means something :D )
Version-Release number of selected component (if applicable):
2.11.1-fc25
List of packages installed - Action taken to revert wine back to 2.10 :
wine-2.11-1.fc25.i686 38/74
wine-2.11-1.fc25.i686 39/74
wine-fonts-2.11-1.fc25.noarch40/74
wine-desktop-2.11-1.fc25.noarch 41/74
wine-pulseaudio-2.11-1.fc25.i686 42/74
wine-alsa-2.11-1.fc25.i686 43/74
wine-capi-2.11-1.fc25.i686 44/74
wine-cms-2.11-1.fc25.i686 45/74
wine-ldap-2.11-1.fc25.i686 46/74
wine-openal-2.11-1.fc25.i686 47/74
wine-opencl-2.11-1.fc25.i686 48/74
wine-twain-2.11-1.fc25.i686 49/74
wine-core-2.11-1.fc25.i686 50/74
wine-common-2.11-1.fc25.noarch 51/74
wine-times-new-roman-fonts-2.11-1.fc25.noarch 52/74
wine-tahoma-fonts-system-2.11-1.fc25.noarch 53/74
wine-pulseaudio-2.11-1.fc25.i686 54/74
wine-tahoma-fonts-2.11-1.fc25.noarch 55/74
wine-alsa-2.11-1.fc25.i686 56/74
wine-capi-2.11-1.fc25.i686 57/74
wine-cms-2.11-1.fc25.i686 58/74
wine-ldap-2.11-1.fc25.i686 59/74
wine-openal-2.11-1.fc25.i686 60/74
wine-opencl-2.11-1.fc25.i686 61/74
wine-twain-2.11-1.fc25.i686 62/74
wine-systemd-2.11-1.fc25.noarch 63/74
wine-arial-fonts-2.11-1.fc25.noarch 64/74
wine-courier-fonts-2.11-1.fc25.noarch 65/74
wine-fixedsys-fonts-2.11-1.fc25.noarch 66/74
wine-marlett-fonts-2.11-1.fc25.noarch 67/74
wine-ms-sans-serif-fonts-2.11-1.fc25.noarch 68/74
wine-small-fonts-2.11-1.fc25.noarch 69/74
wine-symbol-fonts-2.11-1.fc25.noarch 70/74
wine-system-fonts-2.11-1.fc25.noarch 71/74
wine-wingdings-fonts-2.11-1.fc25.noarch 72/74
wine-core-2.11-1.fc25.i686 73/74
wine-filesystem-2.11-1.fc25.noarch 74/74
Bug has been reported to Fedoras Bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?id=1468889
--
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=54270
Bug ID: 54270
Summary: Random crashing in Overwatch 2
Product: Wine
Version: 8.0-rc2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: nanotwerp(a)gmail.com
Distribution: ---
While playing Overwatch 2, I experience random crashing. This especially
happens when I play Ashe, and I do not recall it happening while playing other
characters, but this could be a coincidence. The error I get is:
free(): invalid pointer
06a8:err:seh:call_stack_handlers invalid frame 0000000027B4E3E0
(0000000027952000-0000000027A50000)
06a8:err:seh:NtRaiseException Exception frame is not in stack limits => unable
to dispatch exception.
The same issue was also noted by someone who posted this Blizzard bug report:
https://us.forums.blizzard.com/en/blizzard/t/random-crashes-in-game-wow-cla…
I believe that this issue is what this merge request by Torge Matthies was made
to fix: https://gitlab.winehq.org/wine/wine/-/merge_requests/1152 . Oddly
enough, though, after applying Matthies' patch rebased to 8.0-rc2
(https://github.com/openglfreak/wine-tkg-userpatches/search?q=overwatch), I
still experience this error. I think that some change in 8.0 (Full-ish PE
conversion maybe?) caused this incompatibility with Overwatch 2.
--
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=45416
Bug ID: 45416
Summary: mousepointer of runes of magic disapears if the window
gets blurred and refocused
Product: Wine
Version: 3.11
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: winebugs(a)evolution-hosting.eu
Distribution: Fedora
Version: wine-3.11-1.fc27.x86_64 / wine-staging-common-3.11-1.i686
mousepointer of runes of magic disapears if the window gets blurred and
refocused
aka.. mouse out of the window and back in.
After selecting an item in the back, it gets back to normal, but if you can't
hit one, the mousepointer gets only updated when left or right mb is pressed.
the button click just updates the position, but it does not stop the problem,
only a item drop (in the bag ) does.
it was no problem with this version:
# cat /root/wine.works.rpm.liste
mingw32-wine-gecko-2.47-2.fc26.noarch
mingw64-wine-gecko-2.47-2.fc26.noarch
wine-2.10-1.fc25.i686
wine-2.10-1.fc25.x86_64
wine-alsa-2.10-1.fc25.i686
wine-alsa-2.10-1.fc25.x86_64
wine-arial-fonts-2.10-1.fc25.noarch
wine-capi-2.10-1.fc25.i686
wine-capi-2.10-1.fc25.x86_64
wine-cms-2.10-1.fc25.i686
wine-cms-2.10-1.fc25.x86_64
wine-common-2.10-1.fc25.noarch
wine-core-2.10-1.fc25.i686
wine-core-2.10-1.fc25.x86_64
wine-courier-fonts-2.10-1.fc25.noarch
wine-debuginfo-1.9.3-1.fc23.x86_64
wine-desktop-2.10-1.fc25.noarch
wine-filesystem-2.10-1.fc25.noarch
wine-fixedsys-fonts-2.10-1.fc25.noarch
wine-fonts-2.10-1.fc25.noarch
wine-ldap-2.10-1.fc25.i686
wine-ldap-2.10-1.fc25.x86_64
wine-marlett-fonts-2.10-1.fc25.noarch
wine-mono-4.7.0-1.fc25.noarch
wine-ms-sans-serif-fonts-2.10-1.fc25.noarch
wine-openal-2.10-1.fc25.i686
wine-openal-2.10-1.fc25.x86_64
wine-opencl-2.10-1.fc25.i686
wine-opencl-2.10-1.fc25.x86_64
wine-pulseaudio-2.10-1.fc25.i686
wine-pulseaudio-2.10-1.fc25.x86_64
wine-small-fonts-2.10-1.fc25.noarch
wine-staging-2.10-1.i686
wine-staging-common-2.10-1.i686
wine-symbol-fonts-2.10-1.fc25.noarch
wine-systemd-2.10-1.fc25.noarch
wine-system-fonts-2.10-1.fc25.noarch
wine-tahoma-fonts-2.10-1.fc25.noarch
wine-tahoma-fonts-system-2.10-1.fc25.noarch
wine-times-new-roman-fonts-2.10-1.fc25.noarch
winetricks-20170517-1.fc25.noarch
wine-twain-2.10-1.fc25.i686
wine-twain-2.10-1.fc25.x86_64
wine-wingdings-fonts-2.10-1.fc25.noarch
--
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=35179
Bug ID: 35179
Summary: Quake Live standalone login window crashes when TAB
pressed
Product: Wine
Version: 1.7.8
Hardware: x86-64
URL: http://quakelive.com
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: gdiplus
Assignee: wine-bugs(a)winehq.org
Reporter: alexandru.balut(a)gmail.com
Classification: Unclassified
Steps to reproduce:
1. Open QuakeLive's Launcher.exe
2. Wait a few seconds for the round Play button to become red. At this point
the username field should be focused.
3. Press TAB three times, notice the app crashes
$ sha1sum .wine-ql/drive_c/Program\ Files\ \(x86\)/Quake\ Live/Launcher.exe
b4d565634bdac72047790d64dbc870b8b8bb5f48 .wine-ql/drive_c/Program Files
(x86)/Quake Live/Launcher.exe
$ sha1sum QuakeLiveSetup_840.exe
843d1542bccaaf1bd46bee0acec95d4bfdfc898b QuakeLiveSetup_840.exe
$ wine --version
wine-1.7.8
--
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=53953
Bug ID: 53953
Summary: Recent Wine 7.21 commit makes the build environment
unable to detect 32-bit FreeType 2 libraries on Fedora
Product: Wine
Version: 7.21
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: build-env
Assignee: wine-bugs(a)winehq.org
Reporter: nanotwerp(a)gmail.com
Distribution: ---
The commit in question is the one linked here:
https://gitlab.winehq.org/wine/wine/-/commit/c7a97b5d5d56ef00a0061b75412c6e…
--
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.