[digikam] [Bug 368167] crash on startup in geoiface QMutex::lock [cause: digikamrc]

[Hans-Peter via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368167

Hans-Peter  changed:

   What|Removed |Added

 CC||hans...@web.de

--- Comment #4 from Hans-Peter  ---
I can confirm what Jens wrote, exactly the same behavior on my machine. I have
Marble with OSM enabled.

HP

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 367970] New: Allow copyof EXIF, IPTC and XMP from one to another image

[Hans-Peter via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=367970

Bug ID: 367970
   Summary: Allow copyof EXIF, IPTC and XMP from one to another
image
   Product: digikam
   Version: 5.1.0
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Metadata
  Assignee: digikam-de...@kde.org
  Reporter: hans...@web.de

Digikam 4.14 and older had a feature to import EXIF and other meta data from
another image. Please implement this in 5.x as well.

Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 365079] Digikam 5.0 beta 7 crashes while showing the splash image.

[Hans-Peter via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365079

Hans-Peter  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #10 from Hans-Peter  ---
Surprise, surprise.

I vaguely remembered that someone had problems with the digikamrc file. So i
tried again, removed .config/digikamrc (from older beta 6) before.  And now
digikam5 from Philips ppa starts fine and i can start real testing or even go
and make new images :)

I think there should be an error message. 

Happy again. Thanks Philip and Gilles for the patience and support.

HP

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 365079] Digikam 5.0 beta 7 crashes while showing the splash image.

[Hans-Peter via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365079

--- Comment #9 from Hans-Peter  ---
Philip,

i also think its a problem with package dependencies. DK 5. beta 6 from your
repo did run, happily together with 14.04. Then suddenly it stopped working,
and from then on none of the 5.x did work, not even a self compiled version. So
my guess is that some Ubuntu library update messed up things. Probably
something with exiv2 or with marble.

Can it be that some Ubuntu libs meanwhile have newer versions like yours?

Regarding backtrace: first bug report has a back trace, but without full debug
info. Would full debug packages produce richer output?If so, give me some time,
this is a hell of installation. Debug packages seem to be depended on almost
everything and are huge.

HP

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 365079] Digikam 5.0 beta 7 crashes while showing the splash image.

[Hans-Peter via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365079

--- Comment #7 from Hans-Peter  ---
I tried normal update. No success, digikam5 crashes as described initially. I
then deinstalled everything from Phillips ppa and most libs with *kf5* or
marble. Reinstalled, no difference. I installed old 4.14 again, still works
(puuh!). So i give up on trying digikam5 for now and stay with 4.14 (which
works mostly nice). Maybe i try again in a month or so. However, if You have
ideas for producing more meaningful debug logs, pls. tell me.

I think what happens is called the "dependency hell" of libraries. Is this
better on FreeBSD?

HP

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 365079] Digikam 5.0 beta 7 crashes while showing the splash image.

[Hans-Peter via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365079

--- Comment #4 from Hans-Peter  ---
As i wrote in previous messages, i did compile it on my Linux box, no
difference to the pre-packed binaries. 

HP

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 365079] Digikam 5.0 beta 7 crashes while showing the splash image.

[Hans-Peter via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365079

--- Comment #2 from Hans-Peter  ---
Thats also what i suspect.

I hoped a version build on my system would do better. And an older version (b6)
did run. So either some Ubuntu update destroyed things or some cutting-edge lib
from the digikam ppa. And i probably also messed up my system when trying to
resolve this by deinstalling or reinstalling things. Oh hell, what happened to
good old static binaries?

Sorry, not the developers fault, but i really love digikam and really would
like to have a stable environment. Does digikam.exe run under wine? (joking,
partially)  

HP

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 365079] New: Digikam 5.0 beta 7 crashes while showing the splash image.

[Hans-Peter via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365079

Bug ID: 365079
   Summary: Digikam 5.0 beta 7 crashes while showing the splash
image.
   Product: digikam
   Version: 5.5.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: digikam-de...@kde.org
  Reporter: hans...@web.de

Version 4.14 runs fine. Tested with pre-compiled packages from Philips Johnsons
Ubuntu ppa and with a self compiled version from git. Showfoto from these
source starts fine.

hph@hackbrett-PC:~/sw/digikam/dk/build/core/app$ gdb ./digikam
GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.04) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./digikam...done.
(gdb) catch throw
Haltepunkt 1 (throw)
(gdb) run
Starting program: /home/hph/sw/digikam/dk/build/core/app/digikam 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffc940c700 (LWP 17550)]
[New Thread 0x7fffc6835700 (LWP 17551)]
digikam.general: AlbumWatch use QFileSystemWatcher
[New Thread 0x7fffc5757700 (LWP 17552)]
QFileSystemWatcher::removePaths: list is empty
digikam.general: Database Parameters:
   Type: "QSQLITE"
   DB Core Name: "/home/hph/Fotos/digicam/digikam4.db"
   DB Thumbs Name:   "/home/hph/Fotos/digicam/thumbnails-digikam.db"
   DB Face Name: "/home/hph/Fotos/digicam/recognition.db"
   Connect Options:  ""
   Host Name:""
   Host port:-1
   Internal Server:  false
   Internal Server Path: ""
   Internal Server Serv Cmd: "mysqld_safe"
   Internal Server Init Cmd: "mysql_install_db"
   Username: ""
   Password: ""

