Digikam crashes under MacOS when built using git + MacPorts

[Phil Stanford]

Hi.
I've previously used Digikam on MacOS (10.6.8), built using MacPorts for both Digikam and all the dependencies.
The MacPorts Digikam version hasn't been updated for some time (still on 2.1.1_1)  and I spotted the instructions for installing using git: 

https://projects.kde.org/projects/extragear/graphics/digikam/repository/revisions/master/entry/README.MACOSX

I was hoping to install the current stable 2.5.0  version of Digikam.

Before starting the process in the instructions above, I made sure that all the MacPorts already installed were up to date, and that I could install and run the current MacPorts version of DIgikam (2.1.1_1).  The only exception was that I activated boost-1.47 rather than 1.48 as I'd read that there had been some recent issues and although I'd read that these had been fixed I wasn't quite sure what Digikam build I would be picking up.

Once I'd proved that everything worked with the updated MacPorts dependencies, I uninstalled digikam by doing 'port uninstall digikam'.

I then followed the instructions in the link above, and everything seemed to work and I had no obvious errors during the build or install.

I started the process above by using the suggested command 'git clone git://anongit.kde.org/digikam-software-compilation' , copying to a new directory I'd made.

After the install, I ran the launchctl DBUS commands and rebooted the Mac (this had been necessary before when using the MacPorts version).

Here, I have to confess my ignorance; I've not used 'git' before, and I was actually expecting the above 'git clone' command to fetch me the latest 'production' version,  however when I start Digikam (from  a terminal) the splash screen shows  2.6.0 not 2.5 so I guess I'm getting the development version.

I can't really tell much more than that since I never get the main window appearing as Digikam crashes.   I will reproduce the terminal output below.

I also tried 'Showfoto' - and that starts up and runs with no problems.  The splash screen for that also says 2.6.0, and the 'About' box gives the version as   6715b8ee6e5ee44bef186a1f0e39bf46a50f5681 with build date today and 'target: debugfull'.

The fact that Showfoto runs OK suggests that probably this is an issue with Digikam + MacPorts, although as mentioned I've not used 'git' before so anything is possible .....

I would be grateful to get some information -

1) Looking at the console log shown below, is there an obvious cause - (the 'too many open files' error seems similar to https://bugs.kde.org/show_bug.cgi?id=289330 but in my instance  DIgikam never starts correctly at all)

2) I don't really wish to be 'bleeding edge',   what should I have done to clone and build Digikam 2.5.0 not the development version

3) How can I clean things up from this build, and either get to the stable 2.5.0 version - or at the very least update to the latest development version - a bit of reading suggests that 'git pull' may do this?

Ideally I would prefer to be able to install the latest released version of Digikam just by using MacPorts as I have other software installed using that package manager  - however unfortunately Digikam rarely gets updated on MacPorts so getting a working version with git too would be good.

Thanks in advance for any pointers - I appreciate I'm rather ignorant of 'git' and how it works at the moment.
Phil

The log from running 'Digikam' follows -
========

$ /Applications/MacPorts/KDE4/digikam.app/Contents/MacOS/digikam &
[1] 680
$ digikam(680)/KSharedDataCache ensureFileAllocated: This system misses support for posix_fallocate() -- ensure this partition has room for at least 10547296 bytes.
digikam(680)/KSharedDataCache: Creating shell of a lock!
digikam(680)/KSharedDataCache: Unable to setup shared cache lock, although it worked when created.
digikam(680)/KSharedDataCache: Unable to unmap shared memory segment 0x11e600000
digikam(680)/digikam (core) Digikam::AlbumWatch::connectToKDirWatch: KDirWatch method =  "FAM"
digikam(680)/digikam (core) Digikam::AlbumManager::setDatabase: DatabaseParameters: [ Type "QSQLITE", Name "/Users/pns/Pictures/digikam4.db" (Thumbnails Name "/Users/pns/Pictures/thumbnails-digikam.db"); ]
QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in use, all queries will cease to work.
digikam(680)/digikam (core) Digikam::DatabaseConfigElementLoader::readConfig: Loading SQL code from config file "/opt/local/share/apps/digikam/database/dbconfig.xml"
digikam(680)/digikam (core) Digikam::DatabaseConfigElementLoader::readConfig: false "1" 1 1
digikam(680)/digikam (core) Digikam::SchemaUpdater::update: SchemaUpdater update
digikam(680)/digikam (core) Digikam::SchemaUpdater::startUpdates: Have a database structure version  6
digikam(680)/digikam (core) Digikam::SchemaUpdater::makeUpdates: makeUpdates  6  to  6
digikam(680)/digikam (core) Digikam::AlbumRootLocation::AlbumRootLocation: Creating new Location  "/"  uuid  "volumeid:?path=%2FUsers%2Fpns%2FPictures"
digikam(680)/digikam (core) Digikam::CollectionManager::updateLocations: location for  "/Users/pns/Pictures"  is available  true
digikam(680)/digikam (core) Digikam::LoadingCache::setCacheSize: Allowing a cache size of 60 MB
digikam(680)/digikam (core) Digikam::ThumbnailSchemaUpdater::startUpdates: Have a thumbnail database structure version  "2"
digikam(680)/digikam (core) Digikam::ThumbnailLoadThread::initializeThumbnailDatabase: Thumbnail db ready for use
digikam(680)/digikam (core) Digikam::AlbumManager::checkNepomukService: Nepomuk server is not reachable. Cannot start Digikam Nepomuk Service
digikam(680)/digikam (core) Digikam::CollectionScanner::completeScan: Complete scan (file scanning deferred) took: 361 msecs.
digikam(680)/digikam (core) Digikam::IccSettings::IccSettingsPriv::scanDirectories: ()
digikam(680)/KSharedDataCache ensureFileAllocated: This system misses support for posix_fallocate() -- ensure this partition has room for at least 10547296 bytes.
digikam(680)/KSharedDataCache: Creating shell of a lock!
digikam(680)/KSharedDataCache: Unable to setup shared cache lock, although it worked when created.
digikam(680)/KSharedDataCache: Unable to unmap shared memory segment 0x1223fb000
digikam(680)/KGEOMAP KGeoMap::KGeoMapWidget::setBackend: "setting backend marble"
digikam(680)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed:  "The name org.kde.kded was not provided by any .service files"

digikam(680)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
digikam(680)/KGEOMAP KGeoMap::KGeoMapWidget::setBackend: "setting backend marble"
digikam(680)/digikam (core) Digikam::AlbumFilterModel::setSearchTextSettings: new search text settings:  "" : hasResult =  false , validRows =  0
digikam(680)/digikam (core) Digikam::ThemeManager::slotChangePalette: ""
digikam(680)/digikam (core) Digikam::ThemeManager::slotChangePalette: ""
digikam(680)/digikam (core) Digikam::ThemeManager::slotChangePalette: ""
digikam(680)/digikam (core) Digikam::ThemeManager::slotChangePalette: ""
digikam(680)/KGEOMAP KGeoMap::ItemMarkerTiler::slotSourceModelReset: ----
digikam(680)/KGEOMAP KGeoMap::ItemMarkerTiler::slotSourceModelReset: ----
QKqueueFileSystemWatcherEngine::addPaths: open: Too many open files
QFileSystemWatcher: failed to add paths: /Users/pns/Pictures/PictureProject/0029/DSC_2659.JPG
QKqueueFileSystemWatcherEngine::addPaths: open: Too many open files
QFileSystemWatcher: failed to add paths: /Users/pns/Pictures/PictureProject/0029/DSC_2660.JPG
QKqueueFileSystemWatcherEngine::addPaths: open: Too many open files
QFileSystemWatcher: failed to add paths: /Users/pns/Pictures/PictureProject/0029/DSC_2661.JPG
QKqueueFileSystemWatcherEngine::addPaths: open: Too many open files

(lots of similar lines for other image folders under my ID have been deleted)

digikam(680)/digikam (core) Digikam::SearchTabHeader::selectedSearchChanged: changing to SAlbum  0x0
digikam(680)/digikam (core) Digikam::SearchTabHeader::selectedSearchChanged: changing to SAlbum  0x122da1230
digikam(680)/digikam (core) Digikam::FuzzySearchView::slotAlbumSelected: Selected new album 0x0
digikam(680)/digikam (core) Digikam::FuzzySearchView::slotAlbumSelected: Not a haar search, returning
digikam(680)/digikam (core) Digikam::FuzzySearchView::slotAlbumSelected: Selected new album 0x122db72c0
QEventDispatcherUNIXPrivate(): Unable to create thread pipe: Too many open files
QEventDispatcherUNIXPrivate(): Can not continue without a thread pipe
QKqueueFileSystemWatcherEngine: error during kevent wait: Bad file descriptor
KCrash: Application 'digikam' crashing...
KCrash: Attempting to start /opt/local/lib/kde4/libexec/drkonqi.app/Contents/MacOS/drkonqi from kdeinit
Warning: Path of socketfile exceeds UNIX_PATH_MAX.
KCrash: Attempting to start /opt/local/lib/kde4/libexec/drkonqi.app/Contents/MacOS/drkonqi directly
drkonqi(683)/KSharedDataCache ensureFileAllocated: This system misses support for posix_fallocate() -- ensure this partition has room for at least 10547296 bytes.
drkonqi(683)/KSharedDataCache: Creating shell of a lock!
drkonqi(683)/KSharedDataCache: Unable to setup shared cache lock, although it worked when created.
drkonqi(683)/KSharedDataCache: Unable to unmap shared memory segment 0x118d2d000

