https://bugs.winehq.org/show_bug.cgi?id=47987
Bug ID: 47987
Summary: Output with WINEDEBUG=warn+all contains a class of
false positive 'file not found' messages.
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mail(a)marekpasnikowski.name
Distribution: ---
How to Reproduce: Run winecfg with a WINEDEBUG=warn+all flag. Witness pages of
the following kind of messages, which are mostly blatantly incorrect:
> wine winecfg
0009:warn:ntdll:FILE_CreateFile
L"\\??\\Z:\\usr\\bin\\..\\lib\\wine\\kernel32.dll" not found (c0000034)
I can run a complex game within this very prefix - it is healthy. I have been
witnessing this problem for years. And now it is actively hindering my efforts
to locate the reason for a game crash, because of its verbose nature.
--
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=48044
Bug ID: 48044
Summary: wine64 err:msiexec:custom_action_server Failed to
create custom action server pipe
Product: Wine
Version: 4.0.2
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: msi
Assignee: wine-bugs(a)winehq.org
Reporter: daire.byrne(a)gmail.com
Distribution: ---
I realise this has come up many time before (e.g. 45663, 45509, 45856), but I
am still seeing it on both 4.0 and 4.18-staging. I have verified that the
previous patch to address this (circa wine-3.15) has been applied in both
versions:
https://source.winehq.org/git/wine.git/blobdiff/6552ddaaa5c189db504e81a2360…
It could be that I'm doing something wrong (I'm not a wine expert). I only have
the 64bit wine installed (as is the norm for centos/fedora), so have not tried
with a 32bit wine prefix.
Steps to reproduce:
rm -rf ~/.wine
wineboot
winetricks python27
Executing wine msiexec /i python-2.7.16.msi ALLUSERS=1
0030:fixme:ntdll:NtLockFile I/O completion on lock not implemented yet
0038:err:msiexec:custom_action_server Failed to create custom action server
pipe: 2
I have also seen it with a few other random installers too.
--
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=44562
Bug ID: 44562
Summary: NET 4.x Error messages when running any application
Product: Wine
Version: 3.1
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: linards.liepins(a)gmail.com
Distribution: ---
After I run any application (both from shortcut or from terminal), I am getting
error message, that is opening the following Microsoft's help page:
https://support.microsoft.com/en-us/help/2715633/shim-errors-for-the-net-fr…
System details:
[linards@kompiic Lejupielādes]$ sh winetricks list-installed
------------------------------------------------------
You are using a 64-bit WINEPREFIX. Note that many verbs only install 32-bit
versions of packages. If you encounter problems, please retest in a clean
32-bit WINEPREFIX before reporting a bug.
------------------------------------------------------
Using winetricks 20180217-next - sha256sum:
6dd23a6c59febc56a2c5a31aabc0c1b92545ec176c64b494aa088c5d993bf588 with wine-3.1
and WINEARCH=win64
binkw32
d3dx9_42
dotnet40
dotnet452
dotnet_verifier
gmdls
l3codecx
lucida
mfc40
mfc42
physx
steam
tahoma
vcrun2008
vcrun2012
vcrun2015
[linards@kompiic Lejupielādes]$ sudo dnf info wine
Last metadata expiration check: 0:00:08 ago on Tue 20 Feb 2018 08:57:09 AM EET.
Installed Packages
Name : wine
Version : 3.1
Release : 2.fc27
Arch : x86_64
Size : 0.0
Source : wine-3.1-2.fc27.src.rpm
Repo : @System
>From repo : updates-testing
Summary : A compatibility layer for windows applications
URL : http://www.winehq.org/
License : LGPLv2+
Description : Wine as a compatibility layer for UNIX to run Windows
applications. This
: package includes a program loader, which allows unmodified
Windows
: 3.x/9x/NT binaries to run on x86 and x86_64 Unixes. Wine can use
native system
: .dll files if they are available.
:
: In Fedora wine is a meta-package which will install everything
needed for wine
: to work smoothly. Smaller setups can be achieved by installing
some of the
: wine-* sub packages.
--
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=43718
Bug ID: 43718
Summary: erreur grave trouvée dans Big Fish Games ne peut pas
télécharger et installer les jeux
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: eribelge(a)hotmail.fr
Distribution: ---
/home/eric81/Documents/submission_2017-09-07T21:51:34.901897.xlsx
--
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=48193
Bug ID: 48193
Summary: vsoVideoConverter.exe (ConvetXtoVideo VSO Software)
fails on launch classes not registered
Product: Wine
Version: 4.20
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: patobrien1(a)yahoo.com
Distribution: ---
Created attachment 65828
--> https://bugs.winehq.org/attachment.cgi?id=65828
vsoVideoConverter launch output
Ubuntu 19.10 (current) Wine latest development version 4.20. Program from VSO
software Convet X to Video fatal error on launch. First errors are
0009:err:ole:CoGetClassObject class {50ef4544-ac9f-4a8e-b21b-8a26180db13f} not
registered
0009:err:ole:CoGetClassObject no class object
{50ef4544-ac9f-4a8e-b21b-8a26180db13f} could be created for context 0x1
0009:err:ole:CoGetClassObject class {1ebdcf80-a200-11d0-a3a4-00c04fd706ec} not
registered
0009:err:ole:CoGetClassObject no class object
{1ebdcf80-a200-11d0-a3a4-00c04fd706ec} could be created for context 0x1
Attached details.
--
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=48219
Bug ID: 48219
Summary: driver configuration handled oddly
Product: Wine
Version: 4.20
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winmm&mci
Assignee: wine-bugs(a)winehq.org
Reporter: galtgendo(a)o2.pl
Distribution: ---
First of all, parts of
https://wiki.winehq.org/Wine_Developer%27s_Guide/Wine_and_Multimedia seem to be
misleading or wrong (likely because it's somewhat out of date).
Anyway, while I've got 'HKLM\Software\Microsoft\Windows
NT\CurrentVersion\MCI32' entries, wine seems to be ignoring them and needs
system.ini entries.
Also, despite the page saying both [mci] and [mci32] are valid, only the former
works.
--
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=47949
Bug ID: 47949
Summary: .NET 4.x and later do not run on MacOS with 64 bit
prefix
Product: Wine
Version: 4.17
Hardware: x86-64
OS: Mac OS X
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: pembertona(a)gmail.com
No matter the release version, I have not seen a .NET 4.x implementation
running on Mac OS in a win64 prefix.
After many attempts, all paths of installing, upgrading, repairing, etc. end
with:
Application: 64-console4.exe\nFramework Version: v4.0.30319\nDescription: The
process was terminated due to an internal error in the .NET Runtime at IP
000006447F1D6F19 (000006447F100000) with exit code 80131506.\n"
That memory address is the clr.dll itself.
Is anyone aware of any users ever getting MacOS + win64 + .NET 4.x or later
working with wine?
--
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=48216
Bug ID: 48216
Summary: Add a WineTest size, time and test failures comparison
page to the TestBot
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: ---
This would expend on the data collected for bug 48215.
This would be a new page that lets the user pick two (or three or more)
WineTest results and put them in the same size, run time and test unit failure
tables as the JobDetails page would if they were all from the same job.
For each column the user would pick a CommitId and then get a list of the
available task reports (for instance "wxppro (32 bit)", "debian10 (32 bit
Chinese:China)").
This would allow comparing a VM's 32 and 64 bit results (these run in separate
jobs). Or compare a VM's latest result against its past result(s). Or compare
the results of running the tests on Windows 8 with those of Windows 10 on the
same hardware. Or comparing a WineTest run that timed out with one that did
not.
In effect this would be similar to bug 15477 but implemented in the TestBot
rather than the on test.winehq.org, the advantage being that the TestBot has
the infrastructure needed to dynamically build pages.
One approach to implement this would be to pour all the report summary
information into a big table. Something like (JobId, StepNo, TaskNo, CommitId,
TestUnit, Failures, Size, RunTime). However given the performance issues with
our current Perl ORM the performance may well be unacceptably slow (see bug
45023).
Another approach would be to use the task-level summary files (described in bug
48215) and use a much smaller table to map commit ids to the tasks with
relevant results. So this table would just contain (JobId, StepNo, TaskNo,
CommitId) and would be used to know which tasks have results for a given commit
id, and once the tasks have been selected, where to find the summary file
containing the data to put in the tables.
--
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=48215
Bug ID: 48215
Summary: Add size, time and test unit failures tabs to the
JobDetails page
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 JobDetails page only provides access to each task's reports and
logs. This can make it hard to figure out which test units have failures (bug
47904) and harder still to compare the test unit failures across the tasks.
This is ok when testing regular patches since each task typically only runs a
single test unit (except for Wine tasks). But for WineTest tasks it would be
useful to be able to compare which test units failed for each task. The current
workaround is to use test.winehq.org for that, but there too comparing results
as its limitations (see bug 15477), and sometimes the reports a rejected which
is when it would be nice to be able to dig into them.
Similarly it would be quite nice to be able to have a table showing the run
time an report size across test unit and tasks.
One way to present this would be to have a list of tabs at the top of the
JobDetails page:
Reports | Unit Failures | Size | Run time
The Reports tab would show the usual task reports while the other tabs would
show tables with one column per task, one line per test unit and the specified
information in the cells. Ideally clicking on a column header would sort the
table on that column.
This is reasonably easy to do at the JobDetails level: when parsing the reports
we can extract all the required information. All that would be required is to
save it to a summary file (one line per test unit with the count of failures,
size, run time). That would make it easy and quick for JobDetails to retrieve
the information and then it's a matter of getting the HTML side in place.
--
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=47344
Bug ID: 47344
Summary: Amazon WorkSpaces
Product: Wine
Version: 4.10
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: stephen.feyrer(a)greensill.com
Distribution: ---
Created attachment 64675
--> https://bugs.winehq.org/attachment.cgi?id=64675
export WINEDEBUG=+clipboard
Tested on Ubuntu 18.04 LTS, wine-3.0 (Ubuntu 3.0-1ubuntu1).
I am not able to copy from something like Firefox in X and paste in to wine
running Amazon Workspaces client application, neither can I copy from wine
running Amazon Workspaces client application and paste back into X.
Additionally, I have found that I am unable to copy and paste from wine notepad
into the Amazon Workspaces client application or visa versa.
The attached log file was generated after numerous copy and paste attempts were
applied in all directions with as per the following:
cd "${WINEPREFIX:-${HOME}/.wine}/drive_c/Program Files (x86)/Amazon Web
Services, Inc/Amazon WorkSpaces"
export WINEDEBUG=+clipboard
wine workspaces.exe &> ~/wine-4.10_clipboard_log.txt
--
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.