https://bugs.winehq.org/show_bug.cgi?id=47997
Bug ID: 47997
Summary: Allow setting $WINEDEBUG
Product: Wine-Testbot
Version: unspecified
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
To figure out why a test is failing in a TestBot Wine VM it would sometimes be
useful to be able to set $WINEDEBUG.
The trouble with $WINEDEBUG is that it can result in very large logs (e.g. if
set to +all or _relay). But then the tests can already generate large files by
looping on a printf() so that's not really a new issue, it's just less likely
to happen accidentally.
The way to deal with that would be to limit the size of the log and reports
that the TestBot retrieves from the VMs.
Notes:
* The TestBot already collects the whichever traces Wine puts out which would
typically be the FIXME()s and ERR()s. They are at the end of the "full task
log".
* So a workaround is to patch Wine to convert the relevant traces to FIXME()s.
That's not very practical if one does not initially know which ones are going
to be needed which is why being able to set $WINEDEBUG would be better.
--
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=47900
Bug ID: 47900
Summary: Enable caching of screenshots and log files
Product: Wine-Testbot
Version: unspecified
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
web/Screenshot.pl and web/GetFile.pl systematically disable caching of the
files they return by setting their Last-Modified field to the current time.
For Screenshot.pl this may have been to deal with live screenshots that were
updated regularly. But even so this should probably be done through the Expires
field instead. Anyway we don't have live snapshots anymore and when they come
back it will (most likely) be in the form of a timestamped filename so that
once written a file would not change.
The only case where a file may change is when a job is canceled and restarted.
That does not seem to warrant disabling caching altogether.
--
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=47901
Bug ID: 47901
Summary: Stream the files in Screenshot.pl and GetFile.pl
Product: Wine-Testbot
Version: unspecified
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
Screenshot.pl and GetFile.pl load their files entirely in memory before
returning them. That's wasteful.
Also GetFiles.pl loads it in a $ImageBytes variable despite returning patches
and executables.
--
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=44684
Bug ID: 44684
Summary: Shaders fail to compile in Roblox Studio (white
window)
Product: Wine
Version: 3.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: and3md(a)gmail.com
Distribution: ---
Created attachment 60693
--> https://bugs.winehq.org/attachment.cgi?id=60693
Roblox Studio run log
The application displays splash screen correctly. Next, the main window is
showed which is "empty" (the window is white). The cursor changes its shape in
some places so probably it's just a display case. Wine returns a lot of errors:
007d: err: d3dcompiler: compile_shader HLSL shader parsing failed.
007d: fixme: hlsl_parser: declare_vars Complex initializers are not supported
yet.
Hardware: Geforce GTX 1060 (proprietary linux driver).
--
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=19329
Summary: Program installs but client fails to connect to server
Product: Wine
Version: 1.1.25
Platform: PC
URL: http://www.livezilla.net/
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: junk(a)mandd.com
Using Wine 1.1.25 and a clean ~/.wine, I had to install dotnet20 and ie6 (I
used winetricks) before the installer would complete. After that the Livezilla
client will run. But when I try to connect to a Livezilla server, an error
window pops up stating:
--------------------------------------------------------------------
The underlying connection was closed: The connection was closed unexpectedly.
Further information:
The underlying connection was closed: The connection was closed unexpectedly.
--------------------------------------------------------------------
--
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.
http://bugs.winehq.org/show_bug.cgi?id=34865
Bug #: 34865
Summary: Can't execute mingw toolchain provided by Rtools
Product: Wine
Version: 1.7.4
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: mail(a)kirill-mueller.de
Classification: Unclassified
I can't execute "R CMD INSTALL" on an installation of R + Rtools in Wine
(latest version from PPA "ppa:ubuntu-wine/ppa"). A reproducible script and
console output can be found here: https://gist.github.com/krlmlr/7333242 . The
script will set and write to $WINEPREFIX and download to $DOWNLOAD_DIR.
Unfortunately, the logs do not show enough detail. After the line `about to run
R CMD SHLIB -o kimisc.dll rcpp_hello_world.cpp RcppExports.cpp --debug`, a call
to `gcc` is made. (I have added the output of the same call on my Linux system
to the Gist.) To me, it seems that the calling process is not notified when the
child process has completed, and it stops after a timeout. My hope is that this
has been seen before and that there's an easy fix. I'm really new to Wine.
--
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.
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=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=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.