http://bugs.winehq.org/show_bug.cgi?id=35344
Bug ID: 35344
Summary: Cygwin's post-install scripts fail on fork errors
Product: Wine
Version: 1.7.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mail(a)georg.so
Classification: Unclassified
Executing 'wine setup-x86.exe' seems to work quite well (you can step through
the wizard, packages are downloaded and extracted) until the post-installation
bash scripts are executed.
Then I get for each script a message like:
running: C:\cygwin\bin\bash.exe --norc --noprofile
"/etc/postinstall/glib2.0.sh"
[..]
fixme:ntdll:NtQueryInformationProcess (process=0xffffffff) Unimplemented
information class: ProcessSessionInformation
[..]
fixme:ntdll:NtQueryVolumeInformationFile 0xf0: faking attribute info
fixme:ntdll:NtQueryVolumeInformationFile 0xec: faking attribute info
fixme:ntdll:NtQueryInformationFile Unsupported class (34)
[..]
fixme:ntdll:NtQueryVolumeInformationFile 0xf4: faking attribute info
fixme:ntdll:NtQueryInformationFile Unsupported class (8)
[..]
fixme:ntdll:NtQueryVolumeInformationFile 0xfc: faking attribute info
[..]
fixme:ntdll:NtQueryVolumeInformationFile 0x100: faking attribute info
fixme:ntdll:NtQueryVolumeInformationFile 0x124: faking attribute info
[..]
fixme:ntdll:NtQueryVolumeInformationFile 0x128: faking attribute info
[..]
/etc/postinstall/glib2.0.sh: fork: retry: Resource temporarily unavailable
/etc/postinstall/glib2.0.sh: fork: retry: Resource temporarily unavailable
/etc/postinstall/glib2.0.sh: fork: retry: Resource temporarily unavailable
/etc/postinstall/glib2.0.sh: fork: retry: Resource temporarily unavailable
/etc/postinstall/glib2.0.sh: fork: Resource temporarily unavailable
abnormal exit: exit code=254
The fork error message are always displayed after some kind of timeout.
Where to get the setup-x86.exe:
http://cygwin.com/setup-x86.exe
$ md5sum setup-x86.exe
c9818d3500e42fd9eb755d424450871a setup-x86.exe
Executing Cygwin's setup exe inside wine looks a little bit silly, but I want
to create a reference cygwin installation for deployment purposes.
see also: http://wiki.winehq.org/CygwinSupport
--
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=48341
Bug ID: 48341
Summary: Warframe Online Installer show msgbox 'Unsupported
file system format'
Product: Wine-staging
Version: 5.0-rc2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: lvb.crd(a)protonmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 66078
--> https://bugs.winehq.org/attachment.cgi?id=66078
Winecfg staging-5.0-rc2
Can't possible install Warframe from original site via Warframe Online
Installer
because after choosing folder for installing getting msgbox 'Unsupported file
system format'
direct link: http://content.warframe.com/dl/Warframe.msi
SHA1 (Warframe.msi) = de9df6731e2dcee2daece6acd5238393c7cd5696
Was used wine from binary repository of archlinux
direct link:
https://archive.archlinux.org/packages/w/wine-staging/wine-staging-5.0rc2-1…
I already makes several test and found that first "problem" commit -
https://github.com/wine-staging/wine-staging/commit/73caf7ace23578a2bfce5f4…
If use tree before this commit or build 5.0-rc2 without apply
'ntoskrnl-safedisc-2' patchset - this issuie is gone.
There is some additional symptom.
If in version with 'ntoskrnl-safedisc-2' patchset open Winecfg's tab "Drive"
you will see too many string for Disks (all 28 i guess, look screenshot).
If delete these unnecessary "psevdo-disks" and reopen Winecfg - they will
appear 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=47483
Bug ID: 47483
Summary: Significant performance regression in Overwatch due to
loader-KeyboardLayouts patch
Product: Wine-staging
Version: 4.12.1
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: sashok.olen(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Seems like this patch creates a lot of entries in system.reg (around 600 lines)
that all look pretty much like this:
[System\\CurrentControlSet\\Control\\Keyboard Layouts\\000b0c00] 1562521578
6843440
#time=1d534ebe1c1fd30
This somehow??? results in 40% drop of FPS in my test app/game, Overwatch
(could be similar to this? https://bugs.winehq.org/show_bug.cgi?id=47431)
Reverting the patch fixes it but only if I also remove all the spammy entries
from the system.reg in the prefix. Leaving them causes even older versions Wine
versions to experience the performance drop.
--
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=48379
Bug ID: 48379
Summary: RC2 & above break VideoReDo 6 activation
Product: Wine
Version: 5.0-rc2
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: carpprotractor(a)yahoo.co.uk
Distribution: ---
Link to current download page -
https://www.videoredo.net/msgBoard/index.php?resources/videoredo-tvsuite-v6…
I've been using VideoReDo 6 on wine-staging for a good few months now and it
works for the most part (the batch manager doesn't as it can't register the COM
component).
I have a licenced version of VideoReDo which you register with a name & key, as
with a lot of other software.
When I installed rc2 the other week and then opened VideoReDo I was prompted
with the activation wizard. As I had already registered and been using the
application, this was a bit of a surprise, however I followed the activation
process again to register the product, but it failed to register.
There's a thread at https://forum.winehq.org/viewtopic.php?f=8&t=33287&e with
the error messages, which appear to suggest the internet connection is
unavailable.
I created a fresh wine prefix to make sure the existing prefix wasn't the
issue. VideoReDo still failed to activate my licence.
I then downgraded back to rc1. The activation wizard still appeared but it did
let me activate the product (unlike rc2).
This error persists with rc3. I have tested again with a new prefix but still
cannot activate my licence unless I downgrade back to rc1.
I would suggest this is therfore a regression.
--
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=46508
Bug ID: 46508
Summary: wine uninstaller crashes when attempting to remove
apps/games installed through NSIS installer
Product: Wine-staging
Version: 4.0
Hardware: x86
URL: https://sourceforge.net/projects/apexdc/files/ApexDC%2
B%2B/1.2.1/ApexDC%2B%2B_1.2.1_setup.exe/download
OS: Linux
Status: NEW
Keywords: download, Installer
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: gyebro69(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ArchLinux
Created attachment 63358
--> https://bugs.winehq.org/attachment.cgi?id=63358
backtrace
I came across this problem when I was trying to uninstall some of my games
which were obtained from DotEmu. Apparently, their games was using an older
version of the NSIS (Nullsoft Scriptable Install System) installer (v2.37).
The problem: I'm starting with 'wine uninstaller' and select the game to be
removed. I click on the <Modify/Repair> button which launches the NSIS
uninstaller program. At this point Wine's uninstaller process crashes leaving
the NSIS uninstaller still running and functioning. Despite of the crash
removing of the selected program was successful.
The bug is not present in vanilla Wine, only in Staging.
The patch to blame:
https://github.com/wine-staging/wine-staging/blob/master/patches/user32-msg…
To reproduce the problem I dug up an old version of ApexDC++ . The installer is
NSIS v2.45, but the same problem is present.
https://sourceforge.net/projects/apexdc/files/ApexDC%2B%2B/1.2.1/ApexDC%2B%…
ApexDC++_1.2.1_setup.exe
mdsum: 5867d2696df30a27f7d533caffd12af0
--
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=48069
Bug ID: 48069
Summary: floating point exception (core dumped) when
WINEESYNC=1
Product: Wine-staging
Version: 4.19
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ZenAnonX(a)protonmail.ch
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Wine-Staging Crashes with "floating point exception (core dumped)" on running
any application with esync enabled.
Applications run fine with esync disabled on staging or with esync enabled on
master
Most probably introduced with commit fb40c21c7280d5cb66f0cec8ed2f4e4e25e1fc56
--
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=41199
Bug ID: 41199
Summary: SW KoTOR: Unhandled page fault on write access
Product: Wine
Version: 1.9.16
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: bystrzak14(a)gmail.com
Distribution: ---
Created attachment 55439
--> https://bugs.winehq.org/attachment.cgi?id=55439
Log from gameplay
I recently installed KoTOR on Fedora 24. Game starts correctly through Steam
and works fluently, but it randomly crashes during loading new area or saved
game.
I tried tweaking "quartz" to "bultin" as in this thread
https://bugs.winehq.org/show_bug.cgi?id=22910
although is kinda old. Anyway, this didn't solve my problem. Those crashes are
really annoying and I can't really enjoy the game because of that.
I run the game with custom prefix using 32bit.
I attach complete log generated throughout my gameplay.
--
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=47417
Bug ID: 47417
Summary: Overwatch doesn't capture mouse movement to croshairs
Product: Wine-staging
Version: 4.11
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: winehq(a)junaru.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
As of wine-staging 4.10 mouse movement is no longer captured to the crosshairs
while in game.
Mouse works as expected in main menu and up to the point where you enter game
world. When the map loads mouse cursor is still present on screen and
horizontal or vertical movement moves the cursor instead of the croshairs. Left
and right mouse button clicks work as expected.
Once every 10 or so game launches the mouse IS captured to the crosshairs and
everything works as expected. (some race condition?)
This issue is not present in wine-staging 4.8. (archlinux packaged wine-staging
4.9 has different issues that prevent testing)
GPU: RX580 (amdgpu) DXVK 1.2.2
# pacman -Q|grep 'vulkan\|mesa\|linux\|xorg-server\|wine'
lib32-mesa 19.1.0-2
lib32-vulkan-icd-loader 1.1.107-1
lib32-vulkan-radeon 19.1.0-2
linux 5.1.14.arch1-1
linux-api-headers 5.1-1
linux-firmware 20190618.acb56f2-1
linux-headers 5.1.14.arch1-1
mesa 19.1.0-3
vulkan-extra-layers 1.1.97.0+10340+118b2f331-1
vulkan-headers 1:1.1.111-1
vulkan-html-docs 1:1.1.111-1
vulkan-icd-loader 1.1.108-1
vulkan-radeon 19.1.0-3
vulkan-trace 1.1.97.0+10340+118b2f331-1
vulkan-validation-layers 1.1.107-1
wine-mono 4.9.0-1
wine-staging 4.11-1
wine_gecko 2.47-2
winetricks 20190615-1
xorg-server 1.20.5-1
xorg-server-common 1.20.5-1
xorg-server-devel 1.20.5-1
xorg-server-xdmx 1.20.5-1
xorg-server-xephyr 1.20.5-1
xorg-server-xnest 1.20.5-1
xorg-server-xvfb 1.20.5-1
--
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=47513
Bug ID: 47513
Summary: mailing-list-patches breaks gamepad input
Product: Wine-staging
Version: 4.12.1
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: sashok.olen(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 64902
--> https://bugs.winehq.org/attachment.cgi?id=64902
+tid,+pid,+plugplay,+hid,+hid_report,+hidp,+xinput,+dinput,+rawinput
With mailing-list-patches patchset, all of my games are unable to detect a
gamepad and receive no input from it.
If I build staging with it reverted, the issues disappears.
Attaching log with
+tid,+pid,+plugplay,+hid,+hid_report,+hidp,+xinput,+dinput,+rawinput debug
channels.
--
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.