[1]+  Abort trap              /Applications/MacPorts/KDE4/digikam.app/Contents/MacOS/digikam



_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Gilles Caulier-4]

Can you run digiKam under gdb, and get a backtrace of crash to investiguate ?

Gilles Caulier

2012/1/8 Phil Stanford <[hidden email]>:

> Hi.
> I've previously used Digikam on MacOS (10.6.8), built using MacPorts for
> both Digikam and all the dependencies.
> The MacPorts Digikam version hasn't been updated for some time (still on
> 2.1.1_1)  and I spotted the instructions for installing using git:
>
> https://projects.kde.org/projects/extragear/graphics/digikam/repository/revisions/master/entry/README.MACOSX
>
> I was hoping to install the current stable 2.5.0  version of Digikam.
>
> Before starting the process in the instructions above, I made sure that all
> the MacPorts already installed were up to date, and that I could install and
> run the current MacPorts version of DIgikam (2.1.1_1).  The only exception
> was that I activated boost-1.47 rather than 1.48 as I'd read that there had
> been some recent issues and although I'd read that these had been fixed I
> wasn't quite sure what Digikam build I would be picking up.
>
> Once I'd proved that everything worked with the updated MacPorts
> dependencies, I uninstalled digikam by doing 'port uninstall digikam'.
>
> I then followed the instructions in the link above, and everything seemed to
> work and I had no obvious errors during the build or install.
>
> I started the process above by using the suggested command 'git clone
> git://anongit.kde.org/digikam-software-compilation' , copying to a new
> directory I'd made.
>
> After the install, I ran the launchctl DBUS commands and rebooted the Mac
> (this had been necessary before when using the MacPorts version).
>
> Here, I have to confess my ignorance; I've not used 'git' before, and I was
> actually expecting the above 'git clone' command to fetch me the latest
> 'production' version,  however when I start Digikam (from  a terminal) the
> splash screen shows  2.6.0 not 2.5 so I guess I'm getting the development
> version.
>
> I can't really tell much more than that since I never get the main window
> appearing as Digikam crashes.   I will reproduce the terminal output below.
>
> I also tried 'Showfoto' - and that starts up and runs with no problems.  The
> splash screen for that also says 2.6.0, and the 'About' box gives the
> version as   6715b8ee6e5ee44bef186a1f0e39bf46a50f5681 with build date today
> and 'target: debugfull'.
>
> The fact that Showfoto runs OK suggests that probably this is an issue with
> Digikam + MacPorts, although as mentioned I've not used 'git' before so
> anything is possible .....
>
> I would be grateful to get some information -
>
> 1) Looking at the console log shown below, is there an obvious cause - (the
> 'too many open files' error seems similar to
> https://bugs.kde.org/show_bug.cgi?id=289330 but in my instance  DIgikam
> never starts correctly at all)
>
> 2) I don't really wish to be 'bleeding edge',   what should I have done to
> clone and build Digikam 2.5.0 not the development version
>
> 3) How can I clean things up from this build, and either get to the stable
> 2.5.0 version - or at the very least update to the latest development
> version - a bit of reading suggests that 'git pull' may do this?
>
> Ideally I would prefer to be able to install the latest released version of
> Digikam just by using MacPorts as I have other software installed using that
> package manager  - however unfortunately Digikam rarely gets updated on
> MacPorts so getting a working version with git too would be good.
>
> Thanks in advance for any pointers - I appreciate I'm rather ignorant of
> 'git' and how it works at the moment.
> Phil
>
> The log from running 'Digikam' follows -
> ========
>
> $ /Applications/MacPorts/KDE4/digikam.app/Contents/MacOS/digikam &
> [1] 680
> $ digikam(680)/KSharedDataCache ensureFileAllocated: This system misses
> support for posix_fallocate() -- ensure this partition has room for at least
> 10547296 bytes.
> digikam(680)/KSharedDataCache: Creating shell of a lock!
> digikam(680)/KSharedDataCache: Unable to setup shared cache lock, although
> it worked when created.
> digikam(680)/KSharedDataCache: Unable to unmap shared memory segment
> 0x11e600000
> digikam(680)/digikam (core) Digikam::AlbumWatch::connectToKDirWatch:
> KDirWatch method =  "FAM"
> digikam(680)/digikam (core) Digikam::AlbumManager::setDatabase:
> DatabaseParameters: [ Type "QSQLITE", Name "/Users/pns/Pictures/digikam4.db"
> (Thumbnails Name "/Users/pns/Pictures/thumbnails-digikam.db"); ]
> QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in
> use, all queries will cease to work.
> digikam(680)/digikam (core)
> Digikam::DatabaseConfigElementLoader::readConfig: Loading SQL code from
> config file "/opt/local/share/apps/digikam/database/dbconfig.xml"
> digikam(680)/digikam (core)
> Digikam::DatabaseConfigElementLoader::readConfig: false "1" 1 1
> digikam(680)/digikam (core) Digikam::SchemaUpdater::update: SchemaUpdater
> update
> digikam(680)/digikam (core) Digikam::SchemaUpdater::startUpdates: Have a
> database structure version  6
> digikam(680)/digikam (core) Digikam::SchemaUpdater::makeUpdates:
> makeUpdates  6  to  6
> digikam(680)/digikam (core) Digikam::AlbumRootLocation::AlbumRootLocation:
> Creating new Location  "/"  uuid  "volumeid:?path=%2FUsers%2Fpns%2FPictures"
> digikam(680)/digikam (core) Digikam::CollectionManager::updateLocations:
> location for  "/Users/pns/Pictures"  is available  true
> digikam(680)/digikam (core) Digikam::LoadingCache::setCacheSize: Allowing a
> cache size of 60 MB
> digikam(680)/digikam (core) Digikam::ThumbnailSchemaUpdater::startUpdates:
> Have a thumbnail database structure version  "2"
> digikam(680)/digikam (core)
> Digikam::ThumbnailLoadThread::initializeThumbnailDatabase: Thumbnail db
> ready for use
> digikam(680)/digikam (core) Digikam::AlbumManager::checkNepomukService:
> Nepomuk server is not reachable. Cannot start Digikam Nepomuk Service
> digikam(680)/digikam (core) Digikam::CollectionScanner::completeScan:
> Complete scan (file scanning deferred) took: 361 msecs.
> digikam(680)/digikam (core)
> Digikam::IccSettings::IccSettingsPriv::scanDirectories: ()
> digikam(680)/KSharedDataCache ensureFileAllocated: This system misses
> support for posix_fallocate() -- ensure this partition has room for at least
> 10547296 bytes.
> digikam(680)/KSharedDataCache: Creating shell of a lock!
> digikam(680)/KSharedDataCache: Unable to setup shared cache lock, although
> it worked when created.
> digikam(680)/KSharedDataCache: Unable to unmap shared memory segment
> 0x1223fb000
> digikam(680)/KGEOMAP KGeoMap::KGeoMapWidget::setBackend: "setting backend
> marble"
> digikam(680)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned
> initialize() D-Bus call failed:  "The name org.kde.kded was not provided by
> any .service files"
>
> digikam(680)/kdecore (K*TimeZone*): No time zone information obtained from
> ktimezoned
> digikam(680)/KGEOMAP KGeoMap::KGeoMapWidget::setBackend: "setting backend
> marble"
> digikam(680)/digikam (core)
> Digikam::AlbumFilterModel::setSearchTextSettings: new search text settings:
> "" : hasResult =  false , validRows =  0
> digikam(680)/digikam (core) Digikam::ThemeManager::slotChangePalette: ""
> digikam(680)/digikam (core) Digikam::ThemeManager::slotChangePalette: ""
> digikam(680)/digikam (core) Digikam::ThemeManager::slotChangePalette: ""
> digikam(680)/digikam (core) Digikam::ThemeManager::slotChangePalette: ""
> digikam(680)/KGEOMAP KGeoMap::ItemMarkerTiler::slotSourceModelReset: ----
> digikam(680)/KGEOMAP KGeoMap::ItemMarkerTiler::slotSourceModelReset: ----
> QKqueueFileSystemWatcherEngine::addPaths: open: Too many open files
> QFileSystemWatcher: failed to add paths:
> /Users/pns/Pictures/PictureProject/0029/DSC_2659.JPG
> QKqueueFileSystemWatcherEngine::addPaths: open: Too many open files
> QFileSystemWatcher: failed to add paths:
> /Users/pns/Pictures/PictureProject/0029/DSC_2660.JPG
> QKqueueFileSystemWatcherEngine::addPaths: open: Too many open files
> QFileSystemWatcher: failed to add paths:
> /Users/pns/Pictures/PictureProject/0029/DSC_2661.JPG
> QKqueueFileSystemWatcherEngine::addPaths: open: Too many open files
>
> (lots of similar lines for other image folders under my ID have been
> deleted)
>
> digikam(680)/digikam (core) Digikam::SearchTabHeader::selectedSearchChanged:
> changing to SAlbum  0x0
> digikam(680)/digikam (core) Digikam::SearchTabHeader::selectedSearchChanged:
> changing to SAlbum  0x122da1230
> digikam(680)/digikam (core) Digikam::FuzzySearchView::slotAlbumSelected:
> Selected new album 0x0
> digikam(680)/digikam (core) Digikam::FuzzySearchView::slotAlbumSelected: Not
> a haar search, returning
> digikam(680)/digikam (core) Digikam::FuzzySearchView::slotAlbumSelected:
> Selected new album 0x122db72c0
> QEventDispatcherUNIXPrivate(): Unable to create thread pipe: Too many open
> files
> QEventDispatcherUNIXPrivate(): Can not continue without a thread pipe
> QKqueueFileSystemWatcherEngine: error during kevent wait: Bad file
> descriptor
> KCrash: Application 'digikam' crashing...
> KCrash: Attempting to start
> /opt/local/lib/kde4/libexec/drkonqi.app/Contents/MacOS/drkonqi from kdeinit
> Warning: Path of socketfile exceeds UNIX_PATH_MAX.
> KCrash: Attempting to start
> /opt/local/lib/kde4/libexec/drkonqi.app/Contents/MacOS/drkonqi directly
> drkonqi(683)/KSharedDataCache ensureFileAllocated: This system misses
> support for posix_fallocate() -- ensure this partition has room for at least
> 10547296 bytes.
> drkonqi(683)/KSharedDataCache: Creating shell of a lock!
> drkonqi(683)/KSharedDataCache: Unable to setup shared cache lock, although
> it worked when created.
> drkonqi(683)/KSharedDataCache: Unable to unmap shared memory segment
> 0x118d2d000
>
> [1]+  Abort trap
> /Applications/MacPorts/KDE4/digikam.app/Contents/MacOS/digikam
>
>
>
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users
>

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Phil Stanford]

