mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 22:26:06 +03:00
[GH-ISSUE #554] Cannot add account after 4.2.0 upgrade, FF 68esr #387
Labels
No labels
browser-specific
bug
correctness issues
enhancement
feature: Google Drive
feature: Linkwarden
feature: git
feature: nextcloud-bookmarks
feature: tabs
feature: webdav
help wanted
native-app
priority: high
priority: low
priority: medium
pull-request
question
question
stale
upstream
waiting for more information
wontfix
🙁 Not following issue template
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/floccus#387
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @wohali on GitHub (Jun 4, 2020).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/554
Describe the bug
I have re-enabled floccus with the 4.2.0 upgrade on my Firefox 68 ESR Linux install, trying to test if the fix for #505 fixes my problem reported in #482 .
I pressed the big "+" button to create a new account. This opens a tab with the 3 options for a new account: NextCloud bookmarks, XBEL, NextCloud Legacy.
The Add Account button has a "click" animation but does nothing.
To Reproduce
See above.
Expected behavior
I should be able to add a new account, but can't.
Screenshots

This is where I get stuck.
Desktop (please complete the following information):
Server (please complete the following information):
n/a
Note: Please write down the actual version numbers instead of writing 'latest'.
Debug log
Unable to provide debug log since no link to retrieve the debug log is possible without an account.
@marcelklehr commented on GitHub (Jun 5, 2020):
Could you check the javascript console for errors on that page?
@elfacht commented on GitHub (Jun 5, 2020):
Same in FF 78.
@elfacht commented on GitHub (Jun 5, 2020):
Maybe this helps:
@marcelklehr commented on GitHub (Jun 5, 2020):
Ooph, that's strange. Looks like there is some b0rked state in the extension storage. It may help to uninstall the extension and reinstall to get rid of that. 🤔
@user-51 commented on GitHub (Jun 5, 2020):
Same problem with FF 78.0b2 (64-bit) on Linux. Uninstalling and reinstalling was not enough, but removing browser-extension-data/floccus@handmadeideas.org and extensions/staged/floccus@handmadeideas.org before reinstalling did the job.
@wohali commented on GitHub (Jun 5, 2020):
I tried this - extension uninstall, then
find ~/.mozilla -name \*floccus\* -exec rm -rf {} \;, which deleted the directories you mention. I then reinstalled.Now, on trying to save an account again, it always comes up as
bob@example.org.Logfile is full of:
The "Floccus bookmark sync" tab is still open with all of my credentials in it, but every time I press Save (and see the green checkmark), it doesn't change the plugin, dropdown, which continues to say my account is
bob@example.organd is erroring with a 404. 😕@wohali commented on GitHub (Jun 5, 2020):
Nothing useful in the JS console:
Could it be related to https://bugzilla.mozilla.org/show_bug.cgi?id=1267027 ?
@ChrisWiegman commented on GitHub (Jun 5, 2020):
I can confirm the bug in FF 77.0.1 on Pop_OS 20.04. Clearing the extension data manually does not fix it either
@ChrisWiegman commented on GitHub (Jun 5, 2020):
When looking into it I see plenty of console errors that it can't connect (as storage has been cleared that isn't for an existing account) and the following when looking at the debugging screen.

@joelmaxuel commented on GitHub (Jun 6, 2020):
Floccus Add-in for Firefox (68.8.0esr) updated yesterday to v4.2.0 - as I already had a NextCloud account already set up, this update now stalls with the icon permanently having a
<->overlay.Debug log has stopped recording anything in this past day.
Bookmarks app version 2.3.1 for NextCloud 15.0.13 (yes, I do have some point-updates to attend to).
@marcelklehr commented on GitHub (Jun 6, 2020):
I was finally able to reproduce and fix this. Thanks for your feedback and patience :)
@elfacht commented on GitHub (Jun 6, 2020):
Now it stucks in synchronisation on FF (also in Chrome).
@marcelklehr commented on GitHub (Jun 6, 2020):
Can you elaborate?
@elfacht commented on GitHub (Jun 6, 2020):
This is happening since half an hour and nothing is syncing (FF and Chrome, latest versions):
@marcelklehr commented on GitHub (Jun 6, 2020):
Mh, can you try restarting the browser? If it's stuck in limbo this usually helps. If it doesn't, logs might be useful to tackle this one.
@elfacht commented on GitHub (Jun 6, 2020):
Already tried that.
From the debug log:
@marcelklehr commented on GitHub (Jun 6, 2020):
Aha! This means that it's waiting for the lock file to be released. It'll give up after a while, but you can remove the lock file manually to get it working again.
@elfacht commented on GitHub (Jun 6, 2020):
Also did that, still no luck. ;)
@elfacht commented on GitHub (Jun 6, 2020):
I have 2 FF running: regular and Developer Edition. On the regular it's working, on the Developer and Chrome it's not working.
@marcelklehr commented on GitHub (Jun 6, 2020):
Does the log file still say the same thing?
@marcelklehr commented on GitHub (Jun 6, 2020):
Ah, I can confirm that. If you reload that tab or reopen the account settings, saving should work. For some reason the initial settings screen after creating the account doesn't save correctly :( see #557
@wohali commented on GitHub (Jun 7, 2020):
@marcelklehr I'm still stuck - will wait until 4.2.1 is actually pushed to the channel (I still have "4.2.0.5" here) and test again.
@wohali commented on GitHub (Jun 7, 2020):
@marcelklehr No, this is not fixed. Reloading the tab or reopening the account settings, it still sees bob@example.com and is *still trying to connect to it. It won't let me actually add an account at all.
Version: 4.2.1
@elfacht commented on GitHub (Jun 7, 2020):
@marcelklehr Yes, the logfile is still the same.
@elfacht commented on GitHub (Jun 7, 2020):
Now this shows up:
Now it works after hitting the sync button!
@github-actions[bot] commented on GitHub (Mar 21, 2023):
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.