wine-bugs August 2025

wine-bugs@winehq.org

1 participants
496 discussions

[Bug 58096] New: Window title bar double-click to return from maximized state sometimes makes window full sized
by WineHQ Bugzilla 14 Aug '25

14 Aug '25

http://bugs.winehq.org/show_bug.cgi?id=58096 Bug ID: 58096 Summary: Window title bar double-click to return from maximized state sometimes makes window full sized 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: wine_bugzilla(a)sctb.ch Distribution: --- I use WINE to run PFE, a text editor. https://www.lancaster.ac.uk/people/steveb/cpaap/pfe/ I've noticed recently that behaviour has changed when double-clicking the title bar. Normally, double clicking title maximizes window, and double clicking again minimizes window. What now *sometimes* happens is that the first double click as expected maximizes, but the second double click returns the window to its normal size but then instantly changes the actual window size to the maximum possible (to the screen size). This is *not* the maximized state, because double clicking now - no matter how many times - does not change the window size. The window has actually been resized (and so further double clicks are converting a screen-sized window to maximized, and then back to screen-sized). At this point the window has to be manually resized back to something non-maximum. My suspicion here is that I might be issuing from the mouse a very rapid *triple* click, and there's some kind of race condition, where the third click is causing the observed behavour; and that this is why it happens *sometimes* only. -- 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.

1 2

[Bug 58046] New: Horizon Chase Turbo: gamepad hotplugging doesn't work
by WineHQ Bugzilla 14 Aug '25

14 Aug '25

https://bugs.winehq.org/show_bug.cgi?id=58046 Bug ID: 58046 Summary: Horizon Chase Turbo: gamepad hotplugging doesn't work Product: Wine Version: 10.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: dinput Assignee: wine-bugs(a)winehq.org Reporter: tinozzo123(a)gmail.com Distribution: --- Created attachment 78302 --> https://bugs.winehq.org/attachment.cgi?id=78302 `WINEDEBUG=+dinput`, launch game with one gamepad, disonnected, reconnected. In Horizon Chase Turbo (tested Epic Games Store version), gamepads are only usable if they have always been connected since the game has been launched. Otherwise, their inputs are completely ignored, and these gamepads will not be listed in the player mapping screen (Multiplayer). This is not the case on Windows. The only exception is in the title screen: "Press Any Button" does work with hotplugged gamepads. Logs are taken on a fresh prefix with `WINEDEBUG=+dinput`. Without this, the only dinput-related log is: ``` 0208:fixme:dinput:hid_joystick_device_try_open device usage ff72:00a1 not implemented! ``` -- 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.

1 3

[Bug 58509] New: AppDB solution to redundant query and storage of Bugzilla versions list per user session
by WineHQ Bugzilla 14 Aug '25

14 Aug '25

http://bugs.winehq.org/show_bug.cgi?id=58509 Bug ID: 58509 Summary: AppDB solution to redundant query and storage of Bugzilla versions list per user session Product: WineHQ Apps Database Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: appdb-unknown Assignee: wine-bugs(a)winehq.org Reporter: wineryyyyy(a)gmail.com Distribution: --- Spawned from merge request addressing bug report: https://gitlab.winehq.org/winehq/appdb/-/merge_requests/23 https://bugs.winehq.org/show_bug.cgi?id=58471 Bug Link Queue is broken @jnewman raised server side concerns about redundantly querying and storing Bugzilla version per user session. A quick fix patch is currently in place to resolve the 500 error, but a better solution that queries and caches the Bugzilla versions server-wide and shared between user sessions was requested as a more optimal solution. -- 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.

1 2

Your personal data has leaked due to suspected harmful activities.
by wine-bugs＠winehq.org 14 Aug '25

14 Aug '25

