https://bugs.kde.org/show_bug.cgi?id=365684
--- Comment #19 from [hidden email] --- Olli, Do you seen my previous comment ? Gilles Caulier -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=365684
--- Comment #20 from Olli Lupton <[hidden email]> --- Hi, Sorry for the delay. I also saw strange characters in the collection paths when I migrated by 4.X database to 5.X, and had to re-add the collections to fix this. However, this does not explain the crashes I have seen. I was able to reproduce the crash in a fresh 5.X session (having deleted the .db files and all the configuration files I know about). The fact I am not able to reproduce the crash using a different user account on the same system suggests to me that the problem is either that there is some other old configuration file I don't know about, or digikam is somehow being affected by environment of one of the user accounts (PATH,DYLD_LIBRARY_PATH etc.). -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=365684
--- Comment #21 from [hidden email] --- >or digikam is somehow being affected by environment of one of the user accounts >(PATH,DYLD_LIBRARY_PATH etc.). None of them. digiKam is packaged as a stand alone bundle application. when you said that it do not crash with a new account, do you point the same collection and the same DB files than with suspicious account ? What's about right access to DB file with the problematic account ? User is in the right group with the the right than good ones ? The DB file/dir can be open in RW by problematic account ? What's happen when you create the DB in another place with problematic account ? Gilles Caulier -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=365684
--- Comment #22 from [hidden email] --- Olli, Do you seen my previous comment ? Gilles Caulier -- You are receiving this mail because: You are the assignee for the bug. |
In reply to this post by bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=365684
--- Comment #23 from [hidden email] --- new 5.6.0 pre-release as bundle is available here : https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM Please check if this problem still reproducible with these versions. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are the assignee for the bug. |
In reply to this post by bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=365684
--- Comment #24 from [hidden email] --- digiKam 5.6.0 is now released and available as bundle for Linux, MacOS and Windows. https://www.digikam.org/news/2017-06-21-5.6.0-release-announcement/ Can you check if problem still exists with this version ? Thanks in advance Gilles Caulier -- You are receiving this mail because: You are the assignee for the bug. |
In reply to this post by bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=365684
--- Comment #25 from [hidden email] --- New digiKam 5.7.0 are built with current implementation as pre-release bundles: https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM Problem still reproducible ? -- You are receiving this mail because: You are the assignee for the bug. |
In reply to this post by bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=365684
Olli Lupton <[hidden email]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #26 from Olli Lupton <[hidden email]> --- Apologies for not following up with this. I am now on 3.6.0 and no longer see this bug. Since I could reproduce it I had to rebuild my library from scratch, so it's not clear whether the newer digikam version actually fixed the problem, or if was due to funny state of the database. -- You are receiving this mail because: You are the assignee for the bug. |
In reply to this post by bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=365684
[hidden email] changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Tags |Tags-Manager -- You are receiving this mail because: You are the assignee for the bug. |
Free forum by Nabble | Edit this page |