November 2017 - Wine-Bugs - list.winehq.org

[Bug 31687] New: DYMO Stamps can't connect to its server
by wine-bugs＠winehq.org Nov. 4, 2018

Nov. 4, 2018

http://bugs.winehq.org/show_bug.cgi?id=31687 Bug #: 31687 Summary: DYMO Stamps can't connect to its server Product: Wine Version: 1.5.12 Platform: x86 URL: http://sites.dymo.com/Promotions/Pages/DYMOStamps.aspx ?locale=enUS OS/Version: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com Depends on: 31685, 31686 Classification: Unclassified Created attachment 41656 --> http://bugs.winehq.org/attachment.cgi?id=41656 WINEDEBUG=crypt,chain,context,secur32 Install the app. You'll need native gdiplus for bug 31686. After that, you can get native hid, for bug 31685. I also installed dotnet20, to verify that it wasn't a mscoree fixme to blame, but the problem happens either way. Start it up, and it asks for your credentials. Put them in, and click next. That gives an error: The remote certificate is invalid according to the validation procedure. terminal output doesn't show much relevant. Tried native wininet/winhttp, which then in turns shows a few fixme's for crypt32/secur32/winsock. If you add in native crypt32, you get: Attempted to read or write protected memory. This is often an indication that other memory is corrupt. and with native secur32 as well: The requested security package is not supported. Not sure what to try next. The initial problem seems to indicate crypt32 or secur32, so hopefully this log will help: WINEDEBUG=crypt,chain,context,secur32 -- 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.

1 9

[Bug 39350] New: Alone in the Dark: The New Nightmare (GOG.com) hangs on start when WRITECOPY enabled
by wine-bugs＠winehq.org Nov. 4, 2018

Nov. 4, 2018

https://bugs.winehq.org/show_bug.cgi?id=39350 Bug ID: 39350 Summary: Alone in the Dark: The New Nightmare (GOG.com) hangs on start when WRITECOPY enabled Product: Wine-staging Version: unspecified Hardware: x86 URL: http://www.gog.com/game/alone_in_the_dark_the_new_nigh tmare OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com CC: michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- I have this problem with the GOG.com version of the game, but can't reproduce it with the original demo version. After starting the game with alone4.exe, it switches screen resolution then hangs with an empty black screen and 100% CPU usage. Plain terminal output doesn't show anything. The game starts properly when STAGING_WRITECOPY variable is unset. wine-1.7.51-225-g3966aff Fedora 22 32-bit -- 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.

1 6

[Bug 43234] New: Allow users to show all full logs
by wine-bugs＠winehq.org Nov. 4, 2018

Nov. 4, 2018

https://bugs.winehq.org/show_bug.cgi?id=43234 Bug ID: 43234 Summary: Allow users to show all full logs Product: Wine-Testbot Version: unspecified Hardware: Other OS: other Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: z.figura12(a)gmail.com Currently it's possible to expand one log at a time to show not only the failing lines but also the trace() output. It would be nice if we had a way to see them all at once, though. Of course the user does get the full results e-mailed to them, but the e-mail can take a while to go through, and also it might be good if other people can get the full logs of a test they didn't run (e.g. because it was linked to by the user.) -- 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.

1 3

[Bug 41723] New: Install ucrtbase.dll on at least one of the machines
by wine-bugs＠winehq.org Nov. 4, 2018

Nov. 4, 2018

https://bugs.winehq.org/show_bug.cgi?id=41723 Bug ID: 41723 Summary: Install ucrtbase.dll on at least one of the machines Product: Wine-Testbot Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: piotr.caban(a)gmail.com Distribution: --- We have tests for ucrtbase.dll in wine but currently they are never run on testbot. It would be nice to install the dll on at least one of the machines. -- 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.

1 3

[Bug 39487] New: Make step dependencies more flexible
by wine-bugs＠winehq.org Nov. 4, 2018

Nov. 4, 2018

https://bugs.winehq.org/show_bug.cgi?id=39487 Bug ID: 39487 Summary: Make step dependencies more flexible 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: --- The TestBot jobs are split into steps and tasks. * The steps are numbered and must be executed in order. Each step has an associated file. * Each step has one or more tasks which can all be run in parallel. Typically the first step is the build step associated to the patch. It produces the 32 and 64 bit executables for the following steps hence why it has to be executed first. When it fails the other steps are skipped which is not the case for the other steps. So the general structure is: Step 1 - patch.diff - Build Step 2 - test_32.exe - One task per VM Step 3 - test_64.exe - One task per VM So one source of inefficiency is that the 64 bit tests cannot start until all the 32 bit tests have completed. It does not necessarily make the overall job execution longer but it can leave a VM host idle while it waits for the remaining 32 bit tests to complete. And if a developer is watching the job's page he will not know of 64 bit failures until then. So while the build step has to come before all others, that condition should be relaxed for the other steps. The database schema presented in bug 39412 adds a DependencyNo field to the Step table so that step dependencies can be made explicit. This would allow making both test steps depend on build one. Note that with this scheme a given step could not directly depend on multiple other steps but that does not seem needed. It would also make more explicit the fact that test steps cannot be run if the build one fails instead of hard-coding that behavior in Jobs::UpdateStatus(). -- 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.

1 2

[Bug 39425] New: Improve resilience to VM host outages
by wine-bugs＠winehq.org Nov. 4, 2018

Nov. 4, 2018

https://bugs.winehq.org/show_bug.cgi?id=39425 Bug ID: 39425 Summary: Improve resilience to VM host outages 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: --- Currently the WineTestBot gets stuck when the connection to the libvirt server on the VM hosts is broken. This includes cases where the libvirt server is restarted, the VM hosts is rebooted or cases where there's a network outage. The reason is that the Engine queries the status of the VMs itself in some circumstances. This creates a TCP connection which is never recreated in case it breaks. The proper fix is to banish all such queries from the Engine: not just to fix this issue but also because some of these operation can be long (a few seconds) and block the main loop of the single-threaded Engine, which can in turn cause the website to lag. -- 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.

1 2

[Bug 42179] New: Better detect which tests need to be rerun
by wine-bugs＠winehq.org Nov. 4, 2018

Nov. 4, 2018

https://bugs.winehq.org/show_bug.cgi?id=42179 Bug ID: 42179 Summary: Better detect which tests need to be rerun 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: --- The TestBot sometimes does not always know which tests need to be rerun and thus tries to run the test executable with no argument. This typically happens in the following circumstances: * When a non-C file is patched, such as a resource or JavaScript file. * When a test file is removed. This case is actually similar to the previous case where the non-C file is the Makefile.in file. Note however that if there is only one test file this works anyway because in that case the test executable just runs that one test by default. I added some test cases for this in the TestBot test suite: https://github.com/fgouget/wine/tree/wtbsuite -- 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.

1 4

[Bug 41720] New: Advanced bug search excludes NEEDINFO bugs by default
by wine-bugs＠winehq.org Nov. 4, 2018

Nov. 4, 2018

https://bugs.winehq.org/show_bug.cgi?id=41720 Bug ID: 41720 Summary: Advanced bug search excludes NEEDINFO bugs by default Product: WineHQ Bugzilla Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: bugzilla-unknown Assignee: wine-bugs(a)winehq.org Reporter: ken(a)codeweavers.com Distribution: --- Go to <https://bugs.winehq.org/query.cgi?format=advanced>. In the Status list, all statuses except CLOSED and NEEDINFO are initially selected. NEEDINFO should also be selected. Only CLOSED should be excluded. I don't know if NEEDINFO bugs are included in the simple search's Status: Open pop-up menu item. See <https://bugs.winehq.org/query.cgi?format=specific>. They should be. -- 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.

1 2

[Bug 41216] New: Dependency Packages for EL7 compatible Systems
by wine-bugs＠winehq.org Nov. 4, 2018

Nov. 4, 2018

