Re: Digikam stuck/frozen on Apple OS X (Gilles Caulier)

[Michael Levin]

Hi Gilles,

        thank you for the idea! I didn’t think of it (nor did I know it goes in /opt!). Here’s what I see when running it from terminal:

% ./digikam
digikam.widgets: Breeze icons ressource file found
digikam.general: AlbumWatch use QFileSystemWatcher
digikam.general: Database Parameters:
   Type:                     "QSQLITE"
   DB Core Name:             "/Users/mlevin/Pictures/digikam4.db"
   DB Thumbs Name:           "/Users/mlevin/Pictures/thumbnails-digikam.db"
   DB Face Name:             "/Users/mlevin/Pictures/recognition.db"
   Connect Options:          ""
   Host Name:                ""
   Host port:                -1
   Internal Server:          false
   Internal Server Path:     ""
   Internal Server Serv Cmd: ""
   Internal Server Init Cmd: ""
   Username:                 ""
   Password:                 ""

digikam.dbengine: Loading SQL code from config file "/opt/digikam/Applications/KF5/digikam.app/Contents/Resources//digikam/database/dbconfig.xml"
digikam.dbengine: Checking XML version ID => expected:  3  found:  3
digikam.coredb: Core database: running schema update
digikam.coredb: Core database: have a structure version  9
digikam.coredb: Core database: makeUpdates  9  to  9
digikam.database: Creating new Location  "/"  uuid  "volumeid:?path=/Users/mlevin/Pictures"
digikam.database: location for  "/Users/mlevin/Pictures"  is available  true
KMemoryInfo: Platform identified :  "Unknown"
KMemoryInfo: TotalRam:  -1
digikam.general: Allowing a cache size of 60 MB
digikam.thumbsdb: ThumbDB SelectThumbnailSetting val ret =  0
digikam.thumbsdb: ThumbDB SelectThumbnailSetting val ret =  0
digikam.thumbsdb: Thumbs database: have a structure version  "3"
digikam.general: Thumbnails database ready for use
digikam.general: Switch to widget style:  “Fusion"

and then nothing - it just sits there, frozen.  What do you think?

thanks!

Mike

