September 2023 - Wine-Bugs - list.winehq.org

[Bug 54794] New: Autodesk Fusion360: New SSO login will not open web browser
by WineHQ Bugzilla Feb. 23, 2024

Feb. 23, 2024

https://bugs.winehq.org/show_bug.cgi?id=54794 Bug ID: 54794 Summary: Autodesk Fusion360: New SSO login will not open web browser Product: Wine Version: 8.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: skala.antonin(a)gmail.com Distribution: --- Created attachment 74289 --> https://bugs.winehq.org/attachment.cgi?id=74289 Running processes Autodesk rolled out new update (03 April) adding new SSO login instead of build-in one. Clicking on Sign In button should open default browser and redirect user into logIn page, but no browser will open (no error visible inside console). We tried to set http/https in HKEY_CLASSES_ROOT registers, also install windows version of Firefox and ivent it runs, Fusion still refuses to open it. Listing processes show, that new login component run (AdskIdentityManager.exe) Exact steps we tried can be found there: https://github.com/cryinkfly/Autodesk-Fusion-360-for-Linux/issues/319 Installer: https://dl.appstreaming.autodesk.com/production/installers/Fusion%20360%20A… -O Fusion360installer.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.

1 13

[Bug 50643] New: IK Product Manager: Unable to download plugins
by WineHQ Bugzilla Feb. 23, 2024

Feb. 23, 2024

https://bugs.winehq.org/show_bug.cgi?id=50643 Bug ID: 50643 Summary: IK Product Manager: Unable to download plugins Product: Wine Version: 6.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wmi&wbemprox Assignee: wine-bugs(a)winehq.org Reporter: gearoidburke(a)outlook.com Distribution: --- Created attachment 69355 --> https://bugs.winehq.org/attachment.cgi?id=69355 Wine log file. IK Product Manger (https://www.ikmultimedia.com/products/productmanager/) should be able to download and install VST plugins from IK Multimedia, however upon clicking the install button for any plugin, the application will become unresponsive for a minute or so before resuming as if nothing had happened. The error in wine seems to be with wmic, with a wmic logicaldisk command failing. The download location, by default ~/Documents/IK Multimedia/IK Product Manager, is empty. Upon clicking the install button on a plugin again, nothing happens. IK Product Manager installs and works as expected up until this point, provided you have a dx11 compatibility layer like dxvk installed, though sometimes I need to use wine-staging to get it to run properly. I would have liked to have tested this in a 32 bit prefix so I could install wmi, but the application is 64 bit only. Wine version is 6.1-1, 64 bit architecture. Tested on both wine and wine-staging. OS is Arch Linux, 64 bit, kernel 5.10. Hardware: Thinkpad X13 Yoga, Intel Core i5-10310U with Intel integrated graphics. -- 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 15

[Bug 52064] New: Solidworks 2008 crashes on startup - Regression since Wine 5.21
by WineHQ Bugzilla Feb. 23, 2024

Feb. 23, 2024

https://bugs.winehq.org/show_bug.cgi?id=52064 Bug ID: 52064 Summary: Solidworks 2008 crashes on startup - Regression since Wine 5.21 Product: Wine Version: 6.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jpleonard12(a)gmail.com Distribution: --- Created attachment 71076 --> https://bugs.winehq.org/attachment.cgi?id=71076 Debug log file SolidWorks 2008 worked well on Wine (32bit) up through Wine 5.21. After this, it crashes on startup, once the full screen workspace is displayed. Sometimes it allows the user to browse for a file, but will always crash before the graphics are displayed. Laptop on which SolidWorks 2008 is still working almost flawlessly: --------------------------------------- Wine 5.21 (32bit/WinXP) Linux Mint 18.3, kernel 4.4.0.159-generic winetricks msxml6 vcrun2005 dotnet20 Mesa DRI Intel(R) Ivybridge Mobile 4.2 (Core Profile) Mesa 18.0.5 3.0 Mesa 18.0.5 Desktop on which SolidWorks crashes on startup ---------------------------------------------- Wine 6.21 (32bit/WinXP) Linux Mint 20.1 kernel 5.11.0.40-generic winetricks msxml6 vcrun2005 dotnet20 Mesa DRI Intel(R) HD Graphics 2500 (IVB GT1) 4.2 (Core Profile) Mesa 21.0.3 3.0 Mesa 21.0.3 Have also attempted to run in plain 64 bit wine instance, as well as many combinations of msxml6, dotnet20, dotnet30, vcrun2005, gdiplus_winxp, as well as most versions of Wine 5.22 thru 6.21. But the crash always occurs in the same spot. -- 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 11

[Bug 51458] New: Western Digital SSD Dashboard displays black screen
by WineHQ Bugzilla Feb. 23, 2024

Feb. 23, 2024

https://bugs.winehq.org/show_bug.cgi?id=51458 Bug ID: 51458 Summary: Western Digital SSD Dashboard displays black screen Product: Wine Version: 6.12 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: alexhenrie24(a)gmail.com Distribution: --- Created attachment 70302 --> https://bugs.winehq.org/attachment.cgi?id=70302 Console output The program installs, but when you try to run it, it just displays a black screen. Console output is attached. I'm guessing this is the problem: 0130:fixme:hlsl_parser:declare_vars Complex initializers are not supported yet. Dashboard version: 3.2.2.9 Installer version: 4.0.2.3 $ sha256sum DashboardSetup.exe 9670e6bd54e1e0729262f13ded12de56d0a02a0e29ba0c9e6e6cb3663de4c781 -- 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 8

