[KPhotoAlbum] Problems with libkgeomap - again

[Johannes Zarl-Zierl]

Hello Matthias,

Glad to hear that the problem disappeared for you!

Thanks for the stack trace - it allowed me to find a possible root cause of 
the crash. This should be fixed in commit 8dbfadf.

Cheers,
  Johannes


On Sunday 14 February 2016 14:08:47 Matthias Heukäufer wrote:
> It is more than a bit embarrassing, but it seems that my problem has
> disappeared. I was absolutely sure that I had tried every possible
> combination of different KPhotoalbum/ KGeomap-versions and installation
> paths, but it seems that I have missed something.
> Anyway, I compiled 4.6.2 again from a freshly downloaded source and now
> it works (well, sort of: I have to reload EXIF-information a couple of
> times for every picture to have it shown at the correct location, but at
> least KPhotoalbum runs stable again).
> Maybe 'make clean' had not taken care of all relevant files.
> Since I have already wasted so much of everybody's time, I will stick
> with what I have for now and wait for kgeomap to become available as a
> regular Debian package.
> 
> Thank you and please apologize the confusion - Matthias
> 
> On 13.02.2016 21:16, Johannes Zarl-Zierl wrote:
> > Hi Matthias,
> > 
> > On Friday 12 February 2016 14:35:48 Matthias Heukäufer wrote:
> >> Whenever I start kphotoalbum (both with my real database or the demo
> >> database), the program crashes a few seconds after I open the thumbnail
> >> viewer.
> >> On the terminal I get the following error message:
> >> ASSERT: "!fileName.isNull()" in file
> >> /home/matthias/temp/kphotoalbum-4.7/ThumbnailView/ThumbnailModel.cpp,
> >> line 179
> > 
> > I did a quick look into possible connections between this failed assert
> > and
> > kgeomap, but I couldn't find anything obvious.
> > If you can provide a full stack trace (from the KDE crash handler), this
> > would be easier to debug.
> > 
> >> When I build the program without kgeomap, it runs fine.
> >> Does anybody have an idea how I could solve this?
> > 
> > The most valuable info is probably a stack trace. To get a good stack
> > trace, it's a good idea to set the CMAKE_BUILD_TYPE to Debug when you run
> > cmake...
> > 
> > HTH,
> > 
> >    Johannes
> > 
> > P.S.: I probably won't be able to get into this before next weekend, so
> > please be patient ;-)
> > 
> > _______________________________________________
> > KPhotoAlbum mailing list
> > KPhotoAlbum at mail.kdab.com
> > https://mail.kdab.com/mailman/listinfo/kphotoalbum