June 2025 - Wine-Bugs - list.winehq.org

[Bug 58427] New: msxml4 fails to install with status 67
by WineHQ Bugzilla July 16, 2025

July 16, 2025

http://bugs.winehq.org/show_bug.cgi?id=58427 Bug ID: 58427 Summary: msxml4 fails to install with status 67 Product: Wine Version: 10.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msxml4 Assignee: wine-bugs(a)winehq.org Reporter: gudvinr+wine(a)gmail.com Distribution: --- Created attachment 78848 --> http://bugs.winehq.org/attachment.cgi?id=78848 install log I'm installing msxml4 using winetricks: $ winetricks -q msxml3 $ winetricks msxml4 Installation is starting and I am going through all the steps. But in the end in console I'm getting this: ------------------------------------------------------ warning: Note: command wine msiexec /i msxml.msi returned status 67. Aborting. ------------------------------------------------------ linux: 6.15.3 wine version: 10.9 (staging) winearch: win64 wow64: + wayland: + (using unset DISPLAY) --- NOTE: As I'm using arch packages, 10.9 is the latest I can test with ATM. -- 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 July 16, 2025

July 16, 2025

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 July 16, 2025

July 16, 2025

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 July 16, 2025

July 16, 2025

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 July 16, 2025

July 16, 2025

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 July 16, 2025

July 16, 2025

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 July 16, 2025

July 16, 2025

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 July 16, 2025

July 16, 2025

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 52085] New: wine-gecko fails to build with 'storage size of mreq isn't known' on Fedora 35 with gcc11
by WineHQ Bugzilla July 16, 2025

July 16, 2025

https://bugs.winehq.org/show_bug.cgi?id=52085 Bug ID: 52085 Summary: wine-gecko fails to build with 'storage size of mreq isn't known' on Fedora 35 with gcc11 Product: Wine-gecko Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-gecko-unknown Assignee: jacek(a)codeweavers.com Reporter: patrick+winehq.org(a)laimbock.com Distribution: --- Created attachment 71096 --> https://bugs.winehq.org/attachment.cgi?id=71096 Log with build failure due to 'storage size of mreq isn't known' wine-gecko 2.47.2 fails to build with 'storage size of mreq isn't known' on Fedora 35 with gcc11. Log snippet attached. -- 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 6

[Bug 34710] New: Can't register/login with Kindle for PC
by wine-bugs＠winehq.org July 15, 2025

July 15, 2025

http://bugs.winehq.org/show_bug.cgi?id=34710 Bug #: 34710 Summary: Can't register/login with Kindle for PC Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: rosc2112(a)yahoo.com Classification: Unclassified Trying to register Kindle for Pc so it'll login to my amazon account, it's giving an error "Registration Failed, please try again (99) Upgraded the latest version of wine, v 1.6 and still having the same problem, except now I'm not even getting any kind of info from the commandline that would indicate what the problem is. Previous version 1.4 was at least indicating there was a problem connecting via ssl, so I found some posts indicating the problem might be tls, hence I upgraded hoping this issue was resolved, but, apparently not? All I'm getting for errors is: fixme:imm:NotifyIME IMC_SETCANDIDATEPOS fixme:imm:ImmReleaseContext (0x2002a, 0x3e52fb8): stub fixme:win:FlashWindowEx 0x33c944 fixme:win:FlashWindowEx 0x33cc14 fixme:win:FlashWindowEx 0x33d314 fixme:win:FlashWindowEx 0x33c944 fixme:win:FlashWindowEx 0x33ccd4 fixme:imm:NotifyIME IMC_SETCANDIDATEPOS fixme:imm:NotifyIME IMC_SETCANDIDATEPOS fixme:win:FlashWindowEx 0x33c9e4 fixme:winsock:WSAIoctl WS_SIO_UDP_CONNRESET stub Any clues for me? :) -- 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 15