Page 1 of 2 12 LastLast
Results 1 to 10 of 19

Thread: digikam 4.3.0

  1. #1
    Join Date
    Oct 2009
    Location
    Sweden
    Posts
    1,015

    Default digikam 4.3.0

    Running opensuse_64 13.1 bottle, KDE4.14.1.
    I did a weekly zypper on my main desktop and my laptop yesterday. Somehow digikam 4.3.0(build date 17 September) have been corrupted and crash one time after another. I started up a VM openSUSE factory who has digikam 4.2.0 and it works like a charm against the same network share.

    Anybody else experience this?


    regards
    I'm shameless like others in the forum -was I to any help or made sense? If yes: click the on the star below to the left. Written whit a ;-) in my eye.

  2. #2
    Join Date
    Sep 2014
    Location
    Wien
    Posts
    5

    Default Re: digikam 4.3.0

    Same for me.

    I managed to reduce the number of crashes by turning off the feature "show images from subfolders" (that's not the original wording, but my back-translation from the language my system is configured to use). This way, there are less thumbnails to be shown at a time, and sometimes (especially when selecting a folder containing not too many images) I am able to use digikam for up to three or four minutes before it crashes.

    I am a bit disappointed because the end-user software is so buggy and unstable, and because OpenSUSE updates occasionally break things. I never had these problems with Ubuntu - either they are lucky, or they must be thoroughly *testing* packages before releasing them...

  3. #3

    Default Re: digikam 4.3.0

    Quote Originally Posted by Ente View Post
    I am a bit disappointed because the end-user software is so buggy and unstable, and because OpenSUSE updates occasionally break things.
    ???
    I hope you do realize that there never was an official openSUSE update to digikam 4.3.0.
    The current version in the update repo for 13.1 is 3.5.0.

    You are using inofficial 3rd party repos, so don't complain about openSUSE's updates breaking things and openSUSE being so buggy and unstable.

    That said, some more information might help.
    Like running digikam in a terminal window and posting the last lines of output when it crashes.
    Or at least describing in more details what you do that makes it crash. I just tried and cannot reproduce a crash here...

    Then maybe filing a bug report at KDE would be a good idea (including a backtrace).
    The developers could then investigate the crash and fix it.

    And if you want to have a stable version, switch back to 3.5.0 from the update repo.

  4. #4
    Join Date
    Jun 2008
    Location
    Florida, USA
    Posts
    970

    Default Re: digikam 4.3.0

    I am also running 13.1 with KDE 4.14.1
    I have the KDE Core and Core Extras repos enabled. I suspect that your Digikam 4.3.0 is installed from Core Extras.

    When 4.3.0 was first released, there were numerous issues due to a libKexiv2 patch that need to be installed.
    That "seemed" to affect some folks who manage videos as well as images, did not affect me.

    Since you mention that your managed assets (images, videos) are on a network share, then I presume you run Digikam with mysql.
    I do not, so you may need to dig into that aspect.
    Starting Digiikam from the CLI is always a good way to get extra information and messages.
    I'll also observe that Digikam upgrades frequently modify the database schemas as new features are added, and many folks have issues going 'backwards" once a schema has been modified by the upgrade (e.g. 4.3.0 back to 4.0.0).

    I suggest you subscribe to the Digikam mailing list via https://www.digikam.org/support where these issues get discussed and identified, if not fixed. Almost always, the fixes require a local compile (by you) or a wait for the correction to propagate thru the packaging process.

    There you will see how difficult it is for the DK developers to manage the update complexity across the various Linus distros, as well as Win and OSX.
    IMHO, the openSUSE packagers for Digikam do an excellent job keeping up with the rapidly evolving Digikam application for those of us who want to stay bleeding edge with this application. If you prefer stability, keep an eye on the mailing list for initial issues to subside before upgrading your version.

    My Digikam is version 4.3.0-19.2 from the KDE Core Extras Repo, has been stable for a couple days now.
    Also, open Digikam and look in Help - Component Information.
    This seems the best way to navigate the 'version' discussions, where the issues almost always reside.
    Version numbering gets somewhat muddled in the packaging and build process.
    Compare what you have installed to this list, which for me is currently working well.

    Code:
    digiKam version 4.3.0
    CPU cores: 4
    Demosaic GPL2 pack support: Unknown
    Demosaic GPL3 pack support: Unknown
    Exiv2 can write to Jp2: Yes
    Exiv2 can write to Jpeg: Yes
    Exiv2 can write to Pgf: Yes
    Exiv2 can write to Png: Yes
    Exiv2 can write to Tiff: Yes
    Exiv2 supports XMP metadata: Yes
    LibCImg: 130
    LibEigen: 3.2.0
    LibExiv2: 0.23
    LibJPEG: 80
    LibJasper: 1.900.1
    LibKDE: 4.14.1
    LibKExiv2: 2.3.1
    LibKGeoMap: 2.0.0
    LibKdcraw: 2.4.2
    LibLCMS: 119
    LibLensFun: 0.2.8-0
    LibPGF: 6.12.24 - external shared library
    LibPNG: 1.6.6
    LibQt: 4.8.5
    LibRaw: 0.15.4
    LibTIFF: LIBTIFF, Version 4.0.3 Copyright (c) 1988-1996 Sam Leffler Copyright (c) 1991-1996 Silicon Graphics, Inc.
    Marble Widget: 0.19.0 (stable release)
    Parallelized PGF codec: No
    Parallelized demosaicing: Unknown
    RawSpeed codec support: Unknown
    Database backend: QSQLITE
    Kdepimlibs support: Yes
    Kipi-Plugins: 4.3.0
    LibGphoto2: 2.5.2.1
    LibKface: 3.4.0
    LibKipi: 2.1.0
    LibOpenCV: 2.4.9
    Desk: i7-4790K Leap 15.1(x86_64)4.12.14-lp151.28.7-default KF5 59.0 Plasma 5.14.4 Qt 5.13.0
    Lap: HPDV7T i7 Leap 15.0(x86_64)4.12.14-lp151.28.7-default KF5 59.0 Plasma 5.14.4 Qt 5.13.0

  5. #5
    Join Date
    Oct 2009
    Location
    Sweden
    Posts
    1,015

    Default Re: digikam 4.3.0

    According to digikam SQLite is used for the data base. Installed version is:
    4.3.0-19.2 from vendor obs://build.opensuse.org/KDE

    Tested version:
    4.3.0-19.1 from KDE:Extra with priority 99 and vendor obs://build.opensuse.org/KDE -with no luck. The same problem.


    But I can see some pattern, directly when try to click the directorys below(a lot of directorys work a-ok) in digikam:

    Code:
    digikam
    Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
    Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
    QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in use, all queries will cease to work.
    digikam(2637)/KEXIV2: Cannot load metadata from file   (Error # 11 :  /home/*****/vol2/My Pictures/Norsbo/3 HÃSTTÃVLING.jpg: The file contains data of an unknown image type 
    digikam(2637)/KEXIV2: Cannot load metadata using Exiv2   (Error # 11 :  /home/*****/vol2/My Pictures/Norsbo/3 HÃSTTÃVLING.jpg: The file contains data of an unknown image type 
    KCrash: Application 'digikam' crashing...
    KCrash: Attempting to start /usr/lib64/kde4/libexec/drkonqi from kdeinit
    sock_file=/home/jodot/.kde4/socket-jodotpc/kdeinit4__0
    digikam(2637)/KEXIV2: Cannot load metadata from file   (Error # 11 :  /home/*****/vol2/My Pictures/Norsbo/3 HÃSTTÃVLING.jpg: The file contains data of an unknown image type 
    digikam(2637)/KEXIV2: Cannot load metadata using Exiv2   (Error # 11 :  /home/*****/vol2/My Pictures/Norsbo/3 HÃSTTÃVLING.jpg: The file contains data of an unknown image type 
    Unable to start Dr. Konqi
    [1]+  Exit 253
    Code:
    digikam
    Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
    Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
    QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in use, all queries will cease to work.
    digikam(2720)/KEXIV2: Cannot load metadata from file   (Error # 11 :  /home/jodot/vol2/My Pictures/England 2002-10/MOV01235.MPG: The file contains data of an unknown image type 
    digikam(2720)/KEXIV2: Cannot load metadata using Exiv2   (Error # 11 :  /home/jodot/vol2/My Pictures/England 2002-10/MOV01235.MPG: The file contains data of an unknown image type 
    KCrash: Application 'digikam' crashing...
    KCrash: Attempting to start /usr/lib64/kde4/libexec/drkonqi from kdeinit
    sock_file=/home/jodot/.kde4/socket-jodotpc/kdeinit4__0
    QSocketNotifier: Invalid socket 10 and type 'Read', disabling...
    QSocketNotifier: Invalid socket 13 and type 'Read', disabling...
    QSocketNotifier: Invalid socket 16 and type 'Read', disabling...
    QSocketNotifier: Invalid socket 61 and type 'Read', disabling...
    QSocketNotifier: Invalid socket 64 and type 'Read', disabling...
    QSocketNotifier: Invalid socket 62 and type 'Read', disabling...
    digikam: Fatal IO error: client killed
    Code:
    digikam
    Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
    Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
    QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in use, all queries will cease to work.
    digikam(3488)/KEXIV2: Cannot load metadata from file   (Error # 11 :  /home/*****/vol2/My Pictures/unsorted1/MOV01980.MPG: The file contains data of an unknown image type 
    digikam(3488)/KEXIV2: Cannot load metadata using Exiv2   (Error # 11 :  /home/*****/vol2/My Pictures/unsorted1/MOV01980.MPG: The file contains data of an unknown image type 
    KCrash: Application 'digikam' crashing...
    KCrash: Attempting to start /usr/lib64/kde4/libexec/drkonqi from kdeinit
    sock_file=/home/jodot/.kde4/socket-jodotpc/kdeinit4__0
    digikam: Fatal IO error: client killed
    
    [1]+  Stopped                 digikam
    jodot@jodotpc:~> QSocketNotifier: Invalid socket 14 and type 'Read', disabling...
    ^C
    [1]+  Exit 253                digikam
    Code:
    digikam
    Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
    Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
    QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in use, all queries will cease to work.
    digikam(2805)/KEXIV2: Cannot load metadata from file   (Error # 11 :  /home/*****/vol2/My Pictures/Saudi Arabia/Riyadh3/MOV01400.MPG: The file contains data of an unknown image type 
    digikam(2805)/KEXIV2: Cannot load metadata using Exiv2   (Error # 11 :  /home/*****/vol2/My Pictures/Saudi Arabia/Riyadh3/MOV01400.MPG: The file contains data of an unknown image type 
    KCrash: Application 'digikam' crashing...
    KCrash: Attempting to start /usr/lib64/kde4/libexec/drkonqi from kdeinit
    sock_file=/home/jodot/.kde4/socket-jodotpc/kdeinit4__0
    digikam: Fatal IO error: client killed
    The above directorys work a-ok in 13.2_64 KDE Factory and Digikam 4.2.0 (tested today again).

    I will wait some more days before try again.

    How it look like when I only test some directorys and not let digikam to crash but close it "normal":

    Code:
    digikam
    Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
    Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
    QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in use, all queries will cease to work.
    libpng warning: iCCP: known incorrect sRGB profile
    digikam(4036) KWidgetItemDelegateEventListener::eventFilter: User of KWidgetItemDelegate should not delete widgets created by createItemWidgets! 
    digikam(4036) KWidgetItemDelegateEventListener::eventFilter: User of KWidgetItemDelegate should not delete widgets created by createItemWidgets! 
    digikam(4036) KWidgetItemDelegateEventListener::eventFilter: User of KWidgetItemDelegate should not delete widgets created by createItemWidgets! 
    digikam(4036) KWidgetItemDelegateEventListener::eventFilter: User of KWidgetItemDelegate should not delete widgets created by createItemWidgets! 
    digikam(4036) KWidgetItemDelegateEventListener::eventFilter: User of KWidgetItemDelegate should not delete widgets created by createItemWidgets! 
    digikam(4036) KWidgetItemDelegateEventListener::eventFilter: User of KWidgetItemDelegate should not delete widgets created by createItemWidgets! 
    digikam(4036) KWidgetItemDelegateEventListener::eventFilter: User of KWidgetItemDelegate should not delete widgets created by createItemWidgets! 
    digikam(4036) KWidgetItemDelegateEventListener::eventFilter: User of KWidgetItemDelegate should not delete widgets created by createItemWidgets! 
    digikam(4036) KWidgetItemDelegateEventListener::eventFilter: User of KWidgetItemDelegate should not delete widgets created by createItemWidgets! 
    digikam(4036) KWidgetItemDelegateEventListener::eventFilter: User of KWidgetItemDelegate should not delete widgets created by createItemWidgets! 
    digikam(4036) KWidgetItemDelegateEventListener::eventFilter: User of KWidgetItemDelegate should not delete widgets created by createItemWidgets! 
    digikam(4036) KWidgetItemDelegateEventListener::eventFilter: User of KWidgetItemDelegate should not delete widgets created by createItemWidgets! 
    digikam(4036) KWidgetItemDelegateEventListener::eventFilter: User of KWidgetItemDelegate should not delete widgets created by createItemWidgets! 
    digikam(4036) KWidgetItemDelegateEventListener::eventFilter: User of KWidgetItemDelegate should not delete widgets created by createItemWidgets!
    regards
    Last edited by jonte1; 23-Sep-2014 at 08:52. Reason: spellcheck (dont laught)!
    I'm shameless like others in the forum -was I to any help or made sense? If yes: click the on the star below to the left. Written whit a ;-) in my eye.

  6. #6

    Default Re: digikam 4.3.0

    This problem is probably KDE bug 339144
    https://bugs.kde.org/show_bug.cgi?id=339144

  7. #7
    Join Date
    Jun 2008
    Location
    Florida, USA
    Posts
    970

    Default Re: digikam 4.3.0

    The noted bug 339144 is a potential source of trouble.
    The updated library will be libkexiv2 2.3.2

    As you can see, my current install still runs OK with version 2.3.1

    I think the issue is dependent on how much metadata manipulation you have stored.


    Database:
    Older Digikams required mysql (or equiv) when running with network file systems.
    More recent versions are partially operational when sqlite is used, but see the FAQ item here:
    https://www.digikam.org/node/219

    Appears there are still some issues. Some suggested fixes are found in that reference.
    Desk: i7-4790K Leap 15.1(x86_64)4.12.14-lp151.28.7-default KF5 59.0 Plasma 5.14.4 Qt 5.13.0
    Lap: HPDV7T i7 Leap 15.0(x86_64)4.12.14-lp151.28.7-default KF5 59.0 Plasma 5.14.4 Qt 5.13.0

  8. #8
    Join Date
    Oct 2009
    Location
    Sweden
    Posts
    1,015

    Default Re: digikam 4.3.0

    I noticed that apper had some updates today, among them DigiKam to 4.3.0-20.1. Runned a zypper dup, booted but it was still the same problem and crashed trying to open the same directories.

    Deleted digikam 4.3.0 in YaST2 and then went to http://download.opensuse.org/factory...s/suse/x86_64/ and downloaded digikam-4.2.0-2.1.2.x86_64.rpm and install it. Digikam still complaining about the same files/directories but do not crash any longer. So I'm pleased for the moment. I have locked digikam 4.2.0 in YaST2/software manager.

    Code:
    digikam
    Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
    Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
    QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in use, all queries will cease to work.
    digikam(3063)/KEXIV2: Cannot load metadata from file   (Error # 11 :  /home/*****/vol2/My Pictures/Saudi Arabia/Riyadh3/MOV01400.MPG: The file contains data of an unknown image type 
    digikam(3063)/digikam (core) Digikam::ThumbnailCreator::createThumbnail: Cannot create thumbnail for  "/home/*****/vol2/My Pictures/Saudi Arabia/Riyadh3/MOV01400.MPG" 
    digikam(3063)/digikam (core) Digikam::ThumbnailCreator::load: Thumbnail is null for  "/home/*****/vol2/My Pictures/Saudi Arabia/Riyadh3/MOV01400.MPG" 
    digikam(3063)/KEXIV2: Cannot load metadata from file   (Error # 11 :  /home/jodot/vol2/My Pictures/Saudi Arabia/Riyadh3/MOV01408.MPG: The file contains data of an unknown image type 
    digikam(3063)/digikam (core) Digikam::ThumbnailCreator::createThumbnail: Cannot create thumbnail for  "/home/*****/vol2/My Pictures/Saudi Arabia/Riyadh3/MOV01408.MPG" 
    digikam(3063)/digikam (core) Digikam::ThumbnailCreator::load: Thumbnail is null for  "/home/*****/vol2/My Pictures/Saudi Arabia/Riyadh3/MOV01408.MPG" 
    digikam(3063)/KEXIV2: Cannot load metadata from file   (Error # 11 :  /home/*****/vol2/My Pictures/Norsbo/3 HÃSTTÃVLING.jpg: The file contains data of an unknown image type 
    digikam(3063)/digikam (core) Digikam::ThumbnailCreator::createThumbnail: Cannot create thumbnail for  "/home/*****/vol2/My Pictures/Norsbo/3 HÄSTTÄVLING.jpg" 
    digikam(3063)/digikam (core) Digikam::ThumbnailCreator::load: Thumbnail is null for  "/home/j*****/vol2/My Pictures/Norsbo/3 HÄSTTÄVLING.jpg" 
    digikam(3063)/KEXIV2: Cannot load metadata from file   (Error # 11 :  /home/*****/vol2/My Pictures/Norsbo/3 HÃSTTÃVLING.jpg: The file contains data of an unknown image type 
    digikam(3063)/KEXIV2: Cannot load metadata from file   (Error # 11 :  /home/*****/vol2/My Pictures/Gamla Berget 2010/Gamla Berget 2010-2/MVI_0016.MOV: The file contains data of an unknown image type 
    digikam(3063)/digikam (core) Digikam::ThumbnailCreator::createThumbnail: Cannot create thumbnail for  "/home/*****/vol2/My Pictures/Gamla Berget 2010/Gamla Berget 2010-2/MVI_0016.MOV" 
    digikam(3063)/digikam (core) Digikam::ThumbnailCreator::load: Thumbnail is null for  "/home/*****/vol2/My Pictures/Gamla Berget 2010/Gamla Berget 2010-2/MVI_0016.MOV"
    regards
    Last edited by jonte1; 24-Sep-2014 at 08:15. Reason: added info
    I'm shameless like others in the forum -was I to any help or made sense? If yes: click the on the star below to the left. Written whit a ;-) in my eye.

  9. #9

    Default Re: digikam 4.3.0

    Good news!
    The fixes from the mentioned bug report have been added to digikam in KDE:Extra right now:
    https://build.opensuse.org/package/r...ev=base&rev=21

    So if you're lucky, your problems might be fixed with the next update...

  10. #10
    Join Date
    Oct 2009
    Location
    Sweden
    Posts
    1,015

    Default Re: digikam 4.3.0

    Installed Digikam 4.3.0-24.1 (via zypper) on Thursday on 2 PC's, -works like a charm and I cant any see any messages about problems when start from a konsole(terminal). Subjective I feel that it is slower when starting up (init database->network drive).

    Another thing that has been touched before and in this tread, -I have a NFS share on my server contains my pictures mounted as a local directory in my PC's. Setting up Digikam I point out the local directory as a source for the pictures, means that Digikam read the local directory and openSUSE takes care of the communication with the network share. Or?

    Is this still considered as a network drive in Digikam? Why I asking? Could be good to know next time I'm post .

    regards
    I'm shameless like others in the forum -was I to any help or made sense? If yes: click the on the star below to the left. Written whit a ;-) in my eye.

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •