Hi there!
I have been using Quelea on Linux for several months now. A friend of mine took time to create translations for more than 150 songs. We used them during Christmas service.
We did not saved the service file since it was very spontaneous. Then we shut down the computer.
When he started the computer the following day to translate some other songs, he founded the song database in Quelea empty! The Bibles we added and user-defined themes are still there, but no song at all!
Anybody has an idea of what happened? Do we have to restart from scratch? 
I add some details:
In the logs of my Linux system I’ve found:
25 déc. 13:13:03 systemd: app-flatpak-org.quelea.Quelea-2020.scope: Consumed 1min 20.766s CPU time.
25 déc. 13:10:03 systemd: Started app-flatpak-org.quelea.Quelea-2020.scope.
25 déc. 13:09:59 systemd: app-flatpak-org.quelea.Quelea-1777.scope: Consumed 51.623s CPU time.
25 déc. 13:08:30 systemd: Started app-flatpak-org.quelea.Quelea-1777.scope.
The file database_new.script has been modified the 25 déc. 13:10:06 and looks like a brand new one (3.1 ko, 50 lines).
Here is my assumption :
As the software usually takes a long time to show up, it has been awkwardly launched two times, and for some reason the second instance has overwritten the database.
Does it seem plausible to you?
This is odd - even if the database is corrupted then it should still be there, Quelea won’t overwrite it.
To rule out the simple stuff - did you log on as the same user? And are other files in the .Quelea folder newly created as well around the same time, or just the database?
Thanks,
Michael
There is one single user on the computer.
database_new.properties has the same modification timestamp than database_new.script, yes.
database_new.lobs has not been changed at that date and database_new.log has been modified more recently (today) and it is empty. I don’t see any other file that keep track of the same timestamp.
The file quelea-debuglog.txt is not long enough to embed information about the issue (its records only concern today).
Thanks!
quelea-debuglog only retains information from the last run - that much is by design, but the database file should never be overwritten like that.
I’m wondering if this is something to do with Flatpak, but it really shouldn’t be. Does the same thing happen now if you create a song in the database and restart Quelea?
I’ve tried to reproduce the bug : I’ve imported songs agin, restarted computer, launched Quelea twice… Everything is fine.
The only difference is the fact there was no translations this time. I wonder whether it is possible translations corrupt the database and force Quelea to create a new one…
The translations were in farsi (arabic alphabet, written from the right to the left).