https://bugs.winehq.org/show_bug.cgi?id=48035
Bug ID: 48035
Summary: Speed up the new failures detection
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: ---
When a task completes the TestBot distinguishes new failures from preexisting
ones by comparing the task's report to the latest WineTest report. Any failure
present in the task's report which is not present in the WineTest report is
new.
This means parsing both reports to extract the errors and diffing them. This
needs to be done whenever we need the list of new failures which is:
* When sending a notification to the developer when a wine-patches job
completes.
* On the JobDetails page.
But the WineTest reports are pretty big (~600KB on Windows, ~1.5MB on Wine)
which translates into non negligible processing time. For instance on my
development environment loading the JobDetails page for a job with 1 Windows
report and 8 Wine reports takes about 0.2 s without the reference WineTest
reports, but close to 2 s when they are present.
So it would help to only store the WineTest failures instead of the full report
(optimisation a in bug 47998). This would cut down not only on the amount of
data to read, but also on the required parsing. Testing this in the same
development environment indicates this could bring the JobDetails processing
time down to about 0.3 s.
--
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=47998
Bug ID: 47998
Summary: Better deal with random test failures
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: ---
Some tests fail randomly. They should be fixed of course but the in the
meantime the TestBot should try not to report them as new failures when they
happen.
To detect new errors the TestBot compares a task's test result with that of the
latest WineTest run. So if a failure did not happen during the last WineTest
run and then happens when testing a patch it will be reported as a new failure.
To avoid that the TestBot should take into account not just the latest WineTest
report, but all the available test reports. This way, if the random failure
happened in any of those runs it will be reported as pre-existing as expected.
How much of a history to take into account can then be adjusted by changing
$JobPurgeDays, or adding a specific setting.
Note that this means if a failure is fixed and is reintroduced soon after it
will not be reported as a new failure. This scenario should be rare enough to
not be an issue in practice.
To implement this:
1. Store the WineTest reports in the var/latest directory with the following
naming format:
<vmname>-job<jobid>_<stepno>_<taskno>-<report>
2. At the start of WineRunTask and WineRunWineTest delete any reference report
in the task's directory (in case the task is restarted), then make new hard
links to the current set of reference reports. Handle this in
LogUtils::GrabReferenceReports() so this code is shared.
3. Add LogUtils::AddReferenceReport() to deal with copying the WineTest reports
to var/latest. Call this function when WineRunTask and WineRunWineTest
complete.
4. In GetNewLogErrors() initially mark all errors as new. Then diff the current
report with each of the reference reports located in the task's directory in
turn and remove any error that's not new from the set of new errors.
Note that currently the reference logs are simple copies of the original
WineTest report. This means these are large files which must be parsed again to
extract errors. With the current $JobPurgeDays setting there will be around 20
reference logs which will require 20 times as much log parsing. So there are
two optimizations one can do, both happening when adding a new reference report
(i.e. in AddReferenceReport()):
a. Instead of copying the full report, save only the errors. That's all the
diff needs and this should reduce the size of the files by a factor of 10 (and
thus speed up parsing).
b. After saving a new reference file, diff it against the old reference files.
Delete any old reference file that has no error not already present in the new
reference file. This will not help much if the set of failures is different
with every run. But otherwise this will speed up both the parsing and diffing.
--
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=42770
Bug ID: 42770
Summary: test.winehq.org: Provide a view showing only the
TestBot VMs
Product: WineHQ.org
Version: unspecified
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: www-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
In Huw's words:
> Something else that would be very useful is the ability to
> display just the test bot VMs. These are the ones we care
> about the most, and the ones that are possible to fix without
> having to get a third-party to manually run a test. I find it
> difficult to just keep track of these VMs when their results get
> swamped by all the other machines’ failures.
>
> I‘d imagine this should be possible to do using static
> pages. The root page (equivalent to data/index.html)
> could be something like data/wtb_index.html. Clicking
> on a build id would take you to data/build-id/wtb_index.html,
> then clicking on an OS flavour would take you to
> data/build-id/wtb_index_flavour.html. You’d also need some
> way to toggle in and out of the mode.
This should be pretty similar to adding the 'flat index' files mentioned in bug
39379.
https://bugs.winehq.org/show_bug.cgi?id=39379
An interesting alternative would be to go the JavaScript way and make the index
files, which are essentially big tables, sortable, filterable on the
client-side.
--
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=47854
Bug ID: 47854
Summary: Block Windows 10 updates
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: ---
Windows Updates can interfere with the Wine tests in many ways:
* By causing disk traffic they could slow down some tests, causing them to time
out. (Some Wine tests are already somewhat slow. Obviously making them faster
and/or improving QEmu's disk performance would be great but barring that
preventing undue external disk traffic is necessary)
* Windows installing an update at the same time WineTest is testing MSI
installs could cause interference.
* There is also a risk of Windows scheduling a reboot during a test, or popping
up a window asking to reboot during Wine's windowing tests.
And in any case Windows Updates are a waste of CPU, network and disk bandwidth
since VMs will be reverted as soon as the test is completed.
For these reasons pre-Windows 10 versions are configured with Windows updates
disabled. But for Windows 10 that's not possible.
So instead the 'Windows Update' service is disabled. However that does not
survive reboots. So LibvirtTool could maybe run a command to re-disable that
service when it creates a live snapshot. That command could also be repeated in
WineRunTask before starting the tests.
Also for Windows 10 >= 1703 it is possible to set the network connection to
metered mode. This appears to prevent updates no matter what limit is set which
means it's preferable to set a large limit to avoid notifications abut being
past the limit.
To set the network connection in metered mode:
* In Windows >= 1703: Settings -> Ethernet -> Ethernet (Connected) -> 'Set as
metered connection'.
* In Windows >= 1809
This page also describes a regedit based approach. It's unclear if it works
with older Windows 10 versions.
https://www.winhelponline.com/blog/ethernet-metered-connection-windows-10-d…
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\NetworkList\DefaultMediaCost]
"Ethernet"=DWORD:2
Note that this requries changing the ownership on DefaultMediaCost to the
Administrators group and then back to its original owner, TrustedInstaller, aka
"NT Service\TrustedInstaller" (use those Advanced buttons).
--
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=47838
Bug ID: 47838
Summary: Add a dual-screen Windows VM
Product: Wine-Testbot
Version: unspecified
Hardware: x86
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Wine has tests that deal with multi-head displays. These would need some
matching multi-head test VMs.
--
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=47849
Bug ID: 47849
Summary: Simplify BuildCros() in Build.pl
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: ---
Build.pl is the script that's responsible for building PE executables that can
be used to runt he tests on Windows VMs.
Currently it's still jumping through hoops to produce PE executables (see
BuildNative() and BuildCross()), which is most likely unnecessary since Wine
now builds all tests as PE executables by default.
So that code could likely be simplified but we would not want to lose speed
advantage either: the build VM never compiles a full Wine which means patches
touching headers don't cause 45+ minutes builds. Also the current code still
works so it's not necessarily urgent.
Side note:
In fact it could be argued that the build VMs are unnecessary now since any
Wine VM could produce these PE executables. There's some caveats with that
though:
- Wine may not produce PE executables on some platforms. For instance for a
while it looked like MinGW was not usable on NetBSD, forcing the TestBot to
produce only regular ELF executables. That got fixed but the issue may happen
again on other Unix platforms. Maybe.
- In the absence of support for load balancing it's useful to have a separate
build VM to spread the load. That VM could be a repurposed Wine VM though.
--
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=47853
Bug ID: 47853
Summary: Allow testing in any locale on Wine VMs
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: ---
Because Wine VMs run Unix, running a test in a locale is a simple matter of
setting $LANG (*), creating a new WinePrefix for good measure, and running the
test normally.
This does assume that the relevant locales have been configured before hand
which is an easy one-time task when setting up the VM.
Wine VMs already have a list of missions they perform for wine-devel patches
from which we can derive a list of locales to offer on the 'Submit job' page
(see bug 47852). But we would not want to run every patch through every
possible locale as this would take too much time (there are dozens of locales).
But extra locales could be included in the 'Submit job' page to allow debugging
of these locales.
(*) And $LC_ALL 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=48651
Bug ID: 48651
Summary: Fix handling of child test processes
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: ---
Wine's test.h provides a winetest_wait_child_process() function to wait for
child processes. But when an error happens it issues some messages which the
TestBot does not recognize.
* If waiting for the child process fails the error message does not look like a
'Test failed' error message which it should to simplify things.
* But winetest_wait_child_process() does not know on which line it was called
so calling winetest_ok() would not provide the right line number.
* The failure to wait for the child process should also distinguish between
CreateProcess() errors (usually those are already reported by the caller),
timeouts and other errors.
* The Testbot does not recognize the 'child process crashed' message. This
causes it to find mismatches between the number of 'Test failed' messages and
the final summary.
* The TestBot also does not recognize the 'failures in child process' summary
line but that probably does not matter.
--
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=48671
Bug ID: 48671
Summary: Some patches may require forcing a wineprefix update
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 updates the wineprefixes when it updates its base Wine source from
the daily Wine commits. The rest of the time it lets Wine deal with updating
the wineprefix is necessary. Furthermore Wine only updates the wineprefix when
wine.inf changes, which is the case for every Wine release.
The problem is that the wineprefix should also be updated when a patchset adds
a WINE_REGISTRY resource to an existing dll. Failing to do so may cause the
patchset tests to fail because the wineprefix is out of date.
See:
https://www.winehq.org/pipermail/wine-devel/2019-December/156914.html
WinePrefix updates are relatively slow compared to the execution time of most
tests (about 30s vs. < 1s) so it would be good not to have to do that for every
task. An alternative would be to force a wineprefix update when a task has
failures and gets rerun as a result (pass an option to the relevant VM-side
scripts).
Note: Shared Gecko and Mono install issues should be discussed on bug 48354.
--
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=48092
Bug ID: 48092
Summary: On cw-rx460 the win32 WineTest run gets interrupted
before it completes
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: ---
cw-rx460 runs wt-daily (*), just like cw-gtx560. But when running the plain 32
bit tests on cw-rx460 (cw-gtx560-t32), wt-daily ends up submitting the test
results before WineTest.exe has completed, resulting in many rejections by
test.winehq.org (https://test.winehq.org/data/errors.html).
WineTest appears to be interrupted most often during kernel32:loader, but
sometimes it's during kernel32:debugger or ieframe:ie. And once in a while the
test completes, though that's pretty rare.
Maybe a test crashes the X server, causing winetest.exe to exit prematurely.
wt-daily is started by cron so it does not depend on the X server and would
start a second winetest command to send the (incomplete) test results.
Then it would start the wow32 and wow64 tests and by that time it's possible
the X server would have restarted. Interestingly wow32 and wow64 don't seem to
cause the X server to crash.
cw-rx460 is not a TestBot VM so this does not impact the TestBot results. But
it could impact the test.winehq.org results the few times where WineTest
completes (though when it does it only gets ~10 failures which is half what the
other Wine machines get).
So I have disabled the 32 bit WineTest runs until this is resolved.
(*) 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=48090
Bug ID: 48090
Summary: Add support for .com programs
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 assumes that if a patch touches a directory in programs, then it
must append .exe to the program's name.
But Wine could also get .com programs, see for instance chcp.com:
https://www.winehq.org/pipermail/wine-devel/2019-November/154371.html
And in fact we already have other programs with non-standard extensions, for
instance winhelp.exe16 and winoldap.mod16.
So if the program's directory already has an extension the TestBot should not
add one. Another option would be to use the MODULE setting in the directory's
Makefile.in file. But the TestBot server does not have access to the Wine
source. It would also make it harder to deal with patches adding test
directories and it would be quite ugly to have to read them every time anyway.
It would make it harder to deal with patches adding dlls/programs as it would
require parsing the patch to retrieve the MODULE value.
Another option may be to never add an extension, though then there's the risk
of getting collisions between the dll and program names, and maybe it impacts
other parts of the TestBot anyway.
_CreateTestInfo() in testbot/lib/WineTestBot/PatchUtils.pm needs to be patched
but there are impacts elsewhere. The WTBS (Wine TestBot test Suite) will also
need to be updated.
--
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=48653
Bug ID: 48653
Summary: Automate checking the WTBS jobs
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 Wine TestBot test Suite (WTBS) is a set of Wine patches that can be used to
check how the TestBot handles test failures, timeouts, patch series, non-Wine
patches, etc:
https://github.com/fgouget/wine/commits/wtbsuite
The patches can either be used in isolation to test a specific aspect, or all
together using formail to do a broad check for TestBot regressions. However as
the test suite has become more complete the number of patches has grown and now
tops 90. So a full check for regressions means checking the results of about 90
TestBot jobs for missing test failures, incorrect report validation messages,
etc. This makes it pretty time consuming.
So the goal is to automate at least the most basic checks.
To do so the plan is to add lines of the form 'WTBS.xxx=yyy' to the commit
messages of the WTBS patches. Each will define a property that should be
checked in the TestBot job and tasks.
Then a TestBot script can be run to go through every job, ignore the queued and
running ones and those have have no associated patch. For the others read the
associated patch and look for the WTBS.xxx lines. Note that for patch series,
only the last set of WTBS values should be taken into account (i.e. the ones
after the "Last patchset part" line).
Here is a sample of the possible properties to check:
* WTB.Job.Remarks
The job 'title' which is derived from the patch subject line.
* WTBS.Job.Status
Whether to expect badpatch, completed, etc.
For tasks the property names would be prefixed with the VM type: build, win
(for win32 and win64), wine. This allows specifying different results for each.
* WTBS.build.Status, WTBS.win.Status, WTBS.wine.Status
Same as Job.Status but at the task level.
* WTBS.win.Failures, WTBS.wine.Failures
The number of test failures expected from the result.
Note that if the Wine Test Unit is buggy we may get more test failures than
expected. This is particularly an issue with Wine VMs if their mission include
test=module or test=all.
So it may make sense to specify WTBS.win.Failures but leave out
WTBS.wine.Failures. Or maybe have a MinFailures property. Or grep the failures
whose message contains 'WTBS' and only compare those to this property.
* WTBS.win.NewFailures, WTBS.wine.NewFailures
The number of new test failures as reported by LoadLogErrors() for each of
the task's report.
* WTBS.win.ReportFailures, WTBS.wine.ReportFailures
In a number of cases what we're interested in is the report validation errors
produced by the TestBot. Just checking the number of such errors may not be
that useful. What we may want is a way to check that it reported missing
failures messages, or too much data being printed, etc. This requires being
able to specify a set of errors that are expected to be present for which this
basic property system is not very well suited.
* WTBS.win.TestUnits
For each VM, collect the Step's FileName and the Task's CmdLineArg values to
determine the test unit being run, and verify that this is a superset of the
TestUnits list. This can be used to ensure that the TestBot ran the right set
of tests (and avoids failures when a new test is added to Wine).
Note that doing the same thing for Wine VMs is harder because those can have
test=module in their mission(s), which changes greatly the list of tests being
run.
It may make sense to provide default values for some properties to not have to
type too much in the commit messages. For instance for the Status properties
one may expect the status to be 'completed'. But given the WTBS tests error
cases a lot that may not be all that useful.
Similarly it may be useful to be able to specify something like
'WTBS.all.Status' to specify the expected Status for the build, win and wine
VMs all at once. But again this may be overkill.
Finally the general rule should be that unspecified properties are not checked.
So if 'WTBS.wine.Failures' is not specified, then the failure count of Wine VMs
should not be checked.
--
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=48654
Bug ID: 48654
Summary: Automate checking the WTBS patches
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: ---
See bug 48653 for a description of the WTBS and how to check the jobs created
when running it on the TestBot.
Some patches in the WTBS are not meant to create TestBot jobs but rather to
verify that it ignores non-Wine patches, or patches that don't impact the tests
or the Wine build, etc.
Those still create entries in the 'wine-devel' page, that is in the TestBot's
Patches table. Each entry gets the patch subject and a disposition property
indicating what the TestBot did with the patch. Unfortunately non-Wine patches
are not kept around so there is no way to get at the WTBS fields for those. So
a TestWTBS.patches script would need to get the WTBS properties from another
source.
For instance it could be given the path to the WTBS mbox and get the properties
from there. It would not need to understand all the intricacies of the mbox
format (though with the appropriate Perl module it may be easy to parse). As a
last resort, all we would care about is:
* The 'From' lines to delimit emails.
* The 'Subject:' lines to match the mbox emails with Patches entries.
* The WTBS properties in the commit message following the Subject line.
Checking the patch objects would require an extra property:
* WTBS.Patch.Disposition
This should be set to the expected patch disposition such as 'No patch
found', 'Not a Wine patch', etc. A default disposition could be set if a
'WTBS.Job.*' or other task property is specified.
--
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=48655
Bug ID: 48655
Summary: Automate checking the WTBS emails
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: ---
See bug 48653 for a description of the WTBS and how to check the jobs created
when running it on the TestBot.
When a 'wine-devel' job completes the TestBot sends one or two emails.
* One of the emails simply sends the task reports to the patch author.
* The other is only sent if a task generated new errors.
The point of the TestWTBS.emails script would be to check that:
1. The TestBot sent the task report email for every Wine patch and not for any
patch email. This would be based off of the WTBS.Patch.Disposition field.
2. The TestBot sent a 'found new errors' email only when new errors are
expected. This would be based off of the 'WTBS.*.NewFailures' property or the
expected errors list.
However for both these checks the script would need access to the emails sent
by the TestBot. The simplest option would be for the tester to set the
WinePatchToOverride property and save the emails to a separate mbox and give
the patch to that mbox to the script.
As in the TestWTBS.patches case, the script would only care about a few lines:
* The 'From' lines to delimit the emails.
* The 'Subject' lines to match them to TestBot jobs and thus to the set of WTBS
properties.
Note that this would not rely on the 'TestBot job xxx results:' part since
the new failures email are lacking it. Instead it would match the rest of the
subject to the job's Remarks field.
* The 'I think I found new failures' line to identify emails reporting new
errors.
The script could later be expanded to check the content of the email or
attachments more in details if needed.
--
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=32216
Bug #: 32216
Summary: WienTestBot should skip some tests on some platforms
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
An example is the ieframe:webbrowser tests which it should skip on NT4 and
Windows 2000 platforms. WineTest.exe is said to already have the necessary code
somewhere, it's just missing from TestLauncher.
See this wine-devel thread for more details:
http://www.winehq.org/pipermail/wine-devel/2012-November/097819.html
--
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=50719
Bug ID: 50719
Summary: The TestBot mishandles renames
Product: Wine-Testbot
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
The TestBot analyses patches to determine whether they are Wine patches and
which tests are impacted and must be rerun.
But when a patch renames a test unit it still schedules a run for the renamed
test unit. For instance if apphelp:apphelp is renamed to apphelp:renamed, the
TestBot still schedules a run of apphelp:apphelp (in addition to the
apphelp:renamed one).
This means it does not keep track of Wine's current files list correctly, which
also impacts identifying whether a patch is a Wine patch or not, particularly
for patch series.
This can be tested with the following wtbsuite tests:
WTBS Check combined renaming and modifying a file (apphelp:apphelp).
[2/2] WTBS S10.2 - ...before renaming it in the next part (amstream:amstream).
[7/7] WTBS S5.7 - Check for rename+addition+removal conflicts (msi:suminfo).
--
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=48208
Bug ID: 48208
Summary: Detect missing entry point 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: ---
When a Windows test executable cannot run because of a missing test executable
the TestBot remains stuck until the 2 minutes timeout. This is because Windows
puts up an error dialog waiting for user input. In such a case the test report
is almost empty and the issue is not obvious until one looks at the screenshot.
The TestBot should detect such a situation and warn the user.
One simple approach would be for the TestBot to detect that the test report
only contains the TestLauncher's start and done lines and indicates a timeout.
In such a case it could add a message to the .err file suggesting to check the
screenshot. This would only be a heuristic though.
A better approach would be for the TestLauncher to detect the error dialog.
Ideally, instead of waiting for the child process for the full 2 minutes it
would periodically check for the presence of this dialog, which would also
speed up the task run. This approach could also be used by WineTest.exe, though
presumably missing entry points would have been detected before making it into
the Wine source.
--
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=50538
Bug ID: 50538
Summary: Wine child process exceptions are miscounted
Product: Wine-Testbot
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
The "WTBS Crash in a child process (kernel32:toolhelp)." test case shows an
inconsistency in the test failures count between the Windows and Wine VMs.
On Windows we get:
1bec:toolhelp: unhandled exception c0000005 at 0054273D
toolhelp:471: unhandled exception c0000005 in child process 1bec
1750:toolhelp: 3 tests executed (0 marked as todo, 1 failure), 0 skipped.
Here there is 1 exception, 1 failure reported by the parent process but 2 error
lines, and the task's failure count ends up being 2.
But in Wine we get:
Unhandled exception: page fault on write access to 0x00000000 in 32-bit code
(0x00542c1d).
toolhelp:471: unhandled exception c0000005 in child process 0104
00fc:toolhelp: 3 tests executed (0 marked as todo, 1 failure), 0 skipped.
So there is still 1 exception, still 1 failure reported by the parent process,
still 2 error lines, but the task's failure count ends up being just 1.
The issue appears to be that ParseWineTestReport() (and probably dissect too)
detects ": unhandled exception...at" lines but not Wine's "Unhandled
exception:" ones.
This means the TestBot may fail to detect exceptions on Wine.
Meanwhile GetReportLineCategory() and _GetLineKey() detect both.
--
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=50491
Bug ID: 50491
Summary: Detecting whether garbled lines are new
Product: Wine-Testbot
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
Sometimes a failure line is garbled because of race conditions or a missing
'\n'. This typically looks something like this:
advpack.c:689: WTBS Garble 2advpack.c:691: WTBS Garble 3advpack.c:692: Test
failed: WTBS A test failure
The TestBot still detects these failures because it knows which test unit is
running at that point in the report and thus looks for something like
'advpack.c:\d+: Test failed: ...'.
But when it tries to detect whether this is a new error line it cannot compare
the whole line with past instances as the garbage part may change or not be
present in WineTest runs (particularly if it contains line numbers). That
suggests it should extract just the current failure string, that is:
advpack.c:692: Test failed: WTBS A test failure
This should maybe also be the string stored in the .errors file.
--
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=27453
Summary: Lag when loading new sound in source games
Product: Wine
Version: 1.3.21
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: congelli501(a)gmail.com
When you start a level in a game powered by valve's source engine, sounds that
are played for the first time since the game was launched will cause the game
to lag.
Ex: open a new portal for the first time in a Portal2 level.
Affects:
- Portal 2
- Left 4 Dead 2
- Probably more...
--
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=7991
Linards <linards.liepins(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |linards.liepins(a)gmail.com
--- Comment #36 from Linards <linards.liepins(a)gmail.com> ---
Is this bug still present on wine-staging 6.7 ?
--
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=51094
Bug ID: 51094
Summary: Battlefield 3 crashes before entering the main menu
with Vulkan renderer
Product: Wine
Version: 6.7
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
Distribution: ---
Created attachment 69954
--> https://bugs.winehq.org/attachment.cgi?id=69954
backtrace
04fc:fixme:d3d:wined3d_device_context_clear_rendertarget_view Not implemented
for WINED3D_RTYPE_BUFFER resources.
04fc:err:d3d11:d3d11_immediate_context_ClearRenderTargetView Failed to clear
view, hr 0x8876086c.
0518:fixme:d3d:wined3d_buffer_vk_prepare_location Unhandled location 0.
0518:err:d3d:wined3d_buffer_invalidate_range Buffer 0x9fcf0c8 does not have any
up to date location.
0518:err:d3d:wined3d_texture_vk_prepare_texture Invalid resource type
WINED3D_RTYPE_BUFFER.
0518:err:d3d:wined3d_context_vk_create_image Failed to create image, vr
unrecognised(-1000011001).
0518:err:d3d:vk_image_view_type_from_wined3d Unhandled resource type
WINED3D_RTYPE_BUFFER.
6.7-64-g4ccf7498aac
--
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=51093
Bug ID: 51093
Summary: Problem with unfilled shapes in MS Word
Product: Wine
Version: 6.7
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jesaenh(a)gmail.com
Distribution: ---
By adding a filled shape (a rectangule, a circle) in MS Word, you can select it
later. It works normal.
However, if it is unfilled, you cannot select it any more, so you can not
change color, size,....
This happens with docx files, not doc.
--
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=10219
Summary: Windows Media Player 11 setup fails
Product: Wine
Version: 0.9.48.
Platform: PC
URL: http://www.microsoft.com/windows/windowsmedia/download/A
llDownloads.aspx?displang=en&qstechnology=
OS/Version: Linux
Status: NEW
Keywords: download, Installer
Severity: normal
Priority: P2
Component: wine-misc
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: alex(a)thehandofagony.com
The setup program for Windows Media Player 11 tries to validate Windows if the
version is set to XP, and this fails. There was talk some time ago about an
ntlm_auth patch that would allow the validation, but it fails for me even
though I have the correct version of Samba installed.
However, the installer does not run the Genuine check if the Windows version is
set to Vista. When run thus it does work, however; it tries to create an
instance of a wuapi.dll class, which is not registered in Wine. When I use a
native dll from XP and register it the console output changes saying no
instance could be created.
The installer then says no updates could be found.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=14547
Summary: Problem with loading of windows from Java applications
Product: Wine
Version: 1.1.1
Platform: Other
OS/Version: other
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: yolande(a)haneder.biz
Created an attachment (id=14894)
--> (http://bugs.winehq.org/attachment.cgi?id=14894)
Files for the test case
We made a test case to show that child windows for Java applications (written
in a class are not appearing) are problematic.
To start the test, you have to install Java on Wine (I tested with java1.5-10)
and start file in the /bin directory of the java installation directory.
What is expected (showing during tests on Windows XP):
There is a mainframe called "Using a JDesktopPane"
Then a row in the main body of the main frame called "Add"
Then a child window called "Internal frame"
Result in Wine:
Totally black screen with only the part with the word "Add" to be visible.
Through hovering the mouse over the black part, you can restore most parts of
your desktop to access other windows.
If you need the source code of any of the file, you just need to ask.
--
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=21764
Summary: Sun JRE (jre-6u16-windows-i586-s) installation failure
Product: Wine
Version: unspecified
Platform: x86
URL: http://java.sun.com/products/archive/j2se/6u16/index.h
tml
OS/Version: Linux
Status: NEW
Keywords: download, regression
Severity: normal
Priority: P2
Component: msi
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: bunglehead(a)gmail.com
Sun JRE 6update16 fails to install with 1.1.39. It's a regression and a commit
to blame is 1ff992314887d03abeb4098789701ff3bfd5d2d8:
msi: Add summary information stream to the streams table.
Reverting helps.
--
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=22024
Summary: sun jre installation (jre-6u18-windows-i586.exe)
Product: Wine
Version: 1.1.40
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: ntoskrnl
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: samuele_catuzzi(a)yahoo.it
Created an attachment (id=26779)
--> (http://bugs.winehq.org/attachment.cgi?id=26779)
wine jre-6u18-windows-i586 install crash
Several crash and register dump during install
Ubunutu 9.10 x86_64
--
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=38624
Bug ID: 38624
Summary: jre-8u45-windows-i586.exe exits silently
Product: Wine
Version: 1.7.43
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dimesio(a)earthlink.net
Distribution: ---
I only tested the 32 bit offline installer, but AppDB test reports indicate the
online installer fails similarly. The only thing printed in the terminal is:
fixme:ole:RemUnknown_QueryInterface No interface for iid
{00000019-0000-0000-c000-000000000046}
This version of JRE requires Vista SP2 or newer; I tested with winecfg set to
Vista, 7, and 8, with the same results.
--
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=38811
Bug ID: 38811
Summary: jre-8u45-windows-i586.exe installer crashes
(GetThreadPreferredUILanguages is a stub)
Product: Wine
Version: 1.7.45
Hardware: x86
URL: http://javadl.sun.com/webapps/download/AutoDL?BundleId
=106246
OS: Linux
Status: NEW
Keywords: download, Installer
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: dimesio(a)earthlink.net
Depends on: 38624
Distribution: SUSE
Filing per https://bugs.winehq.org/show_bug.cgi?id=38624#c1. Tested in
wine-1.7.45-213-g4f3acf3.
--
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=14750
Summary: comctl32: Fixed rebar behaviour when there's capture and
no drag
Product: Wine
Version: CVS/GIT
Platform: Other
OS/Version: other
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: richedit
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: bugzilla(a)tut.by
Created an attachment (id=15249)
--> (http://bugs.winehq.org/attachment.cgi?id=15249)
comctl32: Fixed rebar behaviour when there's capture and no drag
ERR() here causes some applications (i.e. ISIS/Proteus) to crash when mouse
moves over rebar. This patch fixes this behaviour.
--
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=51090
Bug ID: 51090
Summary: Myst IV: cursor jumping in direction of movement
Product: Wine
Version: 6.7
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-dinput
Assignee: wine-bugs(a)winehq.org
Reporter: v19930312(a)gmail.com
Distribution: ---
In Myst IV, cursor will often jump (advance way too quickly) in direction I'm
moving it in, making game rather annoying to play. This can be seen as early as
in main menu.
Interestingly, windows folks also have this problem:
https://steamcommunity.com/app/925940/discussions/0/2148721524009687428/.
TL;DR: they solve it by reducing mouse polling rate (mine is already at 125Hz,
which seems to be okay).
This issue didn't happened some time (few years?) ago, the previous time I've
played, but it may be attributed to change of mouse rather than regression.
--
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=51089
Bug ID: 51089
Summary: Hathi Download Helper crashs
Product: Wine
Version: 1.8
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: bugzilla(a)tonne.to
Distribution: ---
Created attachment 69953
--> https://bugs.winehq.org/attachment.cgi?id=69953
backtrace
Hathi Download Helper crashs after ca 30s
--
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=34122
Bug #: 34122
Summary: Civilization V breaks both expansion packs are
installed
Product: Wine
Version: unspecified
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: kernel32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: mcasadevall(a)ubuntu.com
Classification: Unclassified
Created attachment 45374
--> http://bugs.winehq.org/attachment.cgi?id=45374
Test program that tries to reproduce Civilization V's behavior as seen from the
+files log
With the release of Brave New World for Civiliziation V, the game itself fails
to properly load either expansion if both are loaded. The issue appears to boil
down to the fact that Civ tries to load its datafiles in the order returned by
Find{First,Next}File, and inadvertently loads its expansions in the wrong order
(G&K must be loaded before Brave New World).
This issue can be semi-worked around by renaming files so that their return
order is changed (generally renaming Expansion to Expansion3 seems to do the
trick, but its not foolproof).
On Windows, FindFirstFile returns its files in alphabetical order (likely due
to Steam installing them in that order), and as such, Civ can load things
correctly. I was able to reproduce this bug on Windows by moving everything to
a network drive (which returns a different order), and getting similar results.
To show the problem, I wrote a test program which calls FindFirstFile in a
matter similiar to Civ5 does; said program is attached along with a trace from
+file.
Results from the test program:
Wine git (game does NOT work):
mcasadevall@perdition:~/wine-dev/steam/drive_c/Program
Files/Steam/SteamApps/common/Sid Meier's Civilization V$ $WINE ./a.exe
.\Assets\DLC\DLC_02\SpainInca.Civ5Pkg
.\Assets\DLC\Shared\Upgrade1.Civ5Pkg
.\Assets\DLC\DLC_05\Korea.Civ5Pkg
.\Assets\DLC\Tablet\Tablet.Civ5Pkg
.\Assets\DLC\Expansion2\Expansion2.Civ5Pkg
.\Assets\DLC\DLC_06\AncientWonders.Civ5Pkg
.\Assets\DLC\DLC_04\Denmark.Civ5Pkg
.\Assets\DLC\DLC_01\Mongol.Civ5Pkg
.\Assets\DLC\DLC_03\Polynesia.Civ5Pkg
.\Assets\DLC\Expansion\Expansion1.Civ5Pkg
.\Assets\DLC\DLC_Deluxe\Babylon.Civ5Pkg
Windows XP - NTFS filesystem (game works)
C:\Program Files\Steam\steamapps\common1\Sid Meier's Civilization V>a
.\Assets\DLC\DLC_01\Mongol.Civ5Pkg
.\Assets\DLC\DLC_02\SpainInca.Civ5Pkg
.\Assets\DLC\DLC_03\Polynesia.Civ5Pkg
.\Assets\DLC\DLC_04\Denmark.Civ5Pkg
.\Assets\DLC\DLC_05\Korea.Civ5Pkg
.\Assets\DLC\DLC_06\AncientWonders.Civ5Pkg
.\Assets\DLC\DLC_Deluxe\Babylon.Civ5Pkg
.\Assets\DLC\Expansion\Expansion1.Civ5Pkg
.\Assets\DLC\Expansion2\Expansion2.Civ5Pkg
.\Assets\DLC\Shared\Upgrade1.Civ5Pkg
.\Assets\DLC\Tablet\Tablet.Civ5Pkg
Windows XP - network filesystem (game does NOT work)
X:\wine-dev\steam\drive_c\Program Files\Steam\SteamApps\common\Sid Meier's
Civil
ization V>a
.\Assets\DLC\Tablet\Tablet.Civ5Pkg
.\Assets\DLC\DLC_02\SpainInca.Civ5Pkg
.\Assets\DLC\Shared\Upgrade1.Civ5Pkg
.\Assets\DLC\DLC_05\Korea.Civ5Pkg
.\Assets\DLC\Expansion2\Expansion2.Civ5Pkg
.\Assets\DLC\DLC_06\AncientWonders.Civ5Pkg
.\Assets\DLC\DLC_04\Denmark.Civ5Pkg
.\Assets\DLC\DLC_01\Mongol.Civ5Pkg
.\Assets\DLC\DLC_03\Polynesia.Civ5Pkg
.\Assets\DLC\Expansion\Expansion1.Civ5Pkg
.\Assets\DLC\DLC_Deluxe\Babylon.Civ5Pkg
I believe the underlying cause of this bug may also be the root of bug #31113,
but until I know for sure, they should be considered seperate issues.
--
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=18166
Summary: dlls/ntdll/directory.c: implicit declaration of function
'getdirentries'
Product: Wine
Version: 1.1.19
Platform: PC
OS/Version: NetBSD
Status: NEW
Keywords: patch, source
Severity: major
Priority: P2
Component: build-env
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: austinenglish(a)gmail.com
Created an attachment (id=20631)
--> (http://bugs.winehq.org/attachment.cgi?id=20631)
wrap getdirentries around getdents
gcc -c -I. -I. -I../../include -I../../include -D__WINESRC__ -D_NTSYSTEM_
-D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing
-Wdeclaration-after-statement -Wwrite-strings -Wpointer-arith
-I/usr/pkg/include -I/usr/include -I/usr/X11R7/include/freetype2
-I/usr/X11R7/include -O2 -I/usr/pkg/include -I/usr/include
-I/usr/X11R7/include/freetype2 -I/usr/X11R7/include -o directory.o directory.c
directory.c: In function 'wine_getdirentries':
directory.c:1289: warning: implicit declaration of function 'getdirentries'
Apparently getdirentries is broken on NetBSD. Attached patch (based on one from
their port) fixes it.
--
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=31113
Bug #: 31113
Summary: Civilization V crashes after specific amount of game
turns
Product: Wine
Version: 1.5.5
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: megatog615(a)gmail.com
Classification: Unclassified
Created attachment 40841
--> http://bugs.winehq.org/attachment.cgi?id=40841
Page fault log
After a specific amount of game turns(depending on how the game has played
out), Civilization V will crash with a page fault. If you save the game just
before you can do nothing else and must click "NEXT TURN," you can reproduce
the bug every time. I am going to attach a save file at just this point. All
you have to do is click NEXT TURN.
--
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=45906
Bug ID: 45906
Summary: Soldat instal, start but black / garbage and halt
after game starts
Product: Wine
Version: 3.16
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mrluzeiro(a)ua.pt
Distribution: ---
In the Soldat game,
I can install it, configure and start the program.
After start the program when actually start the game, the screen flickers and
become blank / transparent / garbage..etc.
I managed to run this game on a different hardware so I think the issue may
with this machine hardware.
Linux x86-64
NVidia GT 530 drivers 384.130
I didnt found anything useful or errors from the logs.
--
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=50062
Bug ID: 50062
Summary: Fallout 76 invisible ground textures
Product: Wine
Version: 5.20
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: o.dierick(a)piezo-forte.be
Distribution: ---
Created attachment 68518
--> https://bugs.winehq.org/attachment.cgi?id=68518
Screenshot of missing ground textures; wine 5.20
Hello,
Fallout 76 has invisible ground textures. See attached screenshot.
My setup is:
- Debian 8 amd64 16Gb RAM i7-4930 @ 3.4Ghz;
- NVidia RTX 2070 8GB VRAM + proprietary driver 450.66;
- wine 5.20;
- winetricks corefonts xact_x64;
- virtual desktop + no WM management/decoration + grab fullscreen;
To replicate, install the game (Bethesda.net or Steam windows version), then
you have to use an existing character or create a character and get out of the
first building. That building has no natural floor and the issue only affects
the ground texture, so it's not enough to just start a new game.
Note that the game is affected by a bug that makes the game crash when loading
a save immediately after launching the program. You have to start a new
character first. When character creation is complete, you may return to the
main menu and load the save. This is an application bug [1].
Some graphics settings must be disabled in the INI file to avoid major mouse
and rendering issues. The details can be found on the lutris website [2].
[1]
https://www.reddit.com/r/fo76/comments/a3446i/game_crashes_after_trying_to_…
[2] https://lutris.net/games/fallout-76/
The ground is transparent. The game renders the objects behind mountains and
the performance is directly affected by the rendering distance set in the
option.
- Using Ultra or lowest graphic settings makes no difference;
- I tried changing some values in the INI file without luck;
- The issue occurs with wine-staging 5.20 too.
Regards.
--
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=45864
Bug ID: 45864
Summary: wine mono cannot load 64-bit DLLs
Product: Wine
Version: 3.0.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: mscoree
Assignee: wine-bugs(a)winehq.org
Reporter: paleozogt(a)gmail.com
Distribution: ---
Created attachment 62358
--> https://bugs.winehq.org/attachment.cgi?id=62358
wine mono project and binaries
Attached is an example project that makes a PInvoke call to a custom native
function. It produces HelloWorld.exe (from HelloWorld.cs) and HelloWorld.dll
(from HelloworldNative.cpp).
If I build a 32-bit HelloWorld.dll, I am able to run HelloWorld.exe in Wine
with a WINEPREFIX generated from both WINEARCH=wine32 and WINEARCH=wine64.
However, if I build a 64-bit HelloWorld.dll, I am unable to run HelloWorld.exe
in Wine with a WINEPREFIX generated from either WINEARCH=wine32 or
WINEARCH=wine64. I wouldn't expect WINEARCH=wine32 to work for a 64-bit DLL,
but its surprising that WINEARCH=wine64 doesn't work. (With WINEARCH=wine64
I'm otherwise able to run 64-bit native executables without a problem.)
The failure looks like this:
> >HelloWorld.exe
> 002f:err:mscoree:LoadLibraryShim error reading registry key for installroot
>
> Unhandled Exception:
> System.DllNotFoundException: HelloWorld
> at (wrapper managed-to-native) HelloWorld.Hello:helloWorld ()
> at HelloWorld.Hello.Main () [0x00001] in <93c08d3d3d384696aa77bc80f6a731c1>:0
> [ERROR] FATAL UNHANDLED EXCEPTION: System.DllNotFoundException: HelloWorld
> at (wrapper managed-to-native) HelloWorld.Hello:helloWorld ()
> at HelloWorld.Hello.Main () [0x00001] in <93c08d3d3d384696aa77bc80f6a731c1>:0
It seems like Wine Mono is either running as a 32-bit process or something is
wrong with how Wine Mono's PInvoke DllImport searches for compatible DLLs.
--
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=51012
Bug ID: 51012
Summary: [bubblewrap] wine hungs inside a bubblewrap (or a
similar mount ns sandbox)
Product: Wine
Version: 6.6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: winehq(a)mail.jerryxiao.cc
Distribution: ---
OS: Arch Linux x86_64
Distribution wine version: 6.6-1
Distribution bubblewrap version: 0.4.1-1
Steps to reproduce:
bwrap --dev-bind / / --tmpfs $HOME wineconsole
The process freeze and never starts. Have no idea how to debug that. Any
suggestions are appreciated.
--
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=42563
Bug ID: 42563
Summary: regedit: minor enhancements/corrections to REG_BINARY
edit dialog
Product: Wine
Version: 2.2
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: programs
Assignee: wine-bugs(a)winehq.org
Reporter: galtgendo(a)o2.pl
Distribution: ---
Created attachment 57477
--> https://bugs.winehq.org/attachment.cgi?id=57477
patch implementing the changes
OK, it took me awhile.
As I've written a few weeks ago, due to the display part being
unscrollable/unresizable, long values may sometimes not fit into their
allocated display space. Also, monospace makes simply much more sense here.
The attached patch modifies the default font to monospace variant and tries to
enforce it by using ExtTextOutW.
A possible further enhancement would be to use the proper value for max 0-9A-F
width in address block, instead of the same as in the content block.
--
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=45587
Bug ID: 45587
Summary: wine fails to install dragon naturally speaking 15
Product: Wine
Version: 3.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: susancragin(a)earthlink.net
Distribution: ---
Created attachment 62012
--> https://bugs.winehq.org/attachment.cgi?id=62012
backtrace from failed install
Dragon Naturally Speaking 15 does not install.
Here's what I do.
Start with a 32bit wine prefix.
Install dotnet40
When that is finished, set the program version to Windows 7, which is the
lowest configuration that will run NatSpeak 15.
The program starts out by requesting dotnet 452. This is not a problem provided
dotnet 40 is installed. It makes changes and goes on.
Then it asks for preliminary information, such as what type of English I want
to speak, and so on.
Then the installation hangs.
Notes: the installation does not work with mono. It also does not work
installing dotnet from the installation disk, even though a complete copy is
included with the installation disk. And it doesn't work installing dotnet452
with winetricks.
I have the feeling that this may not be a bug as much as an issue that hasn't
been addressed yet.
These are the last lines of the terminal output, and I have attached the dump.
0270:fixme:advapi:DeregisterEventSource (0xcafe4242) stub
Unhandled Exception: 0270:fixme:ver:GetCurrentPackageId (0x33b890 (nil)): stub
0270:fixme:ntdll:EtwEventRegister ({8e9f5090-2d75-4d03-8a81-e5afbf85daf1},
0x33804b6, (nil), 0x10e6844) stub.
System.IO.FileNotFoundException: Could not load file or assembly
'System.Management.Automation, Version=1.0.0.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35' or one of its dependencies. File not found.
at customactions.Program.ChangeAppStartingCursor()
at customactions.Program.Main(String[] args)
wine: Unhandled exception 0xe0434352 in thread 270 at address 0x7b43c7dc
(thread 0270), starting debugger...
02e5:err:ntdll:RtlpWaitForCriticalSection section 0x7bd176e0 "virtual.c:
csVirtual" wait timed out in thread 02e5, blocked by 02f1, retrying (60 sec)
--
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=47685
Bug ID: 47685
Summary: winecfg: audio test fails with error on cmd line
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: normt40pa(a)yahoo.com
Distribution: ---
When using winecfg and then clicking tab audio, Evering seems good here until I
use the test audio button. I don't compile software ie to copile the new
version of wine. I use what is available on ubuntu.... The problem arises when
I click test audio giving me on the command line error "err:ole:CoInitializeEx
Attempt to change threading model of this apartment from multi-threaded to
apartment threaded" only. No other info after this since I have looked in the
forum for similar errors and none math the solo line as described above
(usually combine with a specific error type after this line. Please advise...
--
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=51072
Bug ID: 51072
Summary: Cant Install SQL Server 2012
Product: Wine-staging
Version: 6.6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ridhoarmand(a)yahoo.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Please fix, i want to install Visual Studio Ultimate 2012
--
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=51071
Bug ID: 51071
Summary: Microsoft Access 365 Runtime setup fails with error
30088-4
Product: Wine
Version: 6.7
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: alexhenrie24(a)gmail.com
Distribution: ---
Created attachment 69935
--> https://bugs.winehq.org/attachment.cgi?id=69935
Terminal output
To reproduce:
1. Run `wine OfficeSetup.exe`
2. Wait 10 minutes
The setup program appears to stall, but eventually a new window pops up with
the message "Error Code: 30088-4".
The problem is reproducible with both the 32-bit and the 64-bit version of the
Access runtime.
$ sha256sum OfficeSetup.exe # 64-bit version
4b390ddefbc1d5f275842321aff5b823f2df58638305f7dbbaf9dbc4fd1ad9d5
--
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=2948
--- Comment #23 from winetest(a)luukku.com ---
still not working as expected, wine 5.0 (Ubuntu 5.0-3ubuntu1) I don't have
newer wine installed.
--
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=24624
Summary: Audacity 1.3.12 treats all file type selections as
"all files" when exporting
Product: Wine
Version: 1.3.4
Platform: x86-64
URL: http://audacity.sourceforge.net/
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: RandomAccountName(a)mail.com
Created an attachment (id=31111)
--> (http://bugs.winehq.org/attachment.cgi?id=31111)
Terminal output
In Audacity, open an audio file and then go to file -> export. On this file
dialog, any selection from the "files of type" drop-down list will (apparently)
be treated as "all files", which leads to two minor annoyances:
1. DLLs and other unrelated file types will be listed while browsing for a
destination folder. (This doesn't happen immediately when the dialog opens,
only after changing the destination directory and/or file type.)
2. If the file extension isn't specified manually, Audacity will try to append
".*" to the end of the file name and then warn that this is a non-standard
extension for this type of file.
--
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=51068
Bug ID: 51068
Summary: winecfg doesn't open if using the intel xorg driver
Product: Wine
Version: 6.7
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ak-su(a)iname.com
Distribution: ---
Created attachment 69929
--> https://bugs.winehq.org/attachment.cgi?id=69929
winecfg 6.7 opening problem with intel xorg driver
If I am using the intel xorg driver with xorg:
Driver "intel" # xorg config snippet
winecfg from winehq-devel 6.7 is not able to open its window.
If I change to using the modesetting xorg driver in Fedora 33,
winecfg 6.7 opens properly.
But if I install winehq-stable 5.0.4-4.1, winecfg works just fine.
(In the attached log, I press ctrl+c at line 18)
--
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=50867
Bug ID: 50867
Summary: wine start /unix stopped working in 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: duck(a)duckcorp.org
Distribution: ---
Quack,
I just upgraded to 6.5 using WineHQ's Debian packages. My computer is using
Debian unstable.
When starting my games using start /unix I now get: (leaving out
fixme:font:opentype_enum_font_names lines)
$ wine start /unix $WINEPREFIX/drive_c/GOG\ Games/Risen\ 3\ -\ Titan\
Lords/LanguageSetup.exe
Application could not be started, or no application associated with the
specified file.
ShellExecuteEx failed: File not found.
If I remove start /unix in this case it works but not all programs will be
happy with this unless I manually go into the right workdir, that is why I use
this feature as recommended in the user's guide.
6.4 worked fine and many versions before. I did not see anything about this in
the news and changelog. Has anything changed?
Regards.
\_o<
--
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=49138
Bug ID: 49138
Summary: winegcc: argc and argv arguments of main() get
corrupted
Product: Wine
Version: 5.7
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: tools
Assignee: wine-bugs(a)winehq.org
Reporter: mail(a)robbertvanderhelm.nl
Distribution: ---
I first came across this issue with winelib compilation in Wine 5.7 while I was
working on yabridge, a Wine VST bridge. The issue still persists on the latest
commit in the Wine repository as I'm writing this (commit bf1abba, with the
release of Wine 5.8). I'm not exactly sure what is going on, but the issue can
be reproduced as follows:
#include <iostream>
int main(int argc, char* argv[]) {
std::cout << "argc = " << argc << std::endl;
std::cout << "argv[0] = " << argv[0] << std::endl;
}
If you compile the above (or the C-equivalent) with `wineg++ test.cpp -o test`
and run test.exe, then at least on my system it will always print 70624 as the
value of argc and some uninitialized looking data for argv[0]. This happens
regardless of whether the program receives any command line arguments or not.
Winelib applications compiled with the toolchain that comes with Wine 5.6 can
be
run without problems under Wine 5.7 or 5.8. The winelib compilation issue with
Wine 5.7+ exists on Ubuntu 18.04, Ubuntu 20.04, Arch Linux and Manjaro, both
when using the distro provided packages and when building Wine from source.
--
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=51002
Bug ID: 51002
Summary: Wined3d: nothing is presented in 3D window.
Product: Packaging
Version: unspecified
Hardware: x86-64
OS: Windows
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-packages
Assignee: wine-bugs(a)winehq.org
Reporter: acyellow(a)gmail.com
CC: dimesio(a)earthlink.net
Created attachment 69845
--> https://bugs.winehq.org/attachment.cgi?id=69845
d3d-error-log
OS: Windows OS
GPU is Nvidia and driver is installed correctly.
Use Wine dll to replace the original Windows dll, including d3d9.dll,
d3d11.dll, wined3d.dll, dxgi.dll.
Run the following D3D11 test case, the failed frame is attached. Nothing is
presented in the 3D window. There are error logs which is attached.
C:\Program Files (x86)\Microsoft DirectX SDK (June
2010)\Samples\C++\Direct3D11\Bin\x64\FluidCS11.exe
Any question or suggestion is welcome.
--
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=50939
Bug ID: 50939
Summary: Solid Edge 15: "MoveElementTo failed" when loading
document previously saved under Wine
Product: Wine
Version: 6.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ole32
Assignee: wine-bugs(a)winehq.org
Reporter: arvidb(a)fripost.org
Distribution: ---
Wine version: wine-6.5-157-gb0319c404a1 (master + applied patch for bug 50917).
When opening a document previously saved under Wine I have to dismiss several
"MoveElementTo failed" error messages. The documents eventually open
successfully (and open without error messages under Windows).
Documents saved under Windows does not exhibit this problem: they open without
error messages also under Wine.
Saving failed completely due to missing "VT_BLOB support" until very recently,
see bug 50917.
Terminal output when opening document (newline between each dismissal of error
- 2 times in this instance):
---
0024:fixme:shell:IPersistFile_fnSaveCompleted
(0xbf6468)->(L"C:\\users\\arvidb\\Recent\\AllenScrewM8.par (13).lnk"): stub
0024:fixme:storage:StorageBaseImpl_MoveElementTo (00C08420
L"\0005Rfunnyd1AvtdbfkuIaamtae3Ie" 00BF6530 L"\0005Rfunnyd1AvtdbfkuIaamtae3Ie"
1): stub
010c:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
010c:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
0024:fixme:reg:RegQueryInfoKeyA security argument not supported.
0024:fixme:reg:RegQueryInfoKeyA security argument not supported.
0024:fixme:reg:RegQueryInfoKeyA security argument not supported.
0024:fixme:reg:RegQueryInfoKeyA security argument not supported.
0024:fixme:reg:RegQueryInfoKeyA security argument not supported.
0024:fixme:reg:RegQueryInfoKeyA security argument not supported.
0024:fixme:reg:RegQueryInfoKeyA security argument not supported.
0024:fixme:reg:RegQueryInfoKeyA security argument not supported.
0024:fixme:reg:RegQueryInfoKeyA security argument not supported.
0024:fixme:reg:RegQueryInfoKeyA security argument not supported.
0024:fixme:reg:RegQueryInfoKeyA security argument not supported.
0024:fixme:reg:RegQueryInfoKeyA security argument not supported.
0024:fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (00B1CC3C 1 C) semi-stub
0024:fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (00B1C9F4 1 C) semi-stub
0024:fixme:storage:StorageBaseImpl_MoveElementTo (09E88B08
L"\0005C3teagxwOttdbfkuIaamtae3Ie" 00BD3778 L"\0005C3teagxwOttdbfkuIaamtae3Ie"
1): stub
0024:fixme:storage:Storage_ConstructTransacted Unimplemented flags 4110012
0024:fixme:reg:RegQueryInfoKeyA security argument not supported.
0024:fixme:reg:RegQueryInfoKeyA security argument not supported.
0024:fixme:reg:RegQueryInfoKeyA security argument not supported.
wine: Read access denied for device L"\\??\\E:\\", FS volume label and serial
are not available.
wine: Read access denied for device L"\\??\\Z:\\", FS volume label and serial
are not available.
---
--
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=50918
Bug ID: 50918
Summary: Solid Edge 15: Save as... cannot save file
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: arvidb(a)fripost.org
Distribution: ---
Created attachment 69732
--> https://bugs.winehq.org/attachment.cgi?id=69732
Terminal log
When trying to save a file using Save as... Solid Edge complains:
"Cannot save the file. You may not have write-access to the file or the
directory."
Simultaneously a line like this is displayed in the terminal:
0024:fixme:storage:StorageBaseImpl_MoveElementTo (0020DD28
L"\0005SummaryInformation" 0A217E98 L"\0005SummaryInformation" 1): stub
I have confirmed that I do have write access to the directory by creating an
empty file there with 'touch <filename>'.
--
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=50919
Bug ID: 50919
Summary: Solid Edge 15: Cannot finalize any feature
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: arvidb(a)fripost.org
Distribution: ---
Created attachment 69733
--> https://bugs.winehq.org/attachment.cgi?id=69733
Terminal log
To repeat: Start program, create new part, create new Protrusion (or Revolved
Protrusion). Click a reference plane and draw a Sketch (a simple square will
do). Click Finish.
Expected outcome: The program should switch to the next step of Protrusion
creation (depth options). New edit boxes and buttons should appear to the right
of the Finish button and the view should switch to isometric/3D.
Actual outcome: The program "mostly" stays in the first step: the view stays in
Sketch mode and no depth options appear, but the Sketch edit-boxes disappears
(see attached images).
When clicking the Finish button the following appears in the terminal:
0118:fixme:reg:RegQueryInfoKeyA security argument not supported.
0118:fixme:ole:OleSetMenuDescriptor (00000000, 000300C6, 00000000, 00000000,
0B798C88), Context sensitive help filtering not implemented!
0118:fixme:ole:OleSetMenuDescriptor (00000000, 000300C6, 00000000, 00000000,
0B798C88), Context sensitive help filtering not implemented!
0118:fixme:reg:RegQueryInfoKeyA security argument not supported.
<and after a short delay:>
0118:err:tooltips:TOOLTIPS_WindowProc unknown msg 041f wp=00000001 lp=00c2dcb4
--
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=5322
Mathew Hodson <mathew.hodson(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC|mathew.hodson(a)gmail.com |
--
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=5322
Mathew Hodson <mathew.hodson(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mathew.hodson(a)gmail.com
--- Comment #47 from Mathew Hodson <mathew.hodson(a)gmail.com> ---
(In reply to Anastasius Focht from comment #46)
> Hello folks,
>
> while revisiting old tickets I already stumbled across this one multiple
> times. Every time I have remember myself about the improper close here.
>
> In short: nothing was fixed here, VC6/VB6/eVC++ installers still crash due
> to missing HKEY_PERFORMANCE_DATA.
>
> https://bugs.winehq.org/show_bug.cgi?id=33037#c12
Shouldn't this bug be marked as a duplicate of bug 33037 then?
--
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=50332
Bug ID: 50332
Summary: Lara Croft Guardian Of Light crashes using new builtin
vulkan renderer
Product: Wine
Version: 5.20
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winevulkan
Assignee: wine-bugs(a)winehq.org
Reporter: andy86(a)fastwebnet.it
Distribution: ---
Created attachment 68919
--> https://bugs.winehq.org/attachment.cgi?id=68919
wine output in 6.0rc2 plus winedbg crash info in wine 5.20 and lcgol minidump
Lara Croft Guardian Of Light crashes immediately using new builtin vulkan
renderer.
I first found this in 5.20 or so, but it is still present in 6.0rc2.
In 5.20-5.21 winedbg open a popup with crash info at moment of the crash, in
6.0rc2 application handles crash itself and produce mdmp file.
--
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=4066
--- Comment #67 from Zebediah Figura <z.figura12(a)gmail.com> ---
(In reply to Linards from comment #66)
> (In reply to Orgad Shaneh from comment #65)
> > I gave up long ago :/
>
> Hmm. Sad :(
>
> So we theoretically should mark the unclosed bugs as WONTFIX-ABANDON?
No reason to do that. DirectPlay can be implemented; it's just that nobody is
working on it right now.
--
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=51056
Bug ID: 51056
Summary: The Sims Complete Collection intro audio is stuttering
Product: Wine
Version: 6.7
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: sashok.olen(a)gmail.com
CC: baskanov(a)gmail.com
Distribution: ---
Created attachment 69917
--> https://bugs.winehq.org/attachment.cgi?id=69917
standard output
When The Sims Complete Collection starts, the jingle in EA intro is not played
correctly. It stutters, going in and out.
Should be noted that this is not a new issue, this was still the case back when
the intro functionality finally started somewhat working last (?) year.
Attached is output with default debug channels. Let me know if more detailed
logging is needed.
--
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=51054
Bug ID: 51054
Summary: wine-staging 6.7 fails to build (user32-rawinput-hid
patch set is broken)
Product: Wine-staging
Version: 6.7
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dmitry(a)baikal.ru
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
wine-staging-6.7 fails to build:
clang -c -o dlls/hidclass.sys/pnp.cross.o dlls/hidclass.sys/pnp.c
-Idlls/hidclass.sys -Iinclude -Iinclude/msvcrt \
-D__WINESRC__ -D_UCRT -DWINE_CROSS_PE -Wall -target i686-windows
-fno-strict-aliasing \
-Wdeclaration-after-statement -Wempty-body -Wignored-qualifiers -Winit-self
-Wno-pragma-pack \
-Wstrict-prototypes -Wtype-limits -Wvla -Wwrite-strings -Wpointer-arith
-Wabsolute-value \
-fno-omit-frame-pointer -gdwarf-2 -gstrict-dwarf -g -O2
dlls/hidclass.sys/pnp.c:261:9: error: void function 'create_child' should not
return a value [-Wreturn-type]
return status;
^ ~~~~~~
1 error generated.
make[1]: *** [Makefile:60318: dlls/hidclass.sys/pnp.cross.o] Error 1
The problem is caused by
https://github.com/wine-staging/wine-staging/blob/master/patches/user32-raw…
--
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=4066
--- Comment #66 from Linards <linards.liepins(a)gmail.com> ---
(In reply to Orgad Shaneh from comment #65)
> I gave up long ago :/
Hmm. Sad :(
So we theoretically should mark the unclosed bugs as WONTFIX-ABANDON?
--
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=4066
--- Comment #65 from Orgad Shaneh <orgads(a)gmail.com> ---
I gave up long ago :/
--
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=6847
Linards <linards.liepins(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |linards.liepins(a)gmail.com
--- Comment #35 from Linards <linards.liepins(a)gmail.com> ---
(In reply to Rosanne DiMesio from comment #34)
> Updating URL field.
Any updates here?
--
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=4066
Linards <linards.liepins(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |linards.liepins(a)gmail.com
--- Comment #64 from Linards <linards.liepins(a)gmail.com> ---
(In reply to Orgad Shaneh from comment #63)
> Unit tests for dplayx (some tests are still skipped though).
Any updates here?
--
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=51022
Bug ID: 51022
Summary: ElevatedInstaller.exe crash
Product: Wine
Version: 6.6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: francoissylvain2(a)orange.fr
Distribution: ---
Created attachment 69870
--> https://bugs.winehq.org/attachment.cgi?id=69870
backtrace
Hello everybody
Ubuntu 20.10 + Wine 6.6.
I use the program Garmin Express to update my GPS.
The bug come when I use the program.
Could you help me please?
Thank you
--
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=48449
Bug ID: 48449
Summary: 'CreateProcess(0, "cmd /C [...]' fails when a trailing
newline follows a redirect in the cmdline
Product: Wine
Version: 5.0-rc5
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: timotheecisnard(a)gmail.com
Distribution: ---
Applications using CreateProcess to invoke "cmd.exe /C" followed by a command,
a redirect to a file, and a newline, result in an "Invalid name" error and the
command not being run. The expected result on Windows is for the trailing
newline to be silently ignored and not treated as part of the file name being
redirected into.
For example, the CreateProcess cmdline "cmd.exe /C echo OK >> test.log\n"
contains a (completely pointless) trailing newline.
Note that the newline is a literal trailing 0x0A character in a cmdline and NOT
an interactive user pressing Enter at a command prompt.
This issue is best reproduced with a 10 line C program:
https://paste.debian.net/1125644/
The bug originally affects ALDEC Active-HDL Lattice Edition 32bit version
10.5.216.6767, where compiling a project works but starting a simulation fails
at the linking step with cryptic errors like "Generation phase ... fail" and
"Error: E8005 : Kernel process initialization failed.".
--
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=42409
Bug ID: 42409
Summary: Tropico 5 has no sound
Product: Wine
Version: 2.1
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: yurishish(a)gmail.com
Distribution: ---
Tropico 5 has no sound. Pulseaudio control panel shows that this game has no
audio output.
Previous Tropico games (3 and 4) and native Linux vesion has no such problem.
Tested in wine 2.1 and 2.1-staging.
--
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=50358
Bug ID: 50358
Summary: Font spacing does not match windows rendering
Product: Wine
Version: 6.0-rc1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: minion.procyk(a)gmail.com
Distribution: ---
Created attachment 68956
--> https://bugs.winehq.org/attachment.cgi?id=68956
windows screenshot
I use project64 through wine using the AQZ Netplay Plugin. When the AQZ window
appears, the text should be aligned under the commands section, but it is not.
--
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=46277
Bug ID: 46277
Summary: Win32 Disk Imager fails to run
Product: Wine
Version: 4.0-rc1
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mrniex(a)protonmail.com
Distribution: ---
Created attachment 62986
--> https://bugs.winehq.org/attachment.cgi?id=62986
output of wine Win32DiskImager.exe
Win32 Disk Imager (https://sourceforge.net/projects/win32diskimager/) crashes
on startup with an error spam. On Wine-Staging the error spam does not happen,
but the stack overflow still happens and the program crashes.
--
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=49170
Bug ID: 49170
Summary: WoW (World of Warcraft) shows colored grass and mosaic
effects
Product: Wine
Version: 5.8
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: blue-t(a)web.de
Distribution: ---
Created attachment 67188
--> https://bugs.winehq.org/attachment.cgi?id=67188
colored chaos ingame
On the login Screen of my Game i have a colored mosaic effect instead of the
background.
Inside the game there is a rainbow colored grass and some parts of the
background are a colored mess.
No AntiAliasing is active and i run on medium settings.
This doesn't happen with the DX11 Legacy renderer or the dx11 renderer, just
dx12 so far.
--
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=42614
Bug ID: 42614
Summary: PowerPoint 2016 crashes during normal use
Product: Wine
Version: 2.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: isiraseneviratne(a)yahoo.com
Distribution: Ubuntu
Created attachment 57559
--> https://bugs.winehq.org/attachment.cgi?id=57559
Backtrace from PowerPoint 2016
PowerPoint 2016 tends to crash with the attached error message during normal
use.
--
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=50979
Bug ID: 50979
Summary: Regression: Wine doesn't run executables in unix path
Product: Wine
Version: 6.6
Hardware: x86-64
OS: Linux
Status: NEW
Severity: critical
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: zzhang(a)codeweavers.com
Distribution: ---
Similar to bug 50858
$ cp ~/.wine/drive_c/windows/notepad.exe ~/Downloads/notepad.exe
$ wine ~/Downloads/notepad.exe
0034:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
0034:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
0064:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
0064:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
006c:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
006c:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
002c:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
002c:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
[1] 385440 segmentation fault (core dumped) ~/src/wine/wow64-build/wine
~/Downloads/notepad.exe
$ which wine
wine: aliased to ~/src/wine/wow64-build/wine
Wine is built as WoW with 'cd wow64-build && ../configure -C CFLAGS="-g -Og"
CROSSCFLAGS="-g -Og" --enable-win64 --enable-silent-rules && make && cd
../wow32-build && ../configure -C CFLAGS="-g -Og" CROSSCFLAGS="-g -Og"
--with-wine64=../wow64-build --enable-silent-rules && make'
Bisect points to
commit f1e614027b5bb4129976ad5fca8caceac573f549
Author: Alexandre Julliard <julliard(a)winehq.org>
Date: Mon Apr 12 09:20:55 2021 +0200
ntdll: Take loadorder into account also for a main exe in .so format.
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=50956
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
In load_main_exe(), nt_name is used before it's initialized for unix file name.
Adding "init_unicode_string( &nt_name, *image );" before "loadorder =
get_load_order( &nt_name );" fixes it.
--
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=40567
Bug ID: 40567
Summary: Application Lock
Product: Wine
Version: 1.8.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: danieldimichel(a)gmail.com
Distribution: ---
Trying to run foobar 2000 either doesn't run at all or takes maybe 5 minutes to
open
danny@danny:~$ wine /home/danny/foobar2000_1.0/foobar2000.exe
fixme:module:load_dll Loader redirect from L"UxTheme.dll" to L"uxtheme-gtk.dll"
Gtk-Message: Failed to load module "unity-gtk-module"
Gtk-Message: Failed to load module "canberra-gtk-module"
Gtk-Message: Failed to load module "canberra-gtk-module"
fixme:msg:pack_message msg 14 (WM_ERASEBKGND) not supported yet
fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub
fixme:win:RegisterShellHookWindow (0x600c6): stub
fixme:uxthemegtk:SetWindowTheme (0x4026c, L"Explorer", (null))
err:ntdll:RtlpWaitForCriticalSection section 0x7bce8720 "directory.c:
dir_section" wait timed out in thread 0084, blocked by 0086, retrying (60 sec)
fixme:uxthemegtk:SetWindowTheme (0x50112, L"Explorer", (null))
fixme:uxthemegtk:SetWindowTheme (0x80102, L"Explorer", (null))
fixme:uxthemegtk:SetWindowTheme (0x8010c, L"Explorer", (null))
fixme:uxthemegtk:SetWindowTheme (0xa00de, L"Explorer", (null))
fixme:uxthemegtk:SetWindowTheme (0x600ca, L"Explorer", (null))
err:ntdll:RtlpWaitForCriticalSection section 0x7bce8720 "directory.c:
dir_section" wait timed out in thread 0084, blocked by 0086, retrying (60 sec)
err:ntdll:RtlpWaitForCriticalSection section 0x7bce8720 "directory.c:
dir_section" wait timed out in thread 0084, blocked by 0086, retrying (60 sec)
err:ntdll:RtlpWaitForCriticalSection section 0x7bce8720 "directory.c:
dir_section" wait timed out in thread 0084, blocked by 0086, retrying (60 sec)
fixme:uxthemegtk:DrawThemeText No color.
fixme:uxthemegtk:DrawThemeText No color.
fixme:uxthemegtk:DrawThemeText No color.
fixme:uxthemegtk:DrawThemeText No color.
fixme:uxthemegtk:DrawThemeText No color.
fixme:uxthemegtk:DrawThemeText No color.
fixme:uxthemegtk:DrawThemeText No color.
fixme:uxthemegtk:DrawThemeText No color.
fixme:uxthemegtk:DrawThemeText No color.
fixme:uxthemegtk:DrawThemeText No color.
fixme:uxthemegtk:DrawThemeText No color.
fixme:uxthemegtk:DrawThemeText No color.
fixme:uxthemegtk:DrawThemeText No color.
fixme:uxthemegtk:DrawThemeText No color.
fixme:uxthemegtk:DrawThemeText No color.
fixme:uxthemegtk:DrawThemeText No color.
err:ole:CoGetClassObject class {1968106d-f3b5-44cf-890e-116fcb9ecef1} not
registered
err:ole:CoGetClassObject class {1968106d-f3b5-44cf-890e-116fcb9ecef1} not
registered
err:ole:create_server class {1968106d-f3b5-44cf-890e-116fcb9ecef1} not
registered
fixme:ole:CoGetClassObject CLSCTX_REMOTE_SERVER not supported
err:ole:CoGetClassObject no class object {1968106d-f3b5-44cf-890e-116fcb9ecef1}
could be created for context 0x17
fixme:wininet:InternetSetOptionW Option INTERNET_OPTION_CODEPAGE (65001): STUB
fixme:wininet:InternetSetOptionW INTERNET_OPTION_CODEPAGE_PATH; STUB
fixme:wininet:InternetSetOptionW INTERNET_OPTION_CODEPAGE_EXTRA; STUB
fixme:uxthemegtk:DrawThemeText No color.
fixme:uxthemegtk:DrawThemeText No color.
fixme:uxthemegtk:DrawThemeText No color.
fixme:uxthemegtk:DrawThemeText No color.
--
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=51018
Bug ID: 51018
Summary: Binaries compiled with an older winegcc won't run on
>=v6.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: a.heider(a)gmail.com
Distribution: ---
An app built with an older winegcc (here v5.6) doesn't run on v6.6+ee13ab0:
Application could not be started, or no application associated with the
specified file.
ShellExecuteEx failed: File not found.
Trying with WINEDEBUG=module yields:
libwine.so.1: cannot open shared object file: No such file or directory
Even though that of course exists in the installed wine directory. Copying
libwine.so.1 from the wine directory next to the application gets rid of that
error message, but it still fails to run.
Building the app with winegcc from v6.6 works around the issue.
Note: It seems that only running apps are affected, dll files build with an
older winegcc still load fine
--
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=50956
Bug ID: 50956
Summary: Cannot disable winemenubuilder.exe by DLL override
Product: Wine
Version: 6.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: maciej.stanczew+b(a)gmail.com
Regression SHA1: 28fe84da45bea7de56539b50eac8ebcec54342de
Distribution: ArchLinux
(I'm not sure if this issue is already covered by other bug reports, but I
don't see this specific flow being described, so I'm submitting a new report.
Also this is still present in 6.6, so it's not related to bug 50867.)
Since 6.5 winemenubuilder.exe cannot be disabled using a DLL override.
Steps to reproduce:
1. Set WINEDLLOVERRIDES=winemenubuilder.exe=d, as described in FAQ[1]
2. Run winecfg to initialize new prefix
3. Run winecfg again
Expected results:
* 'applications', 'desktop-directories', 'icons', and 'mime' directories
normally created by winemenubuilder in $HOME/.local/share are not present
* Wine log shows:
0034:err:module:process_init L"C:\\windows\\system32\\winemenubuilder.exe" not
found
002c:err:wineboot:process_run_key Error running cmd
L"C:\\windows\\system32\\winemenubuilder.exe -a -r" (126).
Actual results:
* Directories above are created anyway
* Log doesn't show anything about winemenubuilder.exe being disabled
Bisection:
28fe84da45bea7de56539b50eac8ebcec54342de is the first bad commit
commit 28fe84da45bea7de56539b50eac8ebcec54342de
Author: Alexandre Julliard <julliard(a)winehq.org>
Date: Wed Mar 24 10:53:53 2021 +0100
ntdll: Load the main image from the Unix side.
My use case for disabling winemenubuilder is that I have two prefixes: one for
normal usage and one for testing.
First, I don't want MIME file associations in any of the prefixes. This can
also be achieved by unchecking "Manage file associations" after the first
winecfg (although it's a bit annoying to have to remember to do this every time
when creating a new prefix).
Second, I want .desktop files to be generated only for the main prefix, not the
testing one. I did this by setting the DLL override only in the testing prefix,
which now doesn't work.
I can temporarily achieve old behavior by removing winemenubuilder.exe from the
prefix, but it will be regenerated on prefix update, so it's not a sustainable
solution.
[1]
https://wiki.winehq.org/FAQ#How_can_I_prevent_Wine_from_changing_the_filety…
--
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=49277
Bug ID: 49277
Summary: Always false condition in dispex.c
Product: Wine
Version: 5.9
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: jscript
Assignee: wine-bugs(a)winehq.org
Reporter: mikrutrafal54(a)gmail.com
Distribution: ---
jsdisp->ctx == ctx so it can't be jsdisp->ctx != ctx
https://github.com/wine-mirror/wine/blob/59987bc9ecdd0dbafd768a95c21a14884b…
--
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=42775
Bug ID: 42775
Summary: Page fault while /regserver mwt.ext
Product: Wine
Version: 2.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: ole32
Assignee: wine-bugs(a)winehq.org
Reporter: joergen.vonbargen(a)minebea-intec.com
Distribution: ---
Created attachment 57787
--> https://bugs.winehq.org/attachment.cgi?id=57787
dump file of the page fault
Installing PR1750 ¹) fails with a page fault in ole32.
After installation failed, the program files remain in filesystem.
The page fault then can be reproduced with
wine ".wine/drive_c/Program Files (x86)/Sartorius/PR1750-60-R5/Mwt.exe"
/regserver
¹) https://appdb.winehq.org/objectManager.php?sClass=application&iId=18183
--
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=32548
Bug #: 32548
Summary: CS:GO error message when launching csgo,exe.
Product: Wine
Version: 1.5.17
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: linards.liepins(a)gmail.com
Classification: Unclassified
Created attachment 42953
--> http://bugs.winehq.org/attachment.cgi?id=42953
Bugreport for CS:GO.
Game almost instantly crashes with bugreport attached below.
--
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=50899
Bug ID: 50899
Summary: WeChat crashes with 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: lilydjwg(a)gmail.com
Distribution: ---
1. Download and install WeChat
download page: https://pc.weixin.qq.com/
file link: https://dldir1.qq.com/weixin/Windows/WeChatSetup.exe
sha1sum: c792c243149220df4a8d2699649a62687516cd40
2. Log in
You'll need an account, which requires a phone number to register
3. Find a conversation with some messages and click
These messages can come from either a previous version or via message sync
provided when logging into the applicaion
4. If it didn't crash, try scroll up the conversion
9bdfb1f34a4f512488c198555249a49f4e7c1172 is the first bad commit
commit 9bdfb1f34a4f512488c198555249a49f4e7c1172
Author: Alexandre Julliard <julliard(a)winehq.org>
Date: Thu Mar 25 12:05:41 2021 +0100
ntdll: Set the initial DllPath to null if it's empty.
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
dlls/ntdll/unix/env.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Crash logs:
04a4:fixme:richedit:ME_GetTextEx GETTEXTEX flags 0x00000004 not supported
04a4:fixme:richedit:ME_GetTextEx GETTEXTEX flags 0x00000004 not supported
04a4:fixme:win:RegisterTouchWindow (000B0094 00000000): stub
04a4:fixme:win:RegisterTouchWindow (000C007C 00000000): stub
04a4:fixme:richedit:ME_GetTextEx GETTEXTEX flags 0x00000004 not supported
04a4:fixme:wincodecs:jpeg_decoder_get_metadata_blocks stub
06c8:fixme:wtsapi:WTSRegisterSessionNotification Stub 000A0060 0x00000000
04a4:fixme:richedit:ME_GetTextEx GETTEXTEX flags 0x00000004 not supported
0604: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 distri
bution.
0604:fixme:heap:RtlSetHeapInformation 00000000 1 00000000 0 stub
[0331/222109:INFO:exception_record.cc(518)] [QB]Process ID: 968 Type: 2
0604:fixme:ntdll:EtwEventRegister ({d2d578d9-2936-45b6-a09f-30e32715f42d},
10133990, 1382DD80, 138A8108) stub.
0604:fixme:gdi:GdiInitializeLanguagePack stub
0604:fixme:ntdll:NtQuerySystemInformation info_class
SYSTEM_PERFORMANCE_INFORMATION
[0331/222109:FATAL:scoped_handle.cc(116)] Check failed: false.
Backtrace:
cef_time_to_timet [0x04D219C1+633457]
CLInfo [0x04D5AD28+230136]
CLInfo [0x04D5ADB1+230273]
CLInfo [0x04D4675C+146732]
EntryPoint [0x06FEB6FC+3775997]
EntryPoint [0x06FEBBAA+3777195]
GetHandleVerifier [0x05386B07+6469335]
GetHandleVerifier [0x0538719E+6471022]
GetHandleVerifier [0x05384230+6458880]
GetHandleVerifier [0x0609F7E5+20202421]
GetHandleVerifier [0x060A0236+20205062]
GetHandleVerifier [0x04D5CD97+6503]
CLInfo [0x04D358A9+77433]
CLInfo [0x04D3513C+75532]
GetHandleVerifier [0x04D5D9FA+9674]
GetHandleVerifier [0x04D5E4BA+12426]
CLInfo [0x04D355A1+76657]
CLInfo [0x04D2D8E5+44725]
TerminateProcessWithoutDump [0x063EC4EF+17263]
TerminateProcessWithoutDump [0x063ECC02+19074]
CLInfo [0x04D2DD1D+45805]
CLInfo [0x04D3F132+116482]
GetThreadSelectorEntry [0x7B64DD60+16]
RtlProcessFlsData [0x7BC77EB7+5383]
RtlProcessFlsData [0x7BC780CA+5914]
(No symbol) [0x00000000]
01fc:fixme:heap:RtlSetHeapInformation 00000000 1 00000000 0 stub
033c:fixme:resource:GetGuiResources (0000088C,0): stub
0058:fixme:mountmgr:query_property Faking StorageDeviceProperty data
--
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=46309
Bug ID: 46309
Summary: Winamp with Classic Skin "jumps randomly" when moved
Product: Wine
Version: 4.0-rc2
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: winex11.drv
Assignee: wine-bugs(a)winehq.org
Reporter: gabrielopcode(a)gmail.com
Distribution: ---
Split from https://bugs.winehq.org/show_bug.cgi?id=15346
When you move Winamp with classic skin, it jumps around randomly. The faster
you move it, the more pronounced this effect is. Eventually it will disappear
because it will touch an edge of the screen (but that has more to do with the
original bug which is a separate problem).
This is probably due to the fact that we use window-relative coordinates and
then translate to screen coordinates ourselves, but those window-relative
aren't synced perfectly with the cursor since Winamp chooses to reposition
itself when moved.
This should be possible to fix by simply using the X-server-supplied
root-relative coordinates and we can even get rid of the redundant
transformations after that, as we have them already in screen coordinates (with
slight translation), which should even simplify the code on top of it...
--
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=50996
Bug ID: 50996
Summary: GCC11 & wineg++ fatal error: stdlib.h: No such file
Product: Wine
Version: 6.6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: patrick+winehq.org(a)laimbock.com
Distribution: ---
Created attachment 69835
--> https://bugs.winehq.org/attachment.cgi?id=69835
Yabridge: add missing #include <optional>
Thank you for wine. On Fedora 34 with GCC11 I'm trying to build yabridge which
uses wineg++. Requires headers (glibc-devel, stdc++-devel, boost-devel, etc are
all installed)
Builds (not) with GCC11 (wine means wine+staging):
Wine 6.3 | Wine 6.6
------------------------------------
Yabridge 3.0.2 Y [1] | N
Yabridge HEAD Y [1] | N
[1] requires attached patch which adds a missing #include <optional> which was
not required with GCC10.
Error:
FAILED: libvst3_base_wine_64bit.a.p/subprojects_vst3_base_source_fbuffer.cpp.o
wineg++ -Ilibvst3_base_wine_64bit.a.p -I. -I.. -I/usr/include
-fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -std=c++2a -O3 -fPIC
-isystem../subprojects/vst3 -isystemsubprojects/vst3 -DRELEASE=1 -DNOMINMAX
-DWINE_NOWINSOCK -m64 -Wno-cpp -MD -MQ
libvst3_base_wine_64bit.a.p/subprojects_vst3_base_source_fbuffer.cpp.o -MF
libvst3_base_wine_64bit.a.p/subprojects_vst3_base_source_fbuffer.cpp.o.d -o
libvst3_base_wine_64bit.a.p/subprojects_vst3_base_source_fbuffer.cpp.o -c
../subprojects/vst3/base/source/fbuffer.cpp
In file included from ../subprojects/vst3/base/source/fbuffer.cpp:40:
/usr/include/c++/11/cstdlib:75:15: fatal error: stdlib.h: No such file or
directory
75 | #include_next <stdlib.h>
| ^~~~~~~~~~
compilation terminated.
winegcc: /usr/bin/g++ failed
My wine/gcc/c++ foo is limited but I'm happy to provide additional information
you require. Thanks.
--
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=45615
Bug ID: 45615
Summary: Rekordbox 5.3.0 terminates with the message
"Unexpected application error"
Product: Wine
Version: 3.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: bghome(a)gmail.com
Distribution: ---
Created attachment 62043
--> https://bugs.winehq.org/attachment.cgi?id=62043
Console output of winedbg
The application crashes with "Unexpected application error" when I load an
audio file into the player.
As the page fault occurred in the rekordbox process, I tried to trace back the
code to the nearest DLL method call, but couldn't.
What I have found so far:
- page fault at address: 140636460
- call comes from subroutine at address: 1408f76d0
- call comes from address 1435C3D40 instruction: IPtoStateMap <rva
loc_1408F7836, 2>
--
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=38572
Bug ID: 38572
Summary: NHL09 Crashing when loading game after selecting all
options in game menus
Product: Wine
Version: 1.7.40
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: ---
Created attachment 51468
--> https://bugs.winehq.org/attachment.cgi?id=51468
NHL09 Game loading crash after game option adjusting
I can only get attached screenshot. Mouse and keyboard inresponsive.
--
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=44691
Bug ID: 44691
Summary: EA origin install error 3:0
Product: Wine
Version: 3.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: maxi.cass11(a)gmail.com
Distribution: ---
Hi, I have tried to install origin with wine 3.3 on a clean wine Prefix on my
computer but with the full version I get an error 3:0
I think it's a permission issue because when you want to look on the Origin
folder it have a locker on it.
And this is the permission of the files:
drwxrwxr-x 7 amosar amosar 4096 Mar 9 00:40 .
drwxrwxr-x 6 amosar amosar 4096 Mar 9 00:39 ..
drwxrwxr-x 4 amosar amosar 4096 Mar 9 00:39 Common Files
drwxrwxr-x 2 amosar amosar 4096 Mar 9 00:39 Internet Explorer
dr-xr-xr-x 2 amosar amosar 4096 Mar 9 00:40 Origin
drwxrwxr-x 2 amosar amosar 4096 Mar 9 00:39 Windows Media Player
drwxrwxr-x 3 amosar amosar 4096 Mar 9 00:39 Windows NT
--
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=41468
Bug ID: 41468
Summary: Supreme Commander Forged Alliance needs CLSID
'{343e68e6-8f82-4a8d-a2da-6e9a944b378c}'
xactengine2_9.dll
Product: Wine
Version: 1.9.20
Hardware: x86-64
OS: Linux
Status: NEW
Severity: minor
Priority: P2
Component: xactengine
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
CC: aeikum(a)codeweavers.com
Distribution: ---
err:ole:CoGetClassObject class {343e68e6-8f82-4a8d-a2da-6e9a944b378c} not
registered
err:ole:CoGetClassObject no class object {343e68e6-8f82-4a8d-a2da-6e9a944b378c}
could be created for context 0x1
wine-1.9.20-92-g1dedd90
--
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=34398
Bug #: 34398
Summary: Daedalic games don't display anything with winemac.drv
Product: Wine
Version: 1.7.1
Platform: x86
OS/Version: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winemac.drv
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: thanoulas(a)gmail.com
Classification: Unclassified
Created attachment 45793
--> http://bugs.winehq.org/attachment.cgi?id=45793
err+all,fixme+all With winemac driver
The games "Chains of Satinav" and "Memoria" show a black display when using the
winemac driver. They both work fine when using the x11 driver.
I've attached a log
--
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=50892
Bug ID: 50892
Summary: WINE 6.3: opentrack-wrapper-wine segfaults with
message "Got unexpected trap 14 during process
initialization".
Product: Wine
Version: 6.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: xeno(a)x-s.com.pl
Distribution: ---
As per Summary opentrack-wrapper-wine.exe.so process (opentrack trackir and
freetrack protocols wrapper) crashes just after launch. If started from console
with
env WINEPREFIX=<my_wine_prefix_path> wine
/usr/lib64/opentrack/opentrack-wrapper-wine.exe.so
it crashes spitting out message:
00fc:err:seh:segv_handler_early Got unexpected trap 14 during process
initialization
Once wine is downgraded to 5.x (here tested with 5.18 and 5.22) wrapper process
starts just fine and stays on until headtracking is stopped.
Tested with opentrack 2.3.12 and 2.3.13, wine 6.3.
Steps to reproduce:
start opentrack
select pointtracker as input, accela as filter wine as output
configure wine output plugin and point it to wine prefix where app that uses
headtracking is installed
start headtracking
start app/game from
Expected result:
- opentrack-wrapper-wine.exe.so stays in the list of active processes
- headtracking works in games/apps running in wine.
Actual results:
- opentrack-wrapper-wine.exe.so process appears for a brief moment then
instantly closes
- headtracking works in opentrack preview window but not in a apps running in
wine.
OpenTrack is fa opensource project obtainable from github:
https://github.com/opentrack/opentrack
I can provide rough but working Fedora x86_64 rpm if needed.
--
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=48486
Bug ID: 48486
Summary: cmd WCMD_ReadAndParseLine contains non-null terminated
strings, causing garbage output in trace logs
Product: Wine
Version: 5.0-rc6
Hardware: x86
OS: Linux
Status: NEW
Severity: trivial
Priority: P2
Component: cmd
Assignee: wine-bugs(a)winehq.org
Reporter: focht(a)gmx.net
Distribution: ---
Hello folks,
as it says. It's already PE but various strings have not been converted yet.
The function in the summary is the one most offending/annoying in trace logs.
There are other occurrences as well.
Example download:
https://github.com/git-for-windows/git/releases/download/v2.25.0.windows.1/…
--- snip ---
...
006a:Call KERNEL32.MultiByteToWideChar(000001b5,00000000,00bd7a78 "\t\t@IF NOT
EXIST bin\\rebase.exe @(\n\t\t\t@IF NOT EXIST bin @MKDIR bin\n\t\t\t@COPY
usr\\bin\\rebase.exe bin\\rebase.exe\n\t\t)\n\t\t@IF NOT EXIST
bin\\msys-2.0.dll @(\n\t\t\t@COPY usr\\bin\\msys-2.0.dll
bin\\msys-2.0.dll\n\t\t)\n\t\t(a)bin\\rebase.exe -b 0x64000000
usr\\bin\\msys-2.0.dll\n"...,00000021,00be5238,00002000) ret=00401a09
006a:Ret KERNEL32.MultiByteToWideChar() retval=00000021 ret=00401a09
006a:Call KERNEL32.HeapFree(00110000,00000000,00bd7a78) ret=00401a22
006a:Ret KERNEL32.HeapFree() retval=00000001 ret=00401a22
006a:Call msvcrt.wcschr(00be523c L"@IF NOT EXIST bin\\rebase.exe @(",00000025)
ret=004137f3
006a:Ret msvcrt.wcschr() retval=00000000 ret=004137f3
006a:Call KERNEL32.CompareStringW(00000400,00001001,00be523e L"IF NOT EXIST
bin\\rebase.exe @(",00000003,0041b706
L"remforifelse\4357\444d\525f\6165\4164\646e\6150\7372\4c65\6e69e\6f4e\6320\6d6f\616d\646e\6e20\726f\6820\6e61\6c64\2065\7573\7070\696c\6465\necho.echo:echo/\764f\7265\6c66\776f\6420\7465\6365\6574\2064\6e69\6320\6d6f\616d\646e\ndo/I",00000003)
ret=00411489
006a:Ret KERNEL32.CompareStringW() retval=00000001 ret=00411489
006a:Call KERNEL32.CompareStringW(00000400,00001001,00be523e L"IF NOT EXIST
bin\\rebase.exe @(",00000003,0041b70c
L"forifelse\4357\444d\525f\6165\4164\646e\6150\7372\4c65\6e69e\6f4e\6320\6d6f\616d\646e\6e20\726f\6820\6e61\6c64\2065\7573\7070\696c\6465\necho.echo:echo/\764f\7265\6c66\776f\6420\7465\6365\6574\2064\6e69\6320\6d6f\616d\646e\ndo/I",00000003)
ret=004115c0
006a:Ret KERNEL32.CompareStringW() retval=00000003 ret=004115c0
006a:Call KERNEL32.CompareStringW(00000400,00001001,00be523e L"IF NOT EXIST
bin\\rebase.exe @(",00000002,0041b712
L"ifelse\4357\444d\525f\6165\4164\646e\6150\7372\4c65\6e69e\6f4e\6320\6d6f\616d\646e\6e20\726f\6820\6e61\6c64\2065\7573\7070\696c\6465\necho.echo:echo/\764f\7265\6c66\776f\6420\7465\6365\6574\2064\6e69\6320\6d6f\616d\646e\ndo/I",00000002)
ret=004115fa
006a:Ret KERNEL32.CompareStringW() retval=00000002 ret=004115fa
...
--- snip ---
Wine source:
https://source.winehq.org/git/wine.git/blob/02f3a133b64ed1f979309e1399738ea…
$ sha1sum Git-2.25.0-32-bit.exe
7dc64019c089d4a9a3700ee7140a7af9a5416199 Git-2.25.0-32-bit.exe
$Â du -sh Git-2.25.0-32-bit.exe
45M Git-2.25.0-32-bit.exe
$Â wine --version
wine-5.0-rc6
Regards
--
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=50978
Bug ID: 50978
Summary: Adobe DNG converter 13.2 fails to launch
Product: Wine
Version: 6.6
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: z.figura12(a)gmail.com
Regression SHA1: 42de71c38780931c510ada6d7ee8681c99bbc60b
Distribution: ---
With:
0024:err:module:import_dll Library version.dll (which is needed by
L"C:\\windows\\system32\\setupapi.dll") not found
followed by cascading messages culminating in
0024:err:module:LdrInitializeThunk Importing dlls for
L"Z:\\bridge\\Downloads\\AdobeDNGConverter_x64_13_2.exe" failed, status
c0000135
The application has a manifest, which includes the following:
<file name="mpr.dll" loadFrom="%SystemRoot%\system32\" />
<file name="netapi32.dll" loadFrom="%SystemRoot%\system32\" />
<file name="netutils.dll" loadFrom="%SystemRoot%\system32\" />
<file name="version.dll" loadFrom="%SystemRoot%\system32\" />
find_actctx_dll() mishandles this and returns the executable path, which
obviously doesn't contain version.dll. Fixing it may require some research.
This is a regression—it worked in 6.4. It's probably a regression from
42de71c3878, since previously we would load builtin version.dll regardless, but
I can't bisect as other regressions prevent Wine from working at that point.
--
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=50801
Bug ID: 50801
Summary: Wine Mono crashes on macOS
Product: Wine
Version: 6.4
Hardware: x86-64
OS: Mac OS X
Status: NEW
Severity: normal
Priority: P2
Component: mscoree
Assignee: wine-bugs(a)winehq.org
Reporter: madewokherd(a)gmail.com
Running the csc.exe shipped with Wine Mono on macOS 11.2.1 crashes with:
0024:err:virtual:virtual_setup_exception stack overflow 1456 bytes in thread
0024 addr 0x7bc2bd61 stack 0x130a50 (0x130000-0x131000-0x230000)
>From a +relay,+seh log, trimmed by thread:
0024:Call msvcrt.memcpy(0022dec0,02950f35,00000010) ret=1801013e1
0024:Ret msvcrt.memcpy() retval=0022dec0 ret=1801013e1
0024:trace:seh:dispatch_exception code=c0000005 flags=0 addr=0000000002951170
ip=0000000002951170 tid=0024
0024:trace:seh:dispatch_exception info[0]=0000000000000001
0034:Call KERNEL32.HeapFree(00020000,00000000,000b96f0) ret=68765c83
0024:trace:seh:dispatch_exception info[1]=0000000000000498
0024:warn:seh:dispatch_exception EXCEPTION_ACCESS_VIOLATION exception
(code=c0000005) raised
0024:trace:seh:dispatch_exception rax=0000000000000498 rbx=0000000000000000
rcx=0000000000000001 rdx=0000000000000010
0024:trace:seh:dispatch_exception rsi=0000000000000010 rdi=0000000000a24dd0
rbp=000000000022e2c0 rsp=000000000022e270
0024:trace:seh:dispatch_exception r8=000000000022e5f0 r9=0000000002950f00
r10=000000000000000a r11=0000000002950f64
0024:trace:seh:dispatch_exception r12=0000000000a32e88 r13=000000000022e928
r14=000000000022e5f0 r15=0000000000000000
0024:trace:seh:call_vectored_handlers calling handler at 00000001801038F0
code=c0000005 flags=0
I haven't been able to get winedbg working well enough to give me any real
information, but that memcpy call is from the end of
mono_breakpoint_clean_code.
I also got this from WINE_MONO_VERBOSE=1:
Method (wrapper alloc) object object:AllocSmall (intptr,intptr) emitted at
0000000002951110 to 000000000295123b (code length 299) [csc.exe]
So we're crashing on access to JIT-compiled code. There's probably a way to
tell from the +seh log whether that's on execute access, but I'm just going to
assume it is.
--
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=50415
Bug ID: 50415
Summary: MPC-HC 1.7.13 crashes when playing video (needs the
EVR filter to support IEVRFilterConfig)
Product: Wine
Version: 6.0-rc4
Hardware: x86-64
URL: https://github.com/mpc-hc/mpc-hc/releases/tag/1.7.13
OS: Linux
Status: NEW
Keywords: download, patch, source
Severity: normal
Priority: P2
Component: quartz
Assignee: wine-bugs(a)winehq.org
Reporter: z.figura12(a)gmail.com
Distribution: ---
Created attachment 69035
--> https://bugs.winehq.org/attachment.cgi?id=69035
evr: Stub IEVRFilterConfig.
The attached patch helps; it falls back to the VMR.
Continued from bug 45096.
--
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=44755
Bug ID: 44755
Summary: reg.exe: does not provide /reg:64 switch in 64-bit
wineprefix
Product: Wine
Version: 3.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: registry
Assignee: wine-bugs(a)winehq.org
Reporter: wine(a)marco-rebhan.de
Distribution: ---
In a 64-bit prefix, the reg.exe command line switches /reg:32 and /reg:64
should be available to enable/disable registry redirection.
A command like `wine reg import /reg:64 test.reg` should be perfectly valid, to
prevent the imported keys from going somewhere in Wow6432Node, but instead it
gives the following error:
reg: Invalid syntax. Type "REG IMPORT /?" for help.
As far as I could figure out, there is no workaround other than manually
importing the keys in the regedit GUI (calling regedit from the command line
with the registry file as an argument doesn't work), which makes importing keys
correctly not automatable.
Using wine-3.4 staging
--
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=28995
Bug #: 28995
Summary: Unable to use named pipes with ">" character in the
name
Product: Wine
Version: 1.3.32
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: kernel32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: valentyn.pavliuchenko(a)gmail.com
Classification: Unclassified
I have an app (Avid VENUE software) that uses pipes to work. The app fails to
launch because of pipe name contains a character ">".
MSDN says:
The pipename part of the name can include any character other than a backslash,
including numbers and special characters. The entire pipe name string can be up
to 256 characters long. Pipe names are not case sensitive.
App logs show the following:
23.957 CreateFile error '\\.\PIPE\D-Show Pipe GUI->DM': Invalid name.
Changing ">" to "_" by direct editing executable files makes problem disappear.
--
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=17823
Summary: A crash when installing Rhino 4.0 trial version
Product: Wine
Version: 1.1.17
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: major
Priority: P3
Component: msi
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: andrej(a)podzimek.org
Created an attachment (id=20083)
--> (http://bugs.winehq.org/attachment.cgi?id=20083)
Output from the installer
When installing a trial version of Rhino 4.0 obtained from here
http://download.rhino3d.com/eval/?p=25, the installer reports successful
completion. However, the terminal output shows a crash.
Presumably, Rhino crashes when run after the installation. A small part of the
GUI is displayed, but remains unresponsive. A dialog window for error-reporting
pops up.
--
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=50898
Bug ID: 50898
Summary: Improve performance for RGB lookups into color tables
conversion
Product: Wine
Version: 6.5
Hardware: x86-64
OS: Linux
Status: NEW
Severity: enhancement
Priority: P2
Component: gdi32
Assignee: wine-bugs(a)winehq.org
Reporter: gabrielopcode(a)gmail.com
Distribution: ---
Created attachment 69710
--> https://bugs.winehq.org/attachment.cgi?id=69710
Generate a lookup cache for RGB into color table conversion
This improves the performance of color conversion from RGB to palette
significantly by generating a lookup cache for 5-bit-per-color RGB values
(centered) into the palette, before doing the conversion, for older
applications and games. The comments in the patch should describe the algorithm
I came up with for large color tables.
Note that Windows also quantizes the lookup to 5-bit-per-color already, so it
very likely does something similar (but seems to do more caching based on my
tests); we have this quantization in wine's code to match Windows, but we don't
take advantage of it, so it's wasted.
Generating it by looking through the color table for each entry in the lookup
cache wouldn't be a good idea if the color table is large. The lookup cache
itself is 32768 entries, which turns out to be the equivalent of a 256x128
image. The current algorithm used by wine works like that already: it goes
through each pixel in the image, and for each pixel, it looks up every color in
the color table, which is extremely slow. Generating the cache like that would
mean images have to be at least 256x128 for it to have any benefit, otherwise
it would be a performance regression instead, and that's not very reasonable to
expect of older applications, and it wouldn't provide much.
So, the table generation algorithm is much more efficient than that for large
amount of colors in the table. In my synthetic tests generating 4096 tables
with various color tables of 256 colors, it turned out to be at least 4x
faster, sometimes even 4.5x depending on color table (even a purely random
color table), for example a random table taking about 14406ms instead of
62056ms on my CPU.
In fact, the algorithm is not far from being constant in terms of amount of
colors in the table, taking only 50% more time from 16 colors to 256. So
basically increasing the amount of colors from 16 to 256 doesn't make that much
difference, since each color usually fills its own part of the lookup cache,
which is not filled again (unless distance is shorter due to quantization, but
that's only for one generation anyway). In contrast, going through each color
in the table for each entry (the original algorithm) would massively increase
the amount of time spent (from less than 10 seconds, up to more than a minute,
or 6x slower).
For a few benchmark examples: a 256-color table with the algorithm takes about
14000ms to do 4096 iterations on my CPU, a 40-color table takes about 12000ms,
so it's only 17% slower with this algorithm. The 40 colors seems to be the
cutoff on my CPU where the algorithms start to differ in performance, with the
straight one being faster at lower amount of colors, presumably due to better
cache locality and branch prediction.
A fast and easy way to "see this in action" is to download Winamp, then launch
it and right-click on the top, click on the "Nullsoft Winamp..." menu item and
then go to the Credits tab. Depending on your CPU you can clearly see the FPS
difference and/or CPU usage for one core. (Note that it still has some fps
drops, this is normal and happens on Windows as well, even when the CPU core is
not maxed out, it's inherent in the app)
http://web.archive.org/web/20180902190237/http://winamparchive.org/dl/winam…
Further improvements would require caching it somehow between calls, but I
believe that requires either more fragile changes to gdi32 code, or semi-hacks
to deal with a typical applications' expectations, so this should be a good
start for now.
--
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=25265
Summary: Foobar2000 won't watch folders
Product: Wine
Version: 1.3.7
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: lucisandor(a)gmail.com
Foobar2000 is a media player with an automatically updated media library. The
library updates correctly when updates are triggered manually, but, under Wine,
it does not detect changes in folders.
Moreover, Foobar2000 provides for such cases a "polling" function, but that is
useless too.
The most upsetting is that changes in watched folders are not detected even
when they were produced by Fooobar2000, e.g., by using the menu option "move
file". If I move a file from one watched folder to another, the media library
will not be aware of the changes in any of the two locations.
--
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=50894
Bug ID: 50894
Summary: Starting rundll32.exe via sysnative fails
Product: Wine
Version: 6.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: rpisl(a)seznam.cz
Distribution: ---
Starting rundll32 via c:\windows\sysnative\rundll32.exe is broken since Wine
6.5. It worked up to Wine 6.4.
wine cmd
c:\>cd c:\windows\sysnative
c:\windows\sysnative>dir
... files listed properly
c:\windows\sysnative>rundll32.exe
wine: failed to open L"c:\\windows\\sysnative\\rundll32.exe": c0000135
Can't recognize 'rundll32.exe' as an internal or external command, or batch
script.
Creating unix symlink from sysnative to system32 in wine prefix is a
workaround.
--
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=49671
Bug ID: 49671
Summary: Supreme Commander demo needs CLSID
{bc3e0fc6-2e0d-4c45-bc61-d9c328319bd8}
xactengine2_4.dll
Product: Wine
Version: 5.14
Hardware: x86-64
URL: https://download.cnet.com/Supreme-Commander-demo/3000-
7483_4-10637347.html
OS: Linux
Status: NEW
Keywords: download
Severity: minor
Priority: P2
Component: xactengine
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
Distribution: ---
0024:err:ole:CoGetClassObject class {bc3e0fc6-2e0d-4c45-bc61-d9c328319bd8} not
registered
0024:err:ole:CoGetClassObject no class object
{bc3e0fc6-2e0d-4c45-bc61-d9c328319bd8} could be created for context 0x1
wine-5.14-132-g1ec8bf9b73
--
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=49286
Bug ID: 49286
Summary: Melodyne 5 crashes due to unimplimented
WS2_32.dll.GetHostNameW
Product: Wine-staging
Version: 5.9
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ToxicBugzilla(a)outlook.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 67291
--> https://bugs.winehq.org/attachment.cgi?id=67291
The backtrace.
Installed Melodyne 5 trial
(https://services.celemony.com/cgi-bin/WebObjects/LicenseApp.woa/wa/demoRegi…)
with mfc42, vcrun6, and vcrun2019 installed in a 64 bit prefix due to Melodyne
5 only working in 64 bit now. (installer will crash without it due to missing
dll contained, plus Melodyne 5 needs vcrun2019 from my research) Installer
works fine, (b47a56f747bf3a477f2a564ee65eb005d40e6ef7 setup.exe)
but launching the resulting Melodyne.exe
(e9b21aa11efbbc01d76df17ee4e7a421c2186986 [sha1 of Melodyne.exe could vary due
to unique installs on every computer? unsure, but setup.exe should stay the
same) itself will give this in the terminal:
002c:fixme:winediag:__wine_start_process Wine Staging 5.8 is a testing version
containing experimental patches.
002c:fixme:winediag:__wine_start_process Please mention your exact version when
filing bug reports on winehq.org.
00c0:fixme:msvcrt:MSVCRT__stdio_common_vsnwprintf_s options 24 not handled
00c0:fixme:msvcrt:MSVCRT__stdio_common_vsnwprintf_s options 24 not handled
00c0:fixme:msvcrt:MSVCRT__stdio_common_vsprintf_s options 24 not handled
00c0:fixme:msvcrt:MSVCRT__stdio_common_vsprintf_s options 24 not handled
00c0:fixme:msvcrt:MSVCRT__stdio_common_vsprintf_s options 24 not handled
00c0:fixme:msvcrt:MSVCRT__stdio_common_vsprintf_s options 24 not handled
00c0:fixme:msvcrt:MSVCRT__stdio_common_vsprintf_s options 24 not handled
00c0:fixme:msvcrt:MSVCRT__stdio_common_vsprintf_s options 24 not handled
00c0:fixme:ole:CoInitializeSecurity
(0000000000000000,-1,0000000000000000,0000000000000000,0,3,0000000000000000,0,0000000000000000)
- stub!
00c0:fixme:msvcrt:MSVCRT__stdio_common_vsprintf_s options 24 not handled
00c0:fixme:msvcrt:MSVCRT__stdio_common_vsprintf_s options 24 not handled
00c0:fixme:msvcrt:MSVCRT__stdio_common_vsprintf_s options 24 not handled
00c0:fixme:msvcrt:MSVCRT__stdio_common_vsprintf_s options 24 not handled
00c0:fixme:msvcrt:MSVCRT__stdio_common_vsprintf_s options 24 not handled
00c0:fixme:msvcrt:MSVCRT__stdio_common_vsprintf_s options 24 not handled
00c0:fixme:msvcrt:MSVCRT__stdio_common_vsnprintf_s options 24 not handled
00c0:fixme:ntdll:NtQuerySystemInformation info_class
SYSTEM_PERFORMANCE_INFORMATION
wine: Call from 0x7bc8b9ac to unimplemented function WS2_32.dll.GetHostNameW,
aborting
wine: Unimplemented function WS2_32.dll.GetHostNameW called at address
000000007BC8B9AC (thread 00c0), starting debugger...
Due to being unable to find any mention of it anywhere except for Microsoft's
website noting of its addition, this is probably a bug in normal Wine &
development as well, but I have yet to test due to time constraints.
Also, when opening "show details" in the debugger,
"00c8:fixme:dbghelp:elf_search_auxv can't find symbol in module" get spammed in
the terminal excessively. (62 times)
--
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.