Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
winterstein opened this issue Jul 9, 2024 · 7 comments
Open

Comments

@winterstein
Copy link

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
Copy link
Member

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
Copy link

aikiks commented Jul 19, 2024

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
Copy link

aikiks commented Jul 19, 2024

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
Copy link

tdislay commented Jul 25, 2024

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

@aikiks
Copy link

aikiks commented Jul 25, 2024

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
Copy link

tdislay commented Jul 29, 2024

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
Copy link

aikiks commented Jul 29, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants