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

[Bug]: Only three accounts supported #1187

Open
tomirgang opened this issue Nov 1, 2024 · 6 comments
Open

[Bug]: Only three accounts supported #1187

tomirgang opened this issue Nov 1, 2024 · 6 comments
Labels
bug Something isn't working

Comments

@tomirgang
Copy link

Describe the bug

I'm using Tuba 0.8.4 from Flathub on VanillaOS 2.
I think I spotted a bug:
I can add more then three accounts, but after every restart only the first three accounts are available.

Steps To Reproduce

  1. Install Tuba 0.8.4 form Flathub
  2. Add more then three Mastodon accounts
  3. Close the app and reopen it.
    Only the first three accounts are available.

Logs and/or Screenshots

No response

Instance Backend

Mastodon

Operating System

VanillaOS 2

Package

Flatpak

Troubleshooting information

No response

Additional Context

No response

@tomirgang tomirgang added the bug Something isn't working label Nov 1, 2024
@GeopJr
Copy link
Owner

GeopJr commented Nov 1, 2024

Thanks for the report!

Tuba securely saves and reads accounts from the secret-service. Sometimes distros and setups have configured it wrong. You can try and see if they are saved correctly using Passwords & Keys (seahorse) and check if there's any errors when running tuba with flatpak run dev.geopjr.Tuba but other than that there's not much I can do.

I'll try VanillaOS in a vm and attempt to re-produce it but from Tuba's side there's no hard-limits and will add as many accounts as the secret-service returns.

@tomirgang
Copy link
Author

Hi @GeopJr,

I just found one entry for Tuba in the secret store:

secret-tool search --all --unlock app_id dev.geopjr.Tuba
[/15]
label = 
5�****more binary stuff***
created = 2024-10-30 06:27:53
modified = 2024-10-30 06:27:53
schema = org.freedesktop.Secret.Generic
attribute.app_id = dev.geopjr.Tuba

and no account information at all.

The console log showed some warnings:

tom@Vanilla  ~ $ flatpak run dev.geopjr.Tuba
(dev.geopjr.Tuba:2): Json-WARNING **: 09:48:00.748: Unsupported type `GeeMap'
(dev.geopjr.Tuba:2): Json-WARNING **: 09:48:00.748: Unsupported type `GType'
(dev.geopjr.Tuba:2): Json-WARNING **: 09:48:00.748: Unsupported type `gpointer'
(dev.geopjr.Tuba:2): Json-WARNING **: 09:48:00.748: Unsupported type `gpointer'
(dev.geopjr.Tuba:2): Json-WARNING **: 09:48:00.748: Unsupported type `GType'
(dev.geopjr.Tuba:2): Json-WARNING **: 09:48:00.748: Unsupported type `gpointer'
(dev.geopjr.Tuba:2): Json-WARNING **: 09:48:00.748: Unsupported type `gpointer'
(dev.geopjr.Tuba:2): Json-WARNING **: 09:48:00.748: Unsupported type `GeeSet'
(dev.geopjr.Tuba:2): Json-WARNING **: 09:48:00.748: Unsupported type `GeeCollection'
(dev.geopjr.Tuba:2): Json-WARNING **: 09:48:00.748: Unsupported type `GeeSet'

@mickeymarse
Copy link

I'm having the same issue, but I'm actually limited to only one account. :(

@GeopJr
Copy link
Owner

GeopJr commented Jan 9, 2025

Someone on Mastodon helped me debug this further, I just haven't gotten back into FOSS from the holidays :P

If the accounts have the same name, try changing the display name of one you are adding temporarily until you add it and then change it back

@mickeymarse
Copy link

No rush at all. Feel free to answer whenever you can.
In my case, accounts have different names and server. No similarities whatsoever.
Happy to check the original thread if you still have the link though.

@GeopJr
Copy link
Owner

GeopJr commented Jan 9, 2025

It was mostly a one off message so nothing to really check out. Uhmm, I don't know.

  • Are there are any errors right after adding your accounts?
  • Do the accounts have any similarities in regards of handle / display name?
  • What's your distro (and DE)?
  • You do have a libsecret backend installed, right? (Kwallet, gnome-keyring, keepass...)
  • Could you make sure the keyring is unlocked with seahorse / Passwords & Keys?
  • What backend software do both the accounts run? (Mastodon, Akkoma etc)

Other than that, I'm out of ideas. We do have some hacks around some issues with some setups (we unlock the whole keyring when we shouldn't have to and we don't on GNOME and KDE at least), but I don't think that has anything to do with it since at least one was saved.

From Tuba's side, all it does is ask libsecret to save the account to the keyring, but if that failed there would be at least 2-3 warnings shown :////

I wish I could reproduce it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants