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=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=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.
https://bugs.winehq.org/show_bug.cgi?id=46740
Bug ID: 46740
Summary: Photoshop CS5 crashes upon opening in Wine-4.0
Product: Wine
Version: 4.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: Syogren.Asherushi(a)gmail.com
Distribution: ---
Created attachment 63744
--> https://bugs.winehq.org/attachment.cgi?id=63744
The backtrace
See attachment.
--
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=51603
Bug ID: 51603
Summary: All applications were run with a crash dialog, and can
not run any application after re-create the .wine
prefix.
Product: Wine-staging
Version: 6.14
Hardware: x86-64
OS: Mac OS X
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: avenjames(a)live.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Created attachment 70452
--> https://bugs.winehq.org/attachment.cgi?id=70452
Backtrace from the crash dialog.
Machine: MacBook Pro Retina-2015mid with OSX 10.14.6 Mojave
I remember that last time I was using OSX 10.13, I got the same problem.
With the Wine-staging from Gcenx's build. But after deleted the .wine and run
the Wine-staging again, it was back to work normally,
But after playing two games: Red Alert 2 and Diablo II,
I don't know if I was playing too long, games was crashed finally and then I
run "wineserver -k" to kill all the wine-preloader processes,
Then after awhile I wanna to play the game again but it was crashed on the
halfway,
then I start the Terminal to input:
winecfg
it was showing:
-----------------------------------------------------------------------------
Last login: Sat Aug 14 16:36:30 on ttys000
192:~ avenue$ winecfg
0024:fixme:esync:do_esync eventfd not supported on this platform.
002c:fixme:esync:do_esync eventfd not supported on this platform.
002c:fixme:winediag:LdrInitializeThunk wine-staging 6.14 is a testing version
containing experimental patches.
002c:fixme:winediag:LdrInitializeThunk Please mention your exact version when
filing bug reports on winehq.org.
wine: Unhandled page fault on read access to 0000000000000000 at address
00000003AF6DF950 (thread 002c), starting debugger...
0034:fixme:esync:do_esync eventfd not supported on this platform.
0040:fixme:esync:do_esync eventfd not supported on this platform.
0040:err:display:prepare_devices Failed to remove monitor
0040:err:display:macdrv_init_monitor Failed to initialize monitor
0040:err:display:cleanup_devices Failed to remove GPU
0040:err:ole:start_rpcss Failed to open service manager
0034:err:display:cleanup_devices Failed to remove GPU
0034:err:display:prepare_devices Failed to remove monitor
0034:err:display:macdrv_init_monitor Failed to initialize monitor
0034:err:display:cleanup_devices Failed to remove GPU
0034:fixme:thread:get_thread_times not implemented on this platform
0058:fixme:esync:do_esync eventfd not supported on this platform.
0060:fixme:esync:do_esync eventfd not supported on this platform.
0040:err:ole:start_rpcss Failed to open service manager
0060:err:display:cleanup_devices Failed to remove GPU
0060:err:ole:start_rpcss Failed to open service manager
/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.200.3/Common/ChunkCompression.cpp:49:
Error: unsupported compressor 8
/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.200.3/Libraries/CompressData/CompressData.c:353:
Error: Unknown compression scheme encountered for file
'/System/Library/CoreServices/CoreTypes.bundle/Contents/Resources/Exceptions.plist'
/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.200.3/Common/ChunkCompression.cpp:49:
Error: unsupported compressor 8
/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.200.3/Libraries/CompressData/CompressData.c:353:
Error: Unknown compression scheme encountered for file
'/System/Library/CoreServices/CoreTypes.bundle/Contents/Library/AppExceptions.bundle/Exceptions.plist'
0024:err:display:cleanup_devices Failed to remove GPU
0070:fixme:esync:do_esync eventfd not supported on this platform.
/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.200.3/Common/ChunkCompression.cpp:49:
Error: unsupported compressor 8
/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.200.3/Libraries/CompressData/CompressData.c:353:
Error: Unknown compression scheme encountered for file
'/System/Library/CoreServices/CoreTypes.bundle/Contents/Resources/Exceptions.plist'
/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.200.3/Common/ChunkCompression.cpp:49:
Error: unsupported compressor 8
/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.200.3/Libraries/CompressData/CompressData.c:353:
Error: Unknown compression scheme encountered for file
'/System/Library/CoreServices/CoreTypes.bundle/Contents/Library/AppExceptions.bundle/Exceptions.plist'
0070:err:display:cleanup_devices Failed to remove GPU
0078:fixme:esync:do_esync eventfd not supported on this platform.
0078:err:display:cleanup_devices Failed to remove GPU
0078:err:display:prepare_devices Failed to remove monitor
0078:err:display:macdrv_init_monitor Failed to initialize monitor
0078:err:display:cleanup_devices Failed to remove GPU
0060:err:display:prepare_devices Failed to remove monitor
0060:err:display:macdrv_init_monitor Failed to initialize monitor
0060:err:display:cleanup_devices Failed to remove GPU
0078:err:winecfg:open_mountmgr failed to open mount manager err 2
192:~ avenue$ 0060:err:ole:start_rpcss Failed to open service manager
---------------------------------------------------------------------------------
Then I tried to input: rm -rf .wine and run again the winecfg to recreate the
files,
it said:
----------------------------------------------------------------------------------
192:~ avenue$ winecfg
wine: created the configuration directory '/Users/avenjames/.wine'
0024:fixme:esync:do_esync eventfd not supported on this platform.
002c:fixme:esync:do_esync eventfd not supported on this platform.
002c:fixme:actctx:parse_depend_manifests Could not find dependent assembly
L"Microsoft.Windows.Common-Controls" (6.0.0.0)
002c:fixme:winediag:LdrInitializeThunk wine-staging 6.14 is a testing version
containing experimental patches.
002c:fixme:winediag:LdrInitializeThunk Please mention your exact version when
filing bug reports on winehq.org.
wine: Unhandled page fault on read access to 0000000000000000 at address
00000003AF6DF950 (thread 002c), starting debugger...
002c:err:seh:start_debugger Couldn't start debugger L"winedbg --auto 40 48" (2)
Read the Wine Developers Guide on how to set up winedbg or another debugger
wine: could not load kernel32.dll, status c0000135
192:~ avenue$
----------------------------------------------------------------------------------
Then WINE CAN NOT RUN ANY APPLICATION AGAIN,
even tried brew re-install the wine but it was still couldn't make it.
attached backtrace.txt for checking.
--
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=47345
Bug ID: 47345
Summary: When clicking on the Drivers tab, winecfg crashes
Product: Wine
Version: 4.10
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: soulsofblack12(a)hotmail.com
Distribution: ---
Created attachment 64676
--> https://bugs.winehq.org/attachment.cgi?id=64676
The error
I am running wine-staging, when i launch winecfg from the console and try to
click on the Drivers tab, winecfg crashes and closes itself.
--
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=42741
Bug ID: 42741
Summary: StarCraft I: 1.18 PTR fails to initialize
ClientSdk.dll
Product: Wine
Version: 2.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: li.davidm96(a)gmail.com
Distribution: ---
Created attachment 57743
--> https://bugs.winehq.org/attachment.cgi?id=57743
stderr output of Wine when running StarCraft.exe
The 1.18 public test release of the upcoming version of StarCraft I does not
launch, as ClientSdk.dll fails to initialize.
Tested with Wine 2.4 (latest from Arch repositories), in a fresh 64-bit
wineprefix. Architecture is AMD64.
The download is here:
https://us.battle.net/forums/en/starcraft/topic/20753915707
sha1sum:
2d6702a425f13659227814fbc903568d63daeb08
/home/lidavidm/Downloads/Starcraft+1.18+PTR+1202.zip
--
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=52380
Bug ID: 52380
Summary: Logos 9 Bible Software (.NET 4.7 app) menus glitching,
flickering and not showing regression
Product: Wine
Version: 7.0-rc5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: johnpgoodman(a)gmail.com
Distribution: ---
Created attachment 71593
--> https://bugs.winehq.org/attachment.cgi?id=71593
Video showing menu glitch regression.
Menu Items docs guides tools and layout work on first click and then flash
there after. This is a regression which only appears in 7.0rc5-staging. devel
doesn't have this bug. Please see the video for demonstration.
N.b. this is not the same as bug 51984 which was resolved.
Help is much appreciated! Below is the installation guide.
The app is a bit like kindle in so much as the engine is free but the resources
cost so there is a free download. Unlike kindle it has many advanced research
features and books link together etc. The main app is free but there are paid
features, resources and subscriptions. To use the app you need a free account
https://www.logos.com/product/194909/logos-9-basic. It uses a downloader app
which last I tried doesn't work with wine. The actual msi link is
https://downloads.logoscdn.com/LBS9/Installer/9.6.0.0024/Logos-x64.msi
Manual Install Procedure:
1 Install wine 6 or newer
2 winetricks corefonts
3 winetricks settings fontsmooth=rgb
4 winetricks dotnet48
5 winetricks settings renderer=gdi (you might need to set the reg key
manually)
6 Install the Logos.msi download but don't run it.
7 wine64 reg add "HKCU\\Software\\Wine\\AppDefaults\\LogosIndexer.exe" /v
Version /t REG_SZ /d vista /f
8 Run Logos and sign in with your free account.
There is a script which downloads a preconfigured wine bottle and sets it all
up in $USER/Logos_BibleP directory which you can then easily remove etc.
https://github.com/ferion11/LogosLinuxInstaller/releases Choose fast install
without wine AppImage.
--
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.