Hi Gilles -
I've attached all the output from gdb.
It's not finding the .o files for a lot of the routines though, I don't know if that matters much - this is the native MacOS gdb,  and not the MacPorts version of gdb - again I'm not sure if that is significant.

I didn't notice the Digikam splash screen come up when running under gdb so whether or not it got as far as just invoking the program from the shell, I don't know.


Many thanks .....
Phil

On 8 January 2012 19:19, Gilles Caulier <[hidden email]> wrote:

Can you run digiKam under gdb, and get a backtrace of crash to investiguate ?

Gilles Caulier

2012/1/8 Phil Stanford <[hidden email]>:

> Hi.
> I've previously used Digikam on MacOS (10.6.8), built using MacPorts for
> both Digikam and all the dependencies.
> The MacPorts Digikam version hasn't been updated for some time (still on
> 2.1.1_1)  and I spotted the instructions for installing using git:
>
> https://projects.kde.org/projects/extragear/graphics/digikam/repository/revisions/master/entry/README.MACOSX
>
> I was hoping to install the current stable 2.5.0  version of Digikam.
>
> Before starting the process in the instructions above, I made sure that all
> the MacPorts already installed were up to date, and that I could install and
> run the current MacPorts version of DIgikam (2.1.1_1).  The only exception
> was that I activated boost-1.47 rather than 1.48 as I'd read that there had
> been some recent issues and although I'd read that these had been fixed I
> wasn't quite sure what Digikam build I would be picking up.
>
> Once I'd proved that everything worked with the updated MacPorts
> dependencies, I uninstalled digikam by doing 'port uninstall digikam'.
>
> I then followed the instructions in the link above, and everything seemed to
> work and I had no obvious errors during the build or install.
>
> I started the process above by using the suggested command 'git clone
> git://anongit.kde.org/digikam-software-compilation' , copying to a new
> directory I'd made.
>
> After the install, I ran the launchctl DBUS commands and rebooted the Mac
> (this had been necessary before when using the MacPorts version).
>
> Here, I have to confess my ignorance; I've not used 'git' before, and I was
> actually expecting the above 'git clone' command to fetch me the latest
> 'production' version,  however when I start Digikam (from  a terminal) the
> splash screen shows  2.6.0 not 2.5 so I guess I'm getting the development
> version.
>
> I can't really tell much more than that since I never get the main window
> appearing as Digikam crashes.   I will reproduce the terminal output below.
>
> I also tried 'Showfoto' - and that starts up and runs with no problems.  The
> splash screen for that also says 2.6.0, and the 'About' box gives the
> version as   6715b8ee6e5ee44bef186a1f0e39bf46a50f5681 with build date today
> and 'target: debugfull'.
>
> The fact that Showfoto runs OK suggests that probably this is an issue with
> Digikam + MacPorts, although as mentioned I've not used 'git' before so
> anything is possible .....
>
> I would be grateful to get some information -
>
> 1) Looking at the console log shown below, is there an obvious cause - (the
> 'too many open files' error seems similar to
> https://bugs.kde.org/show_bug.cgi?id=289330 but in my instance  DIgikam
> never starts correctly at all)
>
> 2) I don't really wish to be 'bleeding edge',   what should I have done to
> clone and build Digikam 2.5.0 not the development version
>
> 3) How can I clean things up from this build, and either get to the stable
> 2.5.0 version - or at the very least update to the latest development
> version - a bit of reading suggests that 'git pull' may do this?
>
> Ideally I would prefer to be able to install the latest released version of
> Digikam just by using MacPorts as I have other software installed using that
> package manager  - however unfortunately Digikam rarely gets updated on
> MacPorts so getting a working version with git too would be good.
>
> Thanks in advance for any pointers - I appreciate I'm rather ignorant of
> 'git' and how it works at the moment.
> Phil
>
> The log from running 'Digikam' follows -
> ========
>
> $ /Applications/MacPorts/KDE4/digikam.app/Contents/MacOS/digikam &
> [1] 680
> $ digikam(680)/KSharedDataCache ensureFileAllocated: This system misses
> support for posix_fallocate() -- ensure this partition has room for at least
> 10547296 bytes.
> digikam(680)/KSharedDataCache: Creating shell of a lock!
> digikam(680)/KSharedDataCache: Unable to setup shared cache lock, although
> it worked when created.
> digikam(680)/KSharedDataCache: Unable to unmap shared memory segment
> 0x11e600000
> digikam(680)/digikam (core) Digikam::AlbumWatch::connectToKDirWatch:
> KDirWatch method =  "FAM"
> digikam(680)/digikam (core) Digikam::AlbumManager::setDatabase:
> DatabaseParameters: [ Type "QSQLITE", Name "/Users/pns/Pictures/digikam4.db"
> (Thumbnails Name "/Users/pns/Pictures/thumbnails-digikam.db"); ]
> QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in
> use, all queries will cease to work.
> digikam(680)/digikam (core)
> Digikam::DatabaseConfigElementLoader::readConfig: Loading SQL code from
> config file "/opt/local/share/apps/digikam/database/dbconfig.xml"
> digikam(680)/digikam (core)
> Digikam::DatabaseConfigElementLoader::readConfig: false "1" 1 1
> digikam(680)/digikam (core) Digikam::SchemaUpdater::update: SchemaUpdater
> update
> digikam(680)/digikam (core) Digikam::SchemaUpdater::startUpdates: Have a
> database structure version  6
> digikam(680)/digikam (core) Digikam::SchemaUpdater::makeUpdates:
> makeUpdates  6  to  6
> digikam(680)/digikam (core) Digikam::AlbumRootLocation::AlbumRootLocation:
> Creating new Location  "/"  uuid  "volumeid:?path=%2FUsers%2Fpns%2FPictures"
> digikam(680)/digikam (core) Digikam::CollectionManager::updateLocations:
> location for  "/Users/pns/Pictures"  is available  true
> digikam(680)/digikam (core) Digikam::LoadingCache::setCacheSize: Allowing a
> cache size of 60 MB
> digikam(680)/digikam (core) Digikam::ThumbnailSchemaUpdater::startUpdates:
> Have a thumbnail database structure version  "2"
> digikam(680)/digikam (core)
> Digikam::ThumbnailLoadThread::initializeThumbnailDatabase: Thumbnail db
> ready for use
> digikam(680)/digikam (core) Digikam::AlbumManager::checkNepomukService:
> Nepomuk server is not reachable. Cannot start Digikam Nepomuk Service
> digikam(680)/digikam (core) Digikam::CollectionScanner::completeScan:
> Complete scan (file scanning deferred) took: 361 msecs.
> digikam(680)/digikam (core)
> Digikam::IccSettings::IccSettingsPriv::scanDirectories: ()
> digikam(680)/KSharedDataCache ensureFileAllocated: This system misses
> support for posix_fallocate() -- ensure this partition has room for at least
> 10547296 bytes.
> digikam(680)/KSharedDataCache: Creating shell of a lock!
> digikam(680)/KSharedDataCache: Unable to setup shared cache lock, although
> it worked when created.
> digikam(680)/KSharedDataCache: Unable to unmap shared memory segment
> 0x1223fb000
> digikam(680)/KGEOMAP KGeoMap::KGeoMapWidget::setBackend: "setting backend
> marble"
> digikam(680)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned
> initialize() D-Bus call failed:  "The name org.kde.kded was not provided by
> any .service files"
>
> digikam(680)/kdecore (K*TimeZone*): No time zone information obtained from
> ktimezoned
> digikam(680)/KGEOMAP KGeoMap::KGeoMapWidget::setBackend: "setting backend
> marble"
> digikam(680)/digikam (core)
> Digikam::AlbumFilterModel::setSearchTextSettings: new search text settings:
> "" : hasResult =  false , validRows =  0
> digikam(680)/digikam (core) Digikam::ThemeManager::slotChangePalette: ""
> digikam(680)/digikam (core) Digikam::ThemeManager::slotChangePalette: ""
> digikam(680)/digikam (core) Digikam::ThemeManager::slotChangePalette: ""
> digikam(680)/digikam (core) Digikam::ThemeManager::slotChangePalette: ""
> digikam(680)/KGEOMAP KGeoMap::ItemMarkerTiler::slotSourceModelReset: ----
> digikam(680)/KGEOMAP KGeoMap::ItemMarkerTiler::slotSourceModelReset: ----
> QKqueueFileSystemWatcherEngine::addPaths: open: Too many open files
> QFileSystemWatcher: failed to add paths:
> /Users/pns/Pictures/PictureProject/0029/DSC_2659.JPG
> QKqueueFileSystemWatcherEngine::addPaths: open: Too many open files
> QFileSystemWatcher: failed to add paths:
> /Users/pns/Pictures/PictureProject/0029/DSC_2660.JPG
> QKqueueFileSystemWatcherEngine::addPaths: open: Too many open files
> QFileSystemWatcher: failed to add paths:
> /Users/pns/Pictures/PictureProject/0029/DSC_2661.JPG
> QKqueueFileSystemWatcherEngine::addPaths: open: Too many open files
>
> (lots of similar lines for other image folders under my ID have been
> deleted)
>
> digikam(680)/digikam (core) Digikam::SearchTabHeader::selectedSearchChanged:
> changing to SAlbum  0x0
> digikam(680)/digikam (core) Digikam::SearchTabHeader::selectedSearchChanged:
> changing to SAlbum  0x122da1230
> digikam(680)/digikam (core) Digikam::FuzzySearchView::slotAlbumSelected:
> Selected new album 0x0
> digikam(680)/digikam (core) Digikam::FuzzySearchView::slotAlbumSelected: Not
> a haar search, returning
> digikam(680)/digikam (core) Digikam::FuzzySearchView::slotAlbumSelected:
> Selected new album 0x122db72c0
> QEventDispatcherUNIXPrivate(): Unable to create thread pipe: Too many open
> files
> QEventDispatcherUNIXPrivate(): Can not continue without a thread pipe
> QKqueueFileSystemWatcherEngine: error during kevent wait: Bad file
> descriptor
> KCrash: Application 'digikam' crashing...
> KCrash: Attempting to start
> /opt/local/lib/kde4/libexec/drkonqi.app/Contents/MacOS/drkonqi from kdeinit
> Warning: Path of socketfile exceeds UNIX_PATH_MAX.
> KCrash: Attempting to start
> /opt/local/lib/kde4/libexec/drkonqi.app/Contents/MacOS/drkonqi directly
> drkonqi(683)/KSharedDataCache ensureFileAllocated: This system misses
> support for posix_fallocate() -- ensure this partition has room for at least
> 10547296 bytes.
> drkonqi(683)/KSharedDataCache: Creating shell of a lock!
> drkonqi(683)/KSharedDataCache: Unable to setup shared cache lock, although
> it worked when created.
> drkonqi(683)/KSharedDataCache: Unable to unmap shared memory segment
> 0x118d2d000
>
> [1]+  Abort trap
> /Applications/MacPorts/KDE4/digikam.app/Contents/MacOS/digikam
>
>
>

> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users
>
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Gilles Caulier-4]

It crash in Geolocation search view. Sound like a component as
libkgeomap or marblewidget dysfunction.

marble globe viewer working fine on your computer. I remember some
problem with marble shared widget used in digiKam if marble maps data
are not installed.

Gilles Caulier

2012/1/8 Phil Stanford <[hidden email]>:

> Hi Gilles -
> I've attached all the output from gdb.
> It's not finding the .o files for a lot of the routines though, I don't know
> if that matters much - this is the native MacOS gdb,  and not the MacPorts
> version of gdb - again I'm not sure if that is significant.
>
> I didn't notice the Digikam splash screen come up when running under gdb so
> whether or not it got as far as just invoking the program from the shell, I
> don't know.
>
>
> Many thanks .....
> Phil
>
>
>
>
> On 8 January 2012 19:19, Gilles Caulier <[hidden email]> wrote:
>>
>> Can you run digiKam under gdb, and get a backtrace of crash to
>> investiguate ?
>>
>> Gilles Caulier
>>
>> 2012/1/8 Phil Stanford <[hidden email]>:
>> > Hi.
>> > I've previously used Digikam on MacOS (10.6.8), built using MacPorts for
>> > both Digikam and all the dependencies.
>> > The MacPorts Digikam version hasn't been updated for some time (still on
>> > 2.1.1_1)  and I spotted the instructions for installing using git:
>> >
>> >
>> > https://projects.kde.org/projects/extragear/graphics/digikam/repository/revisions/master/entry/README.MACOSX
>> >
>> > I was hoping to install the current stable 2.5.0  version of Digikam.
>> >
>> > Before starting the process in the instructions above, I made sure that
>> > all
>> > the MacPorts already installed were up to date, and that I could install
>> > and
>> > run the current MacPorts version of DIgikam (2.1.1_1).  The only
>> > exception
>> > was that I activated boost-1.47 rather than 1.48 as I'd read that there
>> > had
>> > been some recent issues and although I'd read that these had been fixed
>> > I
>> > wasn't quite sure what Digikam build I would be picking up.
>> >
>> > Once I'd proved that everything worked with the updated MacPorts
>> > dependencies, I uninstalled digikam by doing 'port uninstall digikam'.
>> >
>> > I then followed the instructions in the link above, and everything
>> > seemed to
>> > work and I had no obvious errors during the build or install.
>> >
>> > I started the process above by using the suggested command 'git clone
>> > git://anongit.kde.org/digikam-software-compilation' , copying to a new
>> > directory I'd made.
>> >
>> > After the install, I ran the launchctl DBUS commands and rebooted the
>> > Mac
>> > (this had been necessary before when using the MacPorts version).
>> >
>> > Here, I have to confess my ignorance; I've not used 'git' before, and I
>> > was
>> > actually expecting the above 'git clone' command to fetch me the latest
>> > 'production' version,  however when I start Digikam (from  a terminal)
>> > the
>> > splash screen shows  2.6.0 not 2.5 so I guess I'm getting the
>> > development
>> > version.
>> >
>> > I can't really tell much more than that since I never get the main
>> > window
>> > appearing as Digikam crashes.   I will reproduce the terminal output
>> > below.
>> >
>> > I also tried 'Showfoto' - and that starts up and runs with no problems.
>> > The
>> > splash screen for that also says 2.6.0, and the 'About' box gives the
>> > version as   6715b8ee6e5ee44bef186a1f0e39bf46a50f5681 with build date
>> > today
>> > and 'target: debugfull'.
>> >
>> > The fact that Showfoto runs OK suggests that probably this is an issue
>> > with
>> > Digikam + MacPorts, although as mentioned I've not used 'git' before so
>> > anything is possible .....
>> >
>> > I would be grateful to get some information -
>> >
>> > 1) Looking at the console log shown below, is there an obvious cause -
>> > (the
>> > 'too many open files' error seems similar to
>> > https://bugs.kde.org/show_bug.cgi?id=289330 but in my instance  DIgikam
>> > never starts correctly at all)
>> >
>> > 2) I don't really wish to be 'bleeding edge',   what should I have done
>> > to
>> > clone and build Digikam 2.5.0 not the development version
>> >
>> > 3) How can I clean things up from this build, and either get to the
>> > stable
>> > 2.5.0 version - or at the very least update to the latest development
>> > version - a bit of reading suggests that 'git pull' may do this?
>> >
>> > Ideally I would prefer to be able to install the latest released version
>> > of
>> > Digikam just by using MacPorts as I have other software installed using
>> > that
>> > package manager  - however unfortunately Digikam rarely gets updated on
>> > MacPorts so getting a working version with git too would be good.
>> >
>> > Thanks in advance for any pointers - I appreciate I'm rather ignorant of
>> > 'git' and how it works at the moment.
>> > Phil
>> >
>> > The log from running 'Digikam' follows -
>> > ========
>> >
>> > $ /Applications/MacPorts/KDE4/digikam.app/Contents/MacOS/digikam &
>> > [1] 680
>> > $ digikam(680)/KSharedDataCache ensureFileAllocated: This system misses
>> > support for posix_fallocate() -- ensure this partition has room for at
>> > least
>> > 10547296 bytes.
>> > digikam(680)/KSharedDataCache: Creating shell of a lock!
>> > digikam(680)/KSharedDataCache: Unable to setup shared cache lock,
>> > although
>> > it worked when created.
>> > digikam(680)/KSharedDataCache: Unable to unmap shared memory segment
>> > 0x11e600000
>> > digikam(680)/digikam (core) Digikam::AlbumWatch::connectToKDirWatch:
>> > KDirWatch method =  "FAM"
>> > digikam(680)/digikam (core) Digikam::AlbumManager::setDatabase:
>> > DatabaseParameters: [ Type "QSQLITE", Name
>> > "/Users/pns/Pictures/digikam4.db"
>> > (Thumbnails Name "/Users/pns/Pictures/thumbnails-digikam.db"); ]
>> > QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is
>> > still in
>> > use, all queries will cease to work.
>> > digikam(680)/digikam (core)
>> > Digikam::DatabaseConfigElementLoader::readConfig: Loading SQL code from
>> > config file "/opt/local/share/apps/digikam/database/dbconfig.xml"
>> > digikam(680)/digikam (core)
>> > Digikam::DatabaseConfigElementLoader::readConfig: false "1" 1 1
>> > digikam(680)/digikam (core) Digikam::SchemaUpdater::update:
>> > SchemaUpdater
>> > update
>> > digikam(680)/digikam (core) Digikam::SchemaUpdater::startUpdates: Have a
>> > database structure version  6
>> > digikam(680)/digikam (core) Digikam::SchemaUpdater::makeUpdates:
>> > makeUpdates  6  to  6
>> > digikam(680)/digikam (core)
>> > Digikam::AlbumRootLocation::AlbumRootLocation:
>> > Creating new Location  "/"  uuid
>> > "volumeid:?path=%2FUsers%2Fpns%2FPictures"
>> > digikam(680)/digikam (core) Digikam::CollectionManager::updateLocations:
>> > location for  "/Users/pns/Pictures"  is available  true
>> > digikam(680)/digikam (core) Digikam::LoadingCache::setCacheSize:
>> > Allowing a
>> > cache size of 60 MB
>> > digikam(680)/digikam (core)
>> > Digikam::ThumbnailSchemaUpdater::startUpdates:
>> > Have a thumbnail database structure version  "2"
>> > digikam(680)/digikam (core)
>> > Digikam::ThumbnailLoadThread::initializeThumbnailDatabase: Thumbnail db
>> > ready for use
>> > digikam(680)/digikam (core) Digikam::AlbumManager::checkNepomukService:
>> > Nepomuk server is not reachable. Cannot start Digikam Nepomuk Service
>> > digikam(680)/digikam (core) Digikam::CollectionScanner::completeScan:
>> > Complete scan (file scanning deferred) took: 361 msecs.
>> > digikam(680)/digikam (core)
>> > Digikam::IccSettings::IccSettingsPriv::scanDirectories: ()
>> > digikam(680)/KSharedDataCache ensureFileAllocated: This system misses
>> > support for posix_fallocate() -- ensure this partition has room for at
>> > least
>> > 10547296 bytes.
>> > digikam(680)/KSharedDataCache: Creating shell of a lock!
>> > digikam(680)/KSharedDataCache: Unable to setup shared cache lock,
>> > although
>> > it worked when created.
>> > digikam(680)/KSharedDataCache: Unable to unmap shared memory segment
>> > 0x1223fb000
>> > digikam(680)/KGEOMAP KGeoMap::KGeoMapWidget::setBackend: "setting
>> > backend
>> > marble"
>> > digikam(680)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned
>> > initialize() D-Bus call failed:  "The name org.kde.kded was not provided
>> > by
>> > any .service files"
>> >
>> > digikam(680)/kdecore (K*TimeZone*): No time zone information obtained
>> > from
>> > ktimezoned
>> > digikam(680)/KGEOMAP KGeoMap::KGeoMapWidget::setBackend: "setting
>> > backend
>> > marble"
>> > digikam(680)/digikam (core)
>> > Digikam::AlbumFilterModel::setSearchTextSettings: new search text
>> > settings:
>> > "" : hasResult =  false , validRows =  0
>> > digikam(680)/digikam (core) Digikam::ThemeManager::slotChangePalette: ""
>> > digikam(680)/digikam (core) Digikam::ThemeManager::slotChangePalette: ""
>> > digikam(680)/digikam (core) Digikam::ThemeManager::slotChangePalette: ""
>> > digikam(680)/digikam (core) Digikam::ThemeManager::slotChangePalette: ""
>> > digikam(680)/KGEOMAP KGeoMap::ItemMarkerTiler::slotSourceModelReset:
>> > ----
>> > digikam(680)/KGEOMAP KGeoMap::ItemMarkerTiler::slotSourceModelReset:
>> > ----
>> > QKqueueFileSystemWatcherEngine::addPaths: open: Too many open files
>> > QFileSystemWatcher: failed to add paths:
>> > /Users/pns/Pictures/PictureProject/0029/DSC_2659.JPG
>> > QKqueueFileSystemWatcherEngine::addPaths: open: Too many open files
>> > QFileSystemWatcher: failed to add paths:
>> > /Users/pns/Pictures/PictureProject/0029/DSC_2660.JPG
>> > QKqueueFileSystemWatcherEngine::addPaths: open: Too many open files
>> > QFileSystemWatcher: failed to add paths:
>> > /Users/pns/Pictures/PictureProject/0029/DSC_2661.JPG
>> > QKqueueFileSystemWatcherEngine::addPaths: open: Too many open files
>> >
>> > (lots of similar lines for other image folders under my ID have been
>> > deleted)
>> >
>> > digikam(680)/digikam (core)
>> > Digikam::SearchTabHeader::selectedSearchChanged:
>> > changing to SAlbum  0x0
>> > digikam(680)/digikam (core)
>> > Digikam::SearchTabHeader::selectedSearchChanged:
>> > changing to SAlbum  0x122da1230
>> > digikam(680)/digikam (core) Digikam::FuzzySearchView::slotAlbumSelected:
>> > Selected new album 0x0
>> > digikam(680)/digikam (core) Digikam::FuzzySearchView::slotAlbumSelected:
>> > Not
>> > a haar search, returning
>> > digikam(680)/digikam (core) Digikam::FuzzySearchView::slotAlbumSelected:
>> > Selected new album 0x122db72c0
>> > QEventDispatcherUNIXPrivate(): Unable to create thread pipe: Too many
>> > open
>> > files
>> > QEventDispatcherUNIXPrivate(): Can not continue without a thread pipe
>> > QKqueueFileSystemWatcherEngine: error during kevent wait: Bad file
>> > descriptor
>> > KCrash: Application 'digikam' crashing...
>> > KCrash: Attempting to start
>> > /opt/local/lib/kde4/libexec/drkonqi.app/Contents/MacOS/drkonqi from
>> > kdeinit
>> > Warning: Path of socketfile exceeds UNIX_PATH_MAX.
>> > KCrash: Attempting to start
>> > /opt/local/lib/kde4/libexec/drkonqi.app/Contents/MacOS/drkonqi directly
>> > drkonqi(683)/KSharedDataCache ensureFileAllocated: This system misses
>> > support for posix_fallocate() -- ensure this partition has room for at
>> > least
>> > 10547296 bytes.
>> > drkonqi(683)/KSharedDataCache: Creating shell of a lock!
>> > drkonqi(683)/KSharedDataCache: Unable to setup shared cache lock,
>> > although
>> > it worked when created.
>> > drkonqi(683)/KSharedDataCache: Unable to unmap shared memory segment
>> > 0x118d2d000
>> >
>> > [1]+  Abort trap
>> > /Applications/MacPorts/KDE4/digikam.app/Contents/MacOS/digikam
>> >
>> >
>> >
>> > _______________________________________________
>> > Digikam-users mailing list
>> > [hidden email]
>> > https://mail.kde.org/mailman/listinfo/digikam-users
>> >
>> _______________________________________________
>> Digikam-users mailing list
>> [hidden email]
>> https://mail.kde.org/mailman/listinfo/digikam-users
>
>
>
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users
>

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Phil Stanford]

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Gilles Caulier
Sent: 09 January 2012 10:34
To: digiKam - Home Manage your photographs as a professional with the power of open source
Subject: Re: [Digikam-users] Digikam crashes under MacOS when built using git + MacPorts

