November 2021 - Wine-Bugs - list.winehq.org

[Bug 52093] Installing Insta360 pro stitcher breaks wine completely ( e.g. winecfg gives: malloc(): invalid size (unsorted) Aborted)

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=52093 Louis Lenders <xerox.xerox2000x(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xerox.xerox2000x(a)gmail.com Keywords| |download, regression Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Summary|malloc() after installing |Installing Insta360 pro |Insta360 pro stitcher |stitcher breaks wine |(incl. wine config) |completely ( e.g. winecfg | |gives: malloc(): invalid | |size (unsorted) Aborted) --- Comment #1 from Louis Lenders <xerox.xerox2000x(a)gmail.com> --- Confirming Indeed major bug, as it seems to destroy whole functionality of wine... I also tested in wine-6.0, and that seems to go fine, so I`m marking this as regression. sha1sum Insta360Stitcher_Winx64_3.0.0_20190622.exe 60b9e0c43763ce9184bf63ec9c22c764e421f738 Insta360Stitcher_Winx64_3.0.0_20190622.exe -- 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.

Nov. 23, 2021

[Bug 51989] pen-related tests (gdiplus:graphics and gdiplus:graphicspath) fail on latest Windows 10

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=51989 Esme Povirk <madewokherd(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #71108|0 |1 is obsolete| | --- Comment #8 from Esme Povirk <madewokherd(a)gmail.com> --- Created attachment 71109 --> https://bugs.winehq.org/attachment.cgi?id=71109 patch marking the new results broken New testbot job: https://testbot.winehq.org/JobDetails.pl?Key=102569 -- 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.

Nov. 23, 2021

[Bug 51989] pen-related tests (gdiplus:graphics and gdiplus:graphicspath) fail on latest Windows 10

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=51989 --- Comment #7 from Esme Povirk <madewokherd(a)gmail.com> --- I can already see that I messed that up by putting a broken() in an expect(). -- 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.

Nov. 23, 2021

[Bug 51989] pen-related tests (gdiplus:graphics and gdiplus:graphicspath) fail on latest Windows 10

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=51989 --- Comment #6 from Esme Povirk <madewokherd(a)gmail.com> --- Created attachment 71108 --> https://bugs.winehq.org/attachment.cgi?id=71108 patch marking the new results broken Submitted as testbot job: https://testbot.winehq.org/JobDetails.pl?Key=102566 I'm not sure if testbot ran the updated graphicspath tests, or if any of these are the affected machines. -- 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.

Nov. 23, 2021

[Bug 52081] usbip: error: vhci driver is not loaded

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=52081 --- Comment #10 from Zebediah Figura <z.figura12(a)gmail.com> --- It doesn't really work like that. Wine does in fact have support for directly exposing USB devices, so even if there are no host drivers, Windows programs which want to access the device directly will still work (although you'll probably have to set up permissions on the host side so that Wine can actually open them). Note also that Wine exposes these devices on the "kernel" level, so that Windows kernel drivers which layer on top of USB devices will still work. If a bit of software is able to detect a USB device on Windows when using usbip, but doesn't work on Wine when using a host vhci driver, that's probably just because something else in Wine is broken that's preventing the USB device from being enumerated. I'm pretty sure it would fail similarly even if the usbip vchi driver was working. -- 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.

Nov. 23, 2021

[Bug 51989] pen-related tests (gdiplus:graphics and gdiplus:graphicspath) fail on latest Windows 10

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=51989 --- Comment #5 from Esme Povirk <madewokherd(a)gmail.com> --- Here we go. I got the new version from KB5007885: https://support.microsoft.com/en-us/topic/november-9-2021-kb5007186-os-buil… "Addresses an issue in which certain apps might have unexpected results when rendering some user interface elements or when drawing within the app. You might encounter this issue with apps that use GDI+ and set a zero (0) width pen object on displays with high dots per inch (DPI) or resolution, or if the app is using scaling." So this is broken behavior that MS shipped and later fixed. -- 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.

Nov. 23, 2021

[Bug 51989] pen-related tests (gdiplus:graphics and gdiplus:graphicspath) fail on latest Windows 10

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=51989 --- Comment #4 from Esme Povirk <madewokherd(a)gmail.com> --- Do any of the failing VMs have a gdiplus.dll that's at least as new as that one? If not, maybe we should assume this behavior caused a regression in Windows and was backed out. -- 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.

Nov. 23, 2021

[Bug 51989] pen-related tests (gdiplus:graphics and gdiplus:graphicspath) fail on latest Windows 10

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=51989 --- Comment #3 from Esme Povirk <madewokherd(a)gmail.com> --- Apparently my Windows 10 VM has updated Pen Width reporting behavior (Width set to <1 is reported as 1), but not the new rendering behavior. So I can't use that to check. The VM is 21H1, and I have gdiplus.dll version 10.0.19041.1348. The gdiplus tests pass in my VM as-is. -- 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.

Nov. 23, 2021

[Bug 52081] usbip: error: vhci driver is not loaded

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=52081 --- Comment #9 from Alois Schlögl <alois.schloegl(a)gmail.com> --- (In reply to Zebediah Figura from comment #8) > Ah yes, my phrasing was misleading; I apologize. > > I think it'll probably be more useful to debug the Kaluza software; if it's > not seeing USB devices I'm not sure that Win32 vhci is going to help with > that. > > It might be an interesting exercise to make Win32 vhci work anyway, but I > don't think it's going to provide any features that host vchi doesn't. (It > won't be usable from non-Wine processes, for instance.) I think would provide additions features - for the following reason: I've been able to connect these USB devices on some linux host serving as USBIP server, forward those through USBIP to some windows machine, and I've been able to run the corresponding software on Windows (I'm thinking about CED1401, which is data aquisiton system with up to serveral 100kSamples/seconds., as well as the Kaluza/Sentinel dongle license) As far as I know, no vhci was running on the usbip server. The same software does not work when I connect the same USB device to the host system one which Wine is running (and it will not work through usbip, because usbip-client will no run under Wine). I guess that is because there are no linux drivers for these devices, and so it seems to me that the host-based vhci can not handle these cases. (in Kaluza and usbip I had host-vhci loaded, I can not say whether this was the case when testing ced1401). Or let me ask you this. What would happen if you have some usb device with some windows only drivers. There are no linux drivers available for the above examples (CED1401, and Kaluza/Sentinel). Would vhci on the host being able to handle these and provide the these driver functions to Wine and applications running in Wine ? I doubt that, for the reason described above. I guess Wine does a good job with usb devices where the drivers are somehow standardised and are supported on all OS's, like USB memory sticks, USB cameras, HID devices like keyboard and mouse, and perhaps some dongles. Some might not use vhci, for some host-based vhci might work well. But for devices that have no Linux support, and only Drivers for Windows, Wine does not seem to support these USB devices. Would you agree to that ? When looking at this list https://bugs.winehq.org/buglist.cgi?quicksearch=usb&list_id=748976 I guess a number of these devices fall into that category. The hypothesis is that when vhci would be supported within Wine, it would improve support for these devices as well. -- 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.

Nov. 23, 2021

[Bug 49266] Amazon Games installs but won't start (needs WindowsFormsApplicationBase startup code?)

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=49266 Alexey Ugnichev <alexey.ugnichev(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alexey.ugnichev(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.

Nov. 23, 2021