wine-bugs May 2025

wine-bugs@winehq.org

1 participants
932 discussions

[Bug 55556] New: Contradicting support for Intel Arc GPUs while not supporting DXVK in AppDB and/or Bugzilla
by WineHQ Bugzilla 16 Jul '25

16 Jul '25

https://bugs.winehq.org/show_bug.cgi?id=55556 Bug ID: 55556 Summary: Contradicting support for Intel Arc GPUs while not supporting DXVK in AppDB and/or Bugzilla 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: linards.liepins(a)gmail.com Distribution: --- As per https://www.tomshardware.com/news/intel-gpu-driver-optimizations-leverage-v…, the Intel Arc drivers are already using/bundling-ion DXVK to handle DX9 APIs. That means that if you support Intel Arc GPUs as GPU option, you automatically support DXVK as well ( because Wine uses kernel driver as-is, correct? ). That meanst that not accepting buzilla bugs with DXVK is wrong/offernsive/unfriendly. If that isa not true, then PLEASE fix the AppDB and Bugzilla to have conditional handling of Intel GPU and non-Intel-GPU options and educate the maintainers/reviewers accordingly. -- 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 18790] New: Default search does not include resolved bugs
by wine-bugs＠winehq.org 16 Jul '25

16 Jul '25

http://bugs.winehq.org/show_bug.cgi?id=18790 Summary: Default search does not include resolved bugs Product: WineHQ Bugzilla Version: unspecified Platform: PC OS/Version: Linux Status: NEW Keywords: download, source Severity: enhancement Priority: P3 Component: bugzilla-unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: kennybobs(a)o2.co.uk The default search (the search box at the top of this page) does not include closed bugs (rightly so), but it also does not include resolved bugs. This leads to duplicates that could be avoided. See Bug 18601 - a recent regression that is fixed by the next release, but anyone searching for an open bug for Google Sketchup will not see it unless they choose to run an advanced search, which some users clearly don't. I'm sure this is a simple change to the code. -- 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.

2 9

[Bug 24566] New: bugzilla adds mr.bugs to cc list?
by wine-bugs＠winehq.org 16 Jul '25

16 Jul '25

http://bugs.winehq.org/show_bug.cgi?id=24566 Summary: bugzilla adds mr.bugs to cc list? Product: WineHQ Bugzilla Version: unspecified Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: bugzilla-unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com Bugs start out with Mr. Bugs as the default assignee, which is evidently intended so the mailing list gets copied on all bug changes. That's fine. But under some situations, bugzilla seems to also automatically add mr. bugs to the cc list. For instance, here: http://www.winehq.org/pipermail/wine-bugs/2010-September/251648.html Whereupon Dmitry promptly removed it from the cc: http://www.winehq.org/pipermail/wine-bugs/2010-September/251690.html Austin verified that this had been done automatically by repeating his component change: http://www.winehq.org/pipermail/wine-bugs/2010-September/251728.html and then removed the extra cc manually in the next change. What's going on here? Should that cc be added automatically or not? -- 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.

2 8

[Bug 39009] New: "Importance" link on bug report form opens in wrong place on fields descriptions page
by wine-bugs＠winehq.org 16 Jul '25

16 Jul '25

https://bugs.winehq.org/show_bug.cgi?id=39009 Bug ID: 39009 Summary: "Importance" link on bug report form opens in wrong place on fields descriptions page 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: dimesio(a)earthlink.net Distribution: --- The fields description page has two sections for Importance. The first one is right below the status definitions table; right below it are the definitions for Priority and Severity (which is what users need to see). The second Importance section is toward the bottom of the page, and it just describes the field as "the combination of its Priority and Severity" without the severity definitions anywhere in sight. Clicking the Importance link on the bug report form opens the page at the second Importance section when it should open at the first one (or even better, at the Severity section, since that's what we really want users to see). The result is that users don't see the actual definitions for severity even if they do bother to click the link. -- 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.

2 4

[Bug 12091] New: out of place text on bugzilla component description page
by wine-bugs＠winehq.org 16 Jul '25

16 Jul '25

http://bugs.winehq.org/show_bug.cgi?id=12091 Summary: out of place text on bugzilla component description page Product: WineHQ Bugzilla Version: unspecified Platform: Other OS/Version: other Status: NEW Severity: trivial Priority: P2 Component: bugzilla-unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: thestig(a)google.com I can't seem to find the change for this in bugzilla.git... On http://bugs.winehq.org/enter_bug.cgi, someone added the text: <-- You probably want to use that link there! Wine bugs. Submit bugs related to Wine here. <-- Use this if in doubt! but it also appears on this page: http://bugs.winehq.org/describecomponents.cgi?product=Wine which doesn't make any sense. -- 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.

2 6

[Bug 53257] New: Emacs 28.1 is unusable
by WineHQ Bugzilla 16 Jul '25

16 Jul '25