Hi there! I am a professional hacker and have successfully managed to hack your operating system. Currently I have gained full access to your account. In addition, I was secretly monitoring all your activities and watching you for several months. The thing is your computer was infected with harmful spyware due to the fact that you had visited a website with porn content previously. ╭ ᑎ ╮ Let me explain to you what that entails. Thanks to Trojan viruses, I can gain complete access to your computer or any other device that you own. It means that I can see absolutely everything in your screen and switch on the camera as well as microphone at any point of time without your permission. In addition, I can also access and see your confidential information as well as your emails and chat messages. You may be wondering why your antivirus cannot detect my malicious software. Let me break it down for you: I am using harmful software that is driver-based, which refreshes its signatures on 4-hourly basis, hence your antivirus is unable to detect it presence. I have made a video compilation, which shows on the left side the scenes of you happily masturbating, while on the right side it demonstrates the video you were watching at that moment..ᵔ.ᵔ All I need is just to share this video to all email addresses and messenger contacts of people you are in communication with on your device or PC. Furthermore, I can also make public all your emails and chat history. I believe you would definitely want to avoid this from happening. Here is what you need to do - transfer the Bitcoin equivalent of 960 USD to my Bitcoin account (that is rather a simple process, which you can check out online in case if you don't know how to do that). Below is my bitcoin account information (Bitcoin wallet):1BXNuQZQFDNoPjvncpkUBVxPZmwbQtK8g7 Once the required amount is transferred to my account, I will proceed with deleting all those videos and disappear from your life once and for all. Kindly ensure you complete the abovementioned transfer within 50 hours (2 days +). I will receive a notification right after you open this email, hence the countdown will start. Trust me, I am very careful, calculative and never make mistakes. If I discover that you shared this message with others, I will straight away proceed with making your private videos public. Good luck!

1 0

[Bug 58595] New: gitlab fails to run rebase builds due to missing contributor name
by WineHQ Bugzilla 13 Aug '25

13 Aug '25

http://bugs.winehq.org/show_bug.cgi?id=58595 Bug ID: 58595 Summary: gitlab fails to run rebase builds due to missing contributor name Product: WineHQ Gitlab Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: gitlab-unknown Assignee: wine-bugs(a)winehq.org Reporter: hibbsncc1701(a)gmail.com Distribution: --- When I attempted to rebase MR 8679 to current git via the web UI the build failed with an error stating that it did not have a valid committer name. This is despite my name and email address being defined in my gitlab profile and my gitlab settings being set to use the primary email for the web UI actions. The log also indicates that it failed to use my email address instead defaulting to the gitlab runner name. Build log: https://gitlab.winehq.org/hibbsncc1701/wine/-/jobs/180801 -- 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.

1 2

[Bug 58572] New: wine crashes on the wayland driver when virtual-keyboard-unstable-v1 is used
by WineHQ Bugzilla 13 Aug '25

13 Aug '25

http://bugs.winehq.org/show_bug.cgi?id=58572 Bug ID: 58572 Summary: wine crashes on the wayland driver when virtual-keyboard-unstable-v1 is used Product: Wine Version: 10.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winewayland Assignee: wine-bugs(a)winehq.org Reporter: azulbeae(a)icloud.com Distribution: --- https://wayland.app/protocols/virtual-keyboard-unstable-v1 This protocol is used by basically every wayland native/supported on-screen virtual keyboard, and by tools like https://git.sr.ht/~brocellous/wlrctl or https://github.com/atx/wtype Whenever virtual keyboard protocols are used when winewayland.drv is in use, wine immediately crashes. To replicate the issue, install wlrctl or wtype, then make them type any string while wine is running. -- 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.

1 5

[Bug 2082] DirectDraw games only showing black screen
by WineHQ Bugzilla 12 Aug '25

12 Aug '25

http://bugs.winehq.org/show_bug.cgi?id=2082 Ben Shadwick <benshadwick(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|benshadwick(a)gmail.com | -- 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.

1 0

[Bug 2082] DirectDraw games only showing black screen
by WineHQ Bugzilla 12 Aug '25

12 Aug '25

http://bugs.winehq.org/show_bug.cgi?id=2082 Stian Low <wineryyyyy(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wineryyyyy(a)gmail.com --- Comment #179 from Stian Low <wineryyyyy(a)gmail.com> --- (In reply to Zeb Figura from comment #177) > (In reply to chaosesqueteam from comment #176) > I really don't know where you're getting this from. You have started posting > on this bug tracker less than two weeks ago. > Please stop adding noise and complaints to bugs. My interactions with chaosesqueteam recently have felt like interacting with a bot and/or troll. Google search the account and you'll find suspicious suspect activity. Already suspended from Blender community: https://blenderartists.org/t/suspension-reports/1465069/6 -- 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.

1 0

[Bug 2082] DirectDraw games only showing black screen
by WineHQ Bugzilla 12 Aug '25

12 Aug '25

http://bugs.winehq.org/show_bug.cgi?id=2082 --- Comment #178 from chaosesqueteam(a)sogetthis.com --- (In reply to Zeb Figura from comment #177) I've been programming for free software since 2001. 24 years. Been using wine a similar amount of time. Diablo 1 always worked to some degree or another as far as I can remember. I just tried forcing it now to a windowed mode using DxWnd (note: in OSX); only got to see the red bottom of the screen (up from being all black in full screen mode): and then it crashed. This is a regression as far as I can tell. And yes: in free software/ opensource, things are just dismissed and labeled won't fix now. As if it's a professional corporate environment. Started since someone decided to attempt to extract slave labour from graduates by requiring opensource contributions for job placement. Forcing the unwilling (or coercing) to interact with opensource just destroys the culture that caused its success. And the removal of that culture is causing regressions and failure. From the removal of ReiserFS because it's "unmaintained" (this was never a requirement: we used not look a gift horse in the mouth and were grateful for any contributions of code from anyone) with the underlying reason being that it's author is hated by the new people who have replaced the hackers that once built everything in this subject, to various other speech-code related enforcements (codes of conduct): contribution from actual hackers has been "DEEPRECIATTTEEED" (again: we never used to "DEEPREEECIATE" anything: working on old hardware, working with the same configs for decades since the 70s and 80s was a point of pride in linux and the bsds.) and has largely been ceased. People like Hans Reiser are not "allowed" to contribute to opensource anylonger: where as the previous mantra; and promise; was code is what mattered: not character (not that there is anything wrong with Reiser's character: he's a man of brutal and direct action: something the hackers who created free software didn't have any opinion either way about) Things are now ripped out of opensource because of who the author is, and what he believes, and what he did to the beloved class of new-testament coded beliefs: while being of the hated class that loves the ideas of the unadultered old testament and classical works from the same time period (not in english). (Hans Reiser, clearly being of the latter class) ReiserFS made Linux. And it may have made all of opensource in a way. Linux was nothing and nowhere before it. I remember those days. It shot up to the sky on the data centre once the JournalingFS was included. We all switched to it. It also forced the people who made ext2 to add journaling and make ext3 years later. They wouldn't have done it otherwise. With Linux's rise, after ReiserFS was added; everything else rose too. But Hans Reiser is treated like shit now. He is not respected for his work. Same with every other "old" C programmer. They're all kicked out of their own projects. Taken over by entryists. Everything degraded, regressed, and slowed down. The type of men who were attracted to working on these engineering projects don't bother working collectivly anymore: they will not work for FREE under speech codes: or under others ruling over them "socially". Which is the reason this has been added to opensource and freesoftware (though RMS resisted it abit). To discourage engineer participation. It is effective. There was a time when opensource was the top in security, in resource usage, and in keeping old machines running, and in new features. JournalingFS, Pax/GRsecurity hardening, fast execution on ancien regime machines. We had it all. And it was taken away. Socially. When we were targeted by the intelligence agencies, now quite awhile ago. But I remeber it happening. Here's the error in windowed mode on OSX, : seems the same to me: [mvk-info] GPU device: model: Intel HD Graphics 4000 type: Integrated vendorID: 0x8086 deviceID: 0x0166 pipelineCacheUUID: 49B97F26-0A0F-0200-0000-000100000000 GPU memory available: 1536 MB GPU memory used: 0 MB Metal Shading Language 2.2 supports the following GPU Features: GPU Family Mac 2 Read-Write Texture Tier 1 [mvk-info] Created VkInstance for Vulkan version 1.0.0, as requested by app, with the following 2 Vulkan extensions enabled: VK_KHR_external_memory_capabilities v1 VK_KHR_get_physical_device_properties2 v2 016c:fixme:thread:get_thread_times not implemented on this platform 0144:fixme:msg:pack_message msg 14 (WM_ERASEBKGND) not supported yet 0144:fixme:msg:pack_message msg 14 (WM_ERASEBKGND) not supported yet -- 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.

1 0

[Bug 2082] DirectDraw games only showing black screen
by WineHQ Bugzilla 12 Aug '25

12 Aug '25

http://bugs.winehq.org/show_bug.cgi?id=2082 Zeb Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12(a)gmail.com --- Comment #177 from Zeb Figura <z.figura12(a)gmail.com> --- (In reply to chaosesqueteam from comment #176) > Could the entryists that are just going to close and delete this bug be > gotten rid of? That's how free software is now: every "package" or "app" (we > used to call them programs and projects) is brigaded by do-nothings padding > their resume by "resolving" bugs. They just "wont fix" everything and cause > the project to get worse and worse. I really don't know where you're getting this from. You have started posting on this bug tracker less than two weeks ago. No bug you have filed, or even commented on, has been closed WONTFIX. As someone familiar with many of them, I don't imagine they will be either, although some of them are very hard and will probably take a lot of time and resources to fix. The fact that this very bug is 20 years old but still open should be evidence of this. Please stop adding noise and complaints to bugs. Apart from everything else it's a great way to make developers not want to interact with you, or work on the bugs you are filing. -- 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.

1 0

← Newer
1
...
40
41
42
43
44
45
46
...
50
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs August 2025