http://bugs.winehq.org/show_bug.cgi?id=34446
Bug #: 34446
Summary: LANG=ru_RU.UTF-8 locale makes fonts look blurry
Product: Wine
Version: 1.7.1
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winex11.drv
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: t.artem(a)mailcity.com
Classification: Unclassified
Created attachment 45856
--> http://bugs.winehq.org/attachment.cgi?id=45856
en_US.UTF-8 screenshot
I will now attach two screenshots showing the same application running with
en_US.UTF-8 locale
and
ru_RU.UTF-8 locale
English looks fine, Russian looks blurry and very unpleasant.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=42305
Bug ID: 42305
Summary: Microsoft money 2000: the mouse click does not select
the good line
Product: Wine
Version: 2.0-rc6
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dobbyspam(a)gmail.com
Distribution: ---
When entering an expense / recessed, in the drop down menu to the insertion of
the categories, at the click of the mouse select the right item, but when you
release the mouse button, the selected item is the second bottom.
--
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=23493
Summary: Safari, when installed with quiet mode, refuses to run
Product: Wine
Version: 1.2-rc6
Platform: x86
URL: http://www.apple.com/safari
OS/Version: Linux
Status: NEW
Keywords: download, Installer
Severity: minor
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: austinenglish(a)gmail.com
Installing safari normally works fine.
Installing it with silent mode (wine SafariSetup.exe /qn) reports success for
the installer, but trying to run it fails with a messagebox:
Safari can't open.
Your copy of Safari is missing important software resources. Please reinstall
Safari.
OK
terminal shows:
fixme:actctx:parse_depend_manifests Could not find dependent assembly
L"Microsoft.VC80.CRT" (8.0.50727.4053)
fixme:msvcrt:_controlfp_s ((nil) 65536 196608) semi-stub
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
--
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=33760
Bug #: 33760
Summary: Jagged edges on most text and art in the Touhou 14
demo
Product: Wine
Version: unspecified
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: murela_alba(a)abv.bg
Classification: Unclassified
Created attachment 44705
--> http://bugs.winehq.org/attachment.cgi?id=44705
windows 7 main menu 960x720
When running the "Touhou 14 ~ Double Dealing Character" demo (ver 0.01a) on any
resolution other than the highest (1280x960), pretty much all text displays
varying degrees of aliasing. Same goes for the edges of all the 2D art and UI
elements from the loading screen, to the main menu, to the game proper. Here's
the title screen on windows 7 in 960x720 (windowed).
--
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.
https://bugs.winehq.org/show_bug.cgi?id=37010
Bug ID: 37010
Summary: DYMO Stamps "Unable to connect to postage transaction
server" with wine-mono
Product: Wine
Version: 1.7.23
Hardware: x86
URL: http://sites.dymo.com/Promotions/Pages/DYMOStamps.aspx
?locale=enUS
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: mscoree
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
Depends on: 31686
Follow up to bug 31687.
You'll need native gdiplus for bug 31686. Optionally, apply
https://source.winehq.org/patches/data/105843.
The app installs fine, and with native gdiplus, starts up. But when you try to
login, the application cannot connect to the server.
Terminal shows one mscoree fixme:
fixme:mscoree:ConfigFileHandler_startElement Unknown element L"configSections"
in state 2
With native dotnet20, it will attempt to connect, then fails with 'This account
is not active'. Trying to login via the website shows the same problem, so
that's okay. But wine-mono should fail the same way.
I'm using an archived installer:
austin@aw25 ~/oldbugs/31687 $ sha1sum DYMOstampsWebSetup.exe
6f96fbdc9806effa499edba7e89329534b5901a7 DYMOstampsWebSetup.exe
austin@aw25 ~/oldbugs/31687 $ du -h DYMOstampsWebSetup.exe
3.5M DYMOstampsWebSetup.exe
the current version of the program appears to have other .Net/Mono issues
--
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=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.
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.
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.
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.
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.
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.
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.
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.
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.
https://bugs.winehq.org/show_bug.cgi?id=39414
Bug ID: 39414
Summary: Add a partway job status
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: ---
If a task is completed the corresponding job's status is 'Running' even if none
or the remaining tasks is actually Running. So one can sometimes end up with
dozens of 'Running' jobs when only one or two among them actually has an active
task.
So the idea would be to reserve the 'Running' status to jobs for which one task
is actually running. Jobs where some tasks but not all have completed would
instead have the 'Partway' status (suggestions for another name welcome).
Another issue is that when multiple jobs are in the 'Running' or 'Partway'
state it's hard to know which ones have been modified the most recently because
the 'Ended' field is not set. This is probably less important though and a
waterfall like presentation would help (see bug 39413).
--
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=41600
Bug ID: 41600
Summary: Unable to view pre-moderated post in forum
Product: WineHQ.org
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: www-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: brewmanz(a)gmail.com
Distribution: ---
I've just posted a comment in a forum thread, and wish to alter/add another
comment ... but I can't find my post in 'view your posts'!
--
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=40240
Bug ID: 40240
Summary: ntdll:exception causes the Windows 10 VM to crash
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 ntdll:exception test causes the Windows 10 VM (w1064) to crash. Given that
this does not happen on real hardware it is a TestBot bug.
Incidentally this is why we don't get any WineTest result from that VM.
Either there is a way to avoid the crash by adjusting the QEMU configuration or
a QEMU bug should be filed.
--
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=39413
Bug ID: 39413
Summary: Make it easier to monitor the TestBot activity
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: ---
At the bottom of the main page there is a list of the VMs and their status.
However the information there is incomplete:
* When a VM is reverting there is no way to know for how long it has been
reverting.
* When a VM is running a task there is no link to the corresponding task.
* There is no history of events so if someone reports that something strange
happened there is no way to check(*).
So it would be nice to have something like BuildBot's Waterfall display.
http://buildbot.buildbot.net/waterfall
(*) Actually one could check the WineTestBot log but that has its own problems
and requires poring over lots of traces. See bug 39410.
--
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=42070
Bug ID: 42070
Summary: Add "workaround" to defined keywords list to indicate
that one or more workarounds are available for a bug.
Product: WineHQ Bugzilla
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: bugzilla-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: o.dierick(a)piezo-forte.be
Distribution: ---
Enhancement:
Add "workaround" to the defined keyword list for open bugs, when one ore more
working workarounds have been found.
For Moderators:
The conditions for the workaround keyword to be valid would be:
- The workaround is documented in the comments or a reference is made to the
AppDB entry where the workaround is documented (or to an external source).
- The workaround is confirmed to be working at least for one person (not just
an hypothetic workaround).
- If multiple workarounds are discussed, the keyword is valid if one workaround
meets the above conditions.
Why the keyword?:
Other users affected by a bug would know that a workaround exists without
having to read all the comments to find out.
If someone has documented a workaround in the AppDB for a specific application,
and the bug is in fact affecting multiple applications, the keyword would
reduce the need to document the workaround in the AppDB for every affected app,
provided that the bug is properly referenced in the multiple AppDB entries.
--
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=32354
Bug #: 32354
Summary: testbot: A crashing test is not detected
Product: Wine-Testbot
Version: unspecified
Platform: x86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: wine.dev(a)web.de
Classification: Unclassified
A 64bit test crashed on all 64bit testbot machines,
but the summary has "0" as "Number of failures".
Test run for the broken patch:
http://testbot.winehq.org/JobDetails.pl?Key=22963&log_301=1#k301
Later test:
http://testbot.winehq.org/JobDetails.pl?Key=23106&log_302=1#k302
(I send a fix for the broken code in wine in some minutes)
--
By by ... Detlef
--
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.
https://bugs.winehq.org/show_bug.cgi?id=40237
Bug ID: 40237
Summary: account not deletable
Product: WineHQ Bugzilla
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: bugzilla-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: BerlinerPaul(a)web.de
Distribution: ---
hi,
I want to delete my account but I'm unable to find some link in the preferences
for this.
best
--
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=39441
Bug ID: 39441
Summary: The reverts keep getting slower
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: ---
A revert that would take under 10 seconds right after creating the snapshot
would take over 7 minutes 6 months later. So every few months this would cause
the TestBot to become really sluggish and barely able to keep up with the patch
influx. Restarting libvirt, rebooting the host, restoring the VM from backup or
even transferring it to another host had no effect on the revert time.
While the revert is taking place the QEmu process fully occupies one core, no
disk I/O is performed and the VM is not running. The exact reason is not yet
known exactly but it seems to have to do with the VM's timer devices,
particularly the rtc one.
To confuse matters further not all VMs are affected: only Windows 2000, XP,
2003, 2008 and 10 suffer from this. The other post Windows Vista are immune.
Yet the guest is not active while the revert is taking place so it should not
have an impact on it.
Finally at WineConf 2015 it was discovered that the revert time of a live
snapshot is simply proportional to the snapshot's age.
This yielded a first workaround which is to refresh the live snapshots
regularly.
Further investigation showed that the common point between the impacted live
snapshots is that they all have the following clock settings
<clock offset='localtime'>
<timer name='rtc' tickpolicy='delay'/>
<timer name='pit' tickpolicy='delay'/>
<timer name='hpet' present='no'/>
</clock>
while the unaffected VMs have
<clock offset='localtime'/>
But switching from the former to the latter does not fix the affected VMs.
Still this lead to a better fix which has now been put in place: setting
track='guest' on the rtc timer.
Regardless, something is wrong with the way QEmu handles timers and live
snapshots so a bug was reported:
https://bugs.launchpad.net/qemu/+bug/1505041
Maybe this will shed some light on what's really happening and what the correct
timer settings are.
--
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=37104
Bug ID: 37104
Summary: Infinite revert loop
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
The current task scheduling algorithm can enter into an infinite revert loop
while trying to prepare VMs for the next tasks. Assume the following settings:
$MaxRevertingVMs = 2;
$MaxRevertsWhileRunningVMs = 0;
$MaxActiveVMs = 2;
Then the following sequence can play out:
| Steps
VM | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8
----+-----+-----+-----+-----+-----+-----+-----+-----
vm1 | rev | idl | off | off | rev | rev | rev | ...
vm2 | rev | rev | rev | idl | off | off | rev | ...
vm3 | off | off | rev | rev | rev | idl | off | ...
The issue happens in steps 2, 4 and 6.
The scheduler can shut down idle VMs to replace them with VMs that are more
appropriate for the upcoming tasks. This is what happens in these steps: it
decides the idle VM it just prepared is not what it wants after all, and thus
shuts it down and prepares another one.
The problem is it keeps changing its mind over and over and can never actually
start a task because there is always a reverting VM and
$MaxRevertsWhileRunningVMs = 0.
Another prerequisite for this scenario to play out is probably to have multiple
tasks have the exact same priority, so that their order is undefined. But
regardless, the scheduler should probably not be shutting down an idle VM that
has an actual 'pending' task.
--
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=39470
Bug ID: 39470
Summary: https://bugs.winehq.org/page.cgi?id=fields.html needs
to be updated to include new statuses
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: dimesio(a)earthlink.net
Distribution: ---
NEEDINFO and STAGED need to be added and UPSTREAM needs to be changed to
NOTOURBUG.
--
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.