Browsing my pics is not possible anymore-i can neither see,nor select any one. Reproducible: Always Actual Results: browisng pics is a pre-condition for work with digiKam.
Without more information, there is no way to investigate. What do you see as trace when you run digiKam from a console
Gilles: this is the output, I get, if starting digiKam from console: ak@blacky:~$ digikam Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath) Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath) Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon QPainter::begin: Widget painting can only begin as a result of a paintEvent QPainter::translate: Painter not active QPainter::setClipRect: Painter not active QPainter::font: Painter not active QPainter::setFont: Painter not active QPainter::setPen: Painter not active QPainter::font: Painter not active QPainter::setFont: Painter not active QPainter::setPen: Painter not active QPainter::font: Painter not active Axel
There is no debug trace here on the console. Turn on debug space using kdebugdialog before to run digiKam. Look here for more details : https://www.digikam.org/contrib Gilles Caulier
ak@blacky:~$ gdb digikam GNU gdb (Ubuntu 7.8-1ubuntu4) 7.8.0.20141001-cvs Copyright (C) 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> 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: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. 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/55/3c976cc1e6daa139523829eebb8a241c8c70e2.debug...done. done. (gdb) Glilles, digiKam stops at this point regularly. I assume ths is not a valid bug-trace. So: what to do to get digiKam runnining or get rid of this failure? Axel
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. Gilles Caulier
With digiKam 5.0.0 this problem is not reproducible. I close this file now. Don't hesitate to re-open if necessary. Gilles Caulier