http://bugs.winehq.org/show_bug.cgi?id=58646
Bug ID: 58646
Summary: Video preview in CapCut covered by black rectangle
Product: Wine
Version: 10.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ihatemylife0025(a)gmail.com
Distribution: ---
Created attachment 79214
--> http://bugs.winehq.org/attachment.cgi?id=79214
Logs when launching the app and loading a project
After getting CapCut 6.9.0 to run using either this patch
https://bugs.winehq.org/show_bug.cgi?id=58635#c3 or an old version such as 1.5
(link: https://archive.org/details/capcut-1.5.0-windows) and opening a project
there is a black rectangle over the video preview.
This post from another person on wine's forums has screenshots showing the same
issue: https://forum.winehq.org/viewtopic.php?t=40387
A workaround is to decrease the transparency of dialogs in KDE's settings.
--
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=58648
Bug ID: 58648
Summary: Wine Regedit window flickers with Wayland driver-
possible regression
Product: Wine
Version: 10.14
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winewayland
Assignee: wine-bugs(a)winehq.org
Reporter: agarplayerarlon(a)gmail.com
Distribution: ---
Created attachment 79221
--> http://bugs.winehq.org/attachment.cgi?id=79221
video of the issue
If I remember correctly this wasn't happening with Wine 10.13, basically now
when resizing the Wine Regedit Window when using the Wayland driver makes it
flicker a lot.
I don't know if other apps are affected by this issue, I've tried resizing
notepad and it doesn't flicker.
--
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=57699
Bug ID: 57699
Summary: Paint.NET: crashes on startup due to missing entry
point named "DXGIDeclareAdapterRemovalSupport" in dll
"dxgi"
Product: Wine
Version: 10.0-rc6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: anotherkdeuser(a)duck.com
Distribution: ---
Created attachment 77886
--> https://bugs.winehq.org/attachment.cgi?id=77886
The resulting error
When downloading and running the portable version of dotnet from:
https://github.com/paintdotnet/release/releases/tag/v5.1.2
When running it with "Windows version" set to Windows 11, it crashes on startup
and shows some error about a missing entry point in the dll "dxgi".
I'd be happy to supply whatever information you require.
--
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=55943
Bug ID: 55943
Summary: Paint.NET 5.0.11: Immediate crash on startup
Product: Wine
Version: 8.20
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: blankie(a)nixnetmail.com
Distribution: ---
Created attachment 75521
--> https://bugs.winehq.org/attachment.cgi?id=75521
Terminal output
When trying to start paint.net, two instances of winedbg suddenly appear, one
saying "A program on your system has crashed, but WineDbg was unable to attach
to the process to obtain a backtrace." and one providing crash info (which I
saved as backtrace.txt).
paint.net also dropped a crash log in
C:/users/blankie/AppData/Local/paint.net/CrashLogs, and I redirected the output
of `wine Program\ Files/paint.net/paintdotnet.exe` to wineoutput.log.
--
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=52364
Bug ID: 52364
Summary: Mouse sticks (doesn't release without an extra click)
after resizing or moving the battle.net client window
Product: Wine
Version: 7.0-rc4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: lexlexlex(a)gmail.com
Distribution: ---
Steps to reproduce:
1. Install the Battle.net client from Blizzard.
2. Run the Battle.net client, such that its window becomes visible on-screen.
If this is not working, please troubleshoot it until it works, since it is
working here on Manjaro XFCE with wine 7.0-rc4.
3. Move or resize the Battle.net client window by holding the left mouse button
and dragging the mouse anywhere.
4. Release the mouse button that was used to move or resize the Battle.net
client window.
5. Move the mouse cursor elsewhere on the screen.
6. Fully click (mouse-down and mouse-up) the left mouse button again.
7. Move the mouse cursor elsewhere on the screen.
Observed behavior:
During step 5 of the steps to reproduce, the Battle.net client window moved or
was resized according to changes in the position of the mouse cursor. Only
during step 7 did that no longer happen.
Expected behavior:
During step 5 of the steps to reproduce, the Battle.net client window is
expected to no longer move or be resized according to changes in the position
of the mouse cursor.
--
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=58615
Bug ID: 58615
Summary: winepath changes behaviour and strips ending path
separator now
Product: Wine
Version: 10.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: osmanx(a)problemloesungsmaschine.de
Distribution: ---
wine_get_unix_file_name() and wine_get_dos_file_name() have change behaviour
starting with Wine 10.13.
Previously, they returned a path ending in a path separator when the provided
input path also ended in a path separator. Now, they always strip the trailing
path separator. The changed behaviour can trivially be seen with winepath:
Wine < 10.13:
```
Z:\home\manx>winepath -w /home/manx
Z:\home\manx
Z:\home\manx>winepath -w /home/manx/
Z:\home\manx\
Z:\home\manx>winepath -u Z:\home
/home
Z:\home\manx>winepath -u Z:\home\
/home/
```
Wine 10.13:
```
Z:\home\manx>winepath -w /home/manx
Z:\home\manx
Z:\home\manx>winepath -w /home/manx/
Z:\home\manx
Z:\home\manx>winepath -u Z:\home
/home
Z:\home\manx>winepath -u Z:\home\
/home
```
This bug affects OpenMPT, and we had to explicitly work-around the behaviour
change (see
<https://github.com/OpenMPT/openmpt/commit/3c4d38aa63c9baade94b9afc846612fa4…>).
The previous behaviour was present at the very least down to Wine 1.8 as far as
I can remember.
--
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=57027
Bug ID: 57027
Summary: GetFinalPathNameByHandleW does not handle paths
exceeding MAX_PATH (260 chars)
Product: Wine
Version: 9.0
Hardware: aarch64
OS: MacOS
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: wine(a)purisa.me
Hello,
I am writing a Rust program that calls canonicalize() on a path that is over
260 characters long. The Windows implementation of this function calls
GetFinalPathNameByHandleW.
On Windows, this works just fine and returns a valid path. With Wine on macOS,
the call returns a win32 error code ERROR_MORE_DATA (234, 0xEA). I re-ran the
binary with WINEDEBUG=+relay and there is an NtStatus code
STATUS_BUFFER_OVERFLOW (0x80000005) coming from NtQueryObject.
I believe this is because the buffer allocated in Wine's implementation of
GetFinalPathNameByHandleW is not large enough for the ObjectInformation
NtQueryObject is trying to return. Should GetFinalPathNameByHandleW fall back
to a dynamically allocated buffer in this situation?
Thank you!
--
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=56639
Bug ID: 56639
Summary: PSO:BB: Various missing/black textures
Product: Wine-staging
Version: 9.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: myriabelmonte(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Phantasy Star Online Blue Burst was an old online only game made by SEGA so it
requires some setup beforehand to play locally but it's easier than ever to set
up, you will require these tools:
Game Server Software
https://github.com/fuzziqersoftware/newserv
Prepatched Client ready to connect to localhost
https://web.archive.org/web/20240402011115/https://ragol.org/files/bb/TethV…
The game relies on a lot of moving textures to acomplish different sci-fi like
effects, however for some reason these appear missing or black or as solid
static colors in many areas such as terminals, fences, doors, etc.
Is not game breaking by any means but probably also affects other games with
similar techniques to achieve similar effects.
I don't think these bugs are a regression but always had been present in Wine
and left unreported, either way, I've tested these on Wine 9.0, Wine 9.5
Staging (the current one shipping with Fedora 40) on the Steam Deck with Proton
Hotfix and in Bottles using various wine combinations too, the result is always
the same with those graphic glitches.
The Wine console with the debug mode on doesn't really displays anything other
than these two strings that might be relevant
0114:fixme:d3d:wined3d_swapchain_set_gamma_ramp Ignoring flags 0x1.
0114:fixme:d3d:state_linepattern_w Setting line patterns is not supported in
OpenGL core contexts.
So instead, here's an Apitrace of the whole process of logging in, heading into
the lobby where the top green bar at the ceiling is missing its moving texture,
and heading into a game room where most of the gfx bugs happen pointing at
various missing textures along the way.
Apitrace (6GB):
https://drive.google.com/file/d/1poIeU-g5nnpMB3Zq37zuo-pxI6SsoNrK/view?usp=…
Other areas screenshots with more similar gfx bugs are attached to this issue
--
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=18233
Summary: Approach underscore bar inactive with multiple database
open
Product: Wine
Version: 1.1.20
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: ToddAndMargo(a)verizon.net
Hi All,
In Lotus Approach, when you have two or more databases open and have them
windowed (Windows --> cascaded, right-left, top-bottom) the underscore button
in the window's internal caption buttons, although showing (not grayed out),
does not work.
Many thanks,
-T
--
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=58608
Bug ID: 58608
Summary: SCardTransmit should work with pioSendPci=NULL
Product: Wine
Version: 10.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winscard
Assignee: wine-bugs(a)winehq.org
Reporter: pq2sx44teeigl7za(a)chyen.cc
Distribution: ---
Although undocumented, winscard.dll on Windows appears to accept
pioSendPci=NULL for SCardTransmit. Such usage is observed in Taipei Fubon
Bank's agent program. Steps to reproduce are:
1. Download and install
https://ebank.taipeifubon.com.tw/EXT/inc/plugins/TfbWebATMServiceInstall.exe
2. Run C:\Program Files (x86)\TFB\WebATM\TFBWebATMAgent.exe
3. Go to https://ebank.taipeifubon.com.tw/EXT/common/CWA/Index.faces and try to
login ("登入" 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.