buttercup-desktop icon indicating copy to clipboard operation
buttercup-desktop copied to clipboard

Magnet link not opening

Open morojgovany opened this issue 10 months ago • 5 comments

Hi, I'm stuck on adding a vault on google drive, only on linux (tested on Ubuntu 20.04.6 LTS gnome & virtual machine debian 12.5 with gnome), there is the steps I followed to reproduce :

  • Downloaded the AppImage from website
  • Make it executable
  • Run on terminal
  • Follow the google auth steps & allow access (firefox / chrome & vivaldi browsers)
  • After auth when redirecting to the buttercup website, a magnet link is triggered but does nothing on click open

Desktop app still asking for google auth at the end of the process. No errors in the logs except : Failed registering protocol: buttercup on both linux OS. I will try another desktop env to see if the behavior is the same and let you know.

Thanks!

morojgovany avatar Mar 27 '24 14:03 morojgovany

Hi, same issue here, Mint 21.

killerall avatar Mar 27 '24 21:03 killerall

@morojgovany @killerall Hi there. I've been using the AppImage on ArchLinux without any problem. Are AppImage apps handled by AppImageLauncher under Ubuntu/Debian? Do you have xdg-utils installed by default?

If the AppImage is handled correctly, a file should be added under ~/.local/share/applications. The file's name will contain the word Buttercup in it (look for *Buttercup*.desktop). Do you have one? If so, what do you have under Exec and MimeType?

Oxalin avatar Apr 18 '24 04:04 Oxalin

I forgot to ask: are you running the AppImage live or integrating it permanently?

I suspect the first option to be unable to handle the protocol, while the second should create the appropriate files.

Oxalin avatar Apr 19 '24 05:04 Oxalin

Also, could you edit the issue's title? It should refer to Buttercup protocol handling under Linux.

Oxalin avatar Apr 19 '24 05:04 Oxalin

I forgot to ask: are you running the AppImage live or integrating it permanently?

Experienced same problem, was running AppImage live without integrating (just marked it as executable), runnin PopOS 22.04, kernel 6.8.

Running it with (outdated, but still) AppImageLauncher and choosing "Integrate and run" on the first start - registered the protocol with the OS and authentication worked as expected.

av avatar Jun 04 '24 08:06 av