-
Notifications
You must be signed in to change notification settings - Fork 815
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
Nextcloud client crashes after ubuntu 20.04 update #1976
Comments
Sorry off topic, but the owncloud-client is compatible to nextcloud? Good to know since I also have crashes. |
@matis-schotte : fortunately, it is ! |
Thanks, switched to owncloud-client as well. |
Yeah, after using the OwnCloud client for a while now I can confirm that that works quite nice, no problems.
The nextcloud client unfortunately needs _alot_ of polishing....
…> Am 13.06.2020 um 02:15 schrieb Alexander Rössler ***@***.***>:
Thanks, switched as well.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Same issue with Nextcloud version 2.6.5-20200713.144448.adada8b2e-1.0~bionic1 on Kubuntu 20.04
|
Well, the problem is more with mixing owncloud client and nextcloud client. They create in index depending on a parent_hash() function that they provide from within the runtime code of their client. When an insert is then done from another client in the same journal db this can only crash since sqlite won't find the function. This is why you don't get a crash with the owncloud client, you got a journal db compatible with owncloud client only. You can get back on your feet by stopping all clients and then removing the journal db. When you'll start the client again it will make a full sync though, depending on the situation this can take a while. |
I had the same sqlite error after downgrading Nextcloud client from version 3.2 (Fedora 34) to version 3.1 (Debian Bullseye): |
@paulez Thanks for your comment. I just encountered the same Now the client crashes shortly after start with the error mentioned above. Your comment pointed me to the right direction, but I didn't want to fiddle with the database. So I simply deleted it because the document at https://docs.nextcloud.com/desktop/2.6/architecture.html#the-sync-journal says that it is simply rebuilt by the client. Unfortunately this doesn't seem to be quite true because it looks like lot of file (if not even all files) are synchronized from the server again, even though they haven't changed for a long time and were surely in sync when the trouble started. Just for the records. ;-) |
Thank you, paulez ! I had this issue after upgrading to Ubuntu 21.04. The error in syslog was Deleting the index "metadata_parent" from the "metadata" table worked perfectly for me, without having to rebuild the Journal DB or re-syncing any files. Before I deleted the index, I noticed that newer journal databases (which I just created a few days ago) didnt have the index at all, so I felt quite safe deleting it. |
Thank you @paulez! I was experiencing the same problem being discussed in this issue and your comment fixed my problem! For further elaboration on what you need to do for others like me who may not know what or where the "journal db" is, it's a sql db file (like Eg, if your Nextcloud-sync'd dir is
Then, select the |
After updating from ubuntu 19.10 to 20.04 version, my nextcloud-client always crashed after a while.
Expected behaviour
Should not crash
Actual behaviour
Tell us what happens instead
Steps to reproduce
Client configuration
Client version: 2.6.2 from ppa
Operating system: ubuntu 20.04
OS language:
Qt version used by client package (Linux only, see also Settings dialog): Qt 5.12.8 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 9.3.0) on "xcb"
Client package (From Nextcloud or distro) (Linux only): from PPA
Installation path of client:
Server configuration
Nextcloud version:
Storage backend (external storage):
Logs
Second logfile (last lines) after removing the file causing issue previously :
Hope it helps !
My workaround, at that point, was to switch to owncloud-client (which works well).
The text was updated successfully, but these errors were encountered: