SVN version crashes
Locked
 
|
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1 Hi all, the freshly checked out and compiled exiv2/digikam does crash after having checked all the albums and just shown the main screen for a fraction of a second. Is this a known problems and does a solution exist? Regards - Markus -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIYO3hxxUzQSse11ARAsl5AJ9rWWRqU9+Z2TggIAE6wA4GS8PUxACeNEyV jWtLTSXpYy+N95mSB0X/kN8= =xp6W -----END PGP SIGNATURE----- _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
> Hi all,
> the freshly checked out and compiled exiv2/digikam Hum, if you using Exiv2 from trunk, the tiff writing mode branch have been recently merged to trunk and now Exiv2 become very unstable. I'm currently working with Exiv2 author to stabilize code. please revert to last stable Exiv2 0.17.1. Do not use yet Exiv2 from trunk (future 0.18) Best Gilles Caulier > does crash after having > checked all the albums and just shown the main screen for a fraction of a second. > Is this a known problems and does a solution exist? > _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: SVN version crashes
|
|
On Tue, Jun 24, 2008 at 10:04 PM, Gilles Caulier <[hidden email]> wrote:
The same thing happened for me with Exiv2 0.17.1 and the new Digikam 0.9.4-rc1. I haven't compiled in enough debugging symbols to get a proper backtrace. I will try to do this as soon as I have some time. Reverting back to Exiv2 0.16 and Digikam 0.9.4-beta5 works. I have yet to try 0.16 with rc1. Cheers, Daniel Svärd _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
2008/6/24 Daniel Svärd <[hidden email]>:
> > On Tue, Jun 24, 2008 at 10:04 PM, Gilles Caulier <[hidden email]> > wrote: >> >> > Hi all, >> > the freshly checked out and compiled exiv2/digikam >> >> Hum, if you using Exiv2 from trunk, the tiff writing mode branch have >> been recently merged to trunk and now Exiv2 become very unstable. >> >> I'm currently working with Exiv2 author to stabilize code. please >> revert to last stable Exiv2 0.17.1. Do not use yet Exiv2 from trunk >> (future 0.18) > > The same thing happened for me with Exiv2 0.17.1 and the new Digikam > 0.9.4-rc1. I haven't compiled in enough debugging symbols to get a proper > backtrace. I will try to do this as soon as I have some time. > > Reverting back to Exiv2 0.16 and Digikam 0.9.4-beta5 works. I have yet to > try 0.16 with rc1. Warning : binary compatibility is not preserved between 0.16 and 0.17. if you don't recompile libkexiv2 used by digiKam and kipi-plugins you will see strange side effect... like crash (:=))) To be sure, please recompile libkexiv2 and exiv2 with full debug info, and send me gdb trace to hack Here i currently work with Exiv2 from trunk and digiKam 0.10.0 and stability is the hell... but it's the only way to test and stabilize code. Gilles Caulier Gilles > > Cheers, > > Daniel Svärd > > > > _______________________________________________ > 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 |
Re: SVN version crashes
|
|
On Tue, Jun 24, 2008 at 10:35 PM, Gilles Caulier <[hidden email]> wrote: 2008/6/24 Daniel Svärd <[hidden email]>: Oh, I just recompiled libkexiv2 when I updated to exiv2 0.17.1. Do I need to recompile kipi-plugins too? I thought they just used libkexiv2 to access exiv2. Anyways, if I don't recompile libkexiv2 it complains about not finding the correct library version, so that's a given.
I'll try to get a back trace for you now before I fall asleep. Is it ok to attach it here, or should I link it from somewhere? Daniel
_______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
2008/6/24 Daniel Svärd <[hidden email]>:
> > > On Tue, Jun 24, 2008 at 10:35 PM, Gilles Caulier <[hidden email]> > wrote: >> >> 2008/6/24 Daniel Svärd <[hidden email]>: >> > >> > On Tue, Jun 24, 2008 at 10:04 PM, Gilles Caulier >> > <[hidden email]> >> > wrote: >> >> >> >> > Hi all, >> >> > the freshly checked out and compiled exiv2/digikam >> >> >> >> Hum, if you using Exiv2 from trunk, the tiff writing mode branch have >> >> been recently merged to trunk and now Exiv2 become very unstable. >> >> >> >> I'm currently working with Exiv2 author to stabilize code. please >> >> revert to last stable Exiv2 0.17.1. Do not use yet Exiv2 from trunk >> >> (future 0.18) >> > >> > The same thing happened for me with Exiv2 0.17.1 and the new Digikam >> > 0.9.4-rc1. I haven't compiled in enough debugging symbols to get a >> > proper >> > backtrace. I will try to do this as soon as I have some time. >> > >> > Reverting back to Exiv2 0.16 and Digikam 0.9.4-beta5 works. I have yet >> > to >> > try 0.16 with rc1. >> >> Warning : binary compatibility is not preserved between 0.16 and 0.17. >> if you don't recompile libkexiv2 used by digiKam and kipi-plugins you >> will see strange side effect... like crash (:=))) > > Oh, I just recompiled libkexiv2 when I updated to exiv2 0.17.1. Do I need to > recompile kipi-plugins too? I thought they just used libkexiv2 to access > exiv2. Anyways, if I don't recompile libkexiv2 it complains about not > finding the correct library version, so that's a given. > >> >> To be sure, please recompile libkexiv2 and exiv2 with full debug info, >> and send me gdb trace to hack > > I'll try to get a back trace for you now before I fall asleep. Is it ok to > attach it here, or should I link it from somewhere? > You can attach it here. attachement size to mailing list is limited to 40Kb Gilles _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
In reply to this post by Gilles Caulier-4
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1 Gilles Caulier schrieb: | I'm currently working with Exiv2 author to stabilize code. please | revert to last stable Exiv2 0.17.1. Do not use yet Exiv2 from trunk | (future 0.18) OK, just went back to Exiv2 0.16 (this was at hand), compiled and installed it and afterwards did a make clean on the checked out digikam sources before recompilation and now it runs fine again. In the evening I will give Exiv2 0.17.1 a try. Thanks for helping - Markus -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIYRgVxxUzQSse11ARAt+GAJ9m31CVqzUz+LirDNrxYTihnAy1xACghMGn pO0bi4jefllsCERvCfZGvGk= =vgYT -----END PGP SIGNATURE----- _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: SVN version crashes
|
|
In reply to this post by Gilles Caulier-4
On Wed, Jun 25, 2008 at 12:33 AM, Gilles Caulier <[hidden email]> wrote:
No need for that it seems. I just recompiled kipi-plugins as well, to enable debugging symbols, and now it doesn't crash. It seems that this was the problem. I just thought that since the same version of libkexiv2 was used for kipi-plugins, only recompiling libkexiv2 would be enough. Clearly I was wrong. So in short (if anyone else suffers the same problem): upgrade exiv2 to 0.17.1, recompile libkexiv2 0.1.7, recompile kipi-plugins 0.1.5 and it should work. Anyway, now it's working, so I'm happy. Thank you Gilles for your quick replies and I'm sorry for wasting your time. You're doing a great job with Digikam. Cheers, Daniel _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
2008/6/24 Daniel Svärd <[hidden email]>:
> > > On Wed, Jun 25, 2008 at 12:33 AM, Gilles Caulier <[hidden email]> > wrote: >> >> 2008/6/24 Daniel Svärd <[hidden email]>: >> > >> > >> > On Tue, Jun 24, 2008 at 10:35 PM, Gilles Caulier >> > <[hidden email]> >> > wrote: >> >> >> >> 2008/6/24 Daniel Svärd <[hidden email]>: >> >> > >> >> > On Tue, Jun 24, 2008 at 10:04 PM, Gilles Caulier >> >> > <[hidden email]> >> >> > wrote: >> >> >> >> >> >> > Hi all, >> >> >> > the freshly checked out and compiled exiv2/digikam >> >> >> >> >> >> Hum, if you using Exiv2 from trunk, the tiff writing mode branch >> >> >> have >> >> >> been recently merged to trunk and now Exiv2 become very unstable. >> >> >> >> >> >> I'm currently working with Exiv2 author to stabilize code. please >> >> >> revert to last stable Exiv2 0.17.1. Do not use yet Exiv2 from trunk >> >> >> (future 0.18) >> >> > >> >> > The same thing happened for me with Exiv2 0.17.1 and the new Digikam >> >> > 0.9.4-rc1. I haven't compiled in enough debugging symbols to get a >> >> > proper >> >> > backtrace. I will try to do this as soon as I have some time. >> >> > >> >> > Reverting back to Exiv2 0.16 and Digikam 0.9.4-beta5 works. I have >> >> > yet >> >> > to >> >> > try 0.16 with rc1. >> >> >> >> Warning : binary compatibility is not preserved between 0.16 and 0.17. >> >> if you don't recompile libkexiv2 used by digiKam and kipi-plugins you >> >> will see strange side effect... like crash (:=))) >> > >> > Oh, I just recompiled libkexiv2 when I updated to exiv2 0.17.1. Do I >> > need to >> > recompile kipi-plugins too? I thought they just used libkexiv2 to access >> > exiv2. Anyways, if I don't recompile libkexiv2 it complains about not >> > finding the correct library version, so that's a given. >> > >> >> >> >> To be sure, please recompile libkexiv2 and exiv2 with full debug info, >> >> and send me gdb trace to hack >> > >> > I'll try to get a back trace for you now before I fall asleep. Is it ok >> > to >> > attach it here, or should I link it from somewhere? >> > >> >> You can attach it here. attachement size to mailing list is limited to >> 40Kb > > No need for that it seems. I just recompiled kipi-plugins as well, to enable > debugging symbols, and now it doesn't crash. It seems that this was the > problem. I just thought that since the same version of libkexiv2 was used > for kipi-plugins, only recompiling libkexiv2 would be enough. Clearly I was > wrong. yes. you just need to recompile digiKam and kipi-plugins if you update libkexiv2... libkexiv2 is a C++/KDE wrapper around Exiv2. kipi-plugins and digiKam use it to play with metadata. If binary compatibility is preserved no need to re-compile clients program. This is the goal of a shared lib. In current libkexiv2 implementation, i have increased the BC again... > > So in short (if anyone else suffers the same problem): upgrade exiv2 to > 0.17.1, recompile libkexiv2 0.1.7, recompile kipi-plugins 0.1.5 and it > should work. > > Anyway, now it's working, so I'm happy. Thank you Gilles for your quick > replies and I'm sorry for wasting your time. You're doing a great job with > Digikam. No problem. And thanks. Gilles _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
In reply to this post by Markus Spring
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1 Markus Spring schrieb: | In the evening I will give Exiv2 0.17.1 a try. Ok, just checked with Exiv2 0.17.1: After make clean and full compilation everything works like a charm. Unfortunately rotating RAW images from the Sony A700 still does not work in exiv2... Best - Markus -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIYWKmxxUzQSse11ARAlAAAJ4/pf/QOldgEnm6ONzcr9RhzJ39OQCePqV8 prAbDWjkKT4VuDaXLixP40o= =fHWh -----END PGP SIGNATURE----- _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
2008/6/24 Markus Spring <[hidden email]>:
> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Markus Spring schrieb: > | In the evening I will give Exiv2 0.17.1 a try. > > Ok, just checked with Exiv2 0.17.1: After make clean and full compilation > everything works like a charm. > > Unfortunately rotating RAW images from the Sony A700 still does not work in exiv2... because, Exiv2 do not handle yet Sony MRW makernote (based on Minolta makernote) There is a file in Exiv2 bugzilla : http://dev.robotbattle.com/bugs/view.php?id=545 Best Gilles _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
Gilles Caulier schrieb:
> because, Exiv2 do not handle yet Sony MRW makernote (based on Minolta makernote) > > There is a file in Exiv2 bugzilla : > > http://dev.robotbattle.com/bugs/view.php?id=545 Yep, that was me who submitted it in the hope that this could get resolved... Markus _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
«
Return to digikam-users
|
1 view|%1 views
| Free forum by Nabble | Edit this page |