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

[Bug 57655] New: SketchUp8: frozen viewport - OpenGL 'function is no-op' after Save or Export

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57655 Bug ID: 57655 Summary: SketchUp8: frozen viewport - OpenGL 'function is no-op' after Save or Export Product: Wine Version: 10.0-rc4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: opengl Assignee: wine-bugs(a)winehq.org Reporter: tj.iam.tj(a)proton.me Distribution: --- Created attachment 77816 --> https://bugs.winehq.org/attachment.cgi?id=77816 ZIP debug log (26MB uncompressed) The SketchUp 8 viewport stops being updated after a File > Save or File > Export operation. All other interactivity (menus, toolbars, cursor icon) continues to work. This has affected SketchUp8 for many releases; back to 3.x at least but I've never been able to figure it out or determine the debugging steps to generate clues... until today! Seems to be cross-distro (well Debian and derivatives). Currently Debian 12 Bookworm amd64 with kernel v6.12.8. GPU is: $ lspci -nnk -d ::0300 0a:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde GL [FirePro W4100] [1002:682c] Subsystem: Dell Cape Verde GL [FirePro W4100] [1028:2b1e] Kernel driver in use: radeon Kernel modules: radeon, amdgpu I /think/ this also affected hosts using nouveau but it is a long time since I operated a host with Nvidia GPU so may be mistaken. Now to the clue. Using: $ env LIBGL_DEBUG=verbose WINEDEBUG=+timestamp,+opengl,+module WINEPREFIX=~/.local/share/wineprefixes/SketchUp8 wine ./SketchUp.exe |& /usr/bin/tee /tmp/wine-opengl.log and leaving long pauses between each operation so as to match timestamps and annotate them later in the log-file I discovered that after a File > Save operation (where the application creates several new Contexts then switches back to the original, from then onwards all GL function calls result in: function is no-op E.g: 197291.329:0138:trace:module:MODULE_InitDLL (762A0000 L"Skp2Xsi.dll",THREAD_ATTACH,00000000) - CALL 197291.329:0138:trace:module:MODULE_InitDLL (762A0000,THREAD_ATTACH,00000000) - RETURN 1 # 197311 Try to rotate; viewport does not react 197311.444:0024:trace:opengl:wglMakeCurrent hDc 1101009C, newContext 00011000 197311.444:0024:trace:opengl:glLineWidth width 1.000000 function is no-op 197311.444:0024:trace:opengl:glDisable cap 2852 function is no-op 197311.444:0024:trace:opengl:glDisable cap 2896 function is no-op 197311.444:0024:trace:opengl:glColor4ub red 0, green 0, blue 0, alpha 255 function is no-op 197311.444:0024:trace:opengl:glMatrixMode mode 5888 function is no-op 197311.444:0024:trace:opengl:glLoadIdentity function is no-op 197311.444:0024:trace:opengl:glLightfv light 16384, pname 4611, params 0031F92C function is no-op In the attached log I have annotates the beginning of each operation with a line of the form: # ${timestamp} ${description} so they are easy to grep/search. As is seen in the extract above the bug is evidenced starting at: # 197311 Try to rotate; viewport does not react The complete list of annotations is: $ grep '^# ' wine-opengl.log # $ env LIBGL_DEBUG=verbose WINEDEBUG=+timestamp,+opengl,+module WINEPREFIX=~/.local/share/wineprefixes/SketchUp8 wine ./SketchUp.exe |& /usr/bin/tee /tmp/wine-opengl.log # 197184 Application start # 197223 File > open recent # 197259 Rotate viewport # 197287 File > Save # 197311 Try to rotate; viewport does not react # 197348 File > Exit -- 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.

Jan. 11, 2025

