https://bugs.winehq.org/show_bug.cgi?id=51042
Bug ID: 51042
Summary: installing eSignal errors out with "Program Error"
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mathieu.fregeau(a)gmail.com
Distribution: ---
using the installer downloaded form the website
(https://www.esignal.com/support/download), I attempt to install using the wine
command line:
wine eSignal_x64.exe
it installs a dotnet, then passes through the username account validation, but
subsequently Wine creates this error:
Unhandled exception: unimplemented function
concrt140.dll.??0_TaskCollection@details@Concurrency@@QAE@XZ called in 32-bit
code (0x7b032f82).
Register dump:
CS:0023 SS:002b DS:002b ES:002b FS:006b GS:0063
EIP:7b032f82 ESP:0032fd44 EBP:0032fdc8 EFLAGS:00000216( - -- I -A-P- )
EAX:0032fd5c EBX:80000100 ECX:0032fd40 EDX:0032fd70
ESI:00000000 EDI:0091afc8
Stack dump:
0x0032fd44: 0032fdf4 00000008 00000002 01540000
0x0032fd54: 0032fd78 0032fd78 80000100 00000001
0x0032fd64: 00000000 7b032f82 00000002 7d98a00e
0x0032fd74: 7d98a216 0032fdc8 7bc739c6 01530060
0x0032fd84: 00000020 00000000 00000002 01530014
0x0032fd94: 00000020 00000000 00000002 01200000
Backtrace:
=>0 0x7b032f82 (0x0032fdc8)
1 0x7d98903f EntryPoint+0xffffffff() in concrt140 (0x0032fe08)
2 0x7d988270 EntryPoint+0xffffffff() in concrt140 (0x0032fe54)
3 0x004a35ff EntryPoint+0xffffffff() in optionsanalytix (0x0032fec4)
4 0x004012ea EntryPoint+0xffffffff() in optionsanalytix (0x0032fee8)
5 0x007c3027 EntryPoint+0xffffffff() in optionsanalytix (0x0032ff30)
6 0x7b454882 in kernel32 (+0x34881) (0x0032ff48)
7 0x7b454cfc in kernel32 (+0x34cfb) (0x0032ffd8)
8 0x7b45488e in kernel32 (+0x3488d) (0x0032ffec)
0x7b032f82: addl $12,%esp
Modules:
Module Address Debug info Name (58 modules)
PE 400000- c49000 Export optionsanalytix
PE c50000- 10e6000 Deferred mfc140
PE 10000000-10080000 Deferred dbcapi_vc8
PE 7a840000-7a844000 Deferred opengl32
PE 7b020000-7b023000 Deferred kernelbase
PE 7b420000-7b5db000 Export kernel32
PE 7bc30000-7bc34000 Deferred ntdll
PE 7caa0000-7caaf000 Deferred setupapi
PE 7cd00000-7cd04000 Deferred winex11
PE 7d630000-7d633000 Deferred api-ms-win-crt-locale-l1-1-0
PE 7d650000-7d694000 Deferred crypt32
PE 7d780000-7d783000 Deferred msvcp120
PE 7d8a0000-7d8a3000 Deferred msvcr120
PE 7d980000-7d9bd000 Export concrt140
PE 7d9f0000-7da61000 Deferred msvcp140
PE 7daf0000-7daf4000 Deferred gdiplus
PE 7db90000-7dba2000 Deferred urlmon
PE 7dc30000-7dc3b000 Deferred winspool
PE 7dc80000-7dc83000 Deferred usp10
PE 7dcf0000-7dd6e000 Deferred comctl32
PE 7de70000-7df52000 Deferred comdlg32
PE 7dfa0000-7dfa3000 Deferred msimg32
PE 7dfc0000-7dfc4000 Deferred uxtheme
PE 7e000000-7e004000 Deferred imm32
PE 7e050000-7e058000 Deferred oleaut32
PE 7e160000-7e163000 Deferred api-ms-win-crt-filesystem-l1-1-0
PE 7e170000-7e173000 Deferred api-ms-win-crt-time-l1-1-0
PE 7e190000-7e195000 Deferred api-ms-win-crt-math-l1-1-0
PE 7e1a0000-7e1a4000 Deferred api-ms-win-crt-convert-l1-1-0
PE 7e1c0000-7e1c3000 Deferred api-ms-win-crt-heap-l1-1-0
PE 7e1d0000-7e1d3000 Deferred api-ms-win-crt-utility-l1-1-0
PE 7e1e0000-7e1e4000 Deferred api-ms-win-crt-stdio-l1-1-0
PE 7e200000-7e205000 Deferred api-ms-win-crt-multibyte-l1-1-0
PE 7e210000-7e214000 Deferred api-ms-win-crt-string-l1-1-0
PE 7e230000-7e234000 Deferred api-ms-win-crt-runtime-l1-1-0
PE 7e270000-7e274000 Deferred ucrtbase
PE 7e360000-7e374000 Deferred vcruntime140
PE 7e380000-7e384000 Deferred bcrypt
PE 7e3a0000-7e3a3000 Deferred glu32
PE 7e3e0000-7e3e9000 Deferred msacm32
PE 7e410000-7e48d000 Deferred winmm
PE 7e4f0000-7e58b000 Deferred msvcr80
PE 7e600000-7e687000 Deferred msvcp80
PE 7e740000-7e744000 Deferred rpcrt4
PE 7e7f0000-7e818000 Deferred ole32
PE 7e930000-7e933000 Deferred shcore
PE 7e980000-7f256000 Deferred shell32
PE 7f380000-7f388000 Deferred shlwapi
PE 7f3f0000-7f3f7000 Deferred gdi32
PE 7f560000-7f648000 Deferred user32
PE 7f780000-7f78b000 Deferred mpr
PE 7f7d0000-7f7d4000 Deferred version
PE 7f7f0000-7f80f000 Deferred wininet
PE 7f890000-7f894000 Deferred ws2_32
PE 7f8c0000-7f8c4000 Deferred iphlpapi
PE 7f910000-7f914000 Deferred msvcrt
PE 7f9e0000-7f9e4000 Deferred advapi32
PE 7fa50000-7fa53000 Deferred wtsapi32
Threads:
process tid prio (all id:s are in hex)
0000000e services.exe
00000023 0
0000001a 0
00000013 0
00000010 0
0000000f 0
00000011 plugplay.exe
00000017 0
00000016 0
00000012 0
00000018 winedevice.exe
00000020 0
0000001d 0
0000001c 0
0000001b 0
00000019 0
0000001e explorer.exe
00000029 0
00000028 0
00000027 0
0000001f 0
00000021 winedevice.exe
00000026 0
00000025 0
00000024 0
00000022 0
0000002a eSignal_x64.exe
000001aa 0
0000019b 0
00000198 0
0000002b 0
00000197 msiexec.exe
0000019a 0
000001a6 msiexec.exe
000001a5 0
000001bd winemenubuilder.exe
000001c0 0
000001c7 (D) C:\Program Files (x86)\Common Files\Interactive Data\Options
Analytix\OptionsAnalytix.exe
000001cb 0
000001ca 0 <==
System information:
Wine build: wine-5.0 (Ubuntu 5.0-3ubuntu1)
Platform: i386 (WOW64)
Version: Windows XP
Host system: Linux
Host version: 5.4.0-72-generic
--
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=51013
Bug ID: 51013
Summary: Express Digibooks application crashes on launch
Product: Wine
Version: 6.6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: skokkineas(a)protonmail.com
Distribution: ---
You have to install .Net 4.8 for the app to install. After that the main window
of the app is shown with the graphcis stuck to the background and the app
crashes with a Fatal Error. The back trace fails to laod at all.
--
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=50970
Bug ID: 50970
Summary: virtual:try_map_free_area mmap() error Operation not
permitted - since wine 6.5
Product: Wine
Version: 6.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: walecha99(a)gmail.com
Distribution: ---
Created attachment 69803
--> https://bugs.winehq.org/attachment.cgi?id=69803
wine internal executables log
Since wine 6.5, my wine installation cannot start any program except for wine
executables (ie. winecfg or regedit). But even the those wine executables were
generating the same error log (about try_map_free_area). Non-wine executables
adds more error about import_dll. My guess is wine could not open the dll
because the first mmap-related error. The same program runs normally in wine
6.4.
Failed wine version: 6.5, 6.6 (with/without wine-staging)
OS: Slackware64 Current (15-alpha) Multilib
GCC: 10.2
Mingw-w64: 8.0.0
CPU: Intel Haswell
GPU: Intel + AMD
--
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=33660
Bug #: 33660
Summary: CS:GO - Call votes respond
Product: Wine
Version: 1.5.30
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: pepe(a)bloodkings.eu
Classification: Unclassified
Once a player can call vote, and only works the first choice (F1, 1).
--
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=31787
Bug #: 31787
Summary: Run the tests in Wine
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: fgouget(a)codeweavers.com
Classification: Unclassified
The Wine TestBot runs the conformance tests on Windows VMs before they are
committed to Wine. This greatly helped improve the quality of our conformance
tests.
The next step is making sure that the conformance tests work reliably in Wine
too, and that Wine patches don't break them. The hope is that this will help us
improve the state of the WineTest results:
http://test.winehq.org/data/
Doing so will be much more processor intensive than the current process:
* Currently only the conformance test patches are tested whereas we would need
to test almost every single patch (we could ignore some documentation patches
for instance).
* Currently we only have to generate a binary for the one conformance test
that's impacted. That's quick. Testing all Wine patches will require
recompiling Wine every time which takes more time, even with ccache.
* A Wine patch can have wide-ranging effects. For instance a patch to ntdll
could impact pretty much any conformance test. That means rerunning all of them
for every patch... unless we find reliable ways of pruning them (patches to
conformance tests would be an obvious optimization).
* Like for Windows we will need to test various configurations: different
locales; 32, 64 and 32+64 bit Wine builds; different sound backends; possibly
different Linux distributions; if possible FreeBSD and Solaris too (I'm leaving
Mac OS X for another bug). In some cases the same binaries can be used for
multiple tests (e.g. if only the locale changes) but in other cases not.
* Also for the current Wine TestBot an unreliable test only impacts people
modifying that test. But the above point means an unreliable test would impact
most Wine patches, leading to lots of patches being rejected. So this means
unreliable tests become a big issue and need to be handled in some way: fixed
or blacklisted or still run but not considered cause for rejection (so one can
notice when they get fixed).
Then there is the question of whether this should be done by modifying the Wine
TestBot or by using the BuildBot framework:
http://trac.buildbot.net/wiki/AboutBuildbot
Dan Kegel produced a proof of concept system based on BuildBot:
http://wiki.winehq.org/BuildBot
An issue is that without significant integration work, having both a
WineTestBot and BuildBot system would be annoying:
* The Wine TestBot currently has its own user database and BuildBot would add
another one. So it would be one more login to manage for developers unless we
manage to integrate either with another user database (e.g. through LDAP).
* Developers would have to submit patches to both sites and check the results
on both.
* Integration with the Wine Patches site (http://source.winehq.org/patches/)
would need to work with both systems.
--
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=33234
Bug #: 33234
Summary: Improve user management
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: fgouget(a)codeweavers.com
Classification: Unclassified
When an account request is sent to a WineTestBot administrator the URL he gfets
sent to is the UserDetails.pl one but it only has an 'Approve' button, not a
'Reject' one.
This makes it unclear how to reject spam requests for instance (bug 31798), but
this has now been documented. Still, rejecting an application actually requires
going to another page and deleting the provisional account. This should be
simpler: there should be a 'Reject' button right on the UserDetails page that
does that.
Furthermore, the status of the account, 'Pending approval' and 'Pending
activation', should be clearly indicated both on the UserDetails page and on
the UsersList page.
--
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=48093
Bug ID: 48093
Summary: On cw-rx460 the WoW WinePrefixes are (likely) broken
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: ---
On cw-rx460 the wineprefixes created for the wow32 and wow64 test runs are
flawed:
* It looks like they do not define the %windir% and %SystemRoot% environment
variables:
https://www.winehq.org/pipermail/wine-devel/2019-October/152271.html
* They may be responsible for a failure in crypt32:sip
https://www.winehq.org/pipermail/wine-devel/2019-November/154240.html
What's puzzling is that cw-rx460 runs the same wt-daily script (*) as cw-gtx560
and other machines which don't have the same set of failures (see also bug
48092).
cw-rx460 is not a TestBot VM so this does not impact the TestBot results. But
if the wineprefixes are indeed causing extra test failures this could lead
developers on a wild goose chase. So to avoid confusion I disabled the wow32
and wow64 WineTest runs on that machine until I have had time to investigate.
(*) https://github.com/fgouget/wt-daily
--
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=39442
Bug ID: 39442
Summary: Using Spice required to avoid failure in
mmdevapi:capture
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 Windows 7+ VMs all use an ich6 virtual soundcard (they don't support any of
ac97, es1370 or sb16 ones).
But they have failures in mmdevapi:capture such as:
capture.c:586: Returned latency: 5.8050 ms
capture.c:178: Test failed: Position 375 expected 0
capture.c:186: Wait'ed position 375 pad 0 flags 1, amount of frames locked: 448
capture.c:228: Test failed: Position 1719 expected 823
[...]
It turns out that the way the VM is configured for remote access impacts the
result of the tests:
* If configured for VNC then the tests fail as described, even if no client is
connected.
* If configured for Spice access then the tests succeed, even if no client is
connected. And if a client is connected the sound is carried over with pretty
good reliability.
So the way one accesses the VM changes the behavior in the guest. That seems
wrong and I reported it to QEmu:
https://bugs.launchpad.net/qemu/+bug/1499908
I have updated the w7pro64 configuration on 2015/09/25 and it now only has one
intermittent Master volume failure left in mmdevapi:capture. The change does
not seem to have negatively impacted the other tests.
So it seems the change can safely be propagated to the other Windows 7+ VMs.
There may be one issue though, which is that combining QXL with Spice causes
the Windows 10 VM to freeze very quickly. Hopefully that's specific to Windows
10.
--
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=39419
Bug ID: 39419
Summary: Fix the 'Failure running script in VM' errors
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: ---
There are two very common 'boterror' types:
Failure running script in VM: the "nc -q0 '10.42.42.133' '4242'"
command returned 1
and
Failure running script in VM: network read timed out
(Connect:AgentVersion.h:0/9)
Both seem to correspond to a network issue and both seem to almost exclusively
and systematically happen with the w864 and w1064 VMs when running either a 32
or 64 bit WineTest job (i.e. running the full suite).
--
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.