https://bugs.winehq.org/show_bug.cgi?id=8780
--- Comment #32 from Nikolay Sivov <bunglehead(a)gmail.com> ---
It should create SLTG typelibs I believe, so the patch is wrong.
--
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=8780
Fabian Maurer <dark.shadow4(a)web.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dark.shadow4(a)web.de
--- Comment #31 from Fabian Maurer <dark.shadow4(a)web.de> ---
Also affects Visual Pinball, see the forum thread:
https://forum.winehq.org/viewtopic.php?t=37788
Is there plans to have …
[View More]this upstreamed?
--
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.
[View Less]
https://bugs.winehq.org/show_bug.cgi?id=55168
Bug ID: 55168
Summary: BUSY 21 Installer silently exists with Windows version
set to Win10
Product: Wine
Version: 8.10
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dark.shadow4(a)web.de
Distribution: ---
…
[View More]Workaround is "winetricks winxp"
--
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.
[View Less]
https://bugs.winehq.org/show_bug.cgi?id=55147
Bug ID: 55147
Summary: Enter key isn't working in my VB6 Application
Product: Wine
Version: 8.5
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: vbscript
Assignee: wine-bugs(a)winehq.org
Reporter: vikasy.enjay(a)gmail.com
Distribution: ---
The Application is successfully …
[View More]installed in a 32 bit prefix but when i run the
application then on a certain form where Enter Key and Backspace keys are used
for moving to next and previous text fields respectively, it doesn't work.
And when i run the same application in windows Enter key and Backspace key
works perfectly on the same form to move to next text field and backspace key
to previous field respectively.
Thank you for your attention to this matter your assistance will be valued.
--
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.
[View Less]
https://bugs.winehq.org/show_bug.cgi?id=47980
Bug ID: 47980
Summary: Corel DRAW 2019 installer halts at "Initializing" step
Product: Wine
Version: 4.18
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: bignintyfan(a)gmail.com
Distribution: ---
Created attachment 65490
--…
[View More]> https://bugs.winehq.org/attachment.cgi?id=65490
Corel DRAW 2019
Applications such as CorelDRAW 2019 hang at the "Initializing" step when trying
to install. This has been occurring since at least Wine Staging 4.5, but has
persisted to Wine Staging 4.18.
Steps to reproduce:
1. Make sure the "winbind" package is installed (`sudo apt install winbind`)
2. Make a new 64-bit Wine Prefix (`export WINEPREFIX=~/.wine-corel`)
3. Download the trial of CorelDRAW 2019 (https://www.coreldraw.com/en/)
4. (optional) Install dotnet40 using winetricks (`winetricks dotnet40)
5. Run the installer (`wine CorelDRAWGraphicsSuite2019Installer_RW.exe`)
Tracelog is added as an attachment, the final error shown when the window hangs
is "{}:err:seh:setup_exception_record stack overflow 1024 bytes in thread {}
eip f7b34198 esp 00230f30 stack 0x230000-0x231000-0x330000"
--
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.
[View Less]
https://bugs.winehq.org/show_bug.cgi?id=54888
Bug ID: 54888
Summary: Transparent window are displayed as black background
window on wine
Product: Wine
Version: 8.6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: bcjon07(a)gmail.com
Distribution: ---…
[View More]
Some transparent windows are displayed as black background window. Here is a
simple WPF window program that can reproduce this issue. On Windows, all parts
are transparent except for the graphics and text in the middle, but it has a
black background on Wine. It achieves transparency only by adding the following
code to the window constructor (the main point is that WindowChrome is used
instead of AllowTransparent):
WindowStyle = WindowStyle.None;
ResizeMode = ResizeMode.NoResize;
Background = Brushes.Transparent;
WindowChrome.SetWindowChrome(this, new WindowChrome { GlassFrameThickness = new
Thickness(-1) });
Download link of the demo program:
https://drive.google.com/file/d/1MCrnb1N6cLUzVoX_vO4tFO4qlS_qhAwi/view?usp=…
Other clues: Transparent windows implemented using AllowTransparent are valid
on Wine, while those implemented using WindowChrome are invalid. On Windows,
transparent forms implemented using WindowChrome are frequently used due to
better performance(usually). According to my pre investigation,
AllowTransparent seems to be implemented using GDI, but WindowChrome mainly
uses the DWM API
System architecture:
x86_64
Ubuntu 20.04
wine 8.6
wine-mono 7.4.0
--
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.
[View Less]
https://bugs.winehq.org/show_bug.cgi?id=54197
Bug ID: 54197
Summary: cuda-z and warpem fail in wine-staging 7.22 and later
Product: Wine
Version: 7.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: alois.schloegl(a)gmail.com
Distribution: ---
Created attachment …
[View More]73728
--> https://bugs.winehq.org/attachment.cgi?id=73728
screenshot of running cuda-z one wine-staging 7.22
cuda-z fails to run in wine-staging 7.22 and later. It reports the error "CUDA
not found. Please update the nvidia-driver.". cuda-z runs fine under
wine-staging 7.21 (and earlier) on the same machine with the same nvidia
driver.
The application "WarpEM" can be also not used anymore because it does not find
any GPU.
I suspect that disabling the nvcuda-support patches in wine-staging [1] is the
reason for this breakage.
I believe bug #54102 is related, but the bug report says that this occured
already in v7.21. But this issue is not reproducible to me in 7.21 only in
7.22.
[1]
https://gitlab.winehq.org/wine/wine-staging/-/commit/6c3797b3e8dba19698328c…
[2] https://bugs.winehq.org/show_bug.cgi?id=54102
--
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.
[View Less]
https://bugs.winehq.org/show_bug.cgi?id=55011
Bug ID: 55011
Summary: Cuda-application M/WarpEM got stuck or crashes in
wine-staging/7.21, wine/8.9+nvidia-libs
Product: Wine
Version: 8.9
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: nvcuda
Assignee: wine-bugs(a)winehq.org
Reporter: alois.schloegl(a)gmail.…
[View More]com
Distribution: ---
M of WarpEM gets stuck very early and eventually crashes. The following steps
are needed to reproduce this:
1) install WarpEM according to [1] into wine-staging between v7.17 and v7.21,
or wine-8.9 with nvidia-libs.
(do not try with wine-staging 7.22 or later, because that has cuda support
disabled).
This has been testing this with "Shared WoW64" configuration of Wine. Trying to
use Wine with the "new WoW64 approach" using -enable-archs=i386,x86_64 did also
not work for me, because it failed much earlier when trying to install
Cuda/WarpEM.
2) Data (5.5TB!) for testing is available from here [1].
Download and unpack Warpem_test.tar.gz to a directory that is accessible from
wine.
The screenshots Step1-7 should help to understand how M is supposed to be used.
3) Start M.exe. In my case, I do this
ulimit -s 655360
wine $WINEPREFIX/drive_c/Warp/M.exe
or
vglrun wine $WINEPREFIX/drive_c/Warp/M.exe
4) Within M, do the following steps (see also Step1-7 in [2]):
- Step 1: In the GUI window click "LOAD EXISTING FROM FILE"
- Step 2: select ...\M_j33\Gag_c2_processing.population
- Step 3: Upper right corner Refine button.
- Step 4: Click refine
- Step 5+6: workers are now testing the memory
- Step 7: Eventually (after several minutes), one of the works crash, and there
is no further progress.
On Windows, this finishes and a new screen appears for the next step. This is
not the case here. It gets stuck, and and eventually I stopped wine with
<ctrl-C>. A log file is also available [2], but it is too large (1.1 GB) to be
included here. If you have suggestions with WINEDEBUG filter should be used,
let me know.
[1]
https://appdb.winehq.org/objectManager.php?sClass=version&iId=40620&iTestin…
[2] https://pub.ista.ac.at/~schloegl/warpem-test-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.
[View Less]
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.…
[View More]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.
[View Less]
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: …
[View More]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.
[View Less]