Fusion 360 - Login no browser opens

[knimix]

Hi, today i installed bottles and used the fusion 360 installer / script from bottles. The problem is when i click on "Sign In" normally a browser should open but this does not happen. I tried to install a browser inside the bottle (firefox) but this doesn't help.

Is there any fix for this?

[cjwhitedev]

I'm having the same problem.

[shanold]

Exact same issue. I even tried installing a browser in the same bottle hoping it would help :(

[alextrical]

There was a January update from Autodesk that removed the legacy login method when they Rebranded the product to Fusion. Unfortunately you now need to be using a version of Wine that is at least 8.14 (containing this patch) that added the functionality required to login, you will also need to add the mime-type redirection to handle the data given back from the browser once you actually log in.

For a working bottle, the instructions below have worked reliably for me: In your terminal copy and paste the following, changing the 'BOTTLE' variable to whatever name is desired

BOTTLE="Fusion"
flatpak run --command=bottles-cli com.usebottles.bottles new --bottle-name $BOTTLE --environment "custom" --arch "win64" --runner caffe-8.21

Open bottles GUI, enter into the bottle just created and install Fusion

In your terminal copy and paste the following, changing the BOTTLE name to be the same as you used in the step above

BOTTLE="Fusion"

#Define a new application link, that we will use for handling the Mimetype.
flatpak run --command=bottles-cli com.usebottles.bottles add --bottle $BOTTLE -n "AdskIdentityManager" -p "$HOME/.var/app/com.usebottles.bottles/data/bottles/bottles/$BOTTLE/drive_c/Program Files/Autodesk/webdeploy/production/99249ee497b13684a43f5bacd5f1f09974049c6b/Autodesk Identity Manager/AdskIdentityManager.exe" 

#Create mimetype link to handle web login call backs to the Identity Manager
cat > $HOME/.local/share/applications/adskidmgr-opener.desktop << EOL
[Desktop Entry]
Type=Application
Name=adskidmgr Scheme Handler
Exec=flatpak run --command=bottles-cli com.usebottles.bottles run --args-replace -b $BOTTLE -p "AdskIdentityManager" "%u"
StartupNotify=false
MimeType=x-scheme-handler/adskidmgr;
EOL

#Register default mimetype in the system
xdg-mime default adskidmgr-opener.desktop x-scheme-handler/adskidmgr

[cjwhitedev]

This worked for me, with one caveat. there is one directory listed here that was different for me. its a huge string of numbers and letters containing the Autodesk Identity Manager directory, i had to open my file system and find out what mine was named, replaced it in the command, and everything worked fine. thanks!

[alextrical]

hmm, its possible that Autodesk have released yet another update, and as a result the string of numbers has changed. Once i can get the "Run_script" action working in the manifest, i will look into detecting the latest folder from the registry records to allow it to be dynamic

[knimix]

@alextrical yes thanks that worked, but some things were easier to do via the gui than via commands, especially with the long paths which are always different

[alextrical]

Ideally we want all of the steps required added into the application manifest removing the need for the end user to run scripts

[jaype87]

Unfortunately, this doesn't work for me.

Browser opens, but after logging in, nothing happens in fusion. Manually running xdg-open with the url shows Program "AdskIdentityManager" not found So I removed the quotes around AdskIdentityManager from the Exec command and now it is able to execute without complaining. However, the bottles UI crashes and Fusion still waits for conformation.

Any further ideas?

[Thermionix]

Dynamically detecting AdskIdentityManager a draft outline for something in fusion.yml

- action: add-adskidmgr   # - can we call this as part of setup? can we interact with main user $HOME ?
  script: |
    cat > $HOME/.local/share/applications/adskidmgr-opener.desktop << EOL
[Desktop Entry]
Type=Application
Name=adskidmgr Scheme Handler
Exec=flatpak run --command=bottles-cli com.usebottles.bottles run --args-replace -b !bottle_name -p "AdskIdentityManager" "%u"
StartupNotify=false
MimeType=x-scheme-handler/adskidmgr;
EOL
    xdg-mime default adskidmgr-opener.desktop x-scheme-handler/adskidmgr

- action: AdskIdentityManager
  script: |
      $(find "!bottle_drive" -name "AdskIdentityManager.exe" | head -1 | xargs -I '{}' echo {})

Also, will really need to be able to define (unreleased) wine > 9.8 for latest installer to succeed

[Ryan3141]

I found that the .desktop for adskidmgr-opener had an issue with the path to AdskIdentityManager.exe, causing the link from the browser to never allow fusion to login. This is likely due to the backslashes somewhere in one of the script, but I don't know where to look. The original arguements were: 'C:\rogram Files\utodesk\ebdeploy\roduction\738a7f16475c27414ba957f7f0b2ee5b34e4e6d\utodesk Identity Manager\dskIdentityManager.exe' %u Until I corrected it to: 'C:\Program Files\Autodesk\webdeploy\production\b738a7f16475c27414ba957f7f0b2ee5b34e4e6d\Autodesk Identity Manager\AdskIdentityManager.exe' %u

Note: I am using Manjaro, not sure if that affects things.