It crash in Geolocation search view. Sound like a component as libkgeomap or marblewidget dysfunction.

marble globe viewer working fine on your computer. I remember some problem with marble shared widget used in digiKam if marble maps data are not installed.

Gilles Caulier


---------
Hi Gilles
I tried the KDE 'marble' globe viewer installed under MacPorts and that is working fine (it starts and I can pan/zoom maps etc).
Libkgeomap is installed and looks to have been rebuilt yesterday too when I updated MacPorts.

I don't know if that helps or not!
Regards
Phil

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Gilles Caulier-4]

ok,

next component used by libkgeomap is khtml. It's html parser used by
konqueror web browser to display googlemaps.

Konqueror work fine on your computer ?

Other test about libkgeomap : trhis library come with a test program
name calibrator. It's not installed on your computer, it's only
compiled in libkgeomap build directory :

[gilles@localhost calibrator (master)]$ pwd
/mnt/data/Devel/GIT/2.x/build/extra/libkgeomap/calibrator
[gilles@localhost calibrator (master)]$ ls -al
total 452
drwxr-xr-x 3 gilles gilles    416 janv.  9 09:35 ./
drwxr-xr-x 9 gilles gilles    448 janv.  9 09:35 ../
-rw-r--r-- 1 gilles gilles   4505 janv.  3 09:23 calibrator.moc
drwxr-xr-x 4 gilles gilles    232 janv.  9 09:35 CMakeFiles/
-rw-r--r-- 1 gilles gilles   1178 sept. 28 13:07 cmake_install.cmake
-rw-r--r-- 1 gilles gilles    321 sept. 28 13:07 CTestTestfile.cmake
-rwxr-xr-x 1 gilles gilles 420136 janv.  3 09:23 libkgeomap_calibrator*
-rw-r--r-- 1 gilles gilles    338 janv.  3 09:23
libkgeomap_calibrator_automoc.cpp
-rw-r--r-- 1 gilles gilles   1642 sept. 28 13:07
libkgeomap_calibrator_automoc.cpp.files
-rwxr-xr-- 1 gilles gilles    268 janv.  3 09:23 libkgeomap_calibrator.shell*
-rw-r--r-- 1 gilles gilles  10271 sept. 28 13:07 Makefile
[gilles@localhost calibrator (master)]$

