http://bugs.winehq.org/show_bug.cgi?id=31282
Bug #: 31282
Summary: Unable to Run Guild Wars 2; probably dbus issue
Product: Wine
Version: unspecified
Platform: x86
OS/Version: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: marius.olbertz(a)gmail.com
Classification: Unclassified
When I run Guildwars 2 , the following message is shown. I already tried to fix
the problem as discribed here http://trac.macports.org/ticket/20645. However,
Guildwars 2 does start normally.
noname:GW2 Manno$ wine Gw2.exe
Dynamic session lookup supported but failed: launchd did not provide a socket
path, verify that org.freedesktop.dbus-session.plist is loaded!
err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make
sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the
winbind package of your distribution.
But after logging in and confirmung the EULA, the client closes itself. I guess
it's supposed to start the game afterwards, but nothing happens at all.
fixme:heap:HeapSetInformation 0x1d66000 0 0x32fdd8 4
fixme:process:SetProcessDEPPolicy (1): stub
fixme:process:GetLogicalProcessorInformation (0x32f2d4,0x32f900): stub
fixme:process:GetLogicalProcessorInformation (0x0,0x3337e98c): stub
fixme:process:GetLogicalProcessorInformation (0x3337e9b4,0x3337e98c): stub
fixme:process:GetLogicalProcessorInformation (0x0,0x3337e994): stub
fixme:process:GetLogicalProcessorInformation (0x3337e9bc,0x3337e994): stub
fixme:process:GetLogicalProcessorInformation (0x0,0x3337e988): stub
fixme:process:GetLogicalProcessorInformation (0x3337e9b0,0x3337e988): stub
fixme:winsock:WS_getsockopt WS_SO_CONNECT_TIME - faking results
fixme:win:EnumDisplayDevicesW ((null),0,0x3337addc,0x00000000), stub!
fixme:imm:ImmDisableTextFrameService Stub
fixme:wtsapi:WTSRegisterSessionNotification Stub 0x20062 0x00000000
fixme:win:RegisterRawInputDevices (pRawInputDevices=0x3337b050, uiNumDevices=1,
cbSize=12) stub!
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:avrt:AvSetMmThreadCharacteristicsW (L"Audio",0x3563f638): stub
fixme:win:EnumDisplayDevicesW ((null),0,0x3337e77c,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x3337eabc,0x00000000), stub!
fixme:d3d:state_zfunc D3DCMP_NOTEQUAL and D3DCMP_EQUAL do not work correctly
yet.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:win:EnumDisplayDevicesW ((null),0,0x3337eecc,0x00000000), stub!
fixme:imm:ImmDisableTextFrameService Stub
fixme:wtsapi:WTSRegisterSessionNotification Stub 0x30064 0x00000000
fixme:win:RegisterRawInputDevices (pRawInputDevices=0x3337f13c, uiNumDevices=1,
cbSize=12) stub!
xp_destroy_surface: assertion failed: s != NULL
xp_destroy_surface error: 3
X Error of failed request: 0
Major opcode of failed request: 149 (GLX)
Minor opcode of failed request: 26 (X_GLXMakeContextCurrent)
Serial number of failed request: 11307
Current serial number in output stream: 11307
--
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=29569
Bug #: 29569
Summary: mingw make complains "cp: cannot stat
`d3dcompiler_43/libd3dcompiler.a': No such file or
directory"
Product: Wine
Version: 1.3.36
Platform: x86
OS/Version: Windows
Status: NEW
Severity: minor
Priority: P2
Component: build-env
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dank(a)kegel.com
Classification: Unclassified
Configuring wine on mingw per the wiki seems to go fine, but 'make' fails with
rm -f dlls/libd3dcompiler.a && cp -p d3dcompiler_43/libd3dcompiler.a
dlls/libd3d
compiler.a
cp: cannot stat `d3dcompiler_43/libd3dcompiler.a': No such file or directory
There are four problems of this sort in Makefile. Doing
sed -i 's,$(LN_S) ,$(LN_S)/dlls' Makefile
seems to rescue it, and let it get further.
That LN_S comes from function wine_fn_config_dll(), line 414 of aclocal.m4.
There's another one that looks like it needs fixing at line 422, too.
See http://wiki.winehq.org/WineOnWindows and/or
http://kegel.com/wine/wow.html for notes on how to reproduce.
(I had to do
cd dlls/libwine0; make; cd ../..
cd dlls/d3dcompiler_43; make; cd ../..
to get this far, but maybe that was operator error, not sure.)
--
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=24349
Summary: Blackberry Desktop Software (aka Device Manager):
Crashes on Run
Product: Wine
Version: 1.2
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: andrew.in.snow(a)gmail.com
Created an attachment (id=30691)
--> (http://bugs.winehq.org/attachment.cgi?id=30691)
Command line output and backtrace
Desktop Manager does not run.
Installation requires the Windows version to be set to "Windows XP" and no
other modifications are needed.
Application crashes during startup.
OS: Fedora 13
Please note that while I put x86_64 as my hardware, I installed the i686
version of wine from Fedora.
Please let me know what else I can provide.
--
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=30410
Bug #: 30410
Summary: Starcraft 2 crashes on login in Ubuntu 12.04
(regression from Ubuntu 11.10)
Product: Wine
Version: 1.5.1
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: danielreiterhorn(a)gmail.com
Classification: Unclassified
Created attachment 39753
--> http://bugs.winehq.org/attachment.cgi?id=39753
The output of wine
Description: Ubuntu precise (development branch)
Release: 12.04
Linux 3.2.0-22-generic #35-Ubuntu SMP Tue Apr 3 18:33:15 UTC 2012 x86_64 x86_64
x86_64 GNU/Linux
wine-1.5.1
In previous version of ubuntu, wine-1.4 works with StarCraft II and the same
version of wine (and all other versions of wine) fail with starcraft on nvidia
drivers. Dozens of versions of nvidia drivers and 3 versions of wine including
1.5.1 and top of tree 31f6f48bfd7a82d7229cdd7dff812272c27ae812 were also tested
with the same regression on Ubuntu 12.04 that all worked on Ubuntu 11.10
Other users are experiencing the bug and reporting it
http://www.codeweavers.com/support/tickets/browse/?ticket_id=883964;list=6;…http://ubuntuforums.org/archive/index.php/t-1939902.htmlhttp://ubuntuforums.org/showthread.php?t=1939902
It could be a kernel issue.
After successfully testing Starcraft on my Ubuntu 8.04 64-bit system, I
compared the logs. They're quite similar, except for this, in 12.04:
fixme:dbghelp:EnumerateLoadedModulesW64
--
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=36037
Bug ID: 36037
Summary: Crash in load/save menu in Temple of Elemental Evil on
i965
Product: Wine
Version: 1.7.17
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: mecirt(a)yahoo.com
Created attachment 48190
--> http://bugs.winehq.org/attachment.cgi?id=48190
backtrace
Wine crashes in the game "Temple of Elemental Evil" (GOG version with the
Circle of Eight modpack), when pressing the Esc key in the actual game to
display the load/save menu. Instead of showing the menu, the game crashes.
Of note is that this crash only happens when using Intel drivers (i965), but
not when using the nvidia driver through bumblebee (on an Optimus laptop).
Backtrace attached.
--
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=31686
Bug #: 31686
Summary: DYMO Stamps won't start without native gdiplus
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: minor
Priority: P2
Component: gdiplus
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: austinenglish(a)gmail.com
Classification: Unclassified
Shows a few:
fixme:gdiplus:GdipGetLineSpacing ignoring style
Then a flood of:
fixme:gdiplus:GdipDrawLine graphics object has no HDC
fixme:gdiplus:GdipDrawLine graphics object has no HDC
and never starts. Winetricks gdiplus works around it. Attaching a +gdiplus
trace.
--
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=27975
Summary: [INETCPL] Add missing security propsheet to Polish
translation
Product: Wine
Version: unspecified
Platform: x86
OS/Version: All
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: saibamenppl(a)gmail.com
From: http://svn.reactos.org/svn/reactos?view=rev&revision=53012
By Adam 'Saibamen' Stachowicz
--
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=37022
Bug ID: 37022
Summary: Application crashes occasionally
Product: Wine
Version: 1.6.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: bugzilla(a)rols.ch
Created attachment 49193
--> http://bugs.winehq.org/attachment.cgi?id=49193
Backtrace from crash
Application crashes occasionally, cannot find some similarities. Backtrace
shows crash in ntdll ... but backtraces all look the same.
--
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=38552
Bug ID: 38552
Summary: Red alert 2 Yuris revenge: won't run when winedbg-1.7
installed (Copy prot. error)
Product: Wine
Version: 1.7.38
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: owezahra(a)gmail.com
Distribution: ---
Created attachment 51426
--> https://bugs.winehq.org/attachment.cgi?id=51426
sha1sums if needed
Well, on 1.7.38 "RA2 Yuris Revenge" runs (didn't in 1.6.2), but lately i've
seen some glitches (Mission transitions, when you lose, when i took a
screenshot), nothing directly gameplay relevant tough.
But after i installed wine-1.7-dbg the game didn't even start anymore
(something like "please insert correct cd/dvd"), not even showing any wine
command line output to work with.
I've tried some no-cd's, but like my original cnc-tfd dvd i used before they
didn't work.
Is there any point in opening bugs if i can only provide wine cmd output
without anything wine-1.7-dbg may add?
(Also, i had to use the ddraw.dll&aqrit.cfg override (Bug33211) to get both
working (Basegame RA2.exe and RA2MD.exe. RA2MD.exe failed when i removed the
dll))
Thanks,
Thomas
--
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=31103
Bug #: 31103
Summary: Jade Dynasty - The Program Patcher.exe has encountered
a serious problem and needs to close.
Product: Wine
Version: 1.5.7
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: armen(a)winehq.leemail.me
Classification: Unclassified
Created attachment 40835
--> http://bugs.winehq.org/attachment.cgi?id=40835
This file contains the bug back trace.
I downloaded Jade Dynasty from http://jd.perfectworld.com/ unpacked and
installed it by clicking on the install.exe file from its folder
¨JD_EN_Installer_v352_20120402¨
I followed forum guides on how to install the program. Configured wine to
emulate virtual desktop and to use my Display full resolution. Game installed
completely without any errors with wine.
After installation was over, I closed the set up window. Then I clicked on the
game icon from the desktop. The game client didnt start and I got the error
report, which is attached.
Thanks for all who take the time to fix these bugs.
--
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=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.
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=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=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=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.
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=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.