welcome screen browser login not opening? #319
Comments
|
I am encountering EXACTLY the same problem on Ubuntu22.04 with wine 8.0 - thanks for raising the issue. Installation sequence returned no errors Error at Launch (see above): ` 03ac:fixme:system:QueryDisplayConfig (00000002 000000000011A508 0000000058F324B0 000000000011A480 0000000027C744E0 0000000000000000): semi-stub 03ac:fixme:system:NtUserDisplayConfigGetDeviceInfo Unimplemented packet type 11. 03ac:fixme:win:GetPointerDevices (000000000011A500 0000000000000000): partial stub 03ac:fixme:system:QueryDisplayConfig (00000002 000000000011A508 0000000058F324B0 000000000011A480 0000000027C744E0 0000000000000000): semi-stub 03ac:fixme:system:NtUserDisplayConfigGetDeviceInfo Unimplemented packet type 11. Finished request Handshake. But response is empty. Finished request Handshake. But response is empty. Handshake failed Desktop
|
|
I just tested the login on a windows install and noticed that I had a update pending.
Best |
|
same issue, tried copying all the files from a windows installation that is logged in with no luck |
|
Same here on both Fedora 37 and OpenSuse tumbelweed. I'm wondering if there needs to be some form of browser setup in the Wine environment to handle the link |
|
Same issue. Unable to install, attempted to install firefox on the same drive and set registry key. not sure what the solution is here. |
I can confirm that as of 03 April (2 days ago), Fusion 360 has had a 'major product update' with a new sign in experience (see the following blog post https://www.autodesk.com/products/fusion-360/blog/april-2023-major-product-update-whats-new/)
The blog post includes a .gif of the expected behaviour: redirecting the user to browser pop up for sign in. This is indeed a new feature (bug for us!) and will likely persist across all new installations/updates of Fusion360 until fixed. |
|
They have also End of Life'd support for all Windows 10 builds down from 1803, I wonder what version of Win 10 Wine is exposing the build number as. |
|
Not sure if its of use, but this is the output of the console (Last few lines of interest) after running the following command Before clicking the link after clicking the link |
|
Anyone have any luck with this yet? I feel like we're close to getting this working again, yet so far away. |
I tried playing around with the wine registry (probably not advised! see http://www.webupd8.org/2010/03/how-to-make-wine-open-links-in-your.html) to get winebrowser -> pop up, but couldn't get this to work. If anyone has experience playing around with the wine register do have a look! |
|
thank you cryinkfly |
|
unfortunately not, I'm not experienced enough with wine to find the route cause of the issue. Ive just installed a VM with Wireshark to try and see the protocol its using. The Fusion 360 launcher when pressing the login button initiates the communication via TLSv1.2. |
To make Wine open links in your default Linux browser, you can follow these steps using the "wine regedit" command:
That would be the automated process if you chose the Fusion 360 (default) during the installation back then:
Now, when you click on a link in a Wine application, it should open in your default Linux browser. |
cryinkfly
changed the title
|
Still no luck this end, I will try wiping the prefix and running the script to see if that works |
|
Just finished a full rebuild of the Prefix, (oddly it didn't install a start menu option) with the script you uploaded (confirmed the new commands for 'web.reg' are at line 457) Default browser is Firefox 110.0 64bit The reg edit has made no difference this end, to a Fedora 37 based install (Nobara OS) Should I create a new issue at this stage? |
|
Same here, just did clean install and verified that regs were updated. Default browser is Google Chrome 112.0.5615.49 Ubuntu 22.04, Opengl and wine-8.5 (Staging) |
|
Okay, then we must install a web browser into the wineprefix! I testing what now... |
|
I tried to install Chrome before clean install, it runs, but Fusion did not open it. We will probably need to set it as default browser inside wine, although I did not find a way to do it, yet. Simply clicking on |
|
It seems the default browser in Wine is "winebrowser.exe" and redirects to the external browser on the host. for example |
|
Yes, but Fusion seem to use some system call to open a link/default browser so its not catch by winebrowser. Installation folder now contain |
|
I am now only able to launch the program once and after I get |
So i have tested this one with the "default"-Wineprefix installation of Fusion 360:That would be the automated process if you chose the Fusion 360 (default) during the installation back then:
Now, when you click on a link in a Wine application, it should open with the installed Firefox (Windows version). |
cryinkfly
changed the title
|
the link to firefox didn't work here, it looks to be a specific link for your PC. can you try with instead? Alternatively if you want the latest version you can use |
|
Does not work :-((. See log-file. |
on Linux Mint 21.1 it works without any Problem. Did you try a fresh install? |
|
i feel like i might be missing something, ive set the env varriable in bottles, but with no luck , is this fix only on this version ? |
|
Hey guys, I am pretty new to Bottles and Wine, how do i set the env var and is it still working? Thanks guys |
|
Hi @DerDominikNatter, if You use installer from this repository (recommended), launcher already contain necessary env. variable set. For bare wine, start your fusion by For bottles I cannot say (I do not use them personally). |
Hello, when i start the installer command the following error occurs: Did i do something wrong? Thank you very much. Please excuse my silly questions, still in the learning process :) |
|
Launcher need YAD as dependency. You need to instal it first. For Ubuntu/Etc. its |
|
@zap117 @DerDominikNatter in the settings of the Fusion 360 "bottle": |
|
I'm using wine 9.0 and Linux Mint 21.3. I just tried to install Fusion 360 and the program initially opened right after the install. I was logged into my account and everything seemed to be working, but I couldn't see anything related to electrical schematic or pcb, so I'm not sure that I got the current version from the scripts. I closed the application and restarted my machine. When I started F360 from the wine submenu, it asked for webview2
I am a complete newbee, so if you have suggestions, make them simple! I will try WINEPREFIX="your_prefix" FUSION_IDSDK=false WINEDEBUG=-all wine path_to_Fusion360.exe |
|
The command that I used (for others playing along). I got that from the menu launch icon properties and added the FUSION_IDSDK=false WINEDEBUG=-all env WINEPREFIX="/home/gordon/.fusion360/wineprefixes/default" FUSION_IDSDK=false WINEDEBUG=-all wine C:\ProgramData\Microsoft\Windows\Start\ Menu\Programs\Autodesk\Autodesk\ Fusion\ 360.lnk The first time I ran it there were all sorts of errors on the terminal and the program was not functioning completely. After retarting the computer the electrical schematic and pcb options are available and the the errors seem to have disappeared. The only errors are: November 2023 Minor Update (v.2.0.17954) is the version that I downloaded with the scripts. |
|
yes but given that wine can now open urls using xdg-open here's what the browser login looks like:
if the xdg-open part actually works in wine, we just need to create the correct scheme handler in the linux side |
|
All fixed and working now, the following Proof of concept script handles installs and updates, it also gets the latest login method working via the default linux browser and sets up the mimetype to correctly direct the authentication back to the application. |
@dzervas Good catch on the registry value, Assuming we can use a script to grab that value, we can use that track the latest location of AdskIdentityManager.exe as it moves around with updates. Any time we can remove hard coded paths should help our scripts weather out the predictable changes coming our way ;) |
This definitely works, nice job 🙂 Just small note, on clean system I had to install these: Also in order to open auth links I had to install Firefox from DEB and make it default. |
Thank you for the feedback. I hadn't realised I was using non standard packages, I will see if we need the icon to be extracted, if not we can drop at least 2 of those dependencies. Hmm, that sucks it's not working with Snap or Google chrome.... I wonder what's causing that. Glad you found a work around though. Firefox on my system is either Deb or Flatpak. Not quite sure which at the moment. |
|
I Just installed the bottles fusion 360 version, all defaults, and I'm hitting this login issue. I have tried setting my default browser to Google Chrome (what my default is), the 2 versions of Firefox in my list, and opera, browser I don't typically use, but apparently have installed. When I launch with a terminal, I get no real debug information about the login process. I did verify the adskidmgr-opener.desktop file exists and matches the above, and re-ran by hand the xdg-mime command. Anything else I should be trying? Or ways to get more debug information out? |
|
Some progress I suppose, the other thread is closed, so I will respond here. I have added double quotes around it and put it into the startup options of my shortcut. No matter what I put into the arguments I get a popup when I run the shortcut that says: "This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem." Looking for bugs related to this, I found one that suggested editing the adskidmgr-opener.desktop to point to the right path, that does make it so if I click the "launch product" button in Chrome it "succeeds", but I suspect it is failing without showing me the popup. Firefox does the same thing. I appreciate any assistance in getting this working, thanks! |
|
@rks17899 that's what I did exactly for it to work:
|
|
I appreciate the help, but I give up. Before you posted this, I saw my installed version is the default stable, wine 9.0, so I went through dozens of outdated instructions to update, finally got that settled, and tried that (although it still lists it as 9.0 in bottles...) Either way, same result. Then I read and followed along, created a new bottle, installed fusion, found in profiles where to install the wine 9.3 you suggested, did each step, and I hit the same issue with the working directory for the authenticator. Trying to fix that by setting the working directory of the Fuxion360 executable didn't help, while trying a few other attempts, I had to force quite a few times. Now Bottles just hangs doing anything. I can get to the point of trying to set the workspace but then it hangs. I don't know if this is normal, but it takes about 30 seconds to get to the point where I can click login when the app launches, it takes another 10-20 seconds for the browser to open the page, and any time I open the directory in the finder to navigate (like creating the shortcut) it takes a long time (It takes long enough I ignore it for a while). For now, I give up, I appreciate the attempt at support, but I have lost hours just trying to log in. |
|
@rks17899 that's odd. I thought the fact that bottles use flatpak sandboxes should eliminate such discrepancies between user setups, and result must be reproducible. Maybe your system lacks libqt, and that makes you choose working directory that has Qt dll's in it, so instead of using native Qt it runs windows dll's through wine, idk if it makes any sense:) |
|
@monte-monte do you have any other bugs in fusion? like transparent points or anything like that? Can you properly use fusion? we won? |
|
I agree, I would think flatpak and bottles would avoid having these issues. I tried a reboot after messing with trying to re-install/configure QT, and am at the same place, the QT errors if I don't set the working directory (which seems like the fundamental issue, but I'm at a loss how to solve it). |
|
@dzervas I had a bug with being unable to press some buttons in drop-down menus, the menu would simply close, without registering a press, as if I have clicked in another window. This bug was not present in proton-ge build, but as I switched back to wine for authentication to work, I've found that there are two options that fix this issue. One is simply to use virtual desktop, the other is using latency-fix in bottles. I don't know what is it exactly outside of bottle, that's why I prefer them to default wine, it's very easy to try different settings and wine builds to see what's exactly working. |
Strange, I'm on 23.10 too. That's the output of |
|
I have a very similar list: ii libqt5concurrent5:amd64 5.15.10+dfsg-3 amd64 Qt 5 concurrent module |
|
@rks17899 I compared both lists. That's what's your is missing from what I have installed: Mine list is mostly missing some extra Qt6 libs that you have. |
and others
Describe the bug
After starting Fusion360 using Bottles on EndevourOS KDE, the welcome screen opens and prompts me to sign in:
Browser does not open or show a link to sign in.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Web browser (firefox) opens to let me log in
Screenshots
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: