https://bugs.winehq.org/show_bug.cgi?id=55715
Bug ID: 55715
Summary: Folio Views 4 crashes when storing a changed file
Product: Wine
Version: 6.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: hj.bergmann(a)mail.de
Distribution: ---
Created attachment 75220
--> https://bugs.winehq.org/attachment.cgi?id=75220
The backtrace file produced by wine.
Hello,
My system: MX-21.3_x64 Wildflower August 06 2023, base is Debian GNU/Linux 11
(bullseye).
My computer: a desktop FUJITSU ESPRIMO P910, a Quad Core model with Intel Core
i5-3550S, 64 bit type.
The bug:
I installed the Folio Views 4.0 program. It started and loaded an existing .nfo
file, but when I tried to save a changed file, the program crashed. I tried
several times, always the same result. Producing a new file was no problem, but
saving the changed file failed.
Unfortunately the Folio Views program seems to be off the market, at least I
cannot find it on the net.
My program CD is about 20-30 years old. it is a 32 bit version.
I attach the backtrace file
--
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=55679
Bug ID: 55679
Summary: warframe doesn't start in experimental wow64 mode
Product: Wine
Version: 8.16
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: pmargeti34(a)gmail.com
Distribution: ---
Created attachment 75201
--> https://bugs.winehq.org/attachment.cgi?id=75201
warframe doesn't start in experimental wow64 mode
Game launcher fails to run properly, it spawns it's own error dialog which
offers to send crash related data to Digital Extremes. Attached is the output
of launching it from the terminal.
--
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=55608
Bug ID: 55608
Summary: NAM won't open on new update
Product: Wine
Version: 8.16
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: zardivorku(a)gufum.com
Distribution: ---
Created attachment 75145
--> https://bugs.winehq.org/attachment.cgi?id=75145
Log Report
https://github.com/sdatkinson/NeuralAmpModelerPlugin/releases
On latest wine staging update NAM crashes, didn't happen before on prior
update.
Linux Mint Cinnamon
--
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=55316
Bug ID: 55316
Summary: d3d10core:d3d10core fails systematically on
w11pro64-amd
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
d3d10core:d3d10core fails systematically on w11pro64-amd:
test_pipeline_statistics_query():
d3d10core.c:4922: Test failed: Got unexpected GSInvocations count: 2.
d3d10core.c:4941: Test failed: Got unexpected GSInvocations count: 2.
test_sample_c_lz():
d3d10core.c:8553: Test failed: Got 1.00000000e+000, expected 0.00000000e+000 at
(100, 100), sub-resource 0.
d3d10core.c:8553: Test failed: Got 1.00000000e+000, expected 0.00000000e+000 at
(100, 100), sub-resource 0.
See https://test.winehq.org/data/patterns.html#d3d10core:d3d10core
These failures have been happening forever and are specific to the Windows 11 +
AMD RX6600 configuration. In particular they never happened on
fgtbw10pro64_rx550 (Windows 10 + AMD RX550). Also, except for 2023-05-10 to
2023-05-12 (3 days) they are present in all nightlies.
--
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=53218
Bug ID: 53218
Summary: d3d10core:d3d10core - test_uint_shader_instructions()
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: ---
d3d10core:d3d10core - test_uint_shader_instructions() fails in the TestBot VMs:
d3d10core.c:13215: Test failed: Got {0x80000000, 0x00000000, 0x00000000,
0x00000000}, expected {0x00000000, 0xffffffff, 0x00000000, 0x00000000} at (0,
0), sub-resource 0.
d3d10core.c:13215: Test failed: Got {0x00000000, 0x80000000, 0x00000000,
0x00000000}, expected {0xffffffff, 0x00000000, 0x00000000, 0x00000000} at (0,
0), sub-resource 0.
d3d10core.c:13215: Test failed: Got {0xffffffff, 0x00000001, 0x00000000,
0x00000000}, expected {0x00000000, 0x00000001, 0x00000000, 0x00000000} at (0,
0), sub-resource 0.
d3d10core.c:13215: Test failed: Got {0x00000001, 0xffffffff, 0x00000000,
0x00000000}, expected {0x00000001, 0x00000000, 0x00000000, 0x00000000} at (0,
0), sub-resource 0.
https://test.winehq.org/data/patterns.html#d3d10core:d3d10core
These failures:
* Don't happen on Debian 11 + Intel / KDE
* Happen on Debian 11 + QXL + single-monitor
* Happen on Debian 11 + QXL + multi-monitor
* Happen on Debian Testing + QXL + multi-monitor (it actually has a couple
extra)
So they are probably related to QXL.
Note that despite being systematic these failures could cause false positives
due to the test multi-threading (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.
https://bugs.winehq.org/show_bug.cgi?id=55856
Bug ID: 55856
Summary: cgwin hangs during installation at libzstd1-1.5.5-1
Product: Wine
Version: 8.19
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: ---
When installing libzstd1-1.5.5-1 (/usr/bin/cygzstd-1.dll) it hangs, using one
full CPU core constantly.
The UI is still responsive and the installation can be cancelled, but it
doesn't progress.
This is not a regression in Wine, I used 5.0 and the error still occurs.
Download at https://www.cygwin.com/setup-x86_64.exe
Making feof always return 0 makes cygwin continue.
--
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=53522
Bug ID: 53522
Summary: Need for Speed III: joystick doesn't work after evdev
removal
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: dinput
Assignee: wine-bugs(a)winehq.org
Reporter: DirtY.iCE.hu(a)gmail.com
CC: rbernon(a)codeweavers.com
Regression SHA1: adfee25b45af8160848f94fdb24279d63d5f91f4
Distribution: Gentoo
Created attachment 72888
--> https://bugs.winehq.org/attachment.cgi?id=72888
WINEDEBUG=+dinput, ds4 usb, overriden, nfs3 demo with git master wine
I decided to try NFS3 after some time and realized that joystick no longer
works with newer releases. Git bisect lead me to commit
adfee25b45af8160848f94fdb24279d63d5f91f4, where the evdev and js backends were
removed. With the new backend, in NFS3 deadzone calibration screen, all axes
are at constant 0, and it doesn't respond to any keypress either. I've tried it
with DualShock 4 (both usb and bt), DS3 (only usb), and some noname cheap
controller, the same results. Interestingly, in joy.cpl the joysticks do work,
I've tried to click on override to move the controller from the xinput to the
non-xinput list, but no change. I also have no force-feedback support with the
new backend.
Tested it with the retail version of nfs3 and also with this patch, the results
are the same: https://veg.by/en/projects/nfs3/
Also tested it with the demo version and the latest git
(bfc73b0b80a1da2b137b5da4a2fcf530ee3a9d7d), same results.
1. Download demo from here: https://archive.org/details/nfs3_demo
2. Create a new 32-bit wine prefix (I've only compiled a 32-bit wine)
3. In winecfg, set windows compatibility to 98 (otherwise the install refuses
to start), go to drives and add a (fake) cdrom device (otherwise setup refuses
to start), and probably you should set a virtual desktop (the game likes to
mess with your resolution)
4. Run setup.exe (it will throw a registry error but still installs the game)
5. Start the game with taskset: `taskset -c 0 path/to/wine nfs3demo -d3d0` (the
game crashes/freezes if run on multicore cpu)
6. After the race countdown, press esc, controls, and try to bind some keys or
click on dead zone to see axes values.
I'm attaching a log with WINEDEBUG=+dinput and overridden joystick on joy.cpl.
--
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=55882
Bug ID: 55882
Summary: Need For Speed: Porsche Unleashed FMVs display only a
black screen
Product: Wine
Version: 8.19
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: barrosleo10(a)gmail.com
Distribution: ---
Created attachment 75412
--> https://bugs.winehq.org/attachment.cgi?id=75412
ddraw log
The audio of the FMVs plays back properly but all you get is a black screen
--
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=55877
Bug ID: 55877
Summary: DAZ3D stuck on "Building interface…" during startup
Product: Wine
Version: 8.19
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: zappedfish(a)gmail.com
Distribution: ---
DAZ3D 4.22.0.1
Fedora 39, Wine 8.19.
DAZ3D is stuck on "Building interface…" during startup. This didn't help on
previous version, I believe this to be a regression.
--
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.