libkgeomap_calibrator.shell work fine for you ?

Gilles Caulier

2012/1/9 Phil Stanford <[hidden email]>:

> -----Original Message-----
> From: [hidden email] [mailto:[hidden email]]
> On Behalf Of Gilles Caulier
> Sent: 09 January 2012 10:34
> To: digiKam - Home Manage your photographs as a professional with the power
> of open source
> Subject: Re: [Digikam-users] Digikam crashes under MacOS when built using
> git + MacPorts
>
> It crash in Geolocation search view. Sound like a component as libkgeomap or
> marblewidget dysfunction.
>
> marble globe viewer working fine on your computer. I remember some problem
> with marble shared widget used in digiKam if marble maps data are not
> installed.
>
> Gilles Caulier
>
>
> ---------
> Hi Gilles
> I tried the KDE 'marble' globe viewer installed under MacPorts and that is
> working fine (it starts and I can pan/zoom maps etc).
> Libkgeomap is installed and looks to have been rebuilt yesterday too when I
> updated MacPorts.
>
> I don't know if that helps or not!
> Regards
> Phil
>
>
>>
>
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users
>

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Phil Stanford]

On 9 January 2012 11:46, Gilles Caulier <[hidden email]> wrote:

ok,

next component used by libkgeomap is khtml. It's html parser used by
konqueror web browser to display googlemaps.

Konqueror work fine on your computer ?

Other test about libkgeomap : trhis library come with a test program
name calibrator. It's not installed on your computer, it's only
compiled in libkgeomap build directory :

[gilles@localhost calibrator (master)]$ pwd
/mnt/data/Devel/GIT/2.x/build/extra/libkgeomap/calibrator
[gilles@localhost calibrator (master)]$ ls -al
total 452
drwxr-xr-x 3 gilles gilles    416 janv.  9 09:35 ./
drwxr-xr-x 9 gilles gilles    448 janv.  9 09:35 ../
-rw-r--r-- 1 gilles gilles   4505 janv.  3 09:23 calibrator.moc
drwxr-xr-x 4 gilles gilles    232 janv.  9 09:35 CMakeFiles/
-rw-r--r-- 1 gilles gilles   1178 sept. 28 13:07 cmake_install.cmake
-rw-r--r-- 1 gilles gilles    321 sept. 28 13:07 CTestTestfile.cmake
-rwxr-xr-x 1 gilles gilles 420136 janv.  3 09:23 libkgeomap_calibrator*
-rw-r--r-- 1 gilles gilles    338 janv.  3 09:23
libkgeomap_calibrator_automoc.cpp
-rw-r--r-- 1 gilles gilles   1642 sept. 28 13:07
libkgeomap_calibrator_automoc.cpp.files
-rwxr-xr-- 1 gilles gilles    268 janv.  3 09:23 libkgeomap_calibrator.shell*
-rw-r--r-- 1 gilles gilles  10271 sept. 28 13:07 Makefile
[gilles@localhost calibrator (master)]$

libkgeomap_calibrator.shell work fine for you ?

Gilles Caulier

Thanks -

1) Konquerer works fine and I can display Googlemaps

2)  Re libkgeomap_calibrator:

On the Mac, in my build directory, this appears as a Mac application, ie a directory with the .app suffix:

$ pwd
/Users/pns/git-files/digikam-2.5/build/extra/libkgeomap/calibrator

$ ls -l
total 72
drwxr-xr-x  6 pns  staff    204  8 Jan 13:38 CMakeFiles
-rw-r--r--  1 pns  staff    339  8 Jan 13:38 CTestTestfile.cmake
-rw-r--r--  1 pns  staff  10529  8 Jan 13:38 Makefile
-rw-r--r--  1 pns  staff   4505  8 Jan 13:42 calibrator.moc
-rw-r--r--  1 pns  staff   1019  8 Jan 13:38 cmake_install.cmake
drwxr-xr-x  3 pns  staff    102  8 Jan 13:38 libkgeomap_calibrator.app
-rw-r--r--  1 pns  staff    290  8 Jan 13:42 libkgeomap_calibrator_automoc.cpp
-rw-r--r--  1 pns  staff   1536  8 Jan 13:38 libkgeomap_calibrator_automoc.cpp.files


I can run libkgeomap_calibrator.app from the Mac Finder - although I'm not quite sure just what the application is supposed to do, it does start the GUI and can display either Google or marble maps.

You mentioned libkgeomap_calibrator.shell -
All the KDE programs installed under MacPorts appear in the Mac style, ie with in a directory with the .app suffix - a bit further down are the actual executable and the .shell file:

$ pwd
/Users/pns/git-files/digikam-2.5/build/extra/libkgeomap/calibrator/libkgeomap_calibrator.app/Contents/MacOS

$ ls -l
total 280
-rwxr-xr-x  1 pns  staff  139088  8 Jan 13:42 libkgeomap_calibrator
-rwxr-xr--  1 pns  staff     321  8 Jan 13:42 libkgeomap_calibrator.shell

For all the KDE programs I tried, I can open a shell in the program's directory and normally I can run the program with no problems if I use the executable directly, but get an error if I run the .shell version.   Thus for Konqueror -

$ pwd
/Applications/MacPorts/KDE4/konqueror.app/Contents/MacOS
$ ls -l
total 88
-rwxr-xr-x  1 root  admin  37480  8 Oct 02:10 konqueror
-rwxr-xr--  1 root  admin    481  8 Oct 02:10 konqueror.shell


I can type ./konqueror  and get the browser running, but   ./konqueror.shell   gives an error (in this case the path in the shell script is wrong).

This behaviour seems 'normal' for all the KDE applications I tried, and the applications themselves all work when run using the Mac Finder, but I mention it in case it is significant for this problem.

In the case of libkgeomap_calibrator,  if I run ./libkgeomap_calibrator then that works fine, if I run .//libkgeomap_calibrator.shell  then I get the following error:

$ ./libkgeomap_calibrator.shell
dyld: Library not loaded: /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib
  Referenced from: /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib
  Reason: Incompatible library version: vecLib requires version 1.0.0 or later, but libLAPACK.dylib provides version 0.0.0
./libkgeomap_calibrator.shell: line 4: 10835 Trace/BPT trap          DYLD_LIBRARY_PATH=/Users/pns/git-files/digikam-2.5/build/lib/./:/opt/local/lib${DYLD_LIBRARY_PATH:+:$DYLD_LIBRARY_PATH} "/Users/pns/git-files/digikam-2.5/build/extra/libkgeomap/calibrator/libkgeomap_calibrator.app/Contents/MacOS/libkgeomap_calibrator" "$@"


As I say I'm not sure if this is relevant, since all similar attempts to run any KDE application using the .shell version also fail, but I guess that if there were incompatible libs being picked up somewhere that could be the cause.

Thanks again
Phil


 

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[brad]

On Sunday, January 08, 2012 06:36:01 PM Phil Stanford wrote:

> I would be grateful to get some information -
>
> 1) Looking at the console log shown below, is there an obvious cause - (the
> 'too many open files' error seems similar to
> https://bugs.kde.org/show_bug.cgi?id=289330 but in my instance  DIgikam
> never starts correctly at all)
>
> 2) I don't really wish to be 'bleeding edge',   what should I have done to
> clone and build Digikam 2.5.0 not the development version
>

Until the above bug is fixed or workaround is applied, you're going to need to
use digikam from 2.3 or earlier on OS X.

> 3) How can I clean things up from this build, and either get to the stable
> 2.5.0 version - or at the very least update to the latest development
> version - a bit of reading suggests that 'git pull' may do this?

i think, git checkout a5faa1fb should get you to the 2.3.0 release, but my
git-kung-fu is pretty bad.

with regards to your crash i can try to compile it when i get home to see if i
can reproduce it. I haven't been running recent versions due to the bug above.
And since my git-kung-fu is bad, i find it hard to swap between versions of
digikam.

 - brad



_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[brad]

phil,

were you running previous digikam versions? Did you completely uninstall the macports version of digikam? perhaps you're loading old libraries from a previous installation of digikam. Or, perhaps the digikam.rc file is causing problems. 

try,

 mv ~/Library/Preferences/KDE/share/apps/digikam ~/Library/Preferences/KDE/share/apps/digikam.old

then try launching digikam

With regards the the .shell files, those are scripts generated by cmake in an attempt to setup your environment to make launching the application easier. If applications launch fine without the .shell then just use the straight binaries. 

cheers,

 - brad

On Jan 9, 2012, at 10:32 AM, Phil Stanford wrote:

