https://bugs.winehq.org/show_bug.cgi?id=49364
Bug ID: 49364
Summary: far mod for nier automata requires
IDXGIAdapter3::RegisterVideoMemoryBudgetChangeNotifica
tionEvent
Product: Wine
Version: 5.10
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: animegirl(a)stronzi.org
Distribution: ---
Without this function game with mod will just spam this and does not startup:
`
13270.488:00b8:00c4:fixme:dxgi:dxgi_adapter_SetVideoMemoryReservation iface
0xea43f0, node_index 2240653, segment_group 0, reservation 0x0 stub!
13270.488:00b8:00c4:fixme:dxgi:dxgi_adapter_QueryVideoMemoryInfo Ignoring node
index 2240654.
`
Example implementation from dxvk
https://github.com/doitsujin/dxvk/commit/079cda1c0ce225be3db68a39383de47904…
--
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=52379
Bug ID: 52379
Summary: Logos 9 Bible Software (.NET 4.7 app) crash when
opening Faithlife assistant AI tool
Product: Wine
Version: 7.0-rc5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: johnpgoodman(a)gmail.com
Distribution: ---
Created attachment 71592
--> https://bugs.winehq.org/attachment.cgi?id=71592
Terminal output from Crash
The faithlife assistant is a voice controlled simple AI that helps with
searches etc. Opening the tool causes an instant crash as per the terminal
output. Tried installing speechsdk with winetricks... still crashes.
---Install Guide---
The app is a bit like kindle in so much as the engine is free but the resources
cost so there is a free download. Unlike kindle it has many advanced research
features and books link together etc. The main app is free but there are paid
features, resources and subscriptions. To use the app you need a free account
https://www.logos.com/product/194909/logos-9-basic. It uses a downloader app
which last I tried doesn't work with wine. The actual msi link is
https://downloads.logoscdn.com/LBS9/Installer/9.6.0.0024/Logos-x64.msi
---Manual Install Procedure:---
1 Install wine 6 or newer
2 winetricks corefonts
3 winetricks settings fontsmooth=rgb
4 winetricks dotnet48
5 winetricks settings renderer=gdi (you might need to set the reg key
manually)
6 Install the Logos.msi download but don't run it.
7 wine64 reg add "HKCU\\Software\\Wine\\AppDefaults\\LogosIndexer.exe" /v
Version /t REG_SZ /d vista /f
8 Run Logos and sign in with your free account.
---GUI Install Script---
There is a script which downloads a preconfigured wine bottle and sets it all
up in $USER/Logos_BibleP directory which you can then easily remove etc.
https://github.com/ferion11/LogosLinuxInstaller/releases Choose fast install
without wine AppImage.
--
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=52999
Bug ID: 52999
Summary: Redout fails to detect visual c++ runtimes
Product: Wine
Version: 7.8
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: blue-t(a)web.de
Distribution: ---
Created attachment 72366
--> https://bugs.winehq.org/attachment.cgi?id=72366
Logfile
When i try to run Redout, it says you need to install the c++ runtime.
The log does not indicate anything going wrong:
002c:fixme:winediag:LdrInitializeThunk wine-staging 7.8 is a testing version
containing experimental patches.
002c:fixme:winediag:LdrInitializeThunk Please mention your exact version when
filing bug reports on winehq.org.
0118:fixme:imm:ImeSetActiveContext (0000000000CDB7F0, 1): stub
0118:fixme:imm:ImmReleaseContext (000000000001006C, 0000000000CDB7F0): stub
007c:fixme:imm:ImeSetActiveContext (0000000000356C10, 0): stub
007c:fixme:imm:ImmReleaseContext (0000000000010020, 0000000000356C10): stub
0118:fixme:kernelbase:AppPolicyGetProcessTerminationMethod FFFFFFFFFFFFFFFA,
0000000000B9FD70
--
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=52943
Bug ID: 52943
Summary: Logos 9 crashes with stack overflow?
Product: Wine
Version: 7.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: horizon.innovations(a)pm.me
Distribution: ---
Created attachment 72317
--> https://bugs.winehq.org/attachment.cgi?id=72317
Terminal log
Logos 9 started from terminal, logo/splash screen shows, then crashes.
Gnu Guix linux system.
Logos installed via fast or slow script, same result.
Using locally installed wine as appimage doesn't run.
--
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=13142
Summary: NexusTK crashes when editing a board post
Product: Wine
Version: 1.0-rc1
Platform: PC-x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: ninja(a)slaphack.com
Nexus TK (download from http://nexustk.com/, AppDB entry is
http://appdb.winehq.org/objectManager.php?sClass=application&iId=926) crashes
when editing a board post.
It is possible to type the post without problems. As far as I can tell, the
problem occurs when doing something other than continuing to type, or pasting
-- most recently, I attempted to hilight some text, and crash.
By "crash", I mean the game (running in a 1024x768 desktop window) stops
responding entirely, and the log seems to indicate that some process died.
Note: Nexus works flawlessly with version 0.9.40 -- it has no bugs that Nexus
itself doesn't when running under Windows, and, in fact, is often more stable
than on Windows. I'll add regression tests and logs soon...
The game is otherwise usable, as far as I can tell. For now, I will compose in
a separate window, and paste into Nexus.
Every version I have tried since 0.9.40 has had problems. I believe the game
would not even run until 0.9.62, and this bug does happen in 1.0-rc1. Stock
Ubuntu install from a repository.
--
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=50982
Bug ID: 50982
Summary: Mouse clicks are sometimes offset higher (~20 px) than
the mouse cursor in LTSpice, winecfg and explorer
Product: Wine
Version: 6.6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: giradischi0001(a)gmail.com
Distribution: ---
Created attachment 69813
--> https://bugs.winehq.org/attachment.cgi?id=69813
winecfg output during prefix creation and automatic wine-mono download
Mouse interactions are sometimes offset 10~30 (random) pixels up from where the
cursor is displayed
Tried in LTSpice XVII and in winecfg, with wine 6.6 (Arch Linux "wine" package,
wine-mono downloaded by wine and not from the Arch package) in a new win64
Windows 7 prefix.
Wine 6.5 worked fine.
I cannot test with the latest developement version for disk space and available
time problems.
## LTSpice XVII
LTSpice is a light and easy-to-use electronic simulation freeware by Analog
Devices:
https://ltspice.analog.com/software/LTspiceXVII.exe
(Installation log attached, using app defaults)
(Run log attached)
In the component selector: open an existing schematic and right click on a
transistor, or create a new schematic and add a transistor (F2, select "npn",
Enter, place it anywhere with a left click, then Escape) and right click on it,
try to click on new transistor, try to select any of the parts.
In the component selection window, in the Bipolar Transistor right-click menu,
in the transistor selection dialog and also in the save modified file prompt
when exiting, I need to point a bit under the button or item (0~30 pixels,
variable) to actually click on the item and not on whatever is immediately over
it.
Sometimes the offset varies in the same window, for example from about 20
pixels to zero.
I did not find that the toolbar, the menu bar or the schematic view were
affected.
The list of transistor types in the transistor selection dialog also has
another problem: the grey header of the list, with labels such as "Part No.",
"Manufacturer", Polarity", "Vceo[V]", is often drawn blank or with an
incoherent line of the list, and reappears only when scrolling right. This is
mentioned to ease usage of the application, ideally I should file another bug
for this issue, but I haven't done it in the past three years.
## winecfg
While creating the clean prefix (by running winecfg, see also attached log), I
found that mouse clicks are also offset in winecfg, for example when adding a
drive unit (pointing to a folder), the drop-down menu that allows one to select
a drive unit also rolls down only if I click about 20 pixels under its lower
margin, and the same for the OK and Cancel buttons.
The Add button and the other controls in the winecfg tab do not behave offset.
## explorer
The file properties popup has the same offset problem.
It seems to me that the issue manifests itself in popups.
Performing enough clicks and resizes on the window, sometimes the offset goes
away.
--
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=52958
Bug ID: 52958
Summary: vague error messaged "File not found" and "Invalid
name"
Product: Wine
Version: 4.0.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: martijn(a)bytehazard.com
Distribution: ---
Please add a more descriptive error message for the following errors:
"File not found"
[ OK ]
and
"Invalid name"
[ OK ]
Both with 'stop' icon, and shown 10 times in succession.
I *think* they are triggered via "ShellExecute" in my own VB6 legacy
application.
Sorry I can't be more specific than that because the errors are so vague.
For example, it would be tremendously helpful *which* file is not found
(Wine/OS executable/dll file, the targeted command/executable, the file passed
to targeted command/executable, or if it is an error triggered by the
potentially launched application or Wine/OS?
Same for "invalid name". Invalid name what? Name of executable? Drive letter?
Drive mapping? Folder name? File name? Extension name? Application name? OS
name?
The only hint I have is that this message dialogue is Wine styled and thus not
something triggered outside Wine environment. Maybe they are not even related
to ShellExecute.
I'm aware this is probably the most useless bug report ever, I just want to
encourage any developer who is reading this to write more useful error messages
in the future. It has cost both of us more time to write/read this ticket than
to improve the code that displays these errors. And I'm nowhere near finding a
solution for my problem after hours and hours...
No hard feelings, I absolutely love Wine! Thanks for your efforts!
--
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=5989
Austin English <austinenglish(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Fixed by SHA1| |134c03b3bea0a33cd898b7974d1
| |647d97ae83b75
Status|NEW |RESOLVED
--- Comment #17 from Austin English <austinenglish(a)gmail.com> ---
(In reply to Ken Sharp from comment #16)
> In Wine 7.9, running "w2kexcp.exe /u" starts the uninstall program but that
> ends up hanging.
>
> 00fc:fixme:advpack:set_ldids Need to support changing paths - default will
> be used
>
> Trying via "wine uninstaller" only offers a repair option - uninstall is
> greyed out.
>
> The cause has shifted multiple times since this bug was opened. Shall we
> close this and start fresh? The original unimplemented function(s) are now
> implemented.
> https://source.winehq.org/git/wine.git/commit/
> 134c03b3bea0a33cd898b7974d1647d97ae83b75
Seems reasonable to me.
--
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=41264
Bug ID: 41264
Summary: Dead by Daylight: EULA text isn't visible
Product: Wine
Version: 1.9.18
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: sworddragon2(a)aol.com
Distribution: ---
On starting the game the first time an EULA was shown and any text was visible
except the raw EULA text as the container showing it was just completely black.
--
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=52989
Bug ID: 52989
Summary: Final Fantasy XI Setup window is not rendered properly
and appears stuck (msiexec)
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: chiitoo(a)gentoo.org
Distribution: ---
When running the setup for Final Fantasy XI Online, which will execute 'msiexec
/i FINAL_FANTASY_XI.msi', the application window is not rendered properly and
appears to be frozen, but 'msiexec' will be using about 100% of one CPU core.
The window may or may not show the current process being "computing space
requirements", which will not be updated if the window is minimised and
restored for example, showing an empty frame.
After approximately 6 minutes (possibly depending on CPU power, the disk space
available, or/and other unknown factors), the installer will proceed to the
next step.
Unsure if related at all, but the 'msi' debug channel will print a lot of lines
like these with an ever increasing row number:
00fc:trace:msi:MSI_ViewFetch 0526D538 0062F610
00fc:trace:msi:msi_view_get_row view 0526D830, row 48244, rec 0062F610.
00fc:trace:msi:msi_view_refresh_row 01A65D78 0526D830 48244 055F45F8
00fc:trace:msi:msiobj_release object 055F45F8 destroyed
After proceeding further with the setup, there is another space requirements
check which makes the window behave similarly, but the time the window appears
hung is a lot shorter. Other phases during the install, such as copying new
files also have times where the window isn't updated (blank/transparent after
minimise/restore).
This is no recent regression, and has been there for several years (possibly
ever since the release of the latest version of the installer in 2019).
Last tested with: wine-7.8-31-g95024c31551c3
--
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.