https://bugs.winehq.org/show_bug.cgi?id=55070
Bug ID: 55070
Summary: winemenubuilder adds incorrect prefix on 32bit only
Wine
Product: Wine
Version: 8.10
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dofficialgman(a)gmail.com
Distribution: ---
On 32bit (x86 only) wine, the Exec= line automatically created in an
application's .desktop file is incorrect and can not be launched.
eg: /home/gman/.local/share/applications/wine/Programs/7-Zip/7-Zip\ File\
Manager.desktop
```
[Desktop Entry]
Name=7-Zip File Manager
Exec=env WINEPREFIX="/home/gman/.wine/dosdevices/f:/home/gman/.wine" wine
C:\\\\users\\\\gman\\\\AppData\\\\Roaming\\\\Microsoft\\\\Windows\\\\Start\\
Menu\\\\Programs\\\\7-Zip\\\\7-Zip\\ File\\ Manager.lnk
Type=Application
StartupNotify=true
Icon=EA23_7zFM.0
StartupWMClass=7zfm.exe
```
64bit (x64 with WOW64) wine does not have this issue and the generated .desktop
file will be correct.
eg: /home/gman/.local/share/applications/wine/Programs/7-Zip/7-Zip\ File\
Manager.desktop
```
[Desktop Entry]
Name=7-Zip File Manager
Exec=env WINEPREFIX="/home/gman/.wine" wine
C:\\\\users\\\\gman\\\\AppData\\\\Roaming\\\\Microsoft\\\\Windows\\\\Start\\
Menu\\\\Programs\\\\7-Zip\\\\7-Zip\\ File\\ Manager.lnk
Type=Application
StartupNotify=true
Icon=EA23_7zFM.0
StartupWMClass=7zfm.exe
```
Both are with fresh wine installs with fresh/clean prefixes. Confirmed on
multiple devices.
--
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=54183
Bug ID: 54183
Summary: wineserver crash when running d3d9:visual
Product: Wine
Version: 8.0-rc1
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: testcase
Severity: normal
Priority: P2
Component: wineserver
Assignee: wine-bugs(a)winehq.org
Reporter: z.figura12(a)gmail.com
CC: rbernon(a)codeweavers.com
Distribution: ---
d3d9:visual on this machine breaks somewhere in the middle, apparently while
trying to do mode switches, and leaves the display switched off. Not sure what
triggers it exactly; I've certainly had working runs on other machines. What's
important is that then when d3d9_test.exe exits, it triggers a wined3d crash.
Simple tl;dr version is that set_cursor_pos gets triggered not from a client
request, and tries to access current->process, which crashes.
The backtrace is:
Core was generated by `/home/elizabeth/git/wine64/loader/../server/wineserver
-d'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00005598e8b43ac0 in set_cursor_pos (desktop=desktop@entry=0x5598ea1ce5d0,
x=32767, y=32767) at ../wine/server/queue.c:427
427 if ((device = current->process->rawinput_mouse) && (device->flags &
RIDEV_NOLEGACY))
(gdb) bt
#0 0x00005598e8b43ac0 in set_cursor_pos (desktop=desktop@entry=0x5598ea1ce5d0,
x=32767, y=32767) at ../wine/server/queue.c:427
#1 0x00005598e8b43c7b in set_clip_rectangle
(desktop=desktop@entry=0x5598ea1ce5d0, rect=rect@entry=0x0,
send_clip_msg=send_clip_msg@entry=1) at ../wine/server/queue.c:476
#2 0x00005598e8b43da1 in set_foreground_input (input=0x0,
desktop=0x5598ea1ce5d0) at ../wine/server/queue.c:483
#3 set_foreground_input (input=0x0, desktop=0x5598ea1ce5d0) at
../wine/server/queue.c:480
#4 thread_input_destroy (obj=0x5598ea1ba430) at ../wine/server/queue.c:1106
#5 0x00005598e8b3b144 in release_object (ptr=0x5598ea1ba430) at
../wine/server/object.c:451
#6 release_object (ptr=0x5598ea1ba430) at ../wine/server/object.c:440
#7 0x00005598e8b43800 in msg_queue_destroy (obj=0x5598ea1ae4d0) at
../wine/server/queue.c:1077
#8 0x00005598e8b3b144 in release_object (ptr=0x5598ea1ae4d0) at
../wine/server/object.c:451
#9 release_object (ptr=ptr@entry=0x5598ea1ae4d0) at
../wine/server/object.c:440
#10 0x00005598e8b3224e in release_object_from_handle (obj=0x5598ea1ae4d0) at
../wine/server/handle.c:115
#11 handle_table_destroy (obj=0x5598ea1d3810) at ../wine/server/handle.c:185
#12 0x00005598e8b3b144 in release_object (ptr=0x5598ea1d3810) at
../wine/server/object.c:451
#13 release_object (ptr=0x5598ea1d3810) at ../wine/server/object.c:440
#14 0x00005598e8b3260f in close_process_handles
(process=process@entry=0x5598ea1ce7a0) at ../wine/server/handle.c:197
#15 0x00005598e8b3d990 in process_killed (process=0x5598ea1ce7a0) at
../wine/server/process.c:970
#16 remove_process_thread (process=0x5598ea1ce7a0,
thread=thread@entry=0x5598ea1d4020) at ../wine/server/process.c:1020
#17 0x00005598e8b5b37f in kill_thread (thread=0x5598ea1d4020,
violent_death=<optimized out>, violent_death@entry=0) at
../wine/server/thread.c:1294
#18 0x00005598e8b3dcb0 in kill_process (violent_death=0,
process=0x5598ea1ce7a0) at ../wine/server/process.c:1077
#19 kill_process (process=0x5598ea1ce7a0, violent_death=<optimized out>) at
../wine/server/process.c:1058
#20 0x00005598e8b2d587 in fd_poll_event (event=<optimized out>, fd=<optimized
out>) at ../wine/server/fd.c:542
#21 main_loop_epoll () at ../wine/server/fd.c:636
#22 0x00005598e8b2d7ee in main_loop () at ../wine/server/fd.c:992
#23 0x00005598e8b1ea7d in main (argc=2, argv=0x7ffd26625e48) at
../wine/server/main.c:237
Rémi, do you have any immediate insight on what we should be doing 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.
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=9127
Zeb Figura <z.figura12(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Fixed by SHA1| |e8e5e8b5c94f7ec7dfd00fc7684
| |be4f7263fe725
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #112 from Zeb Figura <z.figura12(a)gmail.com> ---
Fixed upstream by
<https://source.winehq.org/git/wine.git/commitdiff/e8e5e8b5c94f7ec7dfd00fc76…>.
--
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=55782
Bug ID: 55782
Summary: System.Windows.Forms expects CreateActCtx() to succeed
with truncated ACTCTX structure
Product: Wine
Version: 8.17
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: source, testcase
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: dmitry(a)baikal.ru
Distribution: ---
Major versions of .Net installed by winetricks (including 4.0, 4.52, 4.72, 4.8)
are affected by this bug.
According to
https://github.com/dotnet/winforms/blob/4.8/src/Common/src/UnsafeNativeMeth…
internal definition of ACTCTX is missing hModule field, and as a result cbSize
doesn't match the expectations of Wine's CreateActCtx() implementation
https://github.com/dotnet/winforms/blob/4.8/src/Common/src/UnsafeNativeMeth…
The following MR aims to fix this bug:
https://gitlab.winehq.org/wine/wine/-/merge_requests/3839
--
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=55742
Bug ID: 55742
Summary: wine crashes when launching Captvty V3
Product: Wine
Version: 8.17
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: gerard.labadie(a)sysgroup.fr
Distribution: ---
Created attachment 75245
--> https://bugs.winehq.org/attachment.cgi?id=75245
the backtrace
I suppose wine 8.17 is installed and an up to date winetricks is present
download the zip on
http://v3.captvty.fr/
mkdir .captvty_v3
unzip -d .captvty_V3 captvty-3.0.1.2.zip
export WINEARCH=win32
export WINEPREFIX=~/.wine_captvty_V3
wineboot --update
winetricks -q --force dotnet48 corefonts
wget http://captvty.fr/getgdiplus -O kb958869.exe
wine kb958869.exe /x:kb958869 /q
cp kb958869/SP3QFE/asms/10/msft/windows/gdiplus/gdiplus.dll
${WINEPREFIX}/drive_c/windows/system32
wine reg add HKCU\\Software\\Wine\\DllOverrides /v gdiplus /d native,builtin /f
Now launch it
wine .captvty_V3/Captvty.exe
on
https://forum.winehq.org/viewtopic.php?t=38088&sid=186a660110f0fdd03b8ff77e…
JKFloris said it was a bug
before the backtrace
wine Captvty.exe
0090:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0090:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0090:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0090:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
00e0:fixme:ntdll:NtQuerySystemInformation info_class
SYSTEM_PERFORMANCE_INFORMATION
00e0:fixme:ntdll:EtwEventSetInformation (deadbeef, 2, 10003241, 28) stub
00e0:fixme:ntdll:EtwEventSetInformation (deadbeef, 2, 011B09AD, 28) stub
00e0:fixme:heap:GetNumaHighestNodeNumber semi-stub: 009EFC74
00e0:fixme:seh:WerRegisterRuntimeExceptionModule
(L"C:\\windows\\Microsoft.NET\\Framework\\v4.0.30319\\mscordacwks.dll",
011A0000) stub
00e8:err:ole:CoGetContextToken apartment not initialised
00e0:fixme:virtual:NtFlushProcessWriteBuffers stub
00e0:fixme:nls:get_dummy_preferred_ui_language (0x8 0x413 009ECF20 00000000
009ECF24) returning a dummy value (current locale)
00e0:fixme:nls:get_dummy_preferred_ui_language (0x8 0x413 009ECF20 00F46898
009ECF24) returning a dummy value (current locale)
00e0:fixme:ntdll:NtQuerySystemInformation
(0x000000ce,0x9ee9f4,0x00000008,(nil)) stub
00e0:fixme:bcrypt:BCryptGetFipsAlgorithmMode 009EE81C - semi-stub
00e0:fixme:nls:LCMapStringEx unsupported lparam f49150
00e0:fixme:advapi:RegisterEventSourceW ((null),L".NET Runtime"): stub
00e0:fixme:advapi:ReportEventW
(CAFE4242,0x0001,0x0000,0x00000402,00000000,0x0001,0x00000000,009EE1C0,00000000):
stub
00e0:err:eventlog:ReportEventW L"Application: Captvty.exe\n"
00e0:err:eventlog:ReportEventW L"Framework Version: v4.0.30319\n"
00e0:err:eventlog:ReportEventW L"Description: The process was terminated due to
an unhandled exception.\n"
00e0:err:eventlog:ReportEventW L"Exception Info:
System.EntryPointNotFoundException\n"
00e0:err:eventlog:ReportEventW L" at _SpA._rsA()\n"
00e0:err:eventlog:ReportEventW L" at _SpA..ctor()\n"
00e0:err:eventlog:ReportEventW L" at _2ob._5yA()\n"
00e0:err:eventlog:ReportEventW L"\n"
00e0:fixme:advapi:DeregisterEventSource (CAFE4242) stub
wine: Unhandled exception 0xe0434352 in thread e0 at address 7B012407 (thread
00e0), starting debugger...
previous versions of Captvty V3 worked, so this may be a regression in
Captvty.exe ou in wine 8.17
--
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=53213
Bug ID: 53213
Summary: d3d11:d3d11 - test_texture() fails in the TestBot VMs
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
d3d11:d3d11 - test_texture() fails in the TestBot VMs:
d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xff0000ff at (0, 0).
d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xff00ffff at (1, 0).
d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xff00ff00 at (2, 0).
d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xffffff00 at (3, 0).
d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xffff0000 at (0, 1).
d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xffff00ff at (1, 1).
d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xff000000 at (2, 1).
d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xff7f7f7f at (3, 1).
d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xffffffff at (0, 2).
d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xffffffff at (1, 2).
d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xffffffff at (2, 2).
d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xff000000 at (3, 2).
d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xffffffff at (0, 3).
d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xff000000 at (2, 3).
d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xff000000 at (3, 3).
https://test.winehq.org/data/patterns.html#d3d11:d3d11
These failures don't happen on my box which has an Intel graphics card instead
of QEmu's QXL graphics card.
Note also that these failures still happen on my debian11 VM which has a single
monitor instead of the TestBot VMs' multi-monitor setup.
So this seems to be related to the VMs QXL GPU.
Note that despite being systematic these failures could cause false positives
(see bug 53212).
--
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.