[Bug 56983] UI: Application using ModernWPF crashes, Windows.UI.ViewManagement.UISettings not implemented

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=56983 Fabian Maurer <dark.shadow4(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|10.0-rc4 |9.13 --- Comment #5 from Fabian Maurer <dark.shadow4(a)web.de> --- Please don't change the reported version. -- 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.

Jan. 11, 2025

[Bug 57653] Software-based iLok activation doesn't seem to work in wine, gives some file I/O error

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57653 --- Comment #8 from el(a)horse64.org --- All the software to test this is available for testing without purchase, so I thought I'd give you the info on how to test this. Steps to reproduce: 1. Go to https://reaper.fm and get the free trial version of reaper, https://www.reaper.fm/files/7.x/reaper730_x64-install.exe using a fresh wine prefix 2. Go to https://www.celemony.com/en/trial and get "Melodyne 5 studio for Windows" ( https://www.celemony.com/cgi-bin/WebObjects/LicenseApp.woa/wa/demoRegistrat… ) and install it using the same wine prefix. 3. Launch REAPER. It will nag you since you're using the trial, wait the few seconds until it lets you click the "Buy me" button (you don't need to actually buy it). 4. In REAPER, you should be looking at a new blank project. If that's not the case, use File > New project. 5. In REAPER, add a track into the project using Track > Insert new track. 6. In REAPER, click the "FX" button on the new track, seen on the left. It should be close to the "ROUTE" button and the track number, "1". If you don't see it, resize the left-hand button area horizontally to be large enough to show it, and/or resize the track itself vertically so it's visible. 7. You should now be looking at the "Add Fx To: Track 1" window. Click FX > Scan for new plugins. Once that is completed, click the "VST3" category. You should be seeing "VST3: Melodyne (Celemony)" now. Double-click that entry to add it to the track. 8. You should now be looking at the "FX: Track 1" window. The "VST3: Melodyne" entry should be marked to your left, and in the center you should be seeing the Melodyne plugin area. It should be showing a popup saying "Welcome!" that asks you to "Activate". Most importantly, the top-right of the Melodyne plugin says: "melodyne: player". This is important to notice. 9. Click "Activate" in the melodyne dialog, which should open a website. On the website, sign up for a free trial with an e-mail of your choice. Now what's supposed to happen at this point is if you go back to the "FX: Track 1" window that is still open, it should no longer show "melodyne: player" in the corner, but it should automatically recognize you just signed up for the trial on the website and it should change to "melodyne: studio". This happens when you're using windows natively or a windows VM, but it doesn't happen with wine 9.17. My apologies if I forgot a step or if something is unclear. -- 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.

Jan. 11, 2025

[Bug 57618] Using MaxQDA 24 is impossible, because test license code is not accepted

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57618 --- Comment #13 from Almalexia <k_nickel(a)posteo.de> --- (In reply to Louis Lenders from comment #11) > (In reply to Almalexia from comment #8) > I'm not sure how to fix it, as I never had that first error myself. Oh okay. > How did you install wine? First I downloaded wine-10.0-rc1.tar.xz, then I unzipped it and followed the steps in the Readme: > QUICK START > From the top-level directory of the Wine source (which contains this file), > run: > ./configure > make > > Then either install Wine: > make install > I think if you install wine in the normal way on your distro, it should pull > in the correct dependencies like libgnutls etc. Okay, but what do you mean with "the normal way"? My first try was using apt-get - but this led to an old wine version, where MaxQDA did not run at all... After it I downloaded the wine package vom wine or github (I do not remember exactly), with this version it started. So what would be the other way to start the newest version, without compiling etc.? -- 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.

Jan. 11, 2025

[Bug 56817] Wuthering Waves launcher doesn't know what browser to use

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=56817 --- Comment #7 from F H <francisco278herrera(a)gmail.com> --- The launcher uses the qt toolkit -- 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.

Jan. 11, 2025

[Bug 57618] Using MaxQDA 24 is impossible, because test license code is not accepted

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57618 --- Comment #12 from Almalexia <k_nickel(a)posteo.de> --- (In reply to Austin English from comment #10) > You don't need to do anything. Okay, thank you for letting me know:)! -- 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.

Jan. 11, 2025

[Bug 57653] Software-based iLok activation doesn't seem to work in wine, gives some file I/O error

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57653 --- Comment #7 from el(a)horse64.org --- I tried again copying in crypt32.dll, wintrust.dll, and imagehlp.dll manually and setting them to native, but that got me the "Melodyne has encountered a problem" error again. In any case, after all this poking around it seems to me like the activation not working with builtin wine crypt32 may be related to whatever this means: 04dc:fixme:cryptasn:CryptDecodeObjectEx Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 04dc:fixme:cryptasn:CryptDecodeObjectEx Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 04dc:fixme:ole:CoInitializeSecurity 0000000000000000, -1, 0000000000000000, 0000000000000000, 0, 3, 0000000000000000, 0, 0000000000000000 stub 04dc:fixme:cryptasn:CryptDecodeObjectEx Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 04dc:fixme:cryptasn:CryptDecodeObjectEx Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 So there's probably some sort of crypto that current software iLok wants that wine won't do. -- 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.

Jan. 11, 2025

[Bug 57653] Software-based iLok activation doesn't seem to work in wine, gives some file I/O error

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57653 --- Comment #6 from el(a)horse64.org --- I just tested out "winetricks crypt32" but that results in a different problem where the plugin won't even load. It was worth an attempt, I guess. -- 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.

Jan. 11, 2025

[Bug 57654] New: Return Fire cant find 256 color window

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57654 Bug ID: 57654 Summary: Return Fire cant find 256 color window Product: Wine Version: 10.0-rc5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: adec2011.ac(a)gmail.com Distribution: --- Return Fire complains it cant find a 256 color window when running then closes. It also doesnt run unless you set windows 95/98 Demo is available here https://archive.org/details/Rfire -- 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.

Jan. 11, 2025

[Bug 57653] Software-based iLok activation doesn't seem to work in wine, gives some file I/O error

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57653 --- Comment #5 from el(a)horse64.org --- Created attachment 77815 --> https://bugs.winehq.org/attachment.cgi?id=77815 Error message when using "winetricks crypt32" (different error than when not using winetricks) -- 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.

Jan. 11, 2025