[New Thread 0x7fffc4f56700 (LWP 17553)]
[Thread 0x7fffc4f56700 (LWP 17553) exited]
digikam.dbengine: Loading SQL code from config file
"/usr/share/digikam/database/dbconfig.xml"
digikam.dbengine: Checking XML version ID => expected:  3  found:  3
digikam.coredb: Core database: running schema update
digikam.coredb: Core database: have a structure version  7
digikam.coredb: Core database: makeUpdates  7  to  7
digikam.database: Creating new Location  "/digicam"  uuid 
"volumeid:?uuid=0b2d3b0e-f1e1-4842-9748-132524d7e7f6"
digikam.database: location for  "/home/hph/Fotos/digicam"  is available  true
KMemoryInfo: Platform identified :  "LINUX"
KMemoryInfo: TotalRam:  8102973440
digikam.general: Allowing a cache size of 200 MB
digikam.thumbsdb: ThumbDB SelectThumbnailSetting val ret =  0
digikam.thumbsdb: ThumbDB SelectThumbnailSetting val ret =  0
digikam.thumbsdb: Thumbs database: have a structure version  "3"
digikam.general: Thumbnails database ready for use
digikam.database: Complete scan (file scanning deferred) took: 874 msecs.
digikam.dimg: ("/usr/share/color/icc", "/home/hph/.local/share/icc")
digikam.dimg: No X.org XICC profile installed for screen  0
[New Thread 0x7fffc4f56700 (LWP 17554)]
digikam.general: Camera XML data:  "/home/hph/.local/share/digikam/cameras.xml"
defaultServiceProvider::requestService(): no service found for -
"org.qt-project.qt.mediaplayer"
digikam.facedb: FaceDB SelectFaceSetting val ret =  0
digikam.facedb: FaceDB SelectFaceSetting val ret =  0
digikam.facedb: Face database: have a structure version  "2"
digikam.facesengine: Face database ready for use
digikam.facesengine: Face database ready for use
[New Thread 0x7fffb48a9700 (LWP 17555)]
digikam.geoiface: "setting backend marble"
defaultServiceProvider::requestService(): no service found for -
"org.qt-project.qt.mediaplayer"
digikam.general: Stacked View Mode :  0
digikam.geoiface: "setting backend marble"
digikam.general: "browse_album"
digikam.general: "browse_tag"
digikam.general: "browse_labels"
digikam.general: "browse_date"
digikam.general: "browse_timeline"
digikam.general: "browse_search"
digikam.general: "browse_fuzzysearch"
digikam.general: "browse_gpssearch"
digikam.general: "browse_people"
digikam.dimg: variant:  QVariant(Digikam::LensFunIface::DevicePtr, )
digikam.dimg: dev:  Asahi Optical Co.,Ltd  ::  Pentax Optio 430  ::  4.85
digikam.dimg: Search for camera  "" - ""  ==> false
digikam.dimg: Search for lens  ""  ==> f

[digikam] [Bug 364563] digiKam crashes when browsing albums, only for images in portrait format

[Hans-Peter via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=364563

Hans-Peter  changed:

   What|Removed |Added

 Status|RESOLVED|CLOSED

--- Comment #5 from Hans-Peter  ---
As you already said in the last reply, it seems to be an issue with libexiv2. I
just updated again to libexiv2 from Phillip Johnsons ppa, and it does also work
again. Strange :)
So i can no longer reproduce the bug. Please close the issue.

Thanks for looking into this.

HP

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 364563] digiKam crashes when browsing albums, only for images in portrait format

[Hans-Peter via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=364563

--- Comment #2 from Hans-Peter  ---
I can provide a sample, but how? Just attach it here in the bugs.kde.org ?

Additional info: it seems that it crashes only with portrait mode images from
my new Sony A77ii, older images can be browsed without crash. I just
de-installed exiv2 from Phillip Johnsons ppa and installed the older
libgexif2-2 from Ubuntu repos instead, this seem to work stable.

HP

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 364563] New: digiKam crashes when browsing albums, only for images in portrait format

