buttercup/buttercup-desktop

Linux Mint (Debian/Ubuntu): Authentication for Google Drive fails

winterstein opened this issue · 7 comments

winterstein commented

Thank you for making ButterCup!

I am unable to authenticate with Google Drive on Linux.

Steps to reproduce:

  1. Run Buttercup.AppImage

Desktop @ v2.28.0-6
Core @ v7.7.1
Flags: installed

  1. Click (Add Vault) button

  2. Browser (Chrome) opens an authentication dialog

  3. Complete the authentication.

  4. Browser asks to open an xdg link

  5. Nothing happens. i.e. the xdg link fails.

perry-mitchell commented

Hello! Thanks for making an issue.

Seems this is semi common on different Linux distros, but I'm not sure what the issue could be. I believe it's usually the OS that decides to register protocols, as we don't configure this per platform - it's baked into Electron.

Not sure there's much I can do to help here, unless someone has time to experiment on these OSes with the protocol (deep link) registration.

You might consider appending logs to confirm this but I believe they'll mention a failure to register the bcup protocol.

aikiks commented

Hi,
Lbuntu 24.04, I have the same issue using the AppImage.
What can I do to help solve the issue?
Where are the log files?
Karl

aikiks commented

image

Out of curiosity I downloaded the newest PreRelease and instead of absolutely nothing happening after the xdg-open request this time the window in the picture opens.
Does that help to solve the issue?

tdislay commented

Try this method to open the link:
#987 (comment)

aikiks commented

thanks for the answer, I tried, but I don't get the error message in the terminal
not in the terminal I started Buttercup from
not the terminal I started chromium from
and I alsy tried to start brave from the terminal, no error message

tdislay commented

Try in firefox (maybe similar with chromium-like browsers) and open the developer console when redirected you should see something like Prevented navigation to “buttercup://auth/google/callback?googledesktopauth......” due to an unknown protocol.

aikiks commented

I tried firefox, this is what I get in the terminal:

----------------------begin
firefox
[Parent 8124, Main Thread] WARNING: Failed to parse /etc/xdg/xdg-Lubuntu/gtk-3.0/settings.ini: Permission denied: 'glib warning', file /build/firefox/parts/firefox/build/toolkit/xre/nsSigHandlers.cpp:187

(firefox:8124): Gtk-WARNING **: 17:44:24.437: Failed to parse /etc/xdg/xdg-Lubuntu/gtk-3.0/settings.ini: Permission denied
[Parent 8124, Main Thread] WARNING: Failed to mkdir /home/karl/snap/firefox/4630/.config/ibus/bus: Not a directory: 'glib warning', file /build/firefox/parts/firefox/build/toolkit/xre/nsSigHandlers.cpp:187

(firefox:8124): IBUS-WARNING **: 17:44:24.602: Failed to mkdir /home/karl/snap/firefox/4630/.config/ibus/bus: Not a directory
-----------------------------end

I don't see the necessary lines.

Anyway, I'm away from the computer for a month or more now. If there will be more ideas about what to do it will take me a while to answer.
Maybe until then the problem is solved, that would be nice.

Also I'm wondering that appimagelauncher is necessary. The program hasn't been updated since a few years already. Wouldn't it be better to somehow find another way to deal with this?

thanks,
Karl