http://bugs.winehq.org/show_bug.cgi?id=28659
Bug #: 28659
Summary: rpcrt4/server test crashes on 32-bit FreeBSD9
Product: Wine
Version: 1.3.30
Platform: x86
OS/Version: FreeBSD
Status: NEW
Keywords: download, source, testcase
Severity: normal
Priority: P2
Component: rpc
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: austinenglish(a)gmail.com
Classification: Unclassified
Created attachment 36831
--> http://bugs.winehq.org/attachment.cgi?id=36831
backtrace
The rpcrt4/rpc test fails as well, but that may be related to missing ntlm_auth
(which I haven't found how to satisfy on FreeBSD). The server test shows that
same error, but also crashes, so something nastier is going on.
Backtrace attached.
--
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=52720
Bug ID: 52720
Summary: cmd.exe:batch times out in Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: cmd
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
cmd.exe:batch started timing out in Wine on 2022-03-17:
batch.c:427: running TEST_CMDLINE.CMD test...
cmd.exe:batch:040c done (258) in 120s
Test failed: timed out
https://test.winehq.org/data/patterns.html#cmd.exe:batch
Unfortunately I was unable to find a change in Wine that would be the cause for
the timeout: in my tests cmd.exe:batch still times out when run from older Wine
versions.
* Based on the WineTest logs cmd.exe:batch was taking about 50 seconds up to
2022-03-16. But the next day that run time more than doubled to about 118 - 170
seconds, causing it to time out most of the time.
* Reverting the Wine source to the 2022-03-16 head, rebuilding from scratch and
recreating the wineprefix did not help: cmd.exe:batch still times out.
* No package upgrades were performed on that date. Plus this regression
happened simultaneously on multiple machines with different upgrade schedules.
* WINETEST_TIME=1 indicates that almost all of the time is spent running
TEST_BUILTINS.CMD:
batch.c:427:0.149 running TEST_BUILTINS.CMD test...
batch.c:136:158.289 Test succeeded
^^^ The first ok() call after WaitForSingleObject() is in the map_file() called
after run_test()
* Running the test manually it looked like the "--- for /R" "Plain directory
enumeration" part of test_builtins.cmd was enumerating all of the computer's
directories, starting with /bin, /boot, /etc, ... That would certainly take a
long time but that run crashed after about 1 minute so this may be unrelated.
--
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=22904
Summary: Register URL protocol handlers under Linux
Product: Wine
Version: unspecified
Platform: All
OS/Version: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: programs
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: kempe.marcus(a)gmail.com
winemenubuilder is able to automatically register file type associations and
build menus under Linux, when triggered by an application under wine.
It would be great if the same thing were true for protocol handlers, so that
these would become registered in much the same way as when using gconftool in
gnome:
gconftool -s /desktop/gnome/url-handlers/spotify/command 'wine
c:\\spotify\\spotify.exe %s' --type String
gconftool-2 -s /desktop/gnome/url-handlers/spotify/enabled --type Boolean true
Would this be possible, hard, or maybe not a good idea?
--
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=16214
Summary: Copy command does not work as expected
Product: Wine
Version: 1.0.1
Platform: Other
OS/Version: other
Status: NEW
Severity: enhancement
Priority: P2
Component: dos
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: scott(a)open-vote.org
>From Launchpad: https://bugs.edge.launchpad.net/ubuntu/+source/wine/+bug/272921
In Windows, the COPY command run in a command prompt allows users to
concatenate files by using a plus ("+") operator, for example:
copy file1+file2 outfile
In wine's cmd.exe, it seems to read file1+file2 as a single path and therefore
outputs a "Path Not Found". Also, it does not recognize the "con" keyword used
to represent stdout/stdin. Therefore another method of concatenating files:
copy file1 outfile
copy file2 con >> outfile
does not work either.
My Ubuntu version is 8.04, AMD64 architecture, though I have seen the same
issue on the x86 version as well.
--
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=20474
Summary: Wine can't be built with GCC in C99 mode
Product: Wine
Version: unspecified
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: build-env
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: yann(a)droneaud.fr
For multiple reason, wine can't be built by GCC in C99 mode ( --std=c99 ).
In particular, wine rely on GCC behavor regarding to extern inline.
It produces errors regarding asm construct conflicting with extern
inline symbols.
It produces errors with multiple defination of inline function in object files.
According to this, it seems that wine is not compatible with C99, but rely a
lot on GCC specific behavor.
See also bug #20306
--
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=16552
Summary: CreateIoCompletionPort fails in Chromium unit tests
Product: Wine
Version: 1.1.10
Platform: Other
URL: http://chromium.org
OS/Version: other
Status: NEW
Keywords: download, source
Severity: normal
Priority: P2
Component: wineserver
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dank(a)kegel.com
http://src.chromium.org/viewvc/chrome/trunk/src/base/message_pump_win.cc
contains the code
port_.Set(CreateIoCompletionPort(INVALID_HANDLE_VALUE, NULL, NULL, 1));
DCHECK(port_.IsValid());
...
HANDLE port = CreateIoCompletionPort(file_handle, port_, key, 1);
DCHECK(port == port_.Get());
The DCHECK fires when running one of the Chromium unit tests:
wine Debug/ui_tests.exe
...
001b:Call KERNEL32.CreateFileW(00ed7208
L"\\\\.\\pipe\\chrome.ChromeTestingInterface:8.1",c0000000,00000000,00000000,00000003,40110000,00000000)
ret=010e0220
001b:Ret KERNEL32.CreateFileW() retval=000000c0 ret=010e0220
...
0021:Call KERNEL32.CreateIoCompletionPort(ffffffff,00000000,00000000,00000001)
ret=01a304b3
0021:Ret KERNEL32.CreateIoCompletionPort() retval=000000c8 ret=01a304b3
0021:Call KERNEL32.CreateIoCompletionPort(000000c0,000000c8,00ed5aa0,00000001)
ret=01a30760
trace:ntdll:NtSetInformationFile
(0xc0,0x7cdee318,0x7cdee320,0x00000008,0x0000001e)
0021:Ret KERNEL32.CreateIoCompletionPort() retval=00000000 ret=01a30760
0021:Call KERNEL32.OutputDebugStringA(00ed95a8
"[26:33:1249:FATAL:message_pump_win.cc(428)] Check failed: port == port_.Get().
\r\n") ret=019a7af3
I think it's failing in wineserver for some reason during NtSetInformationFile
in set_completion_info.
--
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=52792
Bug ID: 52792
Summary: Error messages for invalid .exe files could be
improved
Product: Wine
Version: 7.6
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: wineserver
Assignee: wine-bugs(a)winehq.org
Reporter: aros(a)gmx.com
Distribution: ---
Trying to run a 0 byte .exe file under Wine will get you this:
Application could not be started, or no application associated with the
specified file.
ShellExecuteEx failed: File not found.
This doesn't look correct.
--
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=48004
Bug ID: 48004
Summary: winserver memory overflow
Product: Wine
Version: 4.0.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wineserver
Assignee: wine-bugs(a)winehq.org
Reporter: heiko(a)stark-jena.de
Distribution: ---
with default and 'wineserver -d2 -f -p10' settings
I run simulations with the software Opensim (https://opensim.stanford.edu/) and
restart the Opensim one after the other with a script. This seems to cause a
memory overflow (> 64 GB).
Kill wineserver helps to fix the memory overflow.
Is there a way to debug this?
Best regards,
Heiko
--
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=52716
Bug ID: 52716
Summary: Sending key stroke (using
[System.Windows.Forms.SendKeys]::SendWait) fails
(seems to go into a loop?)
Product: Wine
Version: 7.4
Hardware: x86-64
URL: https://github.com/PowerShell/PowerShell/releases/down
load/v7.0.3/PowerShell-7.0.3-win-x64.msi
OS: Linux
Status: NEW
Keywords: dotnet, download
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: xerox.xerox2000x(a)gmail.com
Distribution: ---
Created attachment 72077
--> https://bugs.winehq.org/attachment.cgi?id=72077
ps script
Hi, I have a powershell script where I need to send a keystroke to a program.
I found code snippet on the internet and made little script that I tested in
windows (using powershell core) and it works.
It sends ctrp^p to notepad, and that opens the printer-dialog correctly on
windows.
On wine however it doesn`t work, cpu-usage goes up so it seems to get into
loop(???)
Script (also see attachment):
###################################################################
Start-Process "notepad.exe"
Sleep 3
$WindowHandle = Get-Process | Where-Object { $_.MainWindowTitle -Match
"Notepad" } | Select-Object -ExpandProperty MainWindowHandle
[void][System.Reflection.Assembly]::LoadWithPartialName('System.Windows.Forms')
[System.Windows.Forms.SendKeys]::SendWait("^{p}")
#####################################################################
Steps to reproduce:
1. winetricks -q dotnet48
2. wget
https://github.com/PowerShell/PowerShell/releases/download/v7.0.3/PowerShel…
3. wine PowerShell-7.0.3-win-x64.msi
4. Save the script from attachment as a.ps1 in current folder
5. wine pwsh -file ./a.ps1
Notepad opens but nothing really happens and cpu-usage goes up
--
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=49988
Bug ID: 49988
Summary: NosTale (and probably some other games) doesn't handle
mouse clicks correctly
Product: Wine
Version: 5.19
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: theszczepancio(a)gmail.com
Distribution: ---
Created attachment 68390
--> https://bugs.winehq.org/attachment.cgi?id=68390
Wine-staging 5.19 log
Releated issues:
https://bugs.winehq.org/show_bug.cgi?id=42999https://bugs.winehq.org/show_bug.cgi?id=21739
Some info:
Tested the issue with wine and wine-staging.
Bug persists in 5.17, 5.18, 5.19 versions of wine.
I have installed Arch Linux on r5 3600/rx5700 XT.
I use D9VK (newest) for improvements of performance.
Installing dinput8 is not fixing anything.
I use Sway/wlroots on wayland, also I own newest kernel.
Game works as should on steam proton with same version of D9VK.
OpenGL backend works fine.
Wine log in attachement.
--
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.