[Hans-Peter via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=364563

Bug ID: 364563
   Summary: digiKam crashes when browsing albums, only for images
in portrait format
   Product: digikam
   Version: 4.14.0
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: Albums View
  Assignee: digikam-de...@kde.org
  Reporter: hans...@web.de

I use Digikam 14.4 from in Xubuntu 16.04 from Philip Johnsons PPA. Since some
days, digikam crashes in album view when going from one image to the next, but
only if the next image is in portrait format. Same crash occurs *sometimes*
when selecting (double click) the first image in an album and this is a
portrait format.



Reproducible: Always

Steps to Reproduce:
1. select album with mix of landscape and portrait images. Select a landscape
image, click for the next one until you reach a portrait format image. Crash. 




gdb digikam
GNU gdb (Ubuntu 7.11-0ubuntu1) 7.11
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from digikam...Reading symbols from
/usr/lib/debug/.build-id/b5/06929a2606d2341c5a32f3dbdb52da5ed76321.debug...done.
done.
(gdb) RUN
Starting program: /usr/bin/digikam 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffcbf61700 (LWP 4980)]
[New Thread 0x7fffc7cc6700 (LWP 4982)]
[New Thread 0x7fffc74c5700 (LWP 4983)]
[New Thread 0x7fffc6cc4700 (LWP 4984)]
[Thread 0x7fffc6cc4700 (LWP 4984) exited]
[New Thread 0x7fffc6cc4700 (LWP 4987)]
[Thread 0x7fffcbf61700 (LWP 4980) exited]
[New Thread 0x7fffc4a96700 (LWP 4990)]
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
QDBusConnection: session D-Bus connection created before QCoreApplication.
Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication.
Application may misbehave.
kbuildsycoca4 running...
[New Thread 0x7fffb628a700 (LWP 5000)]
[Thread 0x7fffb628a700 (LWP 5000) exited]
[New Thread 0x7fffb628a700 (LWP 5001)]
[New Thread 0x7fffabffe700 (LWP 5002)]
[Thread 0x7fffb628a700 (LWP 5001) exited]
[Thread 0x7fffabffe700 (LWP 5002) exited]
[New Thread 0x7fffabffe700 (LWP 5003)]
[New Thread 0x7fffb628a700 (LWP 5004)]
[New Thread 0x7fffab113700 (LWP 5005)]
[New Thread 0x7fffaa912700 (LWP 5006)]
[New Thread 0x7fffaa111700 (LWP 5007)]
[New Thread 0x7fffa9910700 (LWP 5008)]
[New Thread 0x7fffa910f700 (LWP 5009)]
[New Thread 0x7fffa890e700 (LWP 5010)]
[New Thread 0x7fff83fff700 (LWP 5011)]
[New Thread 0x7fff8bfff700 (LWP 5012)]
[New Thread 0x7fff8b7fe700 (LWP 5013)]
[New Thread 0x7fff8affd700 (LWP 5014)]
[New Thread 0x7fff8a7fc700 (LWP 5015)]
[New Thread 0x7fff89ffb700 (LWP 5016)]
[New Thread 0x7fff897fa700 (LWP 5017)]
[New Thread 0x7fff88ff9700 (LWP 5018)]
[New Thread 0x7fff837fe700 (LWP 5019)]
[New Thread 0x7fff82ffd700 (LWP 5020)]
[New Thread 0x7fff827fc700 (LWP 5021)]
[New Thread 0x7fff81ffb700 (LWP 5022)]
[New Thread 0x7fff817fa700 (LWP 5023)]
[New Thread 0x7fff80ff9700 (LWP 5024)]
[New Thread 0x7fff73fff700 (LWP 5025)]
[New Thread 0x7fff737fe700 (LWP 5026)]
[New Thread 0x7fff72ffd700 (LWP 5027)]
[New Thread 0x7fff727fc700 (LWP 5028)]
[New Thread 0x7fff71ffb700 (LWP 5029)]
[New Thread 0x7fff717fa700 (LWP 5030)]
[New Thread 0x7fff70ff9700 (LWP 5031)]
[New Thread 0x7fff707f8700 (LWP 5032)]
[New Thread 0x7fff6fff7700 (LWP 5033)]
[New Thread 0x7fff6f7f6700 (LWP 5034)]
[New Thread 0x7fff6eff5700 (LWP 5035)]
[New Thread 0x7fff6e7f4700 (LWP 5036)]
[New Thread 0x7fff6dff3700 (LWP 5037)]
[New Thread 0x7fff6d7f2700 (LWP 5038)]
[New Thread 0x7fff5d289700 (LWP 5063)]
[New Thread 0x7fff5ca88700 (LWP 5064)]
[New Thread 0x7fff62e17700 (LWP 5066)]
[New Thread 0x7fff61f94700 (LWP 5068)]
[New Thread 0x7fff61793700 (LWP 5069)]

Thread 50 "Thread (pooled)" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fff61f94700 (LWP 5068)]
Digikam::ImageHistogram::calculate (this=0x40cb260) at
/build/digikam-lwP2T0/digikam-4.14.0/core/libs/dimg/filters/levels/imagehistogram.cpp:237
237   
/build/digikam-lwP2T0/digikam-4.14.0/core/libs/dimg/filters/levels/imagehistogram.cpp:
Datei oder Verzeichnis nicht gefunden.
(gdb) bt
#0  Digikam::ImageHistogram::cal