[Bug 45901] New: Avoid GPU synchronization due to GPU-CPU transfer ( Overwatch)
by wine-bugs＠winehq.org Feb. 23, 2024

Feb. 23, 2024

https://bugs.winehq.org/show_bug.cgi?id=45901 Bug ID: 45901 Summary: Avoid GPU synchronization due to GPU-CPU transfer (Overwatch) Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: awesie(a)gmail.com Distribution: --- Created attachment 62422 --> https://bugs.winehq.org/attachment.cgi?id=62422 Patch to avoid GPU synchronization One performance gap with Overwatch on Wine + AMD + Mesa is GPU synchronization due to transfers from GPU texture to CPU texture. By using PBOs and glReadPixels with GL_PIXEL_PACK_BUFFER, we can avoid this synchronization leading to improved performance. The attached patch is one approach to resolve the performance issue, but I am not sure that it is the best way. Feedback is appreciated. Also attached is before and after screenshots with Mesa's HUD. You can observe that the buffer wait time decreases with the patched version. Both the before and after screenshots are on wine-staging master plus my patch for 45723. -- 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 17

[Bug 50297] New: Blindwrite 7 crashes with a stack overflow (followup to #49092)
by WineHQ Bugzilla Feb. 23, 2024

Feb. 23, 2024

https://bugs.winehq.org/show_bug.cgi?id=50297 Bug ID: 50297 Summary: Blindwrite 7 crashes with a stack overflow (followup to #49092) Product: Wine Version: 5.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bernhardu(a)mailbox.org Distribution: --- Created attachment 68867 --> https://bugs.winehq.org/attachment.cgi?id=68867 Do wineserver calls on a different stack by using fibers. I still can reproduce this issue with wine-6.0-rc1. 00f0:err:virtual:virtual_setup_exception stack overflow 4548 bytes in thread 00f0 addr 0x40e68e stack 0x21fe3c (0x220000-0x221000-0x320000) (rr) bt 30 #0 0xb7db9b5e in __libc_disable_asynccancel (oldtype=0) at ../nptl/cancellation.c:72 #1 0xb7e35705 in __GI___writev (iovcnt=2, iov=0x222058, fd=3) at ../sysdeps/unix/sysv/linux/writev.c:26 #2 __GI___writev (fd=3, iov=0x222058, iovcnt=2) at ../sysdeps/unix/sysv/linux/writev.c:24 #3 0xb7bd68ae in send_request (req=0x2221ac) at .../wine-git/dlls/ntdll/unix/server.c:213 #4 0xb7bd69f0 in server_call_unlocked (req_ptr=0x2221ac) at .../wine-git/dlls/ntdll/unix/server.c:273 #5 0xb7bd6a4b in wine_server_call (req_ptr=0x2221ac) at .../wine-git/dlls/ntdll/unix/server.c:289 #6 0xb7bcf1cd in NtOpenKeyEx (key=0x222340, access=131097, attr=0x2222b8, options=0) at .../wine-git/dlls/ntdll/unix/registry.c:112 #7 0xb7bb11be in __wine_syscall_dispatcher () from /home/benutzer/.local/share/rr/wine-1/mmap_pack_2_ntdll.so #8 0x7bc0bdcc in NtOpenKeyEx(a)16 () from /home/benutzer/.local/share/rr/wine-1/mmap_pack_343_ntdll.dll #9 0x7b0561af in RegOpenKeyExW(a)20 (hkey=<optimized out>, name=0x46c06dc, options=0, access=131097, retkey=0x222340) at .../wine-git/dlls/kernelbase/registry.c:208 #10 0x006996a6 in ?? () #11 0x0069ab41 in ?? () #12 0x00699e14 in ?? () #13 0x0069a89b in ?? () #14 0x0069a84f in ?? () #15 0x0073bb4b in ?? () #16 0x007354d2 in ?? () #17 0x00736cc5 in ?? () #18 0x00736f53 in ?? () #19 0x00737f77 in ?? () #20 0x007384a9 in ?? () #21 0x00a9a1a7 in ?? () #22 0x00a99388 in ?? () #23 0x00a99394 in ?? () #24 0x00a99394 in ?? () #25 0x00a99394 in ?? () #26 0x00a99394 in ?? () #27 0x00a99394 in ?? () #28 0x00a99394 in ?? () ... I tried to have another look and got to the impression that blindwrite expects RegOpenKeyExW and RegSetValueExW too use less stack. I experimented a bit and one way to achive this was to do the work in these functions on a different stack. Attached proof of concept uses fibers for this. With this patch blindwrite can finish its stack exhaustion without visible error and shows the trial option dialog. After one successful start that patch is no longer necessarry. Another option to might be to use some more guard pages and switch them to regular pages when we are inside wine code? -- 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 16911] New: WriteProcessMemory() not working for memory protected by X11DRV_DIB_DoProtectDIBSection()
by wine-bugs＠winehq.org Feb. 23, 2024

Feb. 23, 2024

http://bugs.winehq.org/show_bug.cgi?id=16911 Summary: WriteProcessMemory() not working for memory protected by X11DRV_DIB_DoProtectDIBSection() Product: Wine Version: 1.1.12 Platform: PC OS/Version: Linux Status: UNCONFIRMED Keywords: patch, source Severity: minor Priority: P2 Component: winex11.drv AssignedTo: wine-bugs(a)winehq.org ReportedBy: thestig(a)google.com Created an attachment (id=18660) --> (http://bugs.winehq.org/attachment.cgi?id=18660) test program Hi, I have a test case here that works on WinXP but not Wine. I deliberately wrote a standalone test case because I'm not sure which unit test to put it in. It's in fact based off of dlls/kernel32/tests/virtual.c where the other WriteProcessMemory() test is. In this test case, we call CreateDIBSection() which returns a HBITMAP (hbitmap) and some memory (mem). Next, we call SetDIBits() with hbitmap. We get into X11DRV_SetDIBits(), where it calls X11DRV_DIB_Lock( physBitmap, DIB_Status_GdiMod );. This marks the memory (mem) as PAGE_NOACCESS, and leaves it in that state as SetDIBts() returns. Normally if the process tries to access it, we get a page fault that's handled by X11DRV_DIB_FaultHandler(), and everything works. However, when the test code calls WriteProcessMemory(), we talk to wineserver in NtWriteVirtualMemory(). In wine_server_call(), we do send_request(), where writev() tries to read 'mem' and fails with EFAULT. This doesn't trigger X11DRV_DIB_FaultHandler(), and WriteProcessMemory() fails. -- 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 5

[Bug 50098] New: FFXIV_Textools crashes on start
by WineHQ Bugzilla Feb. 18, 2024

Feb. 18, 2024

https://bugs.winehq.org/show_bug.cgi?id=50098 Bug ID: 50098 Summary: FFXIV_Textools crashes on start Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: nsextyfour(a)protonmail.com Distribution: --- Created attachment 68574 --> https://bugs.winehq.org/attachment.cgi?id=68574 I try to start FFXIV_TexTools, and then try to copy the text from the error dialog. FFXIV Textools, a modding tool for Final Fantasy XIV, will not launch in Wine. https://textools.dualwield.net/ It brings up an error window, and when I try to copy the text from it, the window disappears due to a crash. If I click 'yes', I get another error window. Clicking yes on this brings another, and then another. After the fourth, the program closes. -- 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 8

[Bug 54093] New: Tomb Raider Level Editor - Custom Level "Biohazard" has problems loading Save-File
by WineHQ Bugzilla Feb. 15, 2024

Feb. 15, 2024

https://bugs.winehq.org/show_bug.cgi?id=54093 Bug ID: 54093 Summary: Tomb Raider Level Editor - Custom Level "Biohazard" has problems loading Save-File Product: Wine Version: 7.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: maiktapwagner(a)aol.com Distribution: --- Hello everyone, download link is at: https://www.trle.net/levels/levels/2021/0621/TombRaider95-TRBiohazard.zip with a sha256sum of: bash-5.1$ sha256sum TombRaider95-TRBiohazard.zip 58b35b648ecaaab691ce9904833730953ae155b4556d752f70d0f0a7442bcfa7 TombRaider95-TRBiohazard.zip Please note that it comes with its own Tomb4.exe and you don't need to have your own copy of any "Tomb Raider" episode. Unpacking the .zip file and running Tomb4.exe is fine. Still created its own prefix though. The problem I am facing is that (at least in the first level) you can save your game state (press Escape to get to menu and press the Arrow-Downkey) but then in turn this new game state isn't being loaded. The progress bar when loading the state goes to 100% but then nothing more happens and you can't get back into the game from where you left off. bash-5.1$ /sbin/lspci | grep VGA 00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R2 Graphics] bash-5.1$ wine --version wine-7.22 Console output will follow in the next couple of minutes. -- 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 21

[Bug 55205] New: Fixed scancodes patchset partially breaks keyboard input in NFS Underground
by WineHQ Bugzilla Feb. 14, 2024

Feb. 14, 2024

https://bugs.winehq.org/show_bug.cgi?id=55205 Bug ID: 55205 Summary: Fixed scancodes patchset partially breaks keyboard input in NFS Underground Product: Wine-staging Version: 8.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: aidas957(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: ArchLinux Created attachment 74801 --> https://bugs.winehq.org/attachment.cgi?id=74801 x11drv,+dinput,+keyboard,+key log with autodetection disabled Hello, So NFS Underground (and likely Underground 2 considering it also uses ActionMap stuff) has partially broken keyboard input with wine-staging if the fixed scancodes patchset is enabled The first thing you notice in the main menu is that the arrow keys don't work at all Also the mappings you set in vanilla Wine/wine-staging without the patchset have slightly changed if you can actually get into the mapping menu (this is with a standard US QWERTY layout by the way) What's interesting is if you enable scancode autodetection in winecfg things go back to normal I have attached a +x11drv,+dinput,+keyboard,+key log with scancode autodetection disabled (I'll send another log with that option enabled after submitting this bug because of Bugzilla limitations) -- 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 7

[Bug 47116] New: Indiana Jones and the Emperor's Tomb: white line
by wine-bugs＠winehq.org Feb. 11, 2024

Feb. 11, 2024

https://bugs.winehq.org/show_bug.cgi?id=47116 Bug ID: 47116 Summary: Indiana Jones and the Emperor's Tomb: white line Product: Wine Version: 4.7 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: legluondunet(a)free.fr Distribution: --- Created attachment 64326 --> https://bugs.winehq.org/attachment.cgi?id=64326 screen captures with white lines Hello, to play Indiana Jones and the Emperor's Tomb with Wine, I know I have to: - override dll msvcrt bug 27594 - disable vertex shader 12400 But now I have a new graphic issue with Wine 4.7 (even with staging version): look at the screen captures I joined to this bug report, there are white lines. -- 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 12

[Bug 49199] New: Wine on macOS no longer loads dylibs from /lib(64)
by WineHQ Bugzilla Feb. 11, 2024

Feb. 11, 2024

https://bugs.winehq.org/show_bug.cgi?id=49199 Bug ID: 49199 Summary: Wine on macOS no longer loads dylibs from /lib(64) Product: Wine Version: 5.6 Hardware: x86-64 OS: Mac OS X Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gcenx83(a)gmail.com Starting from Wine-5.6 the libwine wrappers have been removed in favor of using dlopen() however this now causes component in question to no longer load embedded dylibs into /lib(64) Here’s an example; ```907aaf9e72714293909351648827e7c5aebc12a3 is the first bad commit commit 907aaf9e72714293909351648827e7c5aebc12a3 Author: Alexandre Julliard <julliard(a)winehq.org> Date: Mon Apr 6 11:46:10 2020 +0200 gdi32: Use standard dlopen() instead of the libwine wrappers. Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> dlls/gdi32/dibdrv/opengl.c | 12 +++++------- dlls/gdi32/freetype.c | 20 ++++++++++---------- 2 files changed, 15 insertions(+), 17 deletions(-)``` Any commit doing “ Use standard dlopen() instead of the libwine wrappers.” will now experience this. Previous behavior was the ability to simply embed dylibs into /lib(64) and wine(64) would load them as needed, now rpath is required. Winehq packages will also experience this issue worse once the current embedded libraries swap to using dlopen() -- 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 20

[Bug 39859] New: WineHQ packages for wine-gecko and wine-mono
by wine-bugs＠winehq.org Feb. 11, 2024

Feb. 11, 2024

https://bugs.winehq.org/show_bug.cgi?id=39859 Bug ID: 39859 Summary: WineHQ packages for wine-gecko and wine-mono Product: Packaging Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: wine-packages Assignee: wine-bugs(a)winehq.org Reporter: dimesio(a)earthlink.net CC: michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Most users of the distros we now package for are accustomed to installing wine-gecko and wine-mono from packages. We should provide them. -- 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 16

[Bug 53656] New: cannot install an update because of Conflicting Values set for option
by WineHQ Bugzilla Feb. 11, 2024

Feb. 11, 2024

https://bugs.winehq.org/show_bug.cgi?id=53656 Bug ID: 53656 Summary: cannot install an update because of Conflicting Values set for option Product: Wine Version: 7.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: thereal7kqx(a)gmail.com Distribution: --- Created attachment 73058 --> https://bugs.winehq.org/attachment.cgi?id=73058 the error I am using LMDE 5, based on Debian, and this (bug?) is dragging me down ive tried everything i can to remove this stuff, but the delete button is just shaded black, or it spats out bullshit that it cant be removed. -- 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 4

[Bug 54181] New: nothing provides wine-devel64 = 1:8.0.rc1-1.1 needed by winehq-devel-1:8.0.rc1-1.x86_64
by WineHQ Bugzilla Feb. 11, 2024

Feb. 11, 2024

https://bugs.winehq.org/show_bug.cgi?id=54181 Bug ID: 54181 Summary: nothing provides wine-devel64 = 1:8.0.rc1-1.1 needed by winehq-devel-1:8.0.rc1-1.x86_64 Product: Wine Version: 7.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: thegamemaster(a)hotmail.com Distribution: --- In Fedora 37 KDE Spin on Toshiba Satellite L655. Upon sudo dnf update -y error returned "Problem: cannot instal the best update candidate for package winehq-devel-1:7.22-1.1.x86_66 - nothing provides wine-devel64 = 1:8.0.rc1-1.1 needed by winehq-devel-1:8.0.rc1-1.1.x86_64 wine will not update. -- 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 7

[Bug 54835] New: Installation failure in Ubuntu 22.04 LTS
by WineHQ Bugzilla Feb. 11, 2024

Feb. 11, 2024

https://bugs.winehq.org/show_bug.cgi?id=54835 Bug ID: 54835 Summary: Installation failure in Ubuntu 22.04 LTS Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: saurabh.ghosh(a)nichi.com Distribution: --- Created attachment 74337 --> https://bugs.winehq.org/attachment.cgi?id=74337 Screenshot of the issue I have been trying to install wine in my Ubuntu 22.04 LTS. I have followed all the steps mentioned in (https://wiki.winehq.org/Ubuntu) However, there is a critical conflict in ubuntu. It requires "libgd3:i386", which when installed creates conflict with "libgd3" and removes packages "colord, gnome-control-center, libgd3, libgphoto2-6 & libsane1 sane-utils". Removal of "gnome-control-center" is unacceptable as it handles the ubuntu settings app, also I need "colord" because I use night light settings. I can't seem to find any workaround! Please help. -- 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 4

[Bug 55256] New: apt update does not find any upgrade for 8.0~repack-4 installed version
by WineHQ Bugzilla Feb. 11, 2024

Feb. 11, 2024

https://bugs.winehq.org/show_bug.cgi?id=55256 Bug ID: 55256 Summary: apt update does not find any upgrade for 8.0~repack-4 installed version Product: Wine-staging Version: 8.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: b1779506(a)trbvn.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Os is ubuntu 23.04 Lunar Lobster, with the repo added: sudo dpkg --add-architecture i386 sudo mkdir -pm755 /etc/apt/keyrings sudo wget -O /etc/apt/keyrings/winehq-archive.key https://dl.winehq.org/wine-builds/winehq.key sudo wget -NP /etc/apt/sources.list.d/ https://dl.winehq.org/wine-builds/ubuntu/dists/lunar/winehq-lunar.sources Installed versions of wine: fonts-wine/lunar,lunar,lunar,lunar,lunar,lunar,now 8.0~repack-4 all [installed] libkwineffects14/lunar,lunar,lunar,now 4:5.27.4-0ubuntu1 amd64 [installed,automatic] libwine-development/lunar,lunar,lunar,now 7.20~repack-1 amd64 [installed,automatic] libwine/lunar,lunar,lunar,now 8.0~repack-4 amd64 [installed,automatic] libwine/lunar,lunar,lunar,now 8.0~repack-4 i386 [installed,automatic] wine32/lunar,lunar,lunar,now 8.0~repack-4 i386 [installed] wine64/lunar,lunar,lunar,now 8.0~repack-4 amd64 [installed] wine/lunar,lunar,lunar,lunar,lunar,lunar,now 8.0~repack-4 all [installed,automatic] winetricks/lunar,lunar,lunar,lunar,lunar,lunar,now 20220411-1 all [installed] Running apt update; apt updgrade does not install the desired 8.12. -- 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 23

[Bug 55253] New: Error during update
by WineHQ Bugzilla Feb. 11, 2024

Feb. 11, 2024

https://bugs.winehq.org/show_bug.cgi?id=55253 Bug ID: 55253 Summary: Error during update Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bahman.davoudi.dehaghi(a)gmail.com Distribution: --- Created attachment 74860 --> https://bugs.winehq.org/attachment.cgi?id=74860 It seems that release file is not reachable I am using Ubuntu 20.04 with a Kubuntu desktop. My computer is: Operating System: Kubuntu 20.04 KDE Plasma Version: 5.18.8 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 Kernel Version: 5.15.0-76-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i3 CPU M 330 @ 2.13GHz Memory: 3.7 GiB of RAM I am recently receiving an error during the update saying that the release file is not available. It seems that the release file is available here: https://dl.winehq.org/wine-builds/ubuntu/dists/focal/. I don't know what to do. Thanks for your time and help in advance. -- 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 47558] New: Ubuntu package for 4.12.1 cannot open project in Adobe Premiere Pro 2.0
by wine-bugs＠winehq.org Feb. 11, 2024

Feb. 11, 2024

https://bugs.winehq.org/show_bug.cgi?id=47558 Bug ID: 47558 Summary: Ubuntu package for 4.12.1 cannot open project in Adobe Premiere Pro 2.0 Product: Packaging Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-packages Assignee: wine-bugs(a)winehq.org Reporter: julius.schwartzenberg(a)gmail.com CC: dimesio(a)earthlink.net, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 64946 --> https://bugs.winehq.org/attachment.cgi?id=64946 output of Wine When I run Adobe Premiere Pro 2.0 with Wine 4.12.1 in Ubuntu, I get the following dialog when trying to open a project: Sorry, a serious error has occurred that requires Adobe Premiere Pro to shut down. We will attempt to save your current project. Rebuilding Wine myself from Git, currently the latest commit matches 4.12.1, does not show this problem. -- 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 26

[Bug 50692] New: Office 2019 Professional Plus doesn't install
by WineHQ Bugzilla Feb. 11, 2024

Feb. 11, 2024

https://bugs.winehq.org/show_bug.cgi?id=50692 Bug ID: 50692 Summary: Office 2019 Professional Plus doesn't install Product: Wine Version: 6.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: atillolann-1815(a)yopmail.com Distribution: --- Created attachment 69422 --> https://bugs.winehq.org/attachment.cgi?id=69422 Terminal Log Tried intalling Office 2019 ProPlus Retail, after the loading screen the installer crashes. Using Wine 6.2-developer Arch: x86_64 Distro: Linux Mint 19.0 Cinnamon 64 bit -- 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 32

[Bug 14010] New: RivaTuner 2.09 not work ,no overclocking or sensor ability
by wine-bugs＠winehq.org Feb. 10, 2024

Feb. 10, 2024

http://bugs.winehq.org/show_bug.cgi?id=14010 Summary: RivaTuner 2.09 not work ,no overclocking or sensor ability Product: Wine Version: 1.0.0 Platform: All OS/Version: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: dj--alex(a)ya.ru RivaTuner 2.09 not work ,no overclocking or sensor ability My videocard is very loud without this program!! I and not only i, want to overclocking without BIOS VRAM rewrite. Program can be downloaded free from http://www.radeon.ru/ (Main menu left - newest version) -- 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 4

[Bug 51360] New: vkGetDeviceProcAddr invalid behavior for functions from extensions unsupported by host Vulkan instance
by WineHQ Bugzilla Feb. 9, 2024

Feb. 9, 2024

https://bugs.winehq.org/show_bug.cgi?id=51360 Bug ID: 51360 Summary: vkGetDeviceProcAddr invalid behavior for functions from extensions unsupported by host Vulkan instance Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winevulkan Assignee: wine-bugs(a)winehq.org Reporter: loothelion(a)nvidia.com Distribution: --- I believe the below may also be true for vkGetInstanceProcAddr, but I haven't confirmed this locally. The Vulkan 1.2.182 specification states the following about the behavior of vkGetDeviceProcAddr: > The table below defines the various use cases for vkGetDeviceProcAddr and > expected return value for each case. > > The returned function pointer is of type PFN_vkVoidFunction, and must be cast to > the type of the command being queried before use. The function pointer must only > be called with a dispatchable object (the first parameter) that is device or a > child of device. > > Table 2. vkGetDeviceProcAddr behavior > > device | pName | return value > --------------------------------------------------------------------------------------- > NULL | *[1] | undefined > --------------------------------------------------------------------------------------- > invalid device | *[1] | undefined > --------------------------------------------------------------------------------------- > device | NULL | undefined > --------------------------------------------------------------------------------------- > device | core device-level Vulkan command [2] | fp[3] > --------------------------------------------------------------------------------------- > device | enabled extension device-level commands [2] | fp[3] > --------------------------------------------------------------------------------------- > any other case, not covered above | NULL > > [1] - "*" means any representable value for the parameter (including valid > values, invalid values, and NULL). > > [2] - In this function, device-level excludes all physical-device-level > commands. > > [3] - The returned function pointer must only be called with a dispatchable > object (the first parameter) that is device or a child of device e.g. > VkDevice, VkQueue, or VkCommandBuffer. Winevulkan's behavior differs from this slightly. Note the fifth row of the table uses the language "enabled extension device-level commands", this means that if a command is queried via vkGetDeviceProcAddr and isn't part of core, the extension which introduces it must be enabled for the given VkDevice object in order for vkGetDeviceProcAddr to return a valid function pointer, and otherwise it should return NULL. In order to properly conform to the Vulkan specification Winevulkan should only expose device-level commands whose extensions have been enabled. Note that applications should not be querying for Vulkan commands via vkGetDeviceProcAddr if they know the extension is not supported by the underlying implementation. However in the case of an application which does rely on this bad behavior, Winevulkan will return a function pointer to one of its thunks and then proceed to deference a null function pointer when it tries to call into the underlying host Vulkan implementation. -- 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 47521] New: digikam 6.10 crashes on start
by wine-bugs＠winehq.org Feb. 9, 2024

Feb. 9, 2024

https://bugs.winehq.org/show_bug.cgi?id=47521 Bug ID: 47521 Summary: digikam 6.10 crashes on start Product: Wine Version: 4.11 Hardware: x86 OS: Linux Status: NEW Keywords: download, source Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Distribution: Gentoo Created attachment 64913 --> https://bugs.winehq.org/attachment.cgi?id=64913 crash output Backtrace: =>0 0x66401f0a EntryPoint+0xb6a() in qt5widgets (0x006ff4f8) 1 0x1084cf64 WXMPUtils_DuplicateSubtree_1+0x44c5d3() in libdigikamcore (0x737adae8) 2 0x10388bb9 EntryPoint+0x387818() in libdigikamcore (0x006ff5f8) 3 0x104c0cba WXMPUtils_DuplicateSubtree_1+0xc0329() in libdigikamcore (0x006ff688) 4 0x2278b630 EntryPoint+0xba28f() in libdigikamgui (0x006ffab8) 5 0x2276e7b3 EntryPoint+0x9d412() in libdigikamgui (0x006ffb98) 6 0x00404be5 _ZN7Digikam6DColor11premultiplyEv+0x15e4() in digikam (0x006ffe88) 7 0x00401382 EntryPoint+0xffffffff() in digikam (0x006fff28) 8 0x7b47e022 call_process_entry+0x11() in kernel32 (0x006fff48) 9 0x7b480acc start_process+0xeb(entry=<couldn't compute location>, peb=<couldn't compute location>) [Z:\home\austin\wine-git\dlls\kernel32\process.c:1297] in kernel32 (0x006fffd8) 10 0x7b47e02e start_process_wrapper+0x9() in kernel32 (0x006fffec) 0x66401f0a EntryPoint+0xb6a in qt5widgets: movl 0x4(%eax),%ecx austin(a)laptop:~/Downloads$ du -sh digiKam-6.1.0-Win32.exe 321M digiKam-6.1.0-Win32.exe austin(a)laptop:~/Downloads$ sha256sum digiKam-6.1.0-Win32.exe fb870263a8bb2bd178590dfacfe68110b68d8c5b0ca53606084162a1a5e42b44 digiKam-6.1.0-Win32.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.

2 7

[Bug 43993] New: Quick3270 5.21: crashes when using the Connect function
by wine-bugs＠winehq.org Feb. 9, 2024

Feb. 9, 2024

https://bugs.winehq.org/show_bug.cgi?id=43993 Bug ID: 43993 Summary: Quick3270 5.21: crashes when using the Connect function Product: Wine Version: 2.0.3 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: q3270(a)grr.la Distribution: --- Application crashes when I choose Session -> Connect option. Application error messages is: "Could not find imported function in DLL C:\windows\system32\ws2_32.dll" Console output relevant messages: fixme:module:load_library unsupported flag(s) used (flags: 0x00000800) fixme:shell:SetCurrentProcessExplicitAppUserModelID L"DN-Computing.Quick3270.DisplayEmulator": stub fixme:htmlhelp:HtmlHelpW HH case HH_INITIALIZE not handled. fixme:ntdll:NtQueryInformationToken QueryInformationToken( ..., TokenElevation, ...) semi-stub fixme:htmlhelp:HtmlHelpW HH_PRETRANSLATEMESSAGE unimplemented Application is available as trial here: https://www.dn-computing.com/download.htm Prior to launching the application I've installed wine-mono and wine-gecko. Unsuccessfully tried: - replacing ws2_32.dll with an original one - debugging with +relay, the log doesn't show the missing procedure name -- 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 3

[Bug 51843] New: dlls/ws2_32/socket.c:839:17: error: ‘IP_ADD_SOURCE_MEMBERSHIP’ undeclared here
by WineHQ Bugzilla Feb. 9, 2024

Feb. 9, 2024

https://bugs.winehq.org/show_bug.cgi?id=51843 Bug ID: 51843 Summary: dlls/ws2_32/socket.c:839:17: error: ‘IP_ADD_SOURCE_MEMBERSHIP’ undeclared here Product: Wine Version: 6.18 Hardware: x86 OS: NetBSD Status: NEW Severity: blocker Priority: P2 Component: winsock Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com gcc -c -o dlls/ws2_32/socket.o dlls/ws2_32/socket.c -Idlls/ws2_32 -Iinclude -D__WINESRC__ -DUSE_WS_PREFIX -D_REENTRANT -fno-PIC -fasynchronous-unwind-tables -Wall -pipe -fno-stack-protector -fno-strict-aliasing -Wdeclaration-after-statement -Wempty-body -Wignored-qualifiers -Wshift-overflow=2 -Wstrict-prototypes -Wtype-limits -Wunused-but-set-parameter -Wvla -Wwrite-strings -Wpointer-arith -Wlogical-op -march=i586 -gdwarf-2 -gstrict-dwarf -fno-omit-frame-pointer -I/usr/pkg/include -I/usr/include -I/usr/pkg/include/freetype2 -I/usr/X11R7/include -O2 -I/usr/pkg/include -I/usr/include -I/usr/pkg/include/freetype2 -I/usr/X11R7/include -g dlls/ws2_32/socket.c:839:17: error: ‘IP_ADD_SOURCE_MEMBERSHIP’ undeclared here (not in a function); did you mean ‘WS_IP_ADD_SOURCE_MEMBERSHIP’? MAP_OPTION( IP_ADD_SOURCE_MEMBERSHIP ), ^ dlls/ws2_32/socket.c:792:37: note: in definition of macro ‘MAP_OPTION’ #define MAP_OPTION(opt) { WS_##opt, opt } ^~~ dlls/ws2_32/socket.c:840:17: error: ‘IP_DROP_SOURCE_MEMBERSHIP’ undeclared here (not in a function); did you mean ‘WS_IP_DROP_SOURCE_MEMBERSHIP’? MAP_OPTION( IP_DROP_SOURCE_MEMBERSHIP ), ^ dlls/ws2_32/socket.c:792:37: note: in definition of macro ‘MAP_OPTION’ #define MAP_OPTION(opt) { WS_##opt, opt } ^~~ dlls/ws2_32/socket.c:841:17: error: ‘IP_BLOCK_SOURCE’ undeclared here (not in a function); did you mean ‘WS_IP_BLOCK_SOURCE’? MAP_OPTION( IP_BLOCK_SOURCE ), ^ dlls/ws2_32/socket.c:792:37: note: in definition of macro ‘MAP_OPTION’ #define MAP_OPTION(opt) { WS_##opt, opt } ^~~ dlls/ws2_32/socket.c:842:17: error: ‘IP_UNBLOCK_SOURCE’ undeclared here (not in a function); did you mean ‘IP_BLOCK_SOURCE’? MAP_OPTION( IP_UNBLOCK_SOURCE ), ^ dlls/ws2_32/socket.c:792:37: note: in definition of macro ‘MAP_OPTION’ #define MAP_OPTION(opt) { WS_##opt, opt } ^~~ dlls/ws2_32/socket.c:923:17: error: ‘AI_ALL’ undeclared here (not in a function); did you mean ‘P_ALL’? MAP_OPTION( AI_ALL ), ^ dlls/ws2_32/socket.c:792:37: note: in definition of macro ‘MAP_OPTION’ #define MAP_OPTION(opt) { WS_##opt, opt } ^~~ dlls/ws2_32/socket.c:923:17: warning: initialization makes integer from pointer without a cast [-Wint-conversion] MAP_OPTION( AI_ALL ), ^ dlls/ws2_32/socket.c:792:37: note: in definition of macro ‘MAP_OPTION’ #define MAP_OPTION(opt) { WS_##opt, opt } ^~~ dlls/ws2_32/socket.c:923:17: note: (near initialization for ‘ws_aiflag_map[4][1]’) MAP_OPTION( AI_ALL ), ^ dlls/ws2_32/socket.c:792:37: note: in definition of macro ‘MAP_OPTION’ #define MAP_OPTION(opt) { WS_##opt, opt } ^~~ dlls/ws2_32/socket.c:923:17: error: initializer element is not constant MAP_OPTION( AI_ALL ), ^ dlls/ws2_32/socket.c:792:37: note: in definition of macro ‘MAP_OPTION’ #define MAP_OPTION(opt) { WS_##opt, opt } ^~~ dlls/ws2_32/socket.c:923:17: note: (near initialization for ‘ws_aiflag_map[4][1]’) MAP_OPTION( AI_ALL ), ^ dlls/ws2_32/socket.c:792:37: note: in definition of macro ‘MAP_OPTION’ #define MAP_OPTION(opt) { WS_##opt, opt } ^~~ dlls/ws2_32/socket.c: In function ‘WS_setsockopt’: dlls/ws2_32/socket.c:5639:27: error: storage size of ‘mreq_source’ isn’t known struct ip_mreq_source mreq_source; ^~~~~~~~~~~ dlls/ws2_32/socket.c:5856:24: error: request for member ‘imr_interface’ in something not a structure or union mreq_source.imr_interface.s_addr = val->imr_interface.S_un.S_addr; ^ dlls/ws2_32/socket.c:5856:38: error: request for member ‘s_addr’ in something not a structure or union mreq_source.imr_interface.s_addr = val->imr_interface.S_un.S_addr; ^ dlls/ws2_32/socket.c:5856:13: warning: statement with no effect [-Wunused-value] mreq_source.imr_interface.s_addr = val->imr_interface.S_un.S_addr; ^~~~~~~~~~~ dlls/ws2_32/socket.c:5857:24: error: request for member ‘imr_multiaddr’ in something not a structure or union mreq_source.imr_multiaddr.s_addr = val->imr_multiaddr.S_un.S_addr; ^ dlls/ws2_32/socket.c:5857:38: error: request for member ‘s_addr’ in something not a structure or union mreq_source.imr_multiaddr.s_addr = val->imr_multiaddr.S_un.S_addr; ^ dlls/ws2_32/socket.c:5857:13: warning: statement with no effect [-Wunused-value] mreq_source.imr_multiaddr.s_addr = val->imr_multiaddr.S_un.S_addr; ^~~~~~~~~~~ dlls/ws2_32/socket.c:5858:24: error: request for member ‘imr_sourceaddr’ in something not a structure or union mreq_source.imr_sourceaddr.s_addr = val->imr_sourceaddr.S_un.S_addr; ^ dlls/ws2_32/socket.c:5858:39: error: request for member ‘s_addr’ in something not a structure or union mreq_source.imr_sourceaddr.s_addr = val->imr_sourceaddr.S_un.S_addr; ^ dlls/ws2_32/socket.c:5858:13: warning: statement with no effect [-Wunused-value] mreq_source.imr_sourceaddr.s_addr = val->imr_sourceaddr.S_un.S_addr; ^~~~~~~~~~~ dlls/ws2_32/socket.c:5861:20: warning: assignment makes integer from pointer without a cast [-Wint-conversion] optlen = sizeof(mreq_source); ^ dlls/ws2_32/socket.c:5639:27: warning: unused variable ‘mreq_source’ [-Wunused-variable] struct ip_mreq_source mreq_source; ^~~~~~~~~~~ dlls/ws2_32/socket.c: In function ‘WS_gethostbyaddr’: dlls/ws2_32/socket.c:6092:19: warning: implicit declaration of function ‘gethostbyaddr_r’; did you mean ‘gethostbyaddr’? [-Wimplicit-function-declaration] int res = gethostbyaddr_r(paddr, len, unixtype, ^~~~~~~~~~~~~~~ gethostbyaddr dlls/ws2_32/socket.c: In function ‘WS_gethostbyname’: dlls/ws2_32/socket.c:6284:23: warning: implicit declaration of function ‘gethostbyname_r’; did you mean ‘gethostbyname2’? [-Wimplicit-function-declaration] int res = gethostbyname_r(name, &hostentry, extrabuf, ebufsize, &host, &locerr); ^~~~~~~~~~~~~~~ gethostbyname2 At top level: dlls/ws2_32/socket.c:1796:12: warning: ‘set_ipx_packettype’ defined but not used [-Wunused-function] static int set_ipx_packettype(int sock, int ptype) ^~~~~~~~~~~~~~~~~~ -- 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