Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Unable to open parameters database on fixed 3.6.4 #268

Closed
noahboegli opened this issue Aug 25, 2024 · 16 comments · Fixed by #339
Closed

Unable to open parameters database on fixed 3.6.4 #268

noahboegli opened this issue Aug 25, 2024 · 16 comments · Fixed by #339
Assignees
@herve-er
Labels
bug Something isn't working

Comments

@noahboegli
Copy link

noahboegli commented Aug 25, 2024 •
edited
Loading

Starting kDrive on linux (AppImage) gives the following error:

kDrive server starting
kDrive server initialization error: Unable to open parameters database.

It was apparently fixed for this version (as noted in #237), but at least for me the issue still arises.
Is there a manual step or database migration that must be done by an intermediary version ?

(upgraded from 3.5.8, since for some reason the update notification does not work on linux, but that's a separate issue)
@noahboegli noahboegli added the bug Something isn't working label Aug 25, 2024
@ChristopheLarchier
Copy link
Contributor

Hello, would it be possible to attach the log of the app? (located in /tmp/kDrive-logdir)
This might happen if you ran an older version of the app after migrating to the latest version.

@noahboegli
Copy link
Author

Sure: 20240826_1054_kDrive.log

I did not ran the old version per say, as the 3.6.4 version never managed to run. I basically shut down 3.5.8 and opened 3.6.4 and it crashed. Reverted back to 3.5.8 and it worked again.

@ngiger
Copy link

ngiger commented Aug 30, 2024

I had the same problem.

After running rm -rfv .config/kDrive/ /tmp/kDrive-logdir

I have the following log 20240830_1052_kDrive.log
Where it complains about a missing file /home/niklaus/squashfs-root/sync-exclude.lst
After touch /home/niklaus/squashfs-root/sync-exclude.lst I could proceed to the login

@Feeback25
Copy link

Hello,
Same problem as noahboegli.
I am using Fedora 40. Kdrive has already worked on my machine.
For a few days, it does not launch.
Here is an extract from the logs:
"18:05:14 AppRun.wrapped: kDrive server initialization error: Unable to open parameters database.
18:05:14 AppRun.wrapped: kDrive server initialization error: Unable to open parameters database.
18:05:14 AppRun.wrapped: Warning: Ignoring WAYLAND_DISPLAY on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
18:05:14 AppRun.wrapped: kDrive server starting
18:05:13 systemd: Started app-gnome-kdrive-15001.scope - Application launched by gnome-shell."
Thanks for your help

@harryburli
Copy link

Hi,
same issue here using "kDrive-3.6.4.20240814-amd64.AppImage" on Linux Mint 21.3 Cinnamon.
do you know a work around?

Bildschirmfoto vom 2024-09-12 15-52-26

I have the following log

20240912_1605_kDrive.log

Thank you in advance!

@ClementKunz ClementKunz pinned this issue Sep 17, 2024
@herve-er
Copy link
Contributor

Hello everyone,
After investigating, we have identified an issue with the migration of the parameters database from version 3.5.8 when skipping version 3.6.1. Unfortunately, we will not be able to provide a fix in the upcoming version (3.6.5) but it should be available in the next one.

However, we have found a workaround to resolve this issue on your installations:

  1. Close kDrive if it is already open.
  2. Launch the 3.5.8 AppImage.
  3. Once it has started, close it.
  4. Launch the 3.6.1 AppImage. (Download links below)
  5. Once it has started, close it.
  6. You should now be able to use kDrive 3.6.4.

kDrive 3.6.1 Linux AMD: https://kdrive.infomaniakgroup.com/app/share/100338/a41db454-e355-47c9-8e4c-c2789a23b164
kDrive 3.6.1 Linux ARM: https://kdrive.infomaniakgroup.com/app/share/100338/333a80e7-dfe6-4dd9-81ea-d3cdbf542baf

We apologize for the inconvenience.

@herve-er herve-er self-assigned this Sep 17, 2024
@herve-er
Copy link
Contributor

Hi @ngiger,

After touch /home/niklaus/squashfs-root/sync-exclude.lst I could proceed to the login

To avoid unexpected behavior, I suggest replacing the empty sync-exclude.lst file you created with the one bellow.
sync-exclude-linux.zip

@herve-er herve-er mentioned this issue Sep 17, 2024
Closed
@harryburli
Copy link

harryburli commented Sep 17, 2024 via email

@herve-er
Copy link
Contributor

Hello @harryburli,
It seems that the image of the popup was not attached to your comment. Could you please provide us with it?

Thank you.

@harryburli
Copy link

harryburli commented Sep 18, 2024 via email

@herve-er
Copy link
Contributor

Unfortunately, the attached files from your emails were not transferred to the GitHub discussion. Could you please upload them directly from the GitHub discussion ( #268 )?

Thank you.

@harryburli
Copy link

Jep!
20240917_2057_kDrive.log.gz
20240917_2059_kDrive.log
Bildschirmfoto vom 2024-09-17 20-45-00

@herve-er
Copy link
Contributor

Hi @harryburli,
Thank you for the additional information.

Since this is unrelated to the parameters database issue, I have opened a new one for you --> #307

@noahboegli
Copy link
Author

Hello everyone, After investigating, we have identified an issue with the migration of the parameters database from version 3.5.8 when skipping version 3.6.1. Unfortunately, we will not be able to provide a fix in the upcoming version (3.6.5) but it should be available in the next one.

However, we have found a workaround to resolve this issue on your installations:

1. Close kDrive if it is already open.

2. Launch the 3.5.8 AppImage.

3. Once it has started, close it.

4. Launch the 3.6.1 AppImage. (Download links below)

5. Once it has started, close it.

6. You should now be able to use kDrive 3.6.4.

kDrive 3.6.1 Linux AMD: https://kdrive.infomaniakgroup.com/app/share/100338/a41db454-e355-47c9-8e4c-c2789a23b164 kDrive 3.6.1 Linux ARM: https://kdrive.infomaniakgroup.com/app/share/100338/333a80e7-dfe6-4dd9-81ea-d3cdbf542baf

We apologize for the inconvenience.

@herve-er Thank you ! I can confirm the upgrad path works.
I don't know if you want to keep this issue open for reference, I'll let you guys be the judges of that.

@herve-er
Copy link
Contributor

@noahboegli Thank you for the feedback!
We will keep this issue open until we develop a proper fix.

@jlebleu
Copy link

jlebleu commented Oct 4, 2024

Hello everyone, After investigating, we have identified an issue with the migration of the parameters database from version 3.5.8 when skipping version 3.6.1. Unfortunately, we will not be able to provide a fix in the upcoming version (3.6.5) but it should be available in the next one.
However, we have found a workaround to resolve this issue on your installations:

1. Close kDrive if it is already open.

2. Launch the 3.5.8 AppImage.

3. Once it has started, close it.

4. Launch the 3.6.1 AppImage. (Download links below)

5. Once it has started, close it.

6. You should now be able to use kDrive 3.6.4.

kDrive 3.6.1 Linux AMD: https://kdrive.infomaniakgroup.com/app/share/100338/a41db454-e355-47c9-8e4c-c2789a23b164 kDrive 3.6.1 Linux ARM: https://kdrive.infomaniakgroup.com/app/share/100338/333a80e7-dfe6-4dd9-81ea-d3cdbf542baf
We apologize for the inconvenience.

@herve-er Thank you ! I can confirm the upgrad path works. I don't know if you want to keep this issue open for reference, I'll let you guys be the judges of that.

Did the same, works for me also, kdrive is restarted!!! Yess

@herve-er herve-er linked a pull request Oct 8, 2024 that will close this issue
KDESKTOP-717-We-should-check-if-a-column-exists-before-trying-to-do-the-alter-table-in-DB #339
Merged
@ChristopheLarchier ChristopheLarchier unpinned this issue Oct 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@herve-er herve-er

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
7 participants
@ngiger @jlebleu @harryburli @noahboegli @Feeback25 @ChristopheLarchier @herve-er