-
Notifications
You must be signed in to change notification settings - Fork 811
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
Client automatically closes when starting #2414
Comments
Looks like something wrong happened in the past with your journal file, it seems like it's somehow corrupted. I'd say you could try quit the client and then remove all the "C:\Users\USER\AppData\Roaming\Nextcloud._sync_0d8d87f03b87.db*" files (not the other sync db file, just those). Then start the client again. Expect a full sync to occur in the corresponding sync folder then, that will take some time. Better also do a backup of that sync folder just in case. |
I had no issues prior to 3.0.1 and it was working fine after upgrading for a few days as well so I'm not exactly sure what happened. I also didn't change any settings on the client or the server aside from app updates. I tried removing the |
I managed to resolve the issue by deleting Is the New
Old
|
Yes. This happens when you get an SSL error for some reason and the client asks you if you want to trust the certificate or not anyway. If you say yes, then this approved certificate ends up in the cfg file. What I find surprising is that it got nothing to do with the database. Are you sure this is related? There are other changes in the new cfg file, like the Multifolders setup which is not there anymore. This is legacy stuff from way way back, could be that somehow this backward compatibility got broken during 3.0 upgrade. |
The client still automatically closed even when I deleted the .db files you mentioned previously. I reinstalled the client and tried removing the db files again but the client persisted to automatically close, which led me to deleting the cfg file instead. Deleting the .cfg file prompted the client to ask for the nextcloud setup instead of instantly closing. But even if this recreates new db files for the setup user, this should still be the same as manually deleting them. So unless there's some other information the client is retrieving from, I'm also not sure why deleting the cfg file resolves this despite the client producing database errors. |
Removing the |
I too had no issues prior to 3.0.1 but after upgrading I could not launch the latest client on multiple computers. After deleting the .cfg file, they all started working again. |
OK, what would be interesting then is putting back your old cfg file and then removing only some bits in it and seeing if that fails. That'd help narrow down the search space. Just make sure that if you remove one key starting with "X\Multifolders\Y" or "X\Folders\Y" you then also remove all the other keys with the same start, they have to come and go together. |
Deleting all of the Following are the lines deleted:
|
OK, looks like the support for the old style config somehow got broken. Will need someone to investigate the code though. |
I have encountered this bug as well. Nextcloud client stopped working on my Linux/Manjaro system a week ago.
Client on Debian Linux seems to work just fine. |
me too. manjaro linux user here; same "allow_failure" error leading to a core dump. |
Now that I think of it... Did you use our daily or the owncloud client with that sync folder by any chance? They both introduce changes to the db which break backward compatibility, you'd have such crash if you use an older client with that folder again. |
thank you, that might be it. I recently (a week or so ago) switched from owncloud to nextcloud on my laptop. will keep an eye out for this (crash hasn't happened again). |
I also had this issue after switching from the nextcloud-client-git package to the nextcloud-client package in the AUR. Same fix as described by er-vin |
Does this solve the problem? |
I just started having this issue after upgrading to the latest client (3.3.6). I am on Debian Bullseye. I tried downgrading to 3.3.5 but still have the same problem. I removed the corresponding .db files and restarted the client and it worked. Just reporting in case it is useful information. |
Edit: I had the same problem, but the error was related with the compton window compositor. After changing to mate's default compositor, the client stopped crashing. |
On re-installing Debian to an older version, keeping same home directory, I had this error. Deleting nextcloud.cfg fixed it. |
Same problem, can confirm that deleting the cfg file fixes it. I didn't have any Multifolders lines in my cfg file, so the problem isn't that. |
Expected behaviour
Opening nextcloud client should open the client
Actual behaviour
Opening nextcloud client automatically closes the client without any error or messages.
Steps to reproduce
Client configuration
Client version: 3.0.1
Operating system: Windows
OS language: English
Installation path of client:
C:\Program Files\Nextcloud
Logs
Please use Gist (https://gist.github.com/) or a similar code paster for longer
logs.
The text was updated successfully, but these errors were encountered: