https://bugs.winehq.org/show_bug.cgi?id=50804
Bug ID: 50804
Summary: LTSpice XVII will not start
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: will.nilges(a)gmail.com
Distribution: ---
Created attachment 69614
--> https://bugs.winehq.org/attachment.cgi?id=69614
.desktop startup errors
After installing LTSpice (which appears to work fine), the program will not
start, failing silently if you use the provided .desktop file (either of them),
and giving little helpful output otherwise.
I believe that LTSpice worked fine on some earlier version of Wine 6. 6.1 seems
to work.
A possibly related issue is that the installer complains at you with the
following message:
"You have User Account Control (UAC) enabled but did not 'Run As Administrator'
If you want to try to install in a directory you have full permissions, press
'YES' to continue anyway."
I'm running Fedora 33 with GNOME on Wayland. This happens on any of my Fedora
GNOME computers. I have tried no other operating system.
My current workaround is to downgrade to Wine 5.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=51059
Bug ID: 51059
Summary: Incorrect semantics of FILE_OPEN_REPARSE_POINT on
Linux
Product: Wine-staging
Version: 6.7
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jinoh.kang.kr(a)gmail.com
CC: erich.e.hoover(a)gmail.com, leslie_alistair(a)hotmail.com,
z.figura12(a)gmail.com
Distribution: ---
This bug affects the Cygwin installer (https://cygwin.com/setup-x86_64.exe);
specifically, it fails to verify SHA512 checksums of downloaded packages.
(Source at
https://cygwin.com/git/?p=cygwin-apps/setup.git;a=blob;f=package_source.cc,
in method packagesource::check_sha512)
Running the installer with WINEDEBUG=trace+file,trace+server reports:
CreateFileW ("XXXX.tar.xz") [1]
NtCreateFile ("XXXX.tar.xz", w/o FILE_OPEN_REPARSE_POINT) [1]
CreateFileW return [1]
NtQueryInformationFile FileBasicInformation [1]
(server)close_handle [1]
NtCreateFile ("XXXX.tar.xz", w/ FILE_OPEN_REPARSE_POINT) [2]
NtReadFile [2] -> STATUS_INVALID_HANDLE
The square brackets denote file handles. Handle reuse bug has been
ruled out.
This bug can be traced to an incorrect FILE_OPEN_REPARSE_POINT implementation
in Wine-staging, in
"ntdll-Junction_Points/0016-server-Implement-FILE_OPEN_REPARSE_POINT-option.patch":
> diff --git a/server/fd.c b/server/fd.c
> index 4f43f41fb31..a01d4c9c0f7 100644
> --- a/server/fd.c
> +++ b/server/fd.c
> @@ -107,6 +107,10 @@
> #include "winioctl.h"
> #include "ddk/wdm.h"
>
> +#if !defined(O_SYMLINK) && defined(O_PATH)
> +# define O_SYMLINK (O_NOFOLLOW | O_PATH)
> +#endif
On Linux, read/write/ioctl/... operations on an O_PATH descriptor will
fail with EBADF, which is then translated as STATUS_INVALID_HANDLE to the
application.
> +
> #if defined(HAVE_SYS_EPOLL_H) && defined(HAVE_EPOLL_CREATE)
> # include <sys/epoll.h>
> # define USE_EPOLL
> @@ -1958,6 +1962,11 @@ struct fd *open_fd( struct fd *root, const char *name, struct unicode_str nt_nam
> }
> else rw_mode = O_RDONLY;
>
> +#if defined(O_SYMLINK)
> + if ((options & FILE_OPEN_REPARSE_POINT) && !(flags & O_CREAT))
> + flags |= O_SYMLINK;
Another difference is that O_PATH semantics override
O_RDONLY/O_WRONLY/O_RDWR, even if the target file isn't _actually_ a
symbolic link.
To properly implement it on Linux we should:
1. open with O_PATH.
2. check if the file is really a symlink (via fstat?).
3. if not, reopen via /proc/self/fd/%u (now w/o O_NOFOLLOW|O_PATH).
Note that this isn't an issue on XNU (macOS), where O_SYMLINK has an
equivalent semantics to FILE_OPEN_REPARSE_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=50878
Bug ID: 50878
Summary: Neon Noir Benchmark crashes on Wine-Staging before
showing the first scene.
Product: Wine-staging
Version: 6.3
Hardware: x86-64
URL: https://www.cryengine.com/marketplace/product/neon-noi
r
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: lvb.crd(a)protonmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Since Wine-Staging-6.3 it silent crash after clicking to start benchmark button
and loading but before scene rendering after black screen.
I'm already done bisecting. The problem appeared after this commit:
<https://github.com/wine-staging/wine-staging/commit/750044c08c49c7a117fcc91…>
Also I did some more tests on current Wine-Staging and found that
preventing the 0035 patch from applying (and all subsequent ones) - helps.
While if you add patch 0035 applying, but prevent the applying of 0036 and
subsequent - the problem appears again.
0035 patch: "ntdll: Treat undecoded unix symlinks as NT symlinks."
<https://github.com/wine-staging/wine-staging/blob/7b199110bb31100c78aa3ffb7…>
The benchmark is free, but requires registering an account and a separate
launcher to download it (it will not be necessary to run it, you can simply
copy the Neon_Noir_Ray_Tracing_Benchmark_2527 directory with it inside the
fresh prefixes).
On the site need only add the benchmark to your account
https://www.cryengine.com/marketplace/product/neon-noir
For launcher need use `WINEDLLOVERRIDES="libglesv2=d"` because Bug 44985
and `winetricks -q mfc140` need for benchmark itself Bug 44856 Bug 48866
It also seems this application requires `d3d11-Deferred_Context` from Staging,
but the strange thing is, on vanilla Wine without it, it crashes in the same
place and from the outside it seems that the behavior is identical.
Please, check it. And can anyone reproduce 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=50319
Bug ID: 50319
Summary: Powerpoint 2013/365: cursor not moved when clicking in
current text box
Product: Wine
Version: 6.0-rc2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: rcorreia31(a)gmail.com
Distribution: ---
Created attachment 68898
--> https://bugs.winehq.org/attachment.cgi?id=68898
Simple Powerpoint file containing two text boxes
Running wine-6.0-rc2 compiled from source.
Same issue with previous 5.x versions.
Installation done in two different clean prefixes.
Reproduced with KDE Plama 5.20.1 and Xfce 4.16pre1, both compiled from sources,
on Centos 8.3
Both Office 32bit versions were installed using the recommendations from
WineHQ.
Office 2013 :
https://appdb.winehq.org/objectManager.php?sClass=version&iId=26323
Office 365 (2016) :
https://appdb.winehq.org/objectManager.php?sClass=version&iId=35527
Office 2013 : winetricks msxml6
Office 365 : winetricks msxml3 msxml6 riched20 riched30
Two registry updates done for 2013 and 365:
. HKCU\Software\Wine\Direct3D\MaxVersionGL (DWORD) : 30002 (hex)
. HKCU\Software\Wine\Direct2D\max_version_factory (DWORD) : 0
Two files copied for 2013 and 365:
cp "./Common Files/Microsoft Shared/ClickToRun/AppvIsvSubsystems32.dll"
"./Microsoft Office/root/Office16"
cp "./Common Files/Microsoft Shared/ClickToRun/C2R32.dll" "./Microsoft
Office/root/Office16"
Problem: clicking in the current text box does not set the cursor to the
clicked position.
To reproduce:
. Create two text boxes in Powerpoint. I.E.: one for the title and one for the
body ⇒ test case attached WineTestCase.pptx
. Add some text to both.
. Click on the text of a text box: mouse cursor is set to the right location.
. Click on another part of the text in the same current text box: text box
focus is lost and the mouse cursor is not set to where we clicked. In fact the
mouse cursor is not displayed anymore.
If we click on any character in the other non-current text box: the cursor
moves to where we clicked as expected.
So the problem only occurs when we want to put the cursor on another location
within the text box we are already in.
There are another problems that are maybe a side effect of this one:
. Double-click on a text of another text box: the text is not selected. A first
click is necessary to set the focus.
. Select a text by clicking and moving the mouse within the current text box:
the text is not selected.
No workaround found except first reselecting the text box. I.E. Esc+left click,
Right+Left click.
--
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=33198
Bug #: 33198
Summary: Multiple applications ported to WinRT/ARM using
msvcr110.dll require msvcrt.setjmp
Product: Wine
Version: 1.5.25
Platform: arm
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: msvcrt
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: focht(a)gmx.net
Classification: Unclassified
Hello folks,
as the summary says ...
--- snip ---
$ wine ./Audacity.exe
...
err:module:find_forwarded_export function not found for forward 'msvcrt.setjmp'
used by L"C:\\windows\\system32\\msvcr110.dll". If you are using builtin
L"msvcr110.dll", try using the native one instead.
--- snip ---
Currently implemented for x86 64-bit in msvcrt:
http://source.winehq.org/git/wine.git/blob/14a81773c7ce865dd6d919ddee89cad3…
--- snip ---
1371 @ cdecl -arch=x86_64 -norelay -private setjmp(ptr) MSVCRT__setjmp
--- snip ---
Regards
--
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=32992
Bug #: 32992
Summary: ARM port of "WabbitEMU" wants
KERNEL32.dll.RtlLookupFunctionEntry
Product: Wine
Version: 1.5.24
Platform: arm
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: kernel32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: focht(a)gmx.net
Classification: Unclassified
Hello folks,
split from bug 32991 which is about unimplemented function
KERNEL32.dll.RtlUnwindEx
+module,+imports
--- snip ---
...
0009:trace:module:load_dll looking for L"KERNEL32.dll" in
L"Z:\\home\\linaro\\wine-apps\\wabbitemu;.;C:\\windows\\system32;C:\\windows\\system;C:\\windows;C:\\windows\\system32;C:\\windows;C:\\windows\\system32\\wbem"
0009:trace:module:load_dll Found L"C:\\windows\\system32\\KERNEL32.dll" for
L"KERNEL32.dll" at 0x7b820000, count=19
0009:warn:module:import_dll No implementation for KERNEL32.dll.RtlUnwindEx
imported from L"Z:\\home\\linaro\\wine-apps\\wabbitemu\\Wabbitemu.exe", setting
to 0x41820000
0009:trace:imports:import_dll --- RtlUnwindEx KERNEL32.dll.1209 = 0x41820000
0009:trace:imports:import_dll --- GetCommandLineA KERNEL32.dll.481 = 0x7b846be0
0009:trace:imports:import_dll --- RtlPcToFileHeader KERNEL32.dll.1205 =
0x7bc69188
0009:warn:module:import_dll No implementation for
KERNEL32.dll.RtlLookupFunctionEntry imported from
L"Z:\\home\\linaro\\wine-apps\\wabbitemu\\Wabbitemu.exe", setting to 0x41820024
0009:trace:imports:import_dll --- RtlLookupFunctionEntry KERNEL32.dll.1203 =
0x41820024
0009:trace:imports:import_dll --- GetModuleFileNameW KERNEL32.dll.634 =
0x7b86b864
...
--- snip ---
MSDN entry for KERNEL32.dll.RtlLookupFunctionEntry:
http://msdn.microsoft.com/en-us/library/windows/desktop/ms680597%28v=vs.85%…
("ARM Definition")
Regards
--
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=50770
Bug ID: 50770
Summary: Unable to create symlinks to files in a nonexistent
directory
Product: Wine-staging
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: martin(a)martin.st
CC: erich.e.hoover(a)gmail.com, leslie_alistair(a)hotmail.com,
z.figura12(a)gmail.com
Distribution: ---
Created attachment 69562
--> https://bugs.winehq.org/attachment.cgi?id=69562
Testcase
Creating a symlink pointing to a file that doesn't exist, succeeds as it
should, e.g. CreateSymbolicLinkA("link", "nonexistentfile") succeeds. However,
CreateSymbolicLinkA("link", "nonexistentdir\\nonexistentfile") fails.
--
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=50625
Bug ID: 50625
Summary: Unhandled exception with try/catch
Product: Wine
Version: 4.12.1
Hardware: arm
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: david.paradis(a)us.abb.com
Distribution: ---
Created attachment 69319
--> https://bugs.winehq.org/attachment.cgi?id=69319
Test Project File
Hello,
I have run into a bug with try/catch blocks throwing an unhandled exception
even though I have a catch all.
I have attached a very simple test program that when started calls a method
that just throws an exception class back to the caller. This very simple
program works great in Windows and throws an unhandled exception in Wine and
terminates the program.
This is a critical path to my application as I have incorporated a 3rd party
library that uses exceptions for program flow rather than function return
codes. Without a fix our application becomes unstable and crashes when an
intended exception is thrown.
I would really like a solution for the version of Wine that we are running
(4.12.1) as we have Wine running on thousands of remote computers with not easy
solution to upgrade to newer versions. I can however deploy patches to Wine.
Thank you for any assistance with addressing this issue as I have spent the
last couple days annotating the Wine sources to try and find the root cause
without success to this 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.