> On Mar 21, 2018, at 4:13 AM, [hidden email] wrote:
>
> Send Digikam-users mailing list submissions to
> [hidden email]
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://mail.kde.org/mailman/listinfo/digikam-users
> or, via email, send a message with subject or body 'help' to
> [hidden email]
>
> You can reach the person managing the list at
> [hidden email]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Digikam-users digest..."
>
>
> Today's Topics:
>
>   1. Re:  Digikam on Apple OS X? (Gilles Caulier)
>   2. Re:  Importing xmp data from Lightroom 4.4 to Digikam 5.5.0
>      (Gilles Caulier)
>   3. Re:  Importing xmp data from Lightroom 4.4 to Digikam 5.5.0
>      (Gilles Caulier)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 21 Mar 2018 08:35:13 +0100
> From: Gilles Caulier <[hidden email]>
> To: digiKam - Home Manage your photographs as a professional with the
> power of open source <[hidden email]>
> Subject: Re: [digiKam-users] Digikam on Apple OS X?
> Message-ID:
> <[hidden email]>
> Content-Type: text/plain; charset="utf-8"
>
> Hi,
>
> I remember a report like this few week ago.
>
> I think there is a problem with PKG build environment which need to be
> updated (Qt 5.8.0 currently), or at least recompiled from scratch with same
> components version (through Macport), to include compatibility with recent
> MacOs.
>
> The problem come from Macports which break the compilation quickly due to
> packages which need to be updated in compilation rules. Macports is really
> a big puzzle.
>
> As i don't yet installed MacOS 10.13.x for security reasons (i'm wait that
> Apple published a real stable release), i cannot check the problem on my
> Macbook pro.
>
> To investigate, can you go to
> /opt/digikam/Applications/KF5/digikam.app/Contents/MacOS/
> and run digiKam from a console.
>
> Report here all debug trace printed while startup.
>
> Thanks in advance
>
> Gilles Caulier
>
> 2018-03-20 17:55 GMT+01:00 Michael Levin <[hidden email]>:
>
>> Anyone using it on OS X 10.13?  Mine freezes on startup - never even see a
>> window.
>>
>>
>>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20180321/af8fe537/attachment-0001.html>
>
> ------------------------------
>
> Message: 2
> Date: Wed, 21 Mar 2018 08:44:05 +0100
> From: Gilles Caulier <[hidden email]>
> To: digiKam - Home Manage your photographs as a professional with the
> power of open source <[hidden email]>
> Subject: Re: [digiKam-users] Importing xmp data from Lightroom 4.4 to
> Digikam 5.5.0
> Message-ID:
> <[hidden email]>
> Content-Type: text/plain; charset="utf-8"
>
> Hi,
>
> I just tested your test photos, and i think i found the reason why the LR
> metadata are not backported to DK :
>
> digikam.metaengine: Exiv2 ( 3 ) :  XMP Toolkit error 101: Schema namespace
> URI and prefix mismatch
> digikam.metaengine: Exiv2 ( 2 ) :  Failed to decode XMP metadata.
>
> These lines are written on the console by Exiv2 library when files are
> parsed to be registered in database.
>
> An XMP namespace is badly defined in Exiv2 (the URI use to identify the
> namespace). Probably Adobe change the URI as well (which can be a mess).
> I'm not yet sure. I continue to search.
>
> Gilles Caulier
>
> 2018-03-17 22:48 GMT+01:00 jonjt <[hidden email]>:
>
>> Hello Everyone,
>> Thanks for the replies.
>>
>> You will find an example image here:
>> https://drive.google.com/open?id=1GaokEvrZ3MEkIco_WmGHUXORZ4p30sQc
>> This example is a little complicated so, forgive me if my explanation is a
>> bit confusing.
>>
>> This tar.gz file has a few files in it.  First, you will find the .cr2
>> file.
>> Of course, that is the original file I shot with my 7D.  Next, there is
>> "IMG_7109-Edit-2.tif".  This file was the file that I performed noise
>> reduction on with Topaz Denoise.  It's also one of three total .tiff files
>> that I've had in my Lightroom library for some time.  The other two .tif
>> files I created for post processing experimentation.  However, I have not
>> tried editing those files in some time.  As such, I decided not to upload
>> those two files.  However, I thought it prudent to mention these additional
>> files, because I do believe the changes made to those additional files are
>> tracked in the .xmp file that is shown here.
>> Additionally, I've included two other files.  The first file in that last
>> is
>> "IMG_7109-Edit-2 DNG-TEST3.dng".  That was a .dng that I recently exported,
>> to see how previews and edits .dngs.  Previewing this .dng shows the edits,
>> even after I've selected the "Preview shows the full image" option in the
>> configuration widget.  However, when I open this image in the image editor,
>> the changes shown in preview disappear.
>> Finally, "IMG_7109-Edit-2 TIFF-Test.tif" is also included.  The previewed
>> image and that shown in the image editor are both the same; both images
>> show
>> the postprocessing changes I've made in Lightroom 4.4.  Of course, this is
>> different from the other files located in the linked tar.gz file above.
>>
>> I'm guessing that the process for importing changes made in Lightroom 4.4
>> would require me to create a second, .tif, copy of all files edited in
>> lightroom.  Doing so would allow me to preserve the post processing I've
>> done while also saving the .cr2 that has the unmodified raw data.  I wanted
>> to run this by you just to see if there is a better way to migrate.  While
>> I
>> do have enough storage space to keep multiple lossless copies of these
>> original images, I'd prefer to be a bit more efficient with the space that
>> I
>> use.
>>
>> Thanks for the help and please let me know if I should provide anything
>> else
>> (including another example).
>>
>>
>>
>> --
>> Sent from: http://digikam.1695700.n4.nabble.com/digikam-users-
>> f1735189.html
>>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20180321/da079d7f/attachment-0001.html>
>
> ------------------------------
>
> Message: 3
> Date: Wed, 21 Mar 2018 09:12:34 +0100
> From: Gilles Caulier <[hidden email]>
> To: digiKam - Home Manage your photographs as a professional with the
> power of open source <[hidden email]>
> Subject: Re: [digiKam-users] Importing xmp data from Lightroom 4.4 to
> Digikam 5.5.0
> Message-ID:
> <[hidden email]>
> Content-Type: text/plain; charset="utf-8"
>
> Ok, i found.
>
> The problem do not come Exiv2, even if this URI problem need to be fixed
> (Please report the URI problem in Exiv2 project with your test image link).
>
> For digiKam the problem is know and we must fix it for next 6.0.0 release.
>
> https://www.flickr.com/photos/digikam/40934505211/in/dateposted/
>
> Look well my screenshot : i renamed the sidecar from IMG_7109.xmp
> to IMG_7109.CR2.xmp.
>
> And now the metadata import to database work as expected (look tags list
> set in CR2 files). The problem have been already report in bugzilla :
>
> https://bugs.kde.org/show_bug.cgi?id=278935
>
> Best
>
> Gilles Caulier
>
> 2018-03-21 8:44 GMT+01:00 Gilles Caulier <[hidden email]>:
>
>> Hi,
>>
>> I just tested your test photos, and i think i found the reason why the LR
>> metadata are not backported to DK :
>>
>> digikam.metaengine: Exiv2 ( 3 ) :  XMP Toolkit error 101: Schema namespace
>> URI and prefix mismatch
>> digikam.metaengine: Exiv2 ( 2 ) :  Failed to decode XMP metadata.
>>
>> These lines are written on the console by Exiv2 library when files are
>> parsed to be registered in database.
>>
>> An XMP namespace is badly defined in Exiv2 (the URI use to identify the
>> namespace). Probably Adobe change the URI as well (which can be a mess).
>> I'm not yet sure. I continue to search.
>>
>> Gilles Caulier
>>
>> 2018-03-17 22:48 GMT+01:00 jonjt <[hidden email]>:
>>
>>> Hello Everyone,
>>> Thanks for the replies.
>>>
>>> You will find an example image here:
>>> https://drive.google.com/open?id=1GaokEvrZ3MEkIco_WmGHUXORZ4p30sQc
>>> This example is a little complicated so, forgive me if my explanation is a
>>> bit confusing.
>>>
>>> This tar.gz file has a few files in it.  First, you will find the .cr2
>>> file.
>>> Of course, that is the original file I shot with my 7D.  Next, there is
>>> "IMG_7109-Edit-2.tif".  This file was the file that I performed noise
>>> reduction on with Topaz Denoise.  It's also one of three total .tiff files
>>> that I've had in my Lightroom library for some time.  The other two .tif
>>> files I created for post processing experimentation.  However, I have not
>>> tried editing those files in some time.  As such, I decided not to upload
>>> those two files.  However, I thought it prudent to mention these
>>> additional
>>> files, because I do believe the changes made to those additional files are
>>> tracked in the .xmp file that is shown here.
>>> Additionally, I've included two other files.  The first file in that last
>>> is
>>> "IMG_7109-Edit-2 DNG-TEST3.dng".  That was a .dng that I recently
>>> exported,
>>> to see how previews and edits .dngs.  Previewing this .dng shows the
>>> edits,
>>> even after I've selected the "Preview shows the full image" option in the
>>> configuration widget.  However, when I open this image in the image
>>> editor,
>>> the changes shown in preview disappear.
>>> Finally, "IMG_7109-Edit-2 TIFF-Test.tif" is also included.  The previewed
>>> image and that shown in the image editor are both the same; both images
>>> show
>>> the postprocessing changes I've made in Lightroom 4.4.  Of course, this is
>>> different from the other files located in the linked tar.gz file above.
>>>
>>> I'm guessing that the process for importing changes made in Lightroom 4.4
>>> would require me to create a second, .tif, copy of all files edited in
>>> lightroom.  Doing so would allow me to preserve the post processing I've
>>> done while also saving the .cr2 that has the unmodified raw data.  I
>>> wanted
>>> to run this by you just to see if there is a better way to migrate.
>>> While I
>>> do have enough storage space to keep multiple lossless copies of these
>>> original images, I'd prefer to be a bit more efficient with the space
>>> that I
>>> use.
>>>
>>> Thanks for the help and please let me know if I should provide anything
>>> else
>>> (including another example).
>>>
>>>
>>>
>>> --
>>> Sent from: http://digikam.1695700.n4.nabble.com/digikam-users-f1735189.
>>> html
>>>
>>
>>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20180321/a22fc39a/attachment.html>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users
>
>
> ------------------------------
>
> End of Digikam-users Digest, Vol 154, Issue 62
> **********************************************

[Gilles Caulier-4]

There is no special info to investigate. Please report this trace in a new bugzilla entry for future hack to plan

Gilles caulier

--