https://bugs.winehq.org/show_bug.cgi?id=53257 Bug ID: 53257 Summary: Emacs 28.1 is unusable Product: Wine Version: 7.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: EmilySeville7cf(a)gmail.com Distribution: --- Created attachment 72636 --> https://bugs.winehq.org/attachment.cgi?id=72636 screenshot of console emacs I install Emacs 28.1 from here (http://mirror.tochlab.net/pub/gnu/emacs/windows/emacs-28/) emacs-28.1-installer.exe and run it via "C:\Program Files\Emacs\emacs-28.1\bin\runemacs.exe" ". When I use GUI version of Emacs it's window is moved to the left upper corner when I press any button. Workaround: maximize window size and use Emacs. When I use console Emacs version (emacs -nw) from wine cmd I can do nothing at all. Any Emacs shortcut breaks interface. For instance I've tried use "Ctrl+N" and obtain result on the screenshot. -- 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 9

[Bug 41825] New: Typo in "Comments Disabled"
by wine-bugs＠winehq.org 16 Jul '25

16 Jul '25

https://bugs.winehq.org/show_bug.cgi?id=41825 Bug ID: 41825 Summary: Typo in "Comments Disabled" Product: WineHQ.org Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: www-unknown Assignee: wine-bugs(a)winehq.org Reporter: plata(a)mailbox.org Distribution: --- "Comments for this application have be disabled becuase there are no maintainers." -- 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.

2 5

[Bug 46624] New: StarCraft: Remastered Edition disabled Monitors, Gamma Correction and Real-Time Lightning configuration
by wine-bugs＠winehq.org 16 Jul '25

16 Jul '25

https://bugs.winehq.org/show_bug.cgi?id=46624 Bug ID: 46624 Summary: StarCraft: Remastered Edition disabled Monitors, Gamma Correction and Real-Time Lightning configuration Product: Wine-staging Version: 4.0 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: linards.liepins(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 63525 --> https://bugs.winehq.org/attachment.cgi?id=63525 screenshot Attaching Screenshot. Logs not provided as I am using Battle.net Launcher. Distro: Fedora 29 x64 System details / Graphics: Device-1: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] vendor: XFX Pine driver: amdgpu v: kernel bus ID: 01:00.0 chip ID: 1002:67df Display: x11 server: Fedora Project X.org 1.20.3 driver: amdgpu compositor: gnome-shell v: 3.30.2 resolution: 1920x1080~60Hz OpenGL: renderer: Radeon RX 580 Series (POLARIS10 DRM 3.27.0 4.20.6-200.fc29.x86_64 LLVM 7.0.1) v: 4.5 Mesa 18.3.3 direct render: Yes NOTE: Mesa upgraded from Mesa 18.2.8 to 18.3.3 via https://copr.fedorainfracloud.org/coprs/petrb/mesa/ -- 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.

2 53

[Bug 56246] New: Regarding the color depth of BMP in the SavePicture method: the value is unstable.
by WineHQ Bugzilla 16 Jul '25

16 Jul '25

https://bugs.winehq.org/show_bug.cgi?id=56246 Bug ID: 56246 Summary: Regarding the color depth of BMP in the SavePicture method: the value is unstable. Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: win32u Assignee: wine-bugs(a)winehq.org Reporter: taka(a)bahamut7.com Distribution: --- Created attachment 75953 --> https://bugs.winehq.org/attachment.cgi?id=75953 Difference in color depth between Wine and Windows Thank you for the great software. In Windows 10/11, the SavePicture method saves in "24-bit color" even if the display's color setting is "32-bit color". In Wine, if the display's color setting is "32bit color", the picture is saved in "32bit color" and the Windows software throws an error. In Debian, for some reason, it is saved with the value "0". Due to this difference, some software may not work. -- 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 10

[Bug 58122] New: WSAENOTSOCK error when calling winsock.Send() on duplicated socket
by WineHQ Bugzilla 16 Jul '25

16 Jul '25

http://bugs.winehq.org/show_bug.cgi?id=58122 Bug ID: 58122 Summary: WSAENOTSOCK error when calling winsock.Send() on duplicated socket Product: Wine-staging Version: 10.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: digitman63(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Process A creates a listening socket, accepts an incoming connection, and obtains a socket handle hSock. Process A spawns Process B with the InheritHandles flag, passing its own ProcessID and the socket handle hSock as command-line arguments. Process B calls OpenProcess() to get a handle hSrcProcess for the given ProcessID, then duplicates hSock into hDupSock using DuplicateHandle(hSrcProcess, hSock, GetCurrentProcess(), &hDupSock, ...); Process B successfully receives data from the duplicated socket using winsock.recv(hDupSock, ...). Process B attempts to send data via winsock.send(hDupSock, ...), but the call fails with WSAENOTSOCK (10038) ("Socket operation on non-socket"). Process B then tries sending the same data using kernel32.WriteFile(hDupSock, ...), and this operation succeeds. Why does send() fail while WriteFile() works on the same duplicated handle? -- 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 9

← Newer
1
...
10
11
12
13
14
15
16
...
94
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 May 2025