[GH-ISSUE #43] Strange settings behaviour under Linux Firefox 57.0.1 #42

Closed
opened 2026-02-25 22:35:54 +03:00 by kerem · 6 comments
Owner

Originally created by @poVoq on GitHub (Dec 21, 2017).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/43

Under Linux Firefox 57.0.1 the settings pages acts very strange and is partially non-functional.

When I for example want to delete a server, it just kicks me back on the "about:addons", page and the server is not deleted.

Similarly it kicks me back to "about:addons" page when I press the "force sync" button, but when I then go back to the settings page it seems to have worked.

This doesn't happen on my other computer under windows.

Originally created by @poVoq on GitHub (Dec 21, 2017). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/43 Under Linux Firefox 57.0.1 the settings pages acts very strange and is partially non-functional. When I for example want to delete a server, it just kicks me back on the "about:addons", page and the server is not deleted. Similarly it kicks me back to "about:addons" page when I press the "force sync" button, but when I then go back to the settings page it seems to have worked. This doesn't happen on my other computer under windows.
Author
Owner

@marcelklehr commented on GitHub (Dec 25, 2017):

I can't reproduce this. Which version is this and how did you install it?

<!-- gh-comment-id:353889896 --> @marcelklehr commented on GitHub (Dec 25, 2017): I can't reproduce this. Which version is this and how did you install it?
Author
Owner

@poVoq commented on GitHub (Dec 26, 2017):

Floccus 1.32 and Firefox 57.0.1 on a Kubuntu 16.04 system. Floccus was auto-updated from an earlier version that handled account settings a bit different, so maybe that is the cause? Is there a way to completely reset the Floccus settings?

<!-- gh-comment-id:353931055 --> @poVoq commented on GitHub (Dec 26, 2017): Floccus 1.32 and Firefox 57.0.1 on a Kubuntu 16.04 system. Floccus was auto-updated from an earlier version that handled account settings a bit different, so maybe that is the cause? Is there a way to completely reset the Floccus settings?
Author
Owner

@marcelklehr commented on GitHub (Dec 27, 2017):

You could try uninstalling and reinstalling the extension :/

In order to aid in debugging, you can also try and provide some logs:

  • Go to about:debugging
  • enable debugging if it's not enabled already
  • click on debug button next to floccus entry
  • go to floccus options and do whatever triggers the undesired behavior
  • paste the logs somewhere else removing any sensbile info and link to the site here (e.g. use https://pastebin.com)
<!-- gh-comment-id:354196412 --> @marcelklehr commented on GitHub (Dec 27, 2017): You could try uninstalling and reinstalling the extension :/ In order to aid in debugging, you can also try and provide some logs: * Go to `about:debugging` * enable debugging if it's not enabled already * click on `debug` button next to floccus entry * go to floccus options and do whatever triggers the undesired behavior * paste the logs *somewhere else* removing any sensbile info and link to the site here (e.g. use https://pastebin.com)
Author
Owner

@poVoq commented on GitHub (Dec 28, 2017):

Yeah, that's what I did to get rid of a bunch of accidentally created bob@example.com accounts that I could not delete again. The overall issue persists however, it just isn't really effecting my use.

<!-- gh-comment-id:354223759 --> @poVoq commented on GitHub (Dec 28, 2017): Yeah, that's what I did to get rid of a bunch of accidentally created bob@example.com accounts that I could not delete again. The overall issue persists however, it just isn't really effecting my use.
Author
Owner

@marcelklehr commented on GitHub (Jan 30, 2018):

Closing this due to lack of activity. If you find at some point that the behavior does bug you after all or anyone else has similar issues, drop a note here (ideally with logs attached ;)) and I'll reopen :)

<!-- gh-comment-id:361767959 --> @marcelklehr commented on GitHub (Jan 30, 2018): Closing this due to lack of activity. If you find at some point that the behavior does bug you after all or anyone else has similar issues, drop a note here (ideally with logs attached ;)) and I'll reopen :)
Author
Owner

@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.

<!-- gh-comment-id:1478281053 --> @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.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/floccus#42
No description provided.