mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-26 06:35:59 +03:00
[GH-ISSUE #681] database disk image is malformed #438
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#438
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 @tessus on GitHub (Oct 15, 2020).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/681
Describe the bug
sync stopped working. I believe after the upgrade from nextcloud 17.0.10 to 18.0.10.
The bookmarks app works however. I can see all bookmarks properly.
Unfortunately I can't even set
Trigger sync from scratchand then sync, because I get the same error.To Reproduce
Steps to reproduce the behavior:
Expected behavior
It should sync as always
Screenshots
Desktop (please complete the following information):
Server (please complete the following information):
Note: Please write down the actual version numbers instead of writing 'latest'.
Debug log
Those are the only entries.
Additional context
Add any other context about the problem here.
@marcelklehr commented on GitHub (Oct 16, 2020):
I think this is a client-side error. It appears your browser's sqlite database was corrupted for some reason.
@tessus commented on GitHub (Oct 16, 2020):
Hmm, this might be a problem. I can't just delete the database. It holds all bookmarks and whatnot. So how do I fix this?
I imagine something like this: Export stuff in floccus. Close browser. Connect to database. Delete floccus tables. Start browser. Import floccus settings.
But what I find rather strange is that the debug log does not tell me anything. Not the statement, not what the real issue is, nothing. This is not a debug log, but a standard app log with a - sorry to say - useless message. Also, how can this db get corrupted, if nothing but the browser is accessing it? Very mysterious.
@marcelklehr commented on GitHub (Oct 16, 2020):
I agree, I haven't seen that error before.
Are you using sqlite on the server?
This is very peculiar.
@marcelklehr commented on GitHub (Oct 16, 2020):
If not, it seems like the user data of all your browsers got corrupted?
@tessus commented on GitHub (Oct 16, 2020):
No, I use mysql on the server. I don't think Nextcloud does even support sqlite and I wouldn't use it anyway, since concurrency doesn't really work with sqlite.
So how can I fix this? Any ideas?
This also doesn't make sense, because everything else works in those browsers. Let's concentrate on one: Waterfox (which is basically a Firefox clone). For all intents and purposes we can treat is as Firefox.
Where exactly is that data stored? There are many sqlite database in the profile dir. I'm more than happy to drop the floccus tables.
@marcelklehr commented on GitHub (Oct 16, 2020):
Floccus doesn't even use SQLite or any kind of SQL database. The error you see is generated by the browser. I don't know which SQLite file is corrupt.
So facts are: 1) Something internal to the browser is broken. 2) Floccus doesn't function anymore because of this.
Possible options I see are:
@tessus commented on GitHub (Oct 16, 2020):
Creating a new profile is out of the question, because I will lose everything.
Re-installing floccus / browser did not work. Can you please add better debug messages so that we know what the problem is? Component, database, table, stacktrace....
@tessus commented on GitHub (Oct 16, 2020):
Oh wait. Removing floccus and quitting the browser did something. But I can't import my exported json file:
@tessus commented on GitHub (Oct 17, 2020):
How can I import the exported settings? Btw, I exported the settings with the same version of floccus.
@marcelklehr commented on GitHub (Oct 18, 2020):
Firefox
about:debuggingdebugbutton next to floccus entrysync nowfor the account of your choice.Chrome
chrome://extensionsDeveloper modedist/html/background.htmlbutton in floccus' entry next to "Inspect views: "sync nowfor the account of your choice@marcelklehr commented on GitHub (Oct 18, 2020):
mmh, do you have secured your credentials with a passphrase?
@tessus commented on GitHub (Oct 18, 2020):
Nope.
Unfortunately my floccus has no accounts anymore, so I can't debug anything.
@marcelklehr commented on GitHub (Oct 18, 2020):
is this in Waterfox?
@tessus commented on GitHub (Oct 18, 2020):
Yes. Waterfox 2020.08.
@tessus commented on GitHub (Oct 18, 2020):
I'll be away from my computer for a few hours. Ttyl.
@marcelklehr commented on GitHub (Oct 18, 2020):
Can you try the normal firefox, or chrome?
@tessus commented on GitHub (Oct 18, 2020):
Nope, I usually don't use Firefox or Chrome very often and wiped all their settings and add-ons. So now all my browsers have a blank floccus setup.
I've tried to import the settings into Chrome and I get the following message:
I really have to go now, but I'll try Firefox later as well. But even if that worked, it would not be very helpful, because I have to import those settings in Waterfox.
@tessus commented on GitHub (Oct 18, 2020):
In Firefox I get the following:
Unfortunately this doesn't help me very much. I thought that Waterfox and Firefox use the same backend, so this is kind of disheartening.
@marcelklehr commented on GitHub (Oct 18, 2020):
Waterfox probably uses an older version of firefox as its base.
@tessus commented on GitHub (Oct 18, 2020):
Hmm, it might be a bit behind, but it's not an ancient version. But what is really puzzling is that everything else works, or at least I always thought it did. Now I'm not so sure. Why would everything work, but import?
I'm really reluctant to use Firefox/Chrome, because both of them are rather invasive and almost impossible to decouple from their respective sync features. One little mistake and all your data is compromised.
@tessus commented on GitHub (Oct 19, 2020):
Ok, so what does that mean? Import just won't work on Waterfox and that's it? In that case we can close this issue, since I doubt you'll fix the
t.text is not a function.@marcelklehr commented on GitHub (Oct 19, 2020):
Import uses new language / HTML features that Waterfox apparently doesn't support yet.
I guess so. I'm not too inclined to come up with fixes for fringe browsers, atm. I'm happy to accept pull requests, though, as long as normal browsers continue to work.
@tessus commented on GitHub (Oct 19, 2020):
How can I revert to a previous version of floccus?
4.4.0 broke even the selection of the local folder:
@tessus commented on GitHub (Oct 19, 2020):
Never mind. I tried all versions down to 4.2.0. None work anymore for some reason.
This really sucks, since I now don't have a working floccus installation anymore.
Which means I can either use a browser that steals my data or not use floccus. This is just awesome.
@marcelklehr commented on GitHub (Oct 19, 2020):
I think for some reason your browser setup is broken. You could try exporting your bookmarks and all your goodies from waterfox and create a new profile / reinstall waterfox.
FWIW, I think firefox at least asks before they take your data, and you're not required to use their sync mechanism.
@tessus commented on GitHub (Oct 19, 2020):
Yes and no. You can deactivate telemetry via the UI, but they still collect data. So the UI settings are a lie. Currently it is still possible to turn it off properly via
config:aboutoruser.js. The question is for how long.I'll try to export all my data and goodies and start over. I guess that my only option.
Thanks again for your help - and sorry for my ranting.
@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.