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

Git sync fails on tor-browser #1656

Open
1 task done
balki opened this issue Jun 21, 2024 · 4 comments
Open
1 task done

Git sync fails on tor-browser #1656

balki opened this issue Jun 21, 2024 · 4 comments

Comments

@balki
Copy link

balki commented Jun 21, 2024

Which version of floccus are you using?

5.2.3

How many bookmarks do you have, roughly?

300

Are you using other means to sync bookmarks in parallel to floccus?

No

Sync method

Git

Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please.

Tor browser 13.5

Which version of Nextcloud Bookmarks are you using? (if relevant)

No response

Which version of Nextcloud? (if relevant)

No response

What kind of WebDAV server are you using? (if relevant)

No response

Describe the Bug

  • Works fine on firefox but fails on tor-browser
  • Previously have used on tor-browser with nextcloud bookmarks. Used to work fine (~3 years back). Don't have nextcloud instance anymore
  • I tried removing all profiles and recreating from scratch
  • Tried with empty repo and also existing repo
  • OS - Ubuntu 22.04

Let me know if more details are needed to debug. Thanks!

Debug logs

2024-06-21T19:44:24.277Z Starting sync process for account [email protected]:bookmarks-tor.xbel
2024-06-21T19:44:24.461Z onSyncStart: begin
2024-06-21T19:44:24.467Z (git) init
2024-06-21T19:44:24.468Z onSyncFail
2024-06-21T19:44:24.468Z Syncing failed with A mutation operation was attempted on a database that did not allow mutations.
2024-06-21T19:44:24.480Z onSyncFail

Expected Behavior

sync working normal

To Reproduce

image

Debug log provided

  • I have provided a debug log file
@balki balki added the bug label Jun 21, 2024
Copy link

Hello 👋

Thank you for taking the time to open this issue with floccus. I know it's frustrating when software
causes problems. You have made the right choice to come here and open an issue to make sure your problem gets looked at
and if possible solved.
I'm Marcel and I created floccus and have been maintaining it ever since.
I currently work for Nextcloud which leaves me with less time for side projects like this one
than I used to have.
I still try to answer all issues and if possible fix all bugs here, but it sometimes takes a while until I get to it.
Until then, please be patient.
Note also that GitHub is a place where people meet to make software better together. Nobody here is under any obligation
to help you, solve your problems or deliver on any expectations or demands you may have, but if enough people come together we can
collaborate to make this software better. For everyone.
Thus, if you can, you could also have a look at other issues to see whether you can help other people with your knowledge
and experience. If you have coding experience it would also be awesome if you could step up to dive into the code and
try to fix the odd bug yourself. Everyone will be thankful for extra helping hands!
One last word: If you feel, at any point, like you need to vent, this is not the place for it; you can go to the forum,
to twitter or somewhere else. But this is a technical issue tracker, so please make sure to
focus on the tech and keep your opinions to yourself.

I look forward to working with you on this issue
Cheers 💙

@marcelklehr
Copy link
Member

The git sync need IndexedDB to work, Tor Browser is likely using Firefox Private mode which doesn't support IndexedDB it seems :(

@marcelklehr
Copy link
Member

There's an about:config workaround by setting dom.indexedDB.privateBrowsing.enabled to true Of course this will forego the privacy guarantees of private browsing...

@balki
Copy link
Author

balki commented Jun 22, 2024

There's an about:config workaround by setting dom.indexedDB.privateBrowsing.enabled to true

I see this setting is true. Also all indexedDB settings match my firefox.

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Backlog
Development

No branches or pull requests

2 participants