https://bugs.winehq.org/show_bug.cgi?id=57016
Bug ID: 57016
Summary: staging patchinstall.py fails on security wine_todo
Product: Wine-staging
Version: 9.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: zlice(a)crtdrift.us
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 76859
--> https://bugs.winehq.org/attachment.cgi?id=76859
current_broken_diff
wine-staging-9.13/patches/server-Stored_ACLs/0004-server-Temporarily-store-the-full-security-descripto.patch
--
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=57439
Bug ID: 57439
Summary: FL Studio: many 3rd party plugins violently flash in
child windows
Product: Wine
Version: 9.21
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: lildebil.mgt(a)gmail.com
Distribution: ArchLinux
Created attachment 77436
--> https://bugs.winehq.org/attachment.cgi?id=77436
terminal log
As the title says, In FL Studio, many 3rd party vsts have flashing GUIs that
make them unusable and possibly hazardous to a select amount of people with
photosensitive epilepsy.
This only happens in FL Studio, likely due to how it handles plugin windows. In
other DAWs that let the window manager handle the plugin windows this does not
happen.
Side notes:
1. Most of the plugins with this issues are based on the JUCE framework
2. Whenever there is an option akin to "Disable OpenGL rendering" in the plugin
settings, turning it on will usually fix the flashing, but it is almost never
available.
Steps to reproduce:
1. Set the wineprefix to Windows 7, to avoid bug 57247
2. Download and install FL Studio 2024 Trial -
https://install.image-line.com/flstudio/flstudio_win64_24.1.2.4430.exe
3. Download and install one of the plugins with this problem (put .vst3 file
into C:\Program Files\Common Files\VST3) -
https://github.com/tobanteAudio/modEQ/releases/download/v0.4.0/modEQ-v0.4.0…
4. Scan and open plugin in a mixer track, drag plugin window or start audio
playback to see the issue.
I am using wine-staging 9.21 and proprietary Nvidia drivers
--
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=57740
Bug ID: 57740
Summary: FL Studio popups appear on the wrong monitor
Product: Wine
Version: 10.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: edwin.frank.loeffler(a)gmail.com
Distribution: ---
When using FL Studio with wine's Wayland backend and moving the mixer to a
secondary monitor, popups that appear e.g. when right clicking appear on the
primary monitor, not the one with the mixer.
--
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=57648
Bug ID: 57648
Summary: Wrong Cursor on Wayland
Product: Wine
Version: 9.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winewayland
Assignee: wine-bugs(a)winehq.org
Reporter: jakobdev(a)gmx.de
Distribution: ---
When running under XWayland Wine is using the same cursor as the rest of the
system. But when when using the new experimental Wayland driver, Wine is using
a different cursor than the rest of the system (see screenshots).
Wine should implement the cursor shape protocol
(https://wayland.app/protocols/cursor-shape-v1) to fix 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.
https://bugs.winehq.org/show_bug.cgi?id=57569
Bug ID: 57569
Summary: BeamNG.drive minimizes its window during startup, with
UseTakeFocus set to false.
Product: Wine
Version: 10.0-rc2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: winex11.drv
Assignee: wine-bugs(a)winehq.org
Reporter: logos128(a)gmail.com
Regression SHA1: 0cda91856138e1d49fcfd9b6c2c9328146616baa
Distribution: ArchLinux
Happens only with the default (d3d11) renderer in fullscreen mode.
The UseTakeFocus option is set to 'N' in the registry (HKCU\Software\Wine\X11
Driver\UseTakeFocus). Since this option is turned on by default in Wine,
normally it doesn't cause the aforementioned issue. Although, it would be a
problem for Proton, where UseTakeFocus is tuned off by default
(https://github.com/ValveSoftware/wine/commit/d30ce49ed8b40b9c29b5cc374987ca…),
as it helps some games launch properly.
I use it to run Forza Horizon 5, etc., (Wine-Staging + patches + Steam).
I didn't notice this right away, as I use borderless in BeamNG, which works
properly with UseTakeFocus=false.
--
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=57676
Bug ID: 57676
Summary: Dn-FamiTracker 0.5.1.1: most of instrument editor is
blank
Product: Wine
Version: 10.0-rc5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: wine(a)pineight.com
Distribution: ---
When opening an instrument for editing, most controls in the instrument editor
don't get drawn, leaving a blank space where they should be.
Wine version: 10.0-rc5 from dl.winehq.org repository
Distribution: Xubuntu 24.04 amd64
Graphics: X.Org X Window System 7.7+23ubuntu3, Mesa Intel(R) HD Graphics 5500
(BDW GT2), Mesa 24.0.9-0ubuntu0.3
Program identifiers
Download page:
https://github.com/Dn-Programming-Core-Management/Dn-FamiTracker/releases/t…
SHA-1 hashes:
97024e66beed59c61580ea4a23bea25185440323
/<redacted>/Dn-FamiTracker_v0511_x64_Release.7z
201990bcb93c72d47061fe69eb3fc6599518d5e1 /<redacted>/Dn-FamiTracker.exe
Steps to reproduce:
1. Download Dn-FamiTracker_v0511_x64_Release.7z and extract it to a new folder.
2. Open Dn-FamiTracker.exe.
3. At top right is a list of instruments that begins with "[2A03] 00 -".
Double-click the "00 -" to open the instrument editor.
4. The "Instrument editor" floating window appears. It has two panes, with tabs
"2A03 settings" and "DPCM samples".
Behavior on Windows and Wine 9.x:
To the left side is an "Instrument settings" group containing a list of effects
"Volume, Arpeggio, Pitch, Hi-pitch, Duty / Noise", button "Select next empty
slot", and a combo box labeled "Sequence #". To the right is a "Sequence
editor" group with a graph, "Size: [-] 0 [+]" and a text input to enter a
volume sequence as numbers. At bottom is a piano keyboard.
Behavior on Wine 10.0-rc5:
Everything in pane "2A03 settings" other than the graph and the piano keyboard
is blank. Switching to pane "DPCM samples" and back to pane "2A03 settings"
reveals the hidden controls.
--
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=42171
Bug ID: 42171
Summary: IrfanView's 4.44 Help -> About window has wrong
placement for textboxes
Product: Wine
Version: 2.0-rc4
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdi32
Assignee: wine-bugs(a)winehq.org
Reporter: dark.shadow4(a)web.de
Distribution: ArchLinux
Created attachment 56775
--> https://bugs.winehq.org/attachment.cgi?id=56775
Wrong placement of labels
Note: Split of and blocked by 6682, only works with patches not yet in wine.
https://source.winehq.org/patches/data/128612https://source.winehq.org/patches/data/128613
The textboxes in irfanviews about dialog overlap the image.
The issue is somehow related to Bug 41639.
If my lib32-freetype2 is up to date with version 2.7, the font is ugly, but it
renders fine. If downgraded, the font is fine, but the placement is wrong.
I can submit a testcase for that, but which font can I rely on? Wine doesn't
have all fonts after all. Tahoma maybe?
--
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=55981
Bug ID: 55981
Summary: Dragon Age Origins: Runs slowly when using the
experimental wow64 mode
Product: Wine
Version: 8.21
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: berillions(a)gmail.com
Distribution: ---
Created attachment 75572
--> https://bugs.winehq.org/attachment.cgi?id=75572
Dragon Age : Origins main menu with new wow64 + OpenGL renderer
Dragon Age : Origins works with the new wow64 experimental mode but it's very
slowly and unplayable. This bug affect "Beyond Good & Evil" too.
Use DXVK fix this issue so something wrong with new wow64 + opengl renderer ?
--
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=35756
Bug ID: 35756
Summary: Bugzilla robots.txt prevents google indexing
Product: WineHQ Bugzilla
Version: unspecified
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: bugzilla-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: adys.wh(a)gmail.com
https://bugs.winehq.org/robots.txt
This is annoying as bugs cant be found through google.
--
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=28674
Bug #: 28674
Summary: using OpenID login is a necessity
Product: WineHQ Bugzilla
Version: unspecified
Platform: All
OS/Version: All
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: bugzilla-unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: A.Pirard(a)ulg.ac.be
Classification: Unclassified
>We are sorry to report that recently our login database for the
>WineHQ Bugzilla Database was compromised.
>To prevent further damage we have reset your password to what is shown
>below. We strongly suggest that if you shared your WineHQ bugs
>password on any other sites that you change that password as soon
>as possible.
How is it possible to manage passwords on 200 sites if they don't use OpenID?
Is it so hard to understand?
PLEASE USE OPENID LOGIN !!!!!!
--
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.