https://bugs.winehq.org/show_bug.cgi?id=38190
Bug ID: 38190
Summary: FEAR crash at runs
Product: Wine
Version: 1.7.38
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mrdeathjr28(a)yahoo.es
Distribution: ---
Created attachment 50967
--> https://bugs.winehq.org/attachment.cgi?id=50967
backtrace fear
Game config works but when game is launched crash
--
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=58216
Bug ID: 58216
Summary: Inquisitor crashes on start
Product: Wine
Version: 10.7
Hardware: x86-64
URL: https://store.steampowered.com/app/241620/Inquisitor/
OS: Linux
Status: NEW
Keywords: regression
Severity: normal
Priority: P2
Component: winegstreamer
Assignee: wine-bugs(a)winehq.org
Reporter: gyebro69(a)gmail.com
Regression SHA1: 075033d61ffac2a8d42e06e91a12c88f2fa17401
Distribution: ArchLinux
Created attachment 78529
--> http://bugs.winehq.org/attachment.cgi?id=78529
terminal output
The intro video in Inquisitor never worked for me: it was gracefully skipped
and the game loaded directly the main menu.
Since Wine-10.7 the game crashes right after start.
Reverting the following commit fixes the crash for me:
commit 075033d61ffac2a8d42e06e91a12c88f2fa17401
winegstreamer: Make sure WMSyncReader never reads in the background.
'winetricks wmp9' also makes the crash go away (the startup video still does
not work).
Reproduced with the Steam and GOG.com versions.
wine-10.7-73-gf9741837a3b
--
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=48548
Bug ID: 48548
Summary: Support running multiple tests in submitted jobs
Product: Wine-Testbot
Version: unspecified
Hardware: Other
OS: other
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: unknown
Assignee: wine-bugs(a)winehq.org
Reporter: cdavis5x(a)gmail.com
When I submit a job manually on the testbot, I can only run one instance of one
executable. For a binary, this makes sense, since there's only one binary; but
a patch, for which a choice of Wine test executables is offered, can affect
multiple Wine unit tests. I then have to submit the job multiple times, one for
each test unit affected. This seems... suboptimal. It'd be much faster and more
convenient if I could run multiple tests in a single job.
--
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=56059
Bug ID: 56059
Summary: Overwatch 2: highlight saving generates a 1ms (empty)
webm video file
Product: Wine
Version: 9.0-rc2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: forestix(a)nom.one
Distribution: ---
Created attachment 75715
--> https://bugs.winehq.org/attachment.cgi?id=75715
example video file
When attempting to save a game highlight as a webm video file, Overwatch 2
*seems* to be encoding the video as it should, in that it uses the CPU and
takes an appropriate amount of time to complete. However, the resulting file is
only about 700K, and doesn't play in any player.
Examining the file with MediaInfo shows what looks like a reasonable container
with video and audio parts, but only 1ms duration.
I get the same results in all of these Wine versions:
wine-9.0-rc2
wine-9.0-rc2 (Staging)
wine-ge-custom (aka lutris-GE-Proton) 8-23
Game installer download link:
https://download.battle.net/en-us?product=ow&blzcmp=ow_gamesite
Steps to reproduce:
- play a game (easiest way is via Play: Training: Practice vs. AI: Casual)
- after the game is over, return to the main menu
- click username button (top right corner)
- click history tab (top edge)
- click highlights tab (left edge)
- click a highlight from "today's top 5"
- click save button (bottom edge)
- select movie format: webm
- click save button
--
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=56137
Bug ID: 56137
Summary: Overwatch 2 fails to save highlight video files
Product: Wine
Version: 9.0-rc2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: forestix(a)nom.one
Distribution: ---
When attempting to save an Overwatch 2 highlight video as an mp4 file (the
default format), it fails with this error message:
SAVING ERROR
An unknown error has occurred. (6-04)
Steps to reproduce:
- play a game (easiest way is via Play: Training: Practice vs. AI: Casual)
- after the game is over, return to the main menu
- click username button (top right corner)
- click history tab (top edge)
- click highlights tab (left edge)
- click a highlight from "today's top 5"
- click save button (bottom edge)
- select movie format: mp4
- click save button
Note that this is a different kind of failure than the one with .webm format
(bug 56059).
--
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=58078
Bug ID: 58078
Summary: StarCraft Remastered: game is not started with
wine-10.5
Product: Wine-staging
Version: 10.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dimich.dmb(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
The game is not started with wine-10.5
StarCraft.exe process is running and consuming 100% of one CPU core. No video
mode changed, no game window created.
Battle.net launcher is displaying StartCraft as "Playing Now".
After downgrading wine to 10.4 the game starts and works fine.
StartCraft: v1.23.10.13515
OS: Arch Linux
Kernel v6.14.1
GPU: Nvidia, proprietary driver v570.133.07
--
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=57806
Bug ID: 57806
Summary: visual and response lags in Guitar Pro v8.1.3 (build
121)
Product: Wine
Version: 9.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: acidbong(a)tilde.club
Distribution: ---
Created attachment 78013
--> https://bugs.winehq.org/attachment.cgi?id=78013
Guitar Pro in Wine-9.20
I've been using Wine-staging for running Guitar Pro on Linux (Gentoo, then
NixOS), and it's been smooth until 9.20 -> 9.22 update
(https://github.com/NixOS/nixpkgs/pull/359908, nixpkgs maintainers skipped
v9.21). Then visual lags (constant, as if the program runs at 5 FPS) started to
happen. Welp, they aren't solely visual, responsiveness also suffers. Audio,
however, doesn't lag and is still smooth.
The lag is also present on Wine10.
Regression also confirmed on Wine-development v9.22 and with a demo version of
the program and on different PCs (first on an Intel-based laptop (Core
i3-7100), then on an AMD-based one (AMD Ryzen 5 5500U)), both with integrated
GPUs.
Camera recording (not screen capture, because `simplescreenrecorder` (haven't
tried other tools) for some reason reduced these lags): https://0x0.st/8KNw.mp4
Logs are attached below.
--
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=50242
Bug ID: 50242
Summary: Lotus Approach crashes on start up
Product: Wine-staging
Version: 5.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ToddAndMargo(a)zoho.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 68752
--> https://bugs.winehq.org/attachment.cgi?id=68752
Approach crash on start up
Dear Wine Staging Maintainers,
Fedora 33
wine-5.22-1.fc33.x86_64
As of 5.22, Lotus Approach now crashes on start up. Word Pro is okay.
I have attached the trace.
-T
--
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=45870
Bug ID: 45870
Summary: Star Wars Pit Droids fails to install
Product: Wine
Version: 3.16
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: zzarko(a)gmail.com
Distribution: ---
Created attachment 62369
--> https://bugs.winehq.org/attachment.cgi?id=62369
Screenshot of error
I have tried to install an old Win95 game, Star Wars Pit Droids, but it always
crashes during the install (actual error is in screenshot). I have created
32-bit wine environment and selected W95 as OS version.
The game can be found at:
https://www.myabandonware.com/game/star-wars-pit-droids-403
I have tried this with Wine 2.4, same error. I'll add WINEDEBUG=warn+all
outputs for both 3.16 and 2.4 versions.
--
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=48214
Bug ID: 48214
Summary: RPGmaker input does not work after moving window
Product: Wine
Version: 4.0.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-dinput
Assignee: wine-bugs(a)winehq.org
Reporter: ilkka.prusi(a)gmail.com
Distribution: ---
In some games made with RPGMaker VX ACE the input does not work after you have
moved window in desktop (input focus gone and back again).
Symptom is that game character does not move, menu is not opened on pressing
esc and so forth.
This is repeatable on Debian bullseye with wine 4.0.2, Wayland + Gnome on
x86-64 (Linux 5.4.1).
To repeat simply grab the window with mouse, move it, click inside window and
try keyboard input again.
--
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.