On 9 January 2012 11:46, Gilles Caulier <[hidden email]> wrote:

ok,

next component used by libkgeomap is khtml. It's html parser used by
konqueror web browser to display googlemaps.

Konqueror work fine on your computer ?

Other test about libkgeomap : trhis library come with a test program
name calibrator. It's not installed on your computer, it's only
compiled in libkgeomap build directory :

[gilles@localhost calibrator (master)]$ pwd
/mnt/data/Devel/GIT/2.x/build/extra/libkgeomap/calibrator
[gilles@localhost calibrator (master)]$ ls -al
total 452
drwxr-xr-x 3 gilles gilles    416 janv.  9 09:35 ./
drwxr-xr-x 9 gilles gilles    448 janv.  9 09:35 ../
-rw-r--r-- 1 gilles gilles   4505 janv.  3 09:23 calibrator.moc
drwxr-xr-x 4 gilles gilles    232 janv.  9 09:35 CMakeFiles/
-rw-r--r-- 1 gilles gilles   1178 sept. 28 13:07 cmake_install.cmake
-rw-r--r-- 1 gilles gilles    321 sept. 28 13:07 CTestTestfile.cmake
-rwxr-xr-x 1 gilles gilles 420136 janv.  3 09:23 libkgeomap_calibrator*
-rw-r--r-- 1 gilles gilles    338 janv.  3 09:23
libkgeomap_calibrator_automoc.cpp
-rw-r--r-- 1 gilles gilles   1642 sept. 28 13:07
libkgeomap_calibrator_automoc.cpp.files
-rwxr-xr-- 1 gilles gilles    268 janv.  3 09:23 libkgeomap_calibrator.shell*
-rw-r--r-- 1 gilles gilles  10271 sept. 28 13:07 Makefile
[gilles@localhost calibrator (master)]$

libkgeomap_calibrator.shell work fine for you ?

Gilles Caulier

Thanks -

1) Konquerer works fine and I can display Googlemaps

2)  Re libkgeomap_calibrator:

On the Mac, in my build directory, this appears as a Mac application, ie a directory with the .app suffix:

$ pwd
/Users/pns/git-files/digikam-2.5/build/extra/libkgeomap/calibrator

$ ls -l
total 72
drwxr-xr-x  6 pns  staff    204  8 Jan 13:38 CMakeFiles
-rw-r--r--  1 pns  staff    339  8 Jan 13:38 CTestTestfile.cmake
-rw-r--r--  1 pns  staff  10529  8 Jan 13:38 Makefile
-rw-r--r--  1 pns  staff   4505  8 Jan 13:42 calibrator.moc
-rw-r--r--  1 pns  staff   1019  8 Jan 13:38 cmake_install.cmake
drwxr-xr-x  3 pns  staff    102  8 Jan 13:38 libkgeomap_calibrator.app
-rw-r--r--  1 pns  staff    290  8 Jan 13:42 libkgeomap_calibrator_automoc.cpp
-rw-r--r--  1 pns  staff   1536  8 Jan 13:38 libkgeomap_calibrator_automoc.cpp.files


I can run libkgeomap_calibrator.app from the Mac Finder - although I'm not quite sure just what the application is supposed to do, it does start the GUI and can display either Google or marble maps.

You mentioned libkgeomap_calibrator.shell -
All the KDE programs installed under MacPorts appear in the Mac style, ie with in a directory with the .app suffix - a bit further down are the actual executable and the .shell file:

$ pwd
/Users/pns/git-files/digikam-2.5/build/extra/libkgeomap/calibrator/libkgeomap_calibrator.app/Contents/MacOS

$ ls -l
total 280
-rwxr-xr-x  1 pns  staff  139088  8 Jan 13:42 libkgeomap_calibrator
-rwxr-xr--  1 pns  staff     321  8 Jan 13:42 libkgeomap_calibrator.shell

For all the KDE programs I tried, I can open a shell in the program's directory and normally I can run the program with no problems if I use the executable directly, but get an error if I run the .shell version.   Thus for Konqueror -

$ pwd
/Applications/MacPorts/KDE4/konqueror.app/Contents/MacOS
$ ls -l
total 88
-rwxr-xr-x  1 root  admin  37480  8 Oct 02:10 konqueror
-rwxr-xr--  1 root  admin    481  8 Oct 02:10 konqueror.shell


I can type ./konqueror  and get the browser running, but   ./konqueror.shell   gives an error (in this case the path in the shell script is wrong).

This behaviour seems 'normal' for all the KDE applications I tried, and the applications themselves all work when run using the Mac Finder, but I mention it in case it is significant for this problem.

In the case of libkgeomap_calibrator,  if I run ./libkgeomap_calibrator then that works fine, if I run .//libkgeomap_calibrator.shell  then I get the following error:

$ ./libkgeomap_calibrator.shell
dyld: Library not loaded: /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib
  Referenced from: /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib
  Reason: Incompatible library version: vecLib requires version 1.0.0 or later, but libLAPACK.dylib provides version 0.0.0
./libkgeomap_calibrator.shell: line 4: 10835 Trace/BPT trap          DYLD_LIBRARY_PATH=/Users/pns/git-files/digikam-2.5/build/lib/./:/opt/local/lib${DYLD_LIBRARY_PATH:+:$DYLD_LIBRARY_PATH} "/Users/pns/git-files/digikam-2.5/build/extra/libkgeomap/calibrator/libkgeomap_calibrator.app/Contents/MacOS/libkgeomap_calibrator" "$@"


As I say I'm not sure if this is relevant, since all similar attempts to run any KDE application using the .shell version also fail, but I guess that if there were incompatible libs being picked up somewhere that could be the cause.

Thanks again
Phil


 

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Phil Stanford]

On 10 January 2012 02:12, brad <[hidden email]> wrote:

phil,

were you running previous digikam versions? Did you completely uninstall the macports version of digikam? perhaps you're loading old libraries from a previous installation of digikam. Or, perhaps the digikam.rc file is causing problems. 

try,

 mv ~/Library/Preferences/KDE/share/apps/digikam ~/Library/Preferences/KDE/share/apps/digikam.old

then try launching digikam

With regards the the .shell files, those are scripts generated by cmake in an attempt to setup your environment to make launching the application easier. If applications launch fine without the .shell then just use the straight binaries. 

cheers,

 - brad

Brad, thanks for your mails, sorry for tardy replies but work gets in the way of fun sometimes .....!

Re previous versions of Digikam  -
Yes I did uninstall the version I was running under MacPorts.   There are older, 'inactive' ones still on the system, but MacPorts normally seems pretty good at tidying up - inactive ports are just there in case you do want to activate them again, and executables & libraries are normally removed from any paths. 

The tip about renaming the rc file was useful - on the Mac this is
~/Library/Preferences/KDE/share/config/digikamrc   (not .rc) and there's also a ~/Library/Preferences/KDE/share/apps/digikam directory, which in my case just had a cameras.xml file in it.

I moved both of them sideways and restarted Digikam (the 2.6 git build) from the terminal - this time I did get the 'first time' config windows coming up; then of course it started the 'QKqueueFileSystemWatcherEngine::addPaths: open: Too many open files' errors before bombing out on some other issues.

Re this  'too many open files' issue in https://bugs.kde.org/show_bug.cgi?id=289330  -
I'm still a bit unclear there;  is it some new feature / behaviour in Digikam  post 2.3  that's now causing this MacOS 'files per process' limit to be reached?  I've tried with various versions of qt (4.7.2 - 4.7.4) and it doesn't make any difference.

I saw re the albumwatch.patch  file but my knowledge doesn't extend to knowing where or how to apply that!

In terms of my strategy now -
It would seem to be sensible for me to try and get a known-working version (2.3 from what you say) up and running.

I failed to work out how to use git to get a known and released digikam version back from https://projects.kde.org/projects/extragear/graphics/digikam/digikam-software-compilation/repository  

That is probably my lack of knowledge about git of course.

I also wasn't clear on what the difference was between the above URL and https://projects.kde.org/projects/extragear/graphics/digikam/repository

My final attempt last night was to try and see if I could get things to work by downloading the tarball from http://sourceforge.net/projects/digikam/files/digikam/2.3.0/

I unpacked that, and the directories looked similar to what I'd got back using git (for the 2.6 development release) so I followed the instructions I had done before,  in https://projects.kde.org/projects/extragear/graphics/digikam/repository/revisions/master/entry/README.MACOSX

However, that fell at the first hurdle, when I ran the ./download-repos  script it fell over -

---------
$ ./download-repos
sh: line 0: cd: core/.git/hooks: No such file or directory
sh: line 0: cd: extra/libkface/.git/hooks: No such file or directory
sh: line 0: cd: extra/libkgeomap/.git/hooks: No such file or directory
sh: line 0: cd: extra/kipi-plugins/.git/hooks: No such file or directory
sh: line 0: cd: extra/libkexiv2/.git/hooks: No such file or directory
sh: line 0: cd: extra/libkdcraw/.git/hooks: No such file or directory
sh: line 0: cd: extra/libkipi/.git/hooks: No such file or directory
sh: line 0: cd: extra/libksane/.git/hooks: No such file or directory
sh: line 0: cd: extra/libmediawiki/.git/hooks: No such file or directory
sh: line 0: cd: extra/libkvkontakte/.git/hooks: No such file or directory
sh: line 0: cd: doc/digikam/.git/hooks: No such file or directory
sh: line 0: cd: doc/kipi-plugins/.git/hooks: No such file or directory
sh: line 0: cd: .git/hooks: No such file or directory
sh: kdialog: command not found
sh: kdialog: command not found