https://bugs.winehq.org/show_bug.cgi?id=41216 Bug ID: 41216 Summary: Dependency Packages for EL7 compatible Systems Product: Packaging Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-packages Assignee: wine-bugs(a)winehq.org Reporter: b.barwich(a)hotmail.com CC: michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- I am running a CentOS 7 system with an old wine version and I would like to update to the latest official stable Version, but this version is not packaged on any compatible EL7 repository. I checked out the instructions on https://wiki.winehq.org/Fedora but I found that the guide starts at Fedora 22 while CentOS 7 is mostly compatible with Fedora 19 and 20 and hardly with Fedora 21 because of Package Dependencies. I also checked out the recommended "RPM Fusion" Repository but I had to find out that it only offers packages for EL5 and EL6 systems. It is not updated yet to EL7 while effectively suffers from missing Packages that are not shipped by RHEL. So without the "RPM Fusion" Repository I checked out how many Package Dependencies I have available from the required ones in the manual. The Manual at https://wiki.winehq.org/Fedora requires 81 pendent Packages # echo "alsa-plugins-pulseaudio.i686 glibc-devel.i686 glibc-devel libgcc.i686 libX11-devel.i686 freetype-devel.i686 libXcursor-devel.i686 libXi-devel.i686 libNX_Xext-devel.i686 libXext-devel.i686 libXxf86vm-devel.i686 libXrandr-devel.i686 libXinerama-devel.i686 mesa-libGLU-devel.i686 mesa-libOSMesa-devel.i686 libXrender-devel.i686 libpcap-devel.i686 ncurses-devel.i686 libzip-devel.i686 lcms2-devel.i686 zlib-devel.i686 libv4l-devel.i686 libgphoto2-devel.i686 libcapifax-devel.i686 cups-devel.i686 libxml2-devel.i686 openldap-devel.i686 libxslt-devel.i686 gnutls-devel.i686 libpng-devel.i686 flac-libs.i686 json-c.i686 libICE.i686 libSM.i686 libXtst.i686 libasyncns.i686 libedit.i686 liberation-narrow-fonts.noarch libieee1284.i686 libogg.i686 libsndfile.i686 libuuid.i686 libva.i686 libvorbis.i686 libwayland-client.i686 libwayland-server.i686 llvm-libs.i686 mesa-dri-drivers.i686 mesa-filesystem.i686 mesa-libEGL.i686 mesa-libgbm.i686 nss-mdns.i686 ocl-icd.i686 pulseaudio-libs.i686 python-talloc.x86_64 sane-backends-libs.i686 tcp_wrappers-libs.i686 unixODBC.i686 samba-common-tools.x86_64 samba-libs.x86_64 samba-winbind.x86_64 samba-winbind-clients.x86_64 samba-winbind-modules.x86_64 mesa-libGL-devel.i686 fontconfig-devel.i686 libXcomposite-devel.i686 libtiff-devel.i686 openal-soft-devel.i686 mesa-libOpenCL-devel.i686 opencl-utils-devel.i686 alsa-lib-devel.i686 gsm-devel.i686 libjpeg-turbo-devel.i686 pulseaudio-libs-devel.i686 pulseaudio-libs-devel gtk3-devel.i686 libattr-devel.i686 libva-devel.i686 libexif-devel.i686 libexif.i686 glib2-devel.i686"|tr -s " " "\n"|wc -l 81 but on my system I have only 68 / 81 Packages available # yum info alsa-plugins-pulseaudio.i686 glibc-devel.i686 glibc-devel libgcc.i6 libX11-devel.i686 freetype-devel.i686 libXcursor-devel.i686 libXi-devel.i686 libNX_Xext-devel.i686 libXext-devel.i686 libXxf86vm-devel.i686 libXrandr-devel.i686 libXinerama-devel.i686 mesa-libGLU-devel.i686 mesa-libOSMesa-devel.i686 libXrender-devel.i686 libpcap-devel.i686 ncurses-devel.i686 libzip-devel.i686 lcms2-devel.i686 zlib-devel.i686 libv4l-devel.i686 libgphoto2-devel.i686 libcapifax-devel.i686 cups-devel.i686 libxml2-devel.i686 openldap-devel.i686 libxslt-devel.i686 gnutls-devel.i686 libpng-devel.i686 flac-libs.i686 json-c.i686 libICE.i686 libSM.i686 libXtst.i686 libasyncns.i686 libedit.i686 liberation-narrow-fonts.noarch libieee1284.i686 libogg.i686 libsndfile.i686 libuuid.i686 libva.i686 libvorbis.i686 libwayland-client.i686 libwayland-server.i686 llvm-libs.i686 mesa-dri-drivers.i686 mesa-filesystem.i686 mesa-libEGL.i686 mesa-libgbm.i686 nss-mdns.i686 ocl-icd.i686 pulseaudio-libs.i686 python-talloc.x86_64 sane-backends-libs.i686 tcp_wrappers-libs.i686 unixODBC.i686 samba-common-tools.x86_64 samba-libs.x86_64 samba-winbind.x86_64 samba-winbind-clients.x86_64 samba-winbind-modules.x86_64 mesa-libGL-devel.i686 fontconfig-devel.i686 libXcomposite-devel.i686 libtiff-devel.i686 openal-soft-devel.i686 mesa-libOpenCL-devel.i686 opencl-utils-devel.i686 alsa-lib-devel.i686 gsm-devel.i686 libjpeg-turbo-devel.i686 pulseaudio-libs-devel.i686 pulseaudio-libs-devel gtk3-devel.i686 libattr-devel.i686 libva-devel.i686 libexif-devel.i686 libexif.i686 glib2-devel.i686|grep -i nombre|sort|uniq|wc -l 68 from the "RPM Fusion" Repository there are 20 Packages required # echo "libmpg123-devel.i686 gstreamer-plugins-base-devel gstreamer-devel.i686 gstreamer.i686 gstreamer-plugins-base.i686 gstreamer-devel gstreamer1.i686 gstreamer1-devel gstreamer1-plugins-base-devel.i686 gstreamer-plugins-base.x86_64 gstreamer.x86_64 gstreamer1-devel.i686 gstreamer1-plugins-base-devel gstreamer-plugins-base-devel.i686 gstreamer-ffmpeg.i686 gstreamer1-plugins-bad-free-devel.i686 gstreamer1-plugins-bad-free-extras.i686 gstreamer1-plugins-good-extras.i686 gstreamer1-libav.i686 gstreamer1-plugins-bad-freeworld.i686"|tr -s " " "\n"|wc -l 20 but without this Repository I have only 8 / 20 Packages available: # yum info libmpg123-devel.i686 gstreamer-plugins-base-devel gstreamer-devel.i686 gstreamer.i686 gstreamer-plugins-base.i686 gstreamer-devel gstreamer1.i686 gstreamer1-devel gstreamer1-plugins-base-devel.i686 gstreamer-plugins-base.x86_64 gstreamer.x86_64 gstreamer1-devel.i686 gstreamer1-plugins-base-devel gstreamer-plugins-base-devel.i686 gstreamer-ffmpeg.i686 gstreamer1-plugins-bad-free-devel.i686 gstreamer1-plugins-bad-free-extras.i686 gstreamer1-plugins-good-extras.i686 gstreamer1-libav.i686 gstreamer1-plugins-bad-freeworld.i686|grep -iE "nombre[^\:]*:"|sort|uniq|wc -l 8 This is mostly due to RHEL7 not shipping most i686 Packages anymore. -- 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.

1 6

[Bug 39385] New: Make the VM descriptions visible
by wine-bugs＠winehq.org Nov. 4, 2018

Nov. 4, 2018

https://bugs.winehq.org/show_bug.cgi?id=39385 Bug ID: 39385 Summary: Make the VM descriptions visible 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: --- Each VM has a long description of its hardware and software configuration. They are meant to help developers figure out what's special about a specific VM and how it may explain its results. The long descriptions can be found on the test.winehq.org site by looking at individual reports information. But they cannot be seen on the testbot.winehq.org site except by the administrator when editing the VM configuration. They should be visible as a tooltip/infotip in most places when the VM's name is displayed. -- 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.

1 2