Version: 1.9.0 (using KDE 4.6.5) OS: Linux I start didgikam from command line, and I get KGlobal::locale::Warning your global KLocale is being recreated with a valid main component instead of a fake component, this usually means you tried to call i18n related functions before your main component was created. You should not do that since it most likely will not work QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in use, all queries will cease to work. Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) kbuildsycoca4 running... kbuildsycoca4(14017) KConfigGroup::readXdgListEntry: List entry x-scheme-handler/file in "/home/apu/.local/share/applications/mimeapps.list" is not compliant with XDG standard (missing trailing semicolon). kbuildsycoca4(14017) KConfigGroup::readXdgListEntry: List entry x-scheme-handler/trash in "/home/apu/.local/share/applications/mimeapps.list" is not compliant with XDG standard (missing trailing semicolon). The message in didgikam's window is "Initializing Main View" Reproducible: Always Steps to Reproduce: Write digikam& in command line. Expected Results: Doesn't hang, obviously. I am running digikam under gnome, but it does the same thing under KDE on my box. On my Ubuntu laptop, no problem starting! Ubuntu is the latest stable, natty 11.04.
Sound like you installation is broken... I recommend to use 2.x release. 1.9.0 is not maintained anymore... Gilles Caulier
Thx for speedy response. I fixed the trailing semicolons in the mimeapps.list file, and installed digikam 2.2 via the ppa given on the digikam website. I get $ digikam & [1] 2086 apu@apu-desktop:~$ QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in use, all queries will cease to work. Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) kbuildsycoca4 running... kbuildsycoca4 running... and digikam hangs at the same stage: Initializing main view.
Sound like a problem with your Qt4 shared library installation, or another shared component. Try to uninstall all previous and current version of digiKam and re-install it... Gilles Caulier
Well, I did $ sudo apt-get remove digikam [sudo] password for apu: Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: libkface-data libswscale2 kipi-plugins libkface1 libavutil51 kipi-plugins-common libopencv-legacy2.3 libopencv-imgproc2.3 libkdcraw-20 libopencv-objdetect2.3 libopencv-calib3d2.3 libtbb2 libopencv-ml2.3 libopencv-features2d2.3 libopencv-objdetect2.3-data libopencv-video2.3 libavcodec53 digikam-data libopencv-core2.3 libopenni libopencv-flann2.3 libopencv-gpu2.3 liblensfun-data liblensfun0 libkexiv2-10 libavformat53 libexiv2-11 libopencv-contrib2.3 openni-utils libkgeomap-data libkgeomap1 libopencv-highgui2.3 Use 'apt-get autoremove' to remove them. The following packages will be REMOVED: digikam 0 upgraded, 0 newly installed, 1 to remove and 33 not upgraded. After this operation, 14,7 MB disk space will be freed. Do you want to continue [Y/n]? y (Reading database ... 445490 files and directories currently installed.) Removing digikam ... Processing triggers for gnome-menus ... Processing triggers for desktop-file-utils ... Processing triggers for bamfdaemon ... Rebuilding /usr/share/applications/bamf.index... Processing triggers for man-db ... Processing triggers for libc-bin ... ldconfig deferred processing now taking place apu@apu-desktop:~$ sudo apt-get install digikam Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: digikam-doc The following NEW packages will be installed: digikam 0 upgraded, 1 newly installed, 0 to remove and 33 not upgraded. Need to get 0 B/3.966 kB of archives. After this operation, 14,7 MB of additional disk space will be used. Selecting previously deselected package digikam. (Reading database ... 445457 files and directories currently installed.) Unpacking digikam (from .../digikam_2%3a2.2.0-natty~ppa3_amd64.deb) ... Processing triggers for man-db ... Processing triggers for gnome-menus ... Processing triggers for desktop-file-utils ... Processing triggers for bamfdaemon ... Rebuilding /usr/share/applications/bamf.index... Setting up digikam (2:2.2.0-natty~ppa3) ... Processing triggers for libc-bin ... ldconfig deferred processing now taking place apu@apu-desktop:~$ digikam --version Qt: 4.7.2 KDE Development Platform: 4.6.5 (4.6.5) digiKam: 2.2.0 apu@apu-desktop:~$ digikam & [1] 18789 apu@apu-desktop:~$ QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in use, all queries will cease to work. Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) kbuildsycoca4 running... But still the same problem.
Run kdebugdialog, active digiKam/libkipi/libkexiv2/libkdcraw debug space and re-run digiKam from the console Gilles Caulier
In .xsession-errors, I have Window manager warning: Invalid WM_TRANSIENT_FOR window 0x2e00004 specified for 0x2e000b8 (digikam).
Sound like a problem with X11 session (perhaps you videao card drivers) with not deal properly with KDELibs/QtLibs. No idea else... Gilles Caulier
It's video shadding feature problem. Go to KDE control panel and desactivate all video effects. Note : digiKam do not deal with video effects. At startup it just display splashscreen image. that all.. Gilles Caulier
digiKam 2.2.0 is out since few weeks. Crash still valid with this version ? Gilles Caulier
New digiKam 4.11.0 is available. https://www.digikam.org/node/740 Can you reproduce the problem with this release ? Gilles Caulier
digiKam 4.12.0 is out : https://www.digikam.org/node/741 We need a fresh feedback using this release please... Thanks in advance.
This problem is not reproducible with last 5.0.0. I close this file now. Don't hesitate to re-open it if necessary. Gilles Caulier