[Digikam-users] Digikam crashes under MacOS when built using git + MacPorts

Phil Stanford phil.stanford at gmail.com
Wed Jan 11 14:11:25 GMT 2012


On 10 January 2012 02:12, brad <bkn at ithryn.net> 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20120111/7e57afc0/attachment.html>


More information about the Digikam-users mailing list