| Summary: | error while opening database digikam will try to automatically reconnect to the database | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Carlo Gioia <gioia.carlo> |
| Component: | Database-Engine | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | caulier.gilles, metzpinguin |
| Priority: | NOR | ||
| Version First Reported In: | 6.4.0 | ||
| Target Milestone: | --- | ||
| Platform: | Manjaro | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 7.0.0 | |
| Sentry Crash Report: | |||
| Attachments: |
Dijikam.txt
Dijikam 2.txt attachment-24571-0.html attachment-24732-0.html attachment-13078-0.html attachment-13420-0.html |
||
|
Description
Carlo Gioia
2020-04-30 18:42:26 UTC
I can't do much with the bug report ... Let's start: 1. Why is digiKam running when Manjaro is started? Did you activate any session management? 2. What type of database are you using? SQLite or MySQL? 3. Please start digiKam in the console and post the log. If the database is on a drive that has not yet been mounted, the error message would be normal. Make sure that the database is available when digiKam is started. Deactivate session management so that not all programs are restarted. Maik Created attachment 128075 [details] Dijikam.txt Good day Maik, and thank you for helping. 1.0 Based on your question I did some checking and found that i did have the restore previous session option on ... I changed the option to start with empty session .... shut down restarted and came up clean (dijikan did not start until I clicked to start program 2.0 Using Image editor, settings, configure digikam, database, type says SQLite 3.0 started using Konsole ran app ... after waiting a while I cancelled app so you would see rest of text .... text is attached Regards Carlo On Thu, Apr 30, 2020 at 4:14 PM Maik Qualmann <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=420819 > > Maik Qualmann <metzpinguin@gmail.com> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > CC| |metzpinguin@gmail.com > Status|REPORTED |NEEDSINFO > Resolution|--- |WAITINGFORINFO > > --- Comment #1 from Maik Qualmann <metzpinguin@gmail.com> --- > I can't do much with the bug report ... Let's start: > 1. Why is digiKam running when Manjaro is started? Did you activate any > session > management? > 2. What type of database are you using? SQLite or MySQL? > 3. Please start digiKam in the console and post the log. > > If the database is on a drive that has not yet been mounted, the error > message > would be normal. Make sure that the database is available when digiKam is > started. Deactivate session management so that not all programs are > restarted. > > Maik > > -- > You are receiving this mail because: > You reported the bug. Created attachment 128077 [details] Dijikam 2.txt Maik i am attaching a 2nd log ... this time I opened Konsole, started Dolphin, from Dolphin selected directory, then I chose to open using dijikam .... this is how I do not get the database error .... I hope this helps On Fri, May 1, 2020 at 3:33 PM Carlo Gioia <gioia.carlo@gmail.com> wrote: > Good day Maik, and thank you for helping. > 1.0 Based on your question I did some checking and found that i did have > the restore previous session option on ... I changed the option to start > with empty session .... shut down restarted and came up clean (dijikan did > not start until I clicked to start program > 2.0 Using Image editor, settings, configure digikam, database, type says > SQLite > 3.0 started using Konsole ran app ... after waiting a while I cancelled > app so you would see rest of text .... text is attached > > Regards Carlo > > > On Thu, Apr 30, 2020 at 4:14 PM Maik Qualmann <bugzilla_noreply@kde.org> > wrote: > >> https://bugs.kde.org/show_bug.cgi?id=420819 >> >> Maik Qualmann <metzpinguin@gmail.com> changed: >> >> What |Removed |Added >> >> ---------------------------------------------------------------------------- >> CC| |metzpinguin@gmail.com >> Status|REPORTED |NEEDSINFO >> Resolution|--- |WAITINGFORINFO >> >> --- Comment #1 from Maik Qualmann <metzpinguin@gmail.com> --- >> I can't do much with the bug report ... Let's start: >> 1. Why is digiKam running when Manjaro is started? Did you activate any >> session >> management? >> 2. What type of database are you using? SQLite or MySQL? >> 3. Please start digiKam in the console and post the log. >> >> If the database is on a drive that has not yet been mounted, the error >> message >> would be normal. Make sure that the database is available when digiKam is >> started. Deactivate session management so that not all programs are >> restarted. >> >> Maik >> >> -- >> You are receiving this mail because: >> You reported the bug. > > Did you enable Baloo database syc in digiKam setup Metadata page ? Gilles Caulier Created attachment 128086 [details] attachment-24571-0.html 4.0 I don't think so ... under meta data I dont see such an optio .... looking through and searching The digiKam Handbook ... I only find mention of databases on Pages 18,30,31,102 .... so NO If I search under sync database in section 12.2.8 of manual says TODO .... so my answer is NO On Fri, May 1, 2020 at 4:36 PM <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=420819 > > caulier.gilles@gmail.com changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > CC| |caulier.gilles@gmail.com > > --- Comment #4 from caulier.gilles@gmail.com --- > Did you enable Baloo database syc in digiKam setup Metadata page ? > > Gilles Caulier > > -- > You are receiving this mail because: > You reported the bug. Created attachment 128087 [details] attachment-24732-0.html Definitely No ... under the Tools tab, select Maintenance, one of the options is Sync metadata Database ....box is not green meaning not selected On Fri, May 1, 2020 at 5:47 PM Carlo Gioia <gioia.carlo@gmail.com> wrote: > 4.0 I don't think so ... under meta data I dont see such an optio .... > looking through and searching The digiKam Handbook ... I only find mention > of databases on Pages 18,30,31,102 .... so NO > If I search under sync database in section 12.2.8 of manual says TODO .... > so my answer is NO > > > On Fri, May 1, 2020 at 4:36 PM <bugzilla_noreply@kde.org> wrote: > >> https://bugs.kde.org/show_bug.cgi?id=420819 >> >> caulier.gilles@gmail.com changed: >> >> What |Removed |Added >> >> ---------------------------------------------------------------------------- >> CC| |caulier.gilles@gmail.com >> >> --- Comment #4 from caulier.gilles@gmail.com --- >> Did you enable Baloo database syc in digiKam setup Metadata page ? >> >> Gilles Caulier >> >> -- >> You are receiving this mail because: >> You reported the bug. > > The problem is clear, your database is on the removable drive. This is not mounted at the start and the database error is there. The database must be on your local drive and must be available at startup. Maik Created attachment 128095 [details] attachment-13078-0.html 8.0 OK Maik I understand what you are saying, and will see if there is a way out of this. The drive in question is an SSD drive physically mounted in one of the drive bays in the PC attached via a SATA cable a .... I have no idea why it would be considered a removable drive. I implemented your other suggestion so now I only need to start via Dolphin when I first boot up ... a minor inconvenience but liveable .... so please feel free to close the bug and thank you for your help. Stay safe Regards Carlo On Sat, May 2, 2020 at 5:44 AM Maik Qualmann <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=420819 > > --- Comment #7 from Maik Qualmann <metzpinguin@gmail.com> --- > The problem is clear, your database is on the removable drive. This is not > mounted at the start and the database error is there. The database must be > on > your local drive and must be available at startup. > > Maik > > -- > You are receiving this mail because: > You reported the bug. Created attachment 128287 [details] attachment-13420-0.html 9.0 Maik ... FYI .... all issues are now resolved ... in order to get the 2nd SSD properly mounted .... I went into System Settings/Removable Devices/ enabled automatic mounting, enabled mounted all removable media, enabled automatically mount on attached.... NOW everything is clean So thanks for you suggestions it forced me to look at things I would not have considered. ---------- Forwarded message --------- From: Carlo Gioia <gioia.carlo@gmail.com> Date: Sat, May 2, 2020 at 10:17 AM Subject: Re: [digikam] [Bug 420819] error while opening database digikam will try to automatically reconnect to the database To: <bug-control@kde.org> 8.0 OK Maik I understand what you are saying, and will see if there is a way out of this. The drive in question is an SSD drive physically mounted in one of the drive bays in the PC attached via a SATA cable a .... I have no idea why it would be considered a removable drive. I implemented your other suggestion so now I only need to start via Dolphin when I first boot up ... a minor inconvenience but liveable .... so please feel free to close the bug and thank you for your help. Stay safe Regards Carlo On Sat, May 2, 2020 at 5:44 AM Maik Qualmann <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=420819 > > --- Comment #7 from Maik Qualmann <metzpinguin@gmail.com> --- > The problem is clear, your database is on the removable drive. This is not > mounted at the start and the database error is there. The database must be > on > your local drive and must be available at startup. > > Maik > > -- > You are receiving this mail because: > You reported the bug. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! |