https://bugs.winehq.org/show_bug.cgi?id=54480
Bug ID: 54480
Summary: GPU Caps Viewer does not report any CUDA devices
Product: Wine-staging
Version: 8.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: danielyhwong(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
wine version 8.1 does not report any cuda devices in Caps viewer 1.58.01
$ deviceQuery
deviceQuery Starting...
CUDA Device Query (Runtime API) version (CUDART static linking)
Detected 2 CUDA Capable device(s)
CUDA
https://i.imgur.com/zbTiqfC.png
OpenCL
https://i.imgur.com/jvu8nde.png
--
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=55159
Bug ID: 55159
Summary: [ms-mpi] mpiexec is unable to connect to the smpd
service
Product: Wine
Version: 8.0.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: secur32
Assignee: wine-bugs(a)winehq.org
Reporter: christian.friedl(a)gmx.at
Distribution: Ubuntu
Created attachment 74727
--> https://bugs.winehq.org/attachment.cgi?id=74727
Output of `smpd.exe -d` and `mpiexec -d -hosts 1 127.0.0.1 notepad`
Running applications with MS-MPI does not work. In order to circumvent
https://bugs.winehq.org/show_bug.cgi?id=50341 I started smpd.exe manually with:
$ wine 'C:\Program Files\Microsoft MPI\Bin\smpd.exe' -d
In a second shell I ran mpiexec:
$ wine mpiexec -d -hosts 1 127.0.0.1 notepad
The problem is that mpiexec.exe could not connect to smpd.exe because both
kerberos and ntlm authentication fail.
I have the version 2:4.15.13+dfsg-0ubuntu1.1 of the winbind package installed.
The installed MS-MPI version is v10.1.2. Logs including the debug channels
`+kerberos,+ntlm,+secur32,+wininet,+seh,+tid` are attached.
--
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=55162
Bug ID: 55162
Summary: Halo 2: Installer shows empty ie-window
Product: Wine
Version: 8.8
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: odecif(a)gmail.com
Distribution: ---
Created attachment 74732
--> https://bugs.winehq.org/attachment.cgi?id=74732
console log, 32bit with ie6 installed, after starting "Startup.exe"
I do not know why the previous bug was closed in 2015
(https://bugs.winehq.org/show_bug.cgi?id=17543), but the same error still
persists today.
When executing "Startup.exe" on the CD in a clean 32-bit (and 64-bit as well)
prefix a blue windows pops up dislaying absolutely nothing presented (see
image).
If I install ie6 (winetricks ie6) an error pops up (see image).
Attached is a stacktrace of what exists in the console after executing
"Startup.exe" from wineconsole with ie6 installed.
Br
Bob
--
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=55163
Bug ID: 55163
Summary: compact.exe missing
Product: Wine
Version: 8.10
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: sakul8826(a)gmail.com
Distribution: ---
Hello,
I wanted to use "compact.exe," which is a part of the default Windows 10
installation. I selected "Windows 10" in winecfg, and it appears that
compact.exe is missing. I need this program to compress my content (cars, apps,
etc.) in Assetto Corsa's Content Manager to reduce their size. I have very
limited storage available, and this program (compact.exe) would be extremely
helpful. I believe it should be relatively simple to implement this since we
could use a Linux compression and decompression tool.
Are there any plans to implement this?
Thank you in advance.
Best regards,
Tim Gromeyer
--
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=37664
Bug ID: 37664
Summary: CUDA encoder does not work on MediaCoder x64 0.8.33
build 5680
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: rickardj42(a)gmail.com
Distribution: ---
Created attachment 50128
--> https://bugs.winehq.org/attachment.cgi?id=50128
Screenshot of the error message
In MediaCoder x64 0.8.33 build 5680 attempting to select GPU encoder causes
error "No supported acceleration hardware detected", dispite the presence of an
NVidia GeForce 750ti in my system. Attempting to force GPU encoding using CUDA
encoder results in Error (14) on all items(general encoder error).
--
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=55157
Bug ID: 55157
Summary: Net6 x64 app: unable to allocate more than ~1GB of
contiguous memory, OutOfMemory exception
Product: Wine
Version: 8.11
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: korshunov(a)macroscop.com
Distribution: ---
A "big" net6 app may throw an OutOfMemory exception at some point in time. It
was found that the exception occurs when the size of byte array is increased
and exception is repeatable 100% - it always fails when byte array resized from
26mb to 53mb.
Since big app is hard to debug, a simple test app was written, all it tries to
do is to resize array x2 in a loop. Test app fails with dotnet OutOfMemory
exception 100% of the time, but in the test app the "limit" at which it fails
is different, about ~1gb or "Failed at resizing from 534773760 to 1069547520".
Here's the code of the test app:
var array = new byte[1023];
while (true)
try
{
Array.Resize(ref array, array.Length * 2);
}
catch (Exception ex)
{
Console.WriteLine($"Failed at resizing from {array.Length} to
{array.Length * 2}\r\n" + ex);
return;
}
Test app is built for "AnyCPU, x64 preferred". Net6 runtime (6.0.16) is
installed via winetricks. For the tests, x86 version of net6 runtime has been
uninstalled, so the test app is guaranteed to run in x64. Test app is available
via the link below.
What I've already tried:
- wine 8.11 staging - fails with OutOfMemory exception, "Failed at resizing
from 534773760 to 1069547520". WINEDEBUG output available through the link
below.
- wine 8.0 with patch from https://bugs.winehq.org/show_bug.cgi?id=52396 -
fails with same error. WINEDEBUG output available through the link below.
- running app with wine64, used clean prefix - same error.
- wine 7.13 - fails with same error.
- wine 8.11, but test app built for netFramework46 - no OutOfMemory, fails when
overflowing integer, "Failed at resizing from 2139095040 to -16777216" which is
expected, but it shows that it gets to 2gb mark for the array. I consider this
as "working fine". WINEDEBUG output available through the link below.
- WineGE with multiple versions from 6.14 to 8.8, consisting of Proton and
WineGE patches - net6 app working fine with every wineGE version tested, just
as netFramework Test app
- created prefix with wine 8.11, run test app, then run test app with WineGE in
the same exact prefix - wine fails with OutOfMemory while wineGE executes app
normally.
- made different net6 app, which just allocates a single array of ~1.5 GB (new
byte[1_500_000_000]) - app fails with OutOfMemory every time. It fails at about
1GB (950mb works, while 1050mb does not)
Tests were done on three different virtual machines (ubuntu22, centos7,
debian9) with different amount of RAM (4-8 GB, swap is 2.5GB). Wine 8.11 is
installed on Ubuntu 22 with 4GB RAM.
What caught my attention in the logs was the message "find_free_block created
new sub-heap xxx of 0x400000 bytes" (4GB, all of the RAM), which mentioned in
"net6" logs 1 time, and not mentioned in "netFramework46" logs.
What else can I try to fix this or to provide more information?
Links to a WINEDEBUG output (wine8.11-net6, wine8.11-netFramework46, "wine 8.0
with patch"-net6), logs taken with command
WINEDEBUG=+timestamp,+seh,+heap,+virtual,+pid wine
Tests_autoresize/Tests_net6.exe >>wine811_tshvp_net6_resize.log 2>&1
https://drive.google.com/drive/folders/1fgr0J6dKBvBOHWrfYC0UCrflxiAYOjZ2?us…
--
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=55098
Bug ID: 55098
Summary: wine 8.10 32-bit build fails with clang-16
Product: Wine
Version: 8.10
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: randrik(a)mail.ru
Distribution: ---
I tried to build new wine with llvm/clang 16.0.6 and gcc 11.2 (on Slackware
15.0 i586 upgraded manually from earlier vesrions). Kernel is x86_64 but al
userland is i586/i686
Build via slackbuild fails like this:
(will attach end of build log as attach)
--
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=54739
Bug ID: 54739
Summary: oleaut32:typelib - The 64-bit
test_register_typelib_64() crashes in Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: oleaut32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
oleaut32:typelib - The 64-bit test_register_typelib_64() crashes in Wine:
typelib.c:7057: Test failed: got 00000002
typelib.c:8195: Test failed: got wrong return code: 2, side: 0200
typelib.c:8231: Test failed: got: 80040155, side: 0200
typelib.c:8235: Test failed: got: 80040154, side: 0200
Unhandled exception: page fault on read access to 0x0000000000000000 in 64-bit
code (0x00000000428dc1).
[...]
Backtrace:
=>0 0x00000000428dc1 in oleaut32_test (+0x28dc1) (0x0000000050e538)
1 0x000000004460c8 in oleaut32_test (+0x460c8) (0x000000621080c0)
2 0x0000000050dbeb in oleaut32_test (+0x10dbeb) (0x00000000ab4415)
3 0x0000000050d447 in oleaut32_test (+0x10d447) (0000000000000000)
4 0x0000007b629409 BaseThreadInitThunk+0x9(unknown=<internal error>,
entry=<internal error>, arg=<internal error>)
[Z:\home\winetest\tools\testbot\var\wine\dlls\kernel32\thread.c:61] in kernel32
(0000000000000000)
5 0x00000170061213 __wine_pop_frame(entry=000000000050D3E0,
arg=00000000003F0000)
[Z:\home\winetest\tools\testbot\var\wine\include\wine\exception.h:277] in ntdll
(0000000000000000)
6 0x00000170061213 RtlUserThreadStart+0x83(entry=[<register RSP not
accessible in this frame>, arg=[<register RSP not accessible in this frame>)
[Z:\home\winetest\tools\testbot\var\wine\dlls\ntdll\thread.c:295] in ntdll
(0000000000000000)
0x00000000428dc1 oleaut32_test+0x28dc1: mov (%rcx), %rax
See https://test.winehq.org/data/patterns.html#oleaut32:typelib
Where:
2 == ERROR_FILE_NOT_FOUND
0x80040154 == REGDB_E_CLASSNOTREG
0x80040155 == REGDB_E_IIDNOTREG
--
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=50938
Bug ID: 50938
Summary: Stop alt key from getting stuck on alt-tab
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: sojuz151(a)gmail.com
Distribution: ---
When you use alt-tab shortcut to switch to another window and then switch back
in, application will at no point receive alt key up signal. User needs to press
alt again to make this key unstuck. This behevior is observed in Plasma and in
lxde, both of them use alt-tab for windows switching.
Behaviour on windows:
alt key is not stuck in down position after alt-tabing out of any application
How to test:
this can be observed in any keyboard testing program. I used switch hitter for
testing.
Is it really a bug?
Maybe not. Still very annoying in full-screen games.
--
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.