[Bug 56443] New: Totem Arts Launcher.exe repeatedly asking for Unreal Engine Redistributable
https://bugs.winehq.org/show_bug.cgi?id=56443 Bug ID: 56443 Summary: Totem Arts Launcher.exe repeatedly asking for Unreal Engine Redistributable Product: Wine Version: 9.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: 6chars(a)proton.me Distribution: Mint Created attachment 76203 --> https://bugs.winehq.org/attachment.cgi?id=76203 Screenshots and a log while installing the UE redistributable After successfully installing "Totem-Arts-Launcher-latest.exe", when I launch "Totem Arts Launcher.exe" (the installed program), there is a message box that prompts me to install the 'Unreal Engine Redistributable'(currently has garbled text due to a bug). I click 'Okay' to install the required Redistributable, it goes through the operation and says it was installed successfully, but the next time I enter "Totem Arts Launcher.exe" it prompts me AGAIN to install the 'Unreal Engine Redistributable.' The normal behavior was obviously for the redistributable to be installed on my first try and not to be asked about it every time I enter the program. I don't even know for sure if it installed correctly in the first place, despite the 'Successfully install' message. Download link for "Totem-Arts-Launcher-latest.exe": https://totemarts.games/forums/files/file/1-renegade-x/ SHA1 sum for the installer: d9b7f056103183c5a50003b4c164a23cdf605e95 Totem-Arts-Launcher-latest.exe SHA1 sum for the installed program: 76f68237898ce54a3bb7129c2d1185614dc0da06 Totem Arts Launcher.exe My system: Linux Mint 21.3 x86_64, Kernel 6.5.0-25-generic, NVIDIA Geforce GTX 1050 driver 535.161.07, wine-9.4 (Staging). -- 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.
https://bugs.winehq.org/show_bug.cgi?id=56443 --- Comment #1 from Somewhat Cold <6chars(a)proton.me> --- Update for Wine Staging 9.5: Now, when the UE redistributables are being installed, I get an error message when the installer gets to installing DirectX 9.0c. This is the error message: "Path not found. For possible solutions go to: https://udk.com/troubleshooting" And the install process for the redistributables is stopped. Next time I open Totem Arts Launcher.exe, I get asked again to reinstall the UE redistributables. I attached another file called "staging_9.5_update.7z" showing both a screenshot and a log of running "Totem Arts Launcher.exe" and trying to install the UE redistributables (then manually quitting the launcher). -- 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.
https://bugs.winehq.org/show_bug.cgi?id=56443 --- Comment #2 from Somewhat Cold <6chars(a)proton.me> --- Created attachment 76257 --> https://bugs.winehq.org/attachment.cgi?id=76257 Update of the log and screenshot for wine 9.5 -- 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.
https://bugs.winehq.org/show_bug.cgi?id=56443 --- Comment #3 from Somewhat Cold <6chars(a)proton.me> --- Same issue in Staging 9.6. The error: "Path not found. For possible solutions go to: https://udk.com/troubleshooting" When installing the UE redistributables. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=56443 Ken Sharp <imwellcushtymelike(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |https://totemarts.games/for | |ums/files/file/1-renegade-x | |/ Keywords| |download --- Comment #4 from Ken Sharp <imwellcushtymelike(a)gmail.com> --- Why are you using Staging? Have you tried in vanilla Wine? -- 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.
https://bugs.winehq.org/show_bug.cgi?id=56443 --- Comment #5 from Somewhat Cold <6chars(a)proton.me> --- (In reply to Ken Sharp from comment #4)
Why are you using Staging? Have you tried in vanilla Wine?
Thanks for replying. Using Staging is literally the requirement for submitting bugs here: https://wiki.winehq.org/Bugs So, that's why I use staging. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=56443 --- Comment #6 from Austin English <austinenglish(a)gmail.com> --- (In reply to Somewhat Cold from comment #5)
(In reply to Ken Sharp from comment #4)
Why are you using Staging? Have you tried in vanilla Wine?
Thanks for replying. Using Staging is literally the requirement for submitting bugs here:
So, that's why I use staging.
Where do you see that it's a requirement? The only mention is: Set Product to Wine and specify Wine version you are using, if in doubt run `wine --version`. If you are using wine-staging, mention this in the comments. Using wine-staging when reporting bugs is fine, but not required. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=56443 --- Comment #7 from Somewhat Cold <6chars(a)proton.me> --- (In reply to Austin English from comment #6)
(In reply to Somewhat Cold from comment #5)
(In reply to Ken Sharp from comment #4)
Why are you using Staging? Have you tried in vanilla Wine?
Thanks for replying. Using Staging is literally the requirement for submitting bugs here:
So, that's why I use staging.
Where do you see that it's a requirement? The only mention is: Set Product to Wine and specify Wine version you are using, if in doubt run `wine --version`. If you are using wine-staging, mention this in the comments.
Using wine-staging when reporting bugs is fine, but not required.
----------------------- When to report a bug You should report a bug when: You are using the latest development version of Wine (not stable) (See downloads for information on how to get the latest). ----------------------- This is among the first requirements (or recommendations/suggestions, whatever) that I see on that bug reporting guide. So, naturally... I thought I have to use the latest development version. But if this isn't the case, I think this suggestion should be removed for the guide then. Because it says I should report a bug when I'm using the latest unstable version, and that's very confusing if I don't really have to. Anyway, I already do have this launcher working (and the game itself) on Bottles, along with Proton GE and some Windows redistributables installed. I'm only submitting this bug report so that other new people on Linux who want to try out that game just double click the launcher and get everything working with no extra configuration, just like on Windows. That's the whole point of my bug report, to make sure it runs just as on Windows by default on WINE. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=56443 --- Comment #8 from Somewhat Cold <6chars(a)proton.me> --- Also, I have to add, I'm personally using Staging because I sometimes use newer Windows software. e.g. it's recommended to use Staging for more VSTs (through YABridge) to work properly. And I see that I can't install two WINE versions at the same time. This is my personal reason for using Staging. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=56443 Zeb Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12(a)gmail.com --- Comment #9 from Zeb Figura <z.figura12(a)gmail.com> --- The development branch and Wine-Staging aren't the same thing. Wine has a stable branch, a development branch, and then Wine-Staging is a separate branch which has a bunch of lower-quality patches (it's not quite maintained as a branch, but close enough). -- 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.
https://bugs.winehq.org/show_bug.cgi?id=56443 --- Comment #10 from Somewhat Cold <6chars(a)proton.me> --- (In reply to Zeb Figura from comment #9)
The development branch and Wine-Staging aren't the same thing. Wine has a stable branch, a development branch, and then Wine-Staging is a separate branch which has a bunch of lower-quality patches (it's not quite maintained as a branch, but close enough).
Huh... well, that's new to me. I assumed the latest development version was Staging. I mean, technically speaking, Staging is the latest version in development, from what you've described. So I can see why I assumed I should use that on a glance. But, apparently, on a closer, more careful read, like you said, there are three versions with specific purposes. This is actually new information to me, so thanks for clearing it up! Well, I don't know what to do now. I reported 3 bugs already related to this launcher, all using Wine Staging. Two of them were fixed, and this is the last one. I suppose I could try removing Staging and always use the Development version from now on. But, should I do it after this bug is fixed? Were the fixes for this bug that were just made in Staging even applied in the Development branch? Should I avoid using Staging as my main WINE? I don't know. I'm kind of new to this. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=56443 --- Comment #11 from Austin English <austinenglish(a)gmail.com> --- (In reply to Somewhat Cold from comment #10)
Well, I don't know what to do now. I reported 3 bugs already related to this launcher, all using Wine Staging. Two of them were fixed, and this is the last one. I suppose I could try removing Staging and always use the Development version from now on. But, should I do it after this bug is fixed? Were the fixes for this bug that were just made in Staging even applied in the Development branch? Should I avoid using Staging as my main WINE? I don't know. I'm kind of new to this.
Using staging is fine, if that works for you. But you may be asked if the bug also occurs in wine-development (to narrow down if the problem is introduced by one of the staging patches). -- 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.
https://bugs.winehq.org/show_bug.cgi?id=56443 --- Comment #12 from Somewhat Cold <6chars(a)proton.me> --- (In reply to Austin English from comment #11)
(In reply to Somewhat Cold from comment #10)
Well, I don't know what to do now. I reported 3 bugs already related to this launcher, all using Wine Staging. Two of them were fixed, and this is the last one. I suppose I could try removing Staging and always use the Development version from now on. But, should I do it after this bug is fixed? Were the fixes for this bug that were just made in Staging even applied in the Development branch? Should I avoid using Staging as my main WINE? I don't know. I'm kind of new to this.
Using staging is fine, if that works for you. But you may be asked if the bug also occurs in wine-development (to narrow down if the problem is introduced by one of the staging patches).
Got it. So, I get how Development and Staging work now. It's recommended to use Dev when bug reporting in most cases, just to make life simpler. But Staging is fine as well, as long as I understand I may have to double-check if some bug occurs in the Dev version as well (to check for regressions). Also, Staging may break some compatibility that was present in Dev, or... maybe fix something. So for personal use, it's just "use what works." For bug reports, you may have to do additional Dev testing if you use Staging. Thanks for the help guys! Sorry for my previous confusion, but I understand it better now thanks to these replies. I will install the Development version to test how the bug behaves there, and I will report back with a comment. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=56443 --- Comment #13 from Zeb Figura <z.figura12(a)gmail.com> --- (In reply to Somewhat Cold from comment #10)
Well, I don't know what to do now. I reported 3 bugs already related to this launcher, all using Wine Staging. Two of them were fixed, and this is the last one. I suppose I could try removing Staging and always use the Development version from now on. But, should I do it after this bug is fixed? Were the fixes for this bug that were just made in Staging even applied in the Development branch? Should I avoid using Staging as my main WINE? I don't know. I'm kind of new to this.
I would not recommend Wine-Staging unless you have something that specifically needs it, personally. As a maintainer of Wine-Staging and the person who ends up responding to most bug reports, I can say that I will almost always ask if the bug is present in upstream Wine as well—since we basically want Wine bugs to be under Wine and Wine-Staging bugs to be under Wine-Staging. The latter are very specifically my responsibility, and I'd like to shunt off that responsibility whenever I can ;-) So while we accept Wine-Staging bug reports, filing a report where only Staging was tested will generally result in a request to test upstream anyway, unless I can find a clear sign that the bug is in one place or the other. With that said, I don't think Ken Sharp's question of "why are you using Staging" is very useful. The answer is generally "because it's commonly perceived to have more features than upstream Wine". I think that perception is not (anymore) very true, and in any case Staging is mostly targeted fixes for known applications anyway. But just asking "why" is not really an efficient way to communicate that fact. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=56443 --- Comment #14 from Somewhat Cold <6chars(a)proton.me> --- (In reply to Zeb Figura from comment #13)
I would not recommend Wine-Staging unless you have something that specifically needs it, personally.
As a maintainer of Wine-Staging and the person who ends up responding to most bug reports, I can say that I will almost always ask if the bug is present in upstream Wine as well—since we basically want Wine bugs to be under Wine and Wine-Staging bugs to be under Wine-Staging. The latter are very specifically my responsibility, and I'd like to shunt off that responsibility whenever I can ;-)
So while we accept Wine-Staging bug reports, filing a report where only Staging was tested will generally result in a request to test upstream anyway, unless I can find a clear sign that the bug is in one place or the other.
With that said, I don't think Ken Sharp's question of "why are you using Staging" is very useful. The answer is generally "because it's commonly perceived to have more features than upstream Wine". I think that perception is not (anymore) very true, and in any case Staging is mostly targeted fixes for known applications anyway. But just asking "why" is not really an efficient way to communicate that fact.
Got it. The WINE maintainers would like to focus more on Dev, so that bug reporting and fixing is more practical. Staging is more like "We've seen your bug report from Wine-Dev version X.X, and we might have a fix for it on Staging. Try your app now on Staging and report back." So if that fix would work on Staging, it would get implemented into Dev, eventually. I hope I got it right. So, unless someone hasn't tested a Windows app on Dev, there's no point in directly going to Staging. It should be tested in Development versions first of all. As for the perceived extra features, that's why I initially used Staging, yep. Just out of recommendation, word of mouth, or some app I'm using that's also using Windows apps. But I'm going to use Dev from now on, and use Staging only if I really need to, if something would only work on Staging and not Dev. Anyway, thank you for the information, and for being friendly :) I will now attach a log regarding this launcher, but this time actually in Wine-Devel 9.6. Unfortunately, I get the same error message. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=56443 --- Comment #15 from Somewhat Cold <6chars(a)proton.me> --- Created attachment 76342 --> https://bugs.winehq.org/attachment.cgi?id=76342 Log from Wine-Devel 9.6 This time I used Wine-Devel 9.6. Installed the launcher, tried to install the UE redistributables. Same error as before about the "path not being found." -- 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.
https://bugs.winehq.org/show_bug.cgi?id=56443 --- Comment #16 from Somewhat Cold <6chars(a)proton.me> --- Created attachment 76849 --> https://bugs.winehq.org/attachment.cgi?id=76849 Terminal log in WINE v9.13 What happens when I enter Totem Arts Launcher.exe post launcher & post redistributables install, and then installing the redistributables when prompted, and finally exiting the program manually. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=56443 --- Comment #17 from Somewhat Cold <6chars(a)proton.me> --- Update for WINE 9.13: Now, in v9.13, the error about the "path not being found" is gone/fixed. The redistributable installing process is shown to be successfully completed! However, after exiting the Totem Arts Launcher (post successful redistributables install) and entering it again (from '/home/username/.wine/drive_c/Program Files/Totem Arts Launcher.exe'), I get a prompt saying I need to install the redistributables again, as if they haven't even been installed in the first place. So, all I can do is install them again, then I get the message that the install was successfully completed, and after re-entering the program I have to repeat this, ad infinitum. I attached a log (v9.13 Log.7z) of what happens when I enter Totem Arts Launcher.exe post launcher & redistributables install, and then installing the redistributables, and finally exiting the program manually. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=56443 --- Comment #18 from Somewhat Cold <6chars(a)proton.me> --- Update for Wine 9.22: Still the same behavior as last time. After installing Totem Arts Launcher, I get that prompt to install the UE Redistributables, I agree and it proceeds to install them. Yet, whenever I exit the launcher and enter it again, it keeps asking for the redistributables as if they weren't even installed last time. So, same behavior. -- 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.
participants (1)
-
WineHQ Bugzilla