[Digikam-users] Digikam 3.5 is crashing

[Jim Dory]

Peter,

Just an FYI, the DK-3.5 is still crashing on me but the thumbnails are
tamed down a bit. I did try again to build DK-4.0.0-beta1 by renaming the
3.5 ebuild into my local overlay and pointing it at the tarball. I get
about 41% compiled before the first error. I googled it but found nothing.
For what its worth here's the errors:

/var/tmp/portage/media-gfx/digikam-4.0.0_beta1/work/digikam-4.0.0-beta1/core/libs/widgets/metadata/xmpwidget.cpp:126:44:
error: no matching function for call to
'Digikam::DMetadata::getXmpTagsDataList()'
     setMetadataMap(data.getXmpTagsDataList());

<snip>

/usr/include/libkexiv2/kexiv2.h:810:25: note:   candidate expects 2
arguments, 0 provided
digikam/CMakeFiles/digikamcore.dir/build.make:5199: recipe for target
'digikam/CMakeFiles/digikamcore.dir/__/libs/widgets/metadata/xmpwidget.o'
failed
make[2]: ***
[digikam/CMakeFiles/digikamcore.dir/__/libs/widgets/metadata/xmpwidget.o]
Error 1
make[2]: *** Waiting for unfinished jobs....
/var/tmp/portage/media-gfx/digikam-4.0.0_beta1/work/digikam-4.0.0-beta1/core/libs/widgets/metadata/exifwidget.cpp:
In member function 'virtual bool Digikam::ExifWidget::decodeMetadata()':
/var/tmp/portage/media-gfx/digikam-4.0.0_beta1/work/digikam-4.0.0-beta1/core/libs/widgets/metadata/exifwidget.cpp:115:45:
error: no matching function for call to
'Digikam::DMetadata::getExifTagsDataList()'
     setMetadataMap(data.getExifTagsDataList());

Could be something in my ebuild I used from 3.5. Or I'm missing something.
  cheers, JD







On Fri, Jan 3, 2014 at 1:16 PM, Jim Dory <james at dorydesign.com> wrote:

> Peter, thanks for informative reply.
>
> 1) I don't use eix - I'll give it a try.
> 2) I always use emerge -avuND @world when updating.
> 3) I have the elogs emailed me automatically so I can read each one.
> 4) yes, but only when it asks
> 5) depclean not as often as I should, but occasionally
> 6) first go-to when I have a problem, usually doesn't have anything to fix
> these days.
> 7) when my root partition starts filling up I do this.
> 8) when it asks, not as matter of course.
>
> I will say I may have fixed problem but haven't had time to play around
> much to be sure. Possibly things are still broken, but I am finally able to
> get some accurate thumbnails. I will see what happens when I tag some -
> that was throwing the thumbnails off previously.
>
> What I did was try to build an ebuild with digikam-4.0.0.beta1 but it
> would fail during the compile. So I went ahead and as my user (not root)
> installed it via "make && make install [as root]" in my home/Opt directory.
> However, I forgot about specifying an install directory so it installed
> globally. Oops.
>
> I had the exact same problem with the beta version so uninstalled it using
> the make uninstall command. That removed a lot of KDE libraries, which I
> reinstalled using my sets (i.e.: emerge -av @kdegraphics) and a few others.
> So I'm back on dk 3.5, and it seems to be behaving better now.
>
> Not sure why I was having trouble with the dk beta1 ebuild, but that would
> be another thread I guess and maybe something for the gentoo forums.
>
>
> On Fri, Jan 3, 2014 at 12:04 AM, Peter Albrecht <peter at crazymonkeys.de>wrote:
>
>> Hi Jim,
>>
>> on my gentoo system "dev-ruby/sqlite3" is not installed and
>> digikam works fine with sqlite datebase. So I guess, you
>> don't need it.
>>
>> I am no gentoo expert, but
>> "/usr/portage/media-gfx/digikam/digikam-3.5.0.ebuild"
>> says:
>> > CDEPEND="... || ( dev-qt/qtsql:4[mysql] dev-qt/qtsql:4[sqlite] ) ..."
>>
>> I would read this: You need QtSQL (slot 4) with USE-Flag
>> "mysql" or "sqlite" enabled.
>>
>> While "/usr/portage/dev-qt/qtsql/qtsql-4.8.5.ebuild" says:
>> > DEPEND="... sqlite? ( dev-db/sqlite:3 )"
>>
>> Which, I would read like: I you enable "sqlite" USE-Flag,
>> install "dev-db/sqlite slot 3".
>> And "eix ^sqlite$" tells you, slot 3 contains version 3.7.x
>> and 3.8.x.
>>
>> To sum up:
>> If build dev-qt/qtsql with USE-Flag sqlite, sqlite 3.x will
>> be installed automatically.
>>
>> I use at the moment:
>>  - media-gfx/digikam-3.5.0
>>  - dev-db/sqlite-3.7.17
>>  - dev-qt/qtsql-4.8.5
>>
>> This works fine for me. Maybe you try these versions.
>>
>>
>> As for gentoo in general:
>> Maybe you missed some step at your last system update. Wenn
>> I do updates, I go through the following steps:
>>
>>  1) eix-sync   or   emerge --sync; eix-update
>>
>>  2) emerge -vpt --update --newuse --deep world
>>
>>  3) check elogs (if enabled) with "elogv"
>>
>>  4) emerge -va @preserved-rebuild
>>
>>  5) emerge -va --depclean
>>
>>  6) revdep-rebuild -i
>>
>>  7) eclean-dist --destructive
>>
>>  8) dispatch-conf
>>
>>
>> Regards,
>>         Peter
>>
>>
>> On 02.01.2014 23:33, Jim Dory wrote:
>> > Ok, I may have it already as my version is sqlite-3.8.2
>> >
>> > I did enable a sqlite3 USE flag in the make.conf but when doing an
>> "emerge
>> > -avuND @world" no package picks it up. There is a dev-ruby/sqlite3 that
>> > says this: "An extension library to access a SQLite database from Ruby"
>> so
>> > not sure that would do anything for me. Thanks much for the response.
>> >  cheers, Jim
>> >
>> >
>> > On Thu, Jan 2, 2014 at 12:25 PM, Gilles Caulier <
>> caulier.gilles at gmail.com>wrote:
>> >
>> >> yes, you need SQlite3 Qt plugin... not SQlite directly. We use Qt DB
>> SDK
>> _______________________________________________
>> Digikam-users mailing list
>> Digikam-users at kde.org
>> https://mail.kde.org/mailman/listinfo/digikam-users
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20140103/26647d7c/attachment.html>