https://bugs.winehq.org/show_bug.cgi?id=52262
Bug ID: 52262
Summary: Videos in Warwind are very ugly
Product: Wine
Version: 7.0-rc2
Hardware: x86-64
URL: https://web.archive.org/web/20201228084909/https://tele500.abandonware-france.org/fichiers/jeux/1996/jeu-009
75-warwind-pcwin.7z
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: iccvid
Assignee: wine-bugs(a)winehq.org
Reporter: jeremielapuree(a)yahoo.fr
Distribution: Ubuntu
The opening videos are mainly black with some white lines appaearing time to
time. The console output is spammed with the following line:
0024:err:iccvid:decode_cinepak CVID: corruption 29700 (QT/AVI) != (different
number)
--
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=46422
Bug ID: 46422
Summary: Kara no Shoujo does not enter fullscreen correctly
Product: Wine
Version: 4.0-rc4
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: zaplo00(a)mailfence.com
Distribution: ---
Created attachment 63193
--> https://bugs.winehq.org/attachment.cgi?id=63193
screenshot of the problem
See screenshot. Same thing happens in wine virtual desktop as well as in other
desktop environments.
OS: Arch Linux x86_64
Kernel: 4.19.9-arch1-1-ARCH
Uptime: 5 hours, 39 mins
Packages: 1453 (pacman)
Shell: bash 4.4.23
Resolution: 1920x1080, 1920x1080
DE: Cinnamon 4.0.8
WM: Mutter (Muffin)
WM Theme: cinnamon (Adwaita)
Theme: Adwaita [GTK2/3]
Icons: Adwaita [GTK2/3]
Terminal: mate-terminal
Terminal Font: Monospace 10
CPU: AMD Ryzen 7 1700 (16) @ 3.000GHz
GPU: NVIDIA GeForce GTX 1060 3GB
Memory: 2011MiB / 16036MiB
wine log:
0009:fixme:ddraw:DirectDrawEnumerateExA flags 0x00000006 not handled
0042:fixme:d3d:state_linepattern_w Setting line patterns is not supported in
OpenGL core contexts
--
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=50577
Bug ID: 50577
Summary: Saya no Uta: hangs on RtlpWaitForCriticalSection
Product: Wine
Version: 6.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: pernegger(a)gmail.com
Distribution: ---
Created attachment 69251
--> https://bugs.winehq.org/attachment.cgi?id=69251
terminal output at default settings
Note: This is about the Japanese "Windows 10 compatible" release, not an
English localised one. There is no demo version, I'm afraid.
The game runs fine--until it hangs at:
012c:err:ntdll:RtlpWaitForCriticalSection section 103971A4 "?" wait timed out
in thread 012c, blocked by 0024, retrying (60 sec)
The hang may happen, after as little as 1 min, sometimes it's 10 min, and I
might have made it 20 min once. When it happens, it does not recover, the
message just repeats every once in a while.
I'm using the Ubuntu packages from the official winehq repo. Originally I tried
with wine-staging 6.0, then I went backwards version by version through
(wine-staging) 5.18, and finally now I'm on (wine-devel) 6.0 for this bug
report. No discernable difference either way. The run in the attached log
happened in a clean prefix (though I admit I may have forgotten to wipe the
prefix between some downgrades).
--
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=51715
Bug ID: 51715
Summary: crypt32:chain fails on some AMD/Nvidia GPU machines
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: crypt32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
crypt32:chain has the same three failures on a set of Windows machines:
chain.c:3458: Test failed: chainCheck[31]: expected 3 elements, got 4
chain.c:4583: Test failed: simple_chain->cElement = 4
chain.c:4609: Test failed: got string GB, Greater Manchester, Salford, Comodo
CA Limited, AAA Certificate Services, expected US, New Jersey, Jersey City, The
USERTRUST Network, USERTrust RSA Certification Authority
https://test.winehq.org/data/patterns.html#comctl32:header
The only common point is that all these machines have an AMD or Nvidia GPU:
* cw-gtx560 Windows 8.1 Nvidia GTX560 driver 353.82
* cw-gtx560 Windows 10 1507 Nvidia GTX560 driver 391.35
* cw-rx460 Windows 10 1507 AMD RX460 driver 19.11.3
* fgtb-w10pro64 Windows 10 2009 AMD RX550 driver 20.11.3
* fgtb-w10pro64 Windows 10 21H1 AMD RX550 driver 21.8.2
* vn-w10pro Windows 10 21H1 AMD RX570 driver 20.10.35.02
But the failures don't happen whenever there is such a GPU: cw-gtx560-2009 has
the same 391.35 Nvidia driver as cw-gtx560-1507 version and yet does not have
these failures.
--
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=41662
Bug ID: 41662
Summary: Carmageddon (windows 95 version) flickering menus
(possible ddraw issue)
Product: Wine
Version: 1.9.22
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: aaronbpaden(a)gmail.com
Distribution: ---
Created attachment 56059
--> https://bugs.winehq.org/attachment.cgi?id=56059
log
AfteCarmageddonr playing a race in Carmadeddon and returning to the menus, the
tops and bottoms of the screen flicker with an image from the last race.
I'm on radeonsi and it could be a driver issue, but from the logs I think it's
a ddraw issue.
It's not a huge problem as far as Carmageddon is concerned, because the menu is
still fully visible and usable.
--
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=43081
Bug ID: 43081
Summary: Final Fantasy VII 2012: Buggy rendering of graphics
during fights and dialogs
Product: Wine
Version: 2.0.1
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: b33lzebob(a)googlemail.com
Distribution: ---
Created attachment 58266
--> https://bugs.winehq.org/attachment.cgi?id=58266
Archive including screenshots of this graphics bug, sed DLLs and terminal
output.
Strange display of character graphics during fights and dialogs (see
attachment).
System Information:
Wine version: 2.0.1
OS: Ubuntu Gnome 17.04 64bit
CPU: AMD® A4-3305m apu with radeon(tm) hd graphics × 2
GPU: ATI Radeon HD 6480 (Sumo2)
Things I've tried:
- update from Ubuntu Gnome 16.04 to 17.04 to provide form actual graphics
driver
- Added DDLs like described at https://appdb.winehq.org
/objectManager.php?sClass=version&iId=28519 via winetricks
- selected different versions of windows (Windows XP, 7, 8 & 10)
- installed steam- and non-stream-version of this game
--
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=24559
Summary: Final Fantasy 7: error when installing 'Movie Player'
Product: Wine
Version: 1.3.3
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: leighmanthegreat(a)hotmail.com
Created an attachment (id=31005)
--> (http://bugs.winehq.org/attachment.cgi?id=31005)
Clicking 'Install MoviePlayer' option
Using Ubuntu 10.04
Final Fantasy 7 setup program gives you the option to 'Install Movie Player'
clicking this appears to fail with the error message
DirectShow Setup failed with error code: -2147023829
terminal log attached
--
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=33763
Bug #: 33763
Summary: Sacred 2 : HLSL shader parsing failed error with
built-in d3dcompiler_43
Product: Wine
Version: 1.6-rc1
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3dx9
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: xvachon(a)gmail.com
CC: wine-bugs(a)winehq.org
Classification: Unclassified
Created attachment 44714
--> http://bugs.winehq.org/attachment.cgi?id=44714
log trace+d3dcompiler
Follow up of http://bugs.winehq.org/show_bug.cgi?id=25366#c9
Running Sacred 2 in a clean prefix without overrides in 1.6-rc1 results in a
crash. Using overrides d3dcompiler_43 (poor performance) or d3dx9_36 (better
performance) work around the issue. This bug is tagged to d3dcompiler_43
however because of this :
fixme:d3dx:D3DXLoadSurfaceFromMemory Unhandled filter 0x5.
err:d3dcompiler:compile_shader HLSL shader parsing failed.
wine: Unhandled page fault on read access to 0xca7fa113 at address 0x1134484
(thread 0009), starting debugger...
Attached a log trace+d3dcompiler which hopefully reveals meaningful details to
the devs..
--
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=36091
Bug ID: 36091
Summary: Project APT fails to compile vertex shader
Product: Wine
Version: 1.7.17
Hardware: x86
URL: http://www.desura.com/games/project-apt
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3dx9
Assignee: wine-bugs(a)winehq.org
Reporter: madewokherd(a)gmail.com
Created attachment 48280
--> http://bugs.winehq.org/attachment.cgi?id=48280
d3dcompiler,tid log
When clicking "new game" in project apt, I get a message saying "FATAL ERROR in
Vertex Shader compilation". The console shows an error in compile_shader, and
messages in the d3dcompiler channel seem to match up with the details of the
game's error message.
--
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.