**** l10n ****

./project/release/fetch_l10n.rb:33:in `mkdir': File exists - po (Errno::EEXIST)
    from ./project/release/fetch_l10n.rb:33


---------

Indeed, there is no '.git/hooks'  under any of the dirs it mentions.
At that point I decided it was all too hard, and definitely past my bedtime!

I would still like to crack this issue of not having to rely on the Macports version getting updated by the supporter - even though that is by far the simplest way of getting things working!  Having prodded quite a bit with people's help,  with a bit more understanding (and learning on my part!) I feel it ought to be achievable!

So if there are still any further hints to be had re either getting hold of a specific Digikam release under git,   or on how to make the tarball work on MacOS,  I would be grateful ........

Cheers
Phil




_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[brad]

> Brad, thanks for your mails, sorry for tardy replies but work gets in the
> way of fun sometimes .....!
>
no worries, i can relate.

>
> Re this  'too many open files' issue in
> https://bugs.kde.org/show_bug.cgi?id=289330  -
> I'm still a bit unclear there;  is it some new feature / behaviour in
> Digikam  post 2.3  that's now causing this MacOS 'files per process' limit
> to be reached?  I've tried with various versions of qt (4.7.2 - 4.7.4) and
> it doesn't make any difference.
>
the digikam code is using a feature of QT, which is not quite working on OS X.
QT's implementation on OS X regarding file-watching has a hard limit of 255
files, so you have less than 255 images (actually more like 240 images), then
you're all set :). You should actually be able to open the first images out of
your first album (up to, around the first 240 images), i think.

> I saw re the albumwatch.patch  file but my knowledge doesn't extend to
> knowing where or how to apply that!
>
Take another look at the bug report, there's more info on applying the patch.
https://bugs.kde.org/show_bug.cgi?id=289330

i just submitted another patch which is pretty straightforward to apply. Try
the following,
 * checkout the source again and run download-repos
 * download the patch from the bug report ( 0001-disable-filewatching-on-OS-X-
but-dir-watching-still-.patch)
 * change directories to digikam-sc/core
 * run: git am path/tofile/0001-disable-filewatching-on-OS-X-but-dir-watching-
still-.patch
 * then go back to digikam-sc, and run bootstrap.macports and compile.

> In terms of my strategy now -
> It would seem to be sensible for me to try and get a known-working version
> (2.3 from what you say) up and running.
>
> I failed to work out how to use git to get a known and released digikam
> version back from
> https://projects.kde.org/projects/extragear/graphics/digikam/digikam-softwar
> e-compilation/repository
>
>
> That is probably my lack of knowledge about git of course.
>

i have this problem too :) everybody does when they start out, but i'm trying
to get better.

> I also wasn't clear on what the difference was between the above URL and
> https://projects.kde.org/projects/extragear/graphics/digikam/repository
>
This is a little confusing, no doubt. Digikam has a lot of subprojects which
are kept in different git repos. The digikam-software-compilation/repository is
simply a small git repo which doesn't actually have the source code, it's just
meant to be a place holder or stagine area of directories and cmake files. When
you execute download-repos, git pulls down the actually source code for
digikam and it's subprojects (i.e. plugins and other libraries) which are
spread across several different git repos. So, the second URL you referenced,
digikam/repository is the core code of digikam -- no plugins or optional
libraries. This code is downloaded when you execute download-repos.

> My final attempt last night was to try and see if I could get things to
> work by downloading the tarball from
> http://sourceforge.net/projects/digikam/files/digikam/2.3.0/
>
> I unpacked that, and the directories looked similar to what I'd got back
> using git (for the 2.6 development release) so I followed the instructions
> I had done before,  in
> https://projects.kde.org/projects/extragear/graphics/digikam/repository/revi
> sions/master/entry/README.MACOSX
>
> However, that fell at the first hurdle, when I ran the ./download-repos
> script it fell over -
>

If you use the tar ball from the web, then download-repos is not necessary,
all the code should already be in the tar ball, and therefor already on your
system. Follow the instructions on this page for compilation from the tar file:
  http://digikam.org/drupal/download/tarball


>
> I would still like to crack this issue of not having to rely on the
> Macports version getting updated by the supporter - even though that is by
> far the simplest way of getting things working!  Having prodded quite a bit
> with people's help,  with a bit more understanding (and learning on my
> part!) I feel it ought to be achievable!
>
it's all a learning process. as long as you feel it's achievable, then it is
:).

> So if there are still any further hints to be had re either getting hold of
> a specific Digikam release under git,   or on how to make the tarball work
> on MacOS,  I would be grateful ........
>
try the above information -- hopefully that's give you a push in the right
direction.


cheers,
 - brad

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Phil Stanford]

Many thanks for your hints and tips Brad -
I did download the 2.3 tarball last night and gave that a go following your instructions;
I had some issues with FindMarble.cmake which turned out to be a known problem, but following the traditional consultation with Google and the tearing out of a few remaining precious hairs,  it all built and ran OK.

I will also have a go at building from git + your latest patch too and see how that goes.
Thanks again
Phil

On 11 January 2012 15:50, brad <[hidden email]> wrote:

> Brad, thanks for your mails, sorry for tardy replies but work gets in the
> way of fun sometimes .....!
>

no worries, i can relate.

>
> Re this  'too many open files' issue in
> https://bugs.kde.org/show_bug.cgi?id=289330  -
> I'm still a bit unclear there;  is it some new feature / behaviour in
> Digikam  post 2.3  that's now causing this MacOS 'files per process' limit
> to be reached?  I've tried with various versions of qt (4.7.2 - 4.7.4) and
> it doesn't make any difference.
>

the digikam code is using a feature of QT, which is not quite working on OS X.
QT's implementation on OS X regarding file-watching has a hard limit of 255
files, so you have less than 255 images (actually more like 240 images), then
you're all set :). You should actually be able to open the first images out of
your first album (up to, around the first 240 images), i think.

> I saw re the albumwatch.patch  file but my knowledge doesn't extend to
> knowing where or how to apply that!
>

Take another look at the bug report, there's more info on applying the patch.
https://bugs.kde.org/show_bug.cgi?id=289330

i just submitted another patch which is pretty straightforward to apply. Try
the following,
 * checkout the source again and run download-repos
 * download the patch from the bug report ( 0001-disable-filewatching-on-OS-X-
but-dir-watching-still-.patch)
 * change directories to digikam-sc/core
 * run: git am path/tofile/0001-disable-filewatching-on-OS-X-but-dir-watching-
still-.patch
 * then go back to digikam-sc, and run bootstrap.macports and compile.

> In terms of my strategy now -
> It would seem to be sensible for me to try and get a known-working version
> (2.3 from what you say) up and running.
>
> I failed to work out how to use git to get a known and released digikam
> version back from
> https://projects.kde.org/projects/extragear/graphics/digikam/digikam-softwar
> e-compilation/repository
>
>
> That is probably my lack of knowledge about git of course.
>

i have this problem too :) everybody does when they start out, but i'm trying
to get better.

> I also wasn't clear on what the difference was between the above URL and
> https://projects.kde.org/projects/extragear/graphics/digikam/repository
>

This is a little confusing, no doubt. Digikam has a lot of subprojects which
are kept in different git repos. The digikam-software-compilation/repository is
simply a small git repo which doesn't actually have the source code, it's just
meant to be a place holder or stagine area of directories and cmake files. When
you execute download-repos, git pulls down the actually source code for
digikam and it's subprojects (i.e. plugins and other libraries) which are
spread across several different git repos. So, the second URL you referenced,
digikam/repository is the core code of digikam -- no plugins or optional
libraries. This code is downloaded when you execute download-repos.

> My final attempt last night was to try and see if I could get things to
> work by downloading the tarball from
> http://sourceforge.net/projects/digikam/files/digikam/2.3.0/
>
> I unpacked that, and the directories looked similar to what I'd got back
> using git (for the 2.6 development release) so I followed the instructions
> I had done before,  in
> https://projects.kde.org/projects/extragear/graphics/digikam/repository/revi
> sions/master/entry/README.MACOSX
>
> However, that fell at the first hurdle, when I ran the ./download-repos
> script it fell over -
>

If you use the tar ball from the web, then download-repos is not necessary,
all the code should already be in the tar ball, and therefor already on your
system. Follow the instructions on this page for compilation from the tar file:
 http://digikam.org/drupal/download/tarball

>
> I would still like to crack this issue of not having to rely on the
> Macports version getting updated by the supporter - even though that is by
> far the simplest way of getting things working!  Having prodded quite a bit
> with people's help,  with a bit more understanding (and learning on my
> part!) I feel it ought to be achievable!
>

it's all a learning process. as long as you feel it's achievable, then it is
:).

> So if there are still any further hints to be had re either getting hold of
> a specific Digikam release under git,   or on how to make the tarball work
> on MacOS,  I would be grateful ........
>

try the above information -- hopefully that's give you a push in the right
direction.


cheers,
 - brad

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users