https://bugs.winehq.org/show_bug.cgi?id=55955
Bug ID: 55955
Summary: some part of the software is black, if I click a line
it appears, but only a line, never more than a line
Product: Wine
Version: 8.21
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: comctl32
Assignee: wine-bugs(a)winehq.org
Reporter: gerard.labadie(a)sysgroup.fr
Distribution: ---
Created attachment 75543
--> https://bugs.winehq.org/attachment.cgi?id=75543
Display of Captvty 3 on Windows
The resolution of the bug
https://bugs.winehq.org/show_bug.cgi?id=55742
allows to launch successfully Captvty V3, but part of the window is black and
impossible to read
I have attached the file Captvty-3-display-ok, when running on Windows which
shows a normal display
and the file Captvty-linux which shows that the resume of the replay is Ok, but
not the lines with the names of the replays.
reproducer
have wine 8.20 or after, the latest winetricks
create a directory .captvty_V3
download the zip from v3.captvty.fr
unzip it to .captvty_V3
export WINEARCH=win64
export WINPREFIX=~/.captvty_V3
wineboot -u
winetricks -q dotnet48 corefonts gdiplus fontsmooth=rgb vlc win7
mkdir temp
cd temp
cabextract ~/.cache/winetricks/win7sp1/windows6.1-KB976932-X64.exe
cp -rf
./x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2/comctl32.dll
~/.wine_captvty_V3/drive_c/windows/syswow64/comctl32.dll
cd ~
rm -rf temp
launch it with
wine .captvty_V3/Captvty.exe
I noticed from the command line the messages
fixme:uxtheme:BeginBufferedPaint painting parameters are ignored
and
0024:fixme:uxtheme:AllowDarkModeForWindow 00030048 1: stub
using winecfg I tried various options for comctl32, any option with "native"
works (with the black display), any other option crashes the sofware.
in https://forum.winehq.org/viewtopic.php?t=38088
somebody commented
I don't know how to fix the black display, but I strongly believe this might be
due to using the native comctl32 (which is not really a good thing).
I think it might be a good idea to open a bugreport about the application not
being able to load builtin comctl32, maybe one of the developers has an idea
how to fix this, and maybe this "black display" issue might be solved then as
well
--
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=50083
Bug ID: 50083
Summary: ASCOM Platform 6.5 - Installation failed
Product: Wine
Version: 5.0.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: bammzilla(a)astronomy.com.ph
Distribution: ---
Created attachment 68544
--> https://bugs.winehq.org/attachment.cgi?id=68544
Screenshots of popup error screens during install
The ASCOM Platform allows windows desktop planetarium programs to control
astronomical hardware such as telescopes, domes, and cameras.
The software is freely distributable and open source, released under the
Creative Commons Attribution-ShareAlike 3.0 License, but written under the .NET
Platform.
The latest version is ASCOM Platform 6.5, written under .NET Framework 4.8 and
Visual Studio 2019.
To prepare the installation, I ran winetricks -q vcrun2019 dotnet35sp1
dotnet452 dotnet472 dotnet48. No errors were reported in the installation of
dotnet.
I then launched the installer with the following command:
WINEDEBUG=+nls wine ASCOMPlatform65.exe >> ASCOMPlatform65.log 2>&1
The installation went smoothly but popped up several error screens and ended
with an installation failed.
Screenshots of the error screens are attached.
The WINEDEBUG log file is gzipped and attached.
ASCOMPlatform installer log files are zipped and attached.
Download the installer from the following link:
https://github.com/ASCOMInitiative/ASCOMPlatform/releases/download/v6.5Rele…
Full source code of ASCOM Platform is available here:
https://github.com/ASCOMInitiative/ASCOMPlatform
ASCOMPlatform License file:
https://github.com/ASCOMInitiative/ASCOMPlatform/blob/master/LICENSE.txt
Information about ASCOM can be found here:
https://ascom-standards.org/Community/
--
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=57064
Bug ID: 57064
Summary: Bloodrayne 2 (legacy and Terminal Cut): graphical
issue (foggy screen)
Product: Wine
Version: 9.5
Hardware: x86-64
URL: https://archive.org/download/BloodRayne2Demo/BloodRayn
e2Demo.rar
OS: Linux
Status: NEW
Keywords: download, regression
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: gyebro69(a)gmail.com
CC: awesie(a)gmail.com, z.figura12(a)gmail.com
Regression SHA1: f6a1844dbed91b441ad69e7b15b5be242d063e87
Distribution: ArchLinux
Created attachment 76927
--> https://bugs.winehq.org/attachment.cgi?id=76927
terminal output
This bug affects both the legacy version of Bloodrayne 2 (2005) and the
Terminal Cut version (2020).
I made only a cursory test with the game, but the issue is immediately obvious:
The screen looks as if it was covered with haze.
If I turn off these graphics options in the game launcher, the problem still
occurs: bump mapping, dynamic shadows, reflections.
The result of the regression test:
commit f6a1844dbed91b441ad69e7b15b5be242d063e87
wined3d: Use bindless textures for GLSL shaders if possible.
Can be reproduced with Bloodrayne 2 demo version.
BloodRayne2Demo.rar (477M)
md5: 226a09d5f5ce2c4e0b7319627c75e69d
Still present in Wine-9.15.
Tested with NVIDIA 550.40.67.
--
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=57308
Bug ID: 57308
Summary: Cannot load split debug symbols under /usr/lib/debug
Product: Wine
Version: 9.19
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: dbghelp
Assignee: wine-bugs(a)winehq.org
Reporter: pq2sx44teeigl7za(a)chyen.cc
Distribution: ---
We're discussing splitting PE debug symbols into a separate Arch Linux package
to reduce disk usage for users that don't need it:
https://gitlab.archlinux.org/archlinux/packaging/packages/wine/-/issues/16.
Typically, split debug symbol files are placed under /usr/lib/debug.
Apparently, wine tries to find them but something wrong happens. If I run
strace on the UNIX process for winedbg.exe, I got this when a crash happens in
msvcrt.dll:
16423 newfstatat(AT_FDCWD,
"/usr/lib/debug/\\??\\Z:\\usr\\lib\\wine\\x86_64-windows\\msvcrt.dll.debug",
0x7ffffe0ff8e0, 0) = -1 ENOENT
The path should be /usr/lib/debug/usr/lib/wine/x86_64-windows/msvcrt.dll.debug.
It seems Windows paths are not correctly converted to UNIX paths.
--
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=43172
Bug ID: 43172
Summary: IDirectPlay4::EnumConnections needs to support wide
string in DPNAME structure
Product: Wine
Version: 2.10
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: directx-dplay
Assignee: wine-bugs(a)winehq.org
Reporter: leslie_alistair(a)hotmail.com
Distribution: ---
IDirectPlay4::EnumConnections needs to support wide strings in DPNAME returned
in EnumConnections. Currently it just forwards to the ascii version.
--
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=56838
Bug ID: 56838
Summary: FL Studio 21 gui problem
Product: Wine
Version: 9.10
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: HalanoSiblee(a)gmail.com
Distribution: ---
Created attachment 76649
--> https://bugs.winehq.org/attachment.cgi?id=76649
A video of the bug on my linux environment
FL studio 21 works fine for previous version of wine 9.8 and 9.9
since I've updated to 9.10 I got this GUI problem while moving the window of an
plugin Here I'll upload video explaining the bug
My system :
Archlinux
wine 9.10-1
wine-mono 9.1.0-1
Xorg/X11
...
...
...
--
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=56109
Bug ID: 56109
Summary: Broken Radiobutton navigation (Up/Down, Accelerators)
in several InnoSetup installers
Product: Wine
Version: 9.0-rc3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: kyle.kcsoftwares(a)gmail.com
Distribution: ---
Created attachment 75779
--> https://bugs.winehq.org/attachment.cgi?id=75779
Ant Renamer
Broken Radiobutton navigation (Up/Down, Accelerators) in several InnoSetup
installers
Radiobuttons :
I &Accept ..
I do ¬ accept ...
- Click on one or the other then VK_UP or VK_DOWN => Focus change (dotted
rectangle) while selection does not move => THIS IS A BUG
- ALT+A and ALT+N have no effect => THIS IS A BUG
Happens with Ant Renamer 2.12 (see screenshot), TuxPaint 0.9.22 and several
other Inno Setup installers
--
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=56709
Bug ID: 56709
Summary: PackTouchHitTestingProximityEvaluation not located in
USER32.dll when attempting to run Clip Studio Paint
3.0
Product: Wine
Version: 9.8
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: animaloser(a)gmail.com
Distribution: ---
Clip Studio Paint 3.0 fails to open, with a pop-up message that reads "The
procedure point PackTouchHitTestingProximityEvaluation could not be located in
the dynamic link library USER32.dll"
The launcher does run however, even if it's all white, it's been documented in
the appdb entry for the program. The main software, CLIPStudioPaint.exe, does
not.
--
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=13529
Summary: wine doesn't run under a X client for windows under wine
[dogfood?]
Product: Wine
Version: 1.0-rc2
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: andriusmao(a)gmail.com
I was doing some tests and kde runs properly under a X client for windows (such
as Xming and WinaXe) under wine. But wine starts debugger when trying to run
any windows program (such as these provided by WinaXe or such as winecfg) in
"remote" display.
--
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=54571
Bug ID: 54571
Summary: ImageList images hard to see or even invisible
depending on COLOR_WINDOWTEXT
Product: Wine
Version: 8.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: trivial
Priority: P2
Component: comctl32
Assignee: wine-bugs(a)winehq.org
Reporter: dark(a)darkok.xyz
Distribution: ---
Created attachment 74114
--> https://bugs.winehq.org/attachment.cgi?id=74114
Visibility of images depending on Window Text color.
The lighter the Window Text color gets, the less visible the images in an
ImageList get.
This really affects people primarily using dark themes such as myself, as then
the text color is going to be so light the images will be invisible.
I'm not sure if this issue is present in other software, but in this case I am
experiencing this with the GSAE (GS Advanced Editor) tool shipped with Roland
sound modules.
I am able to see the images properly again if I replace what is currently line
1488 of `comctl32/imagelist.c` (ImageList_DrawIndirect) with `if (FALSE)`
instead of `if (himl->hbmMask)` so the else branch always runs (this will
likely break other software though, and in my case is just a temporary
measure).
--
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.