Piter Dias | 30 Jul 03:39 2014

Digikam doesn't seem to work under X2Go

Guys,

I have a small HP Microserver with Ubuntu 13.10 and Digikam 4.1 (compiled by myself). My client is Windows 8 (8, not 8.1).

Since forever I access my box using SSH and Xming X Server without any trouble. Digikam works properly but a bit slow (menu navigation, for example). My server is kind a weak but I wanted to test if I can improve things a bit using a NX connection.

I choose X2Go given the recent changes on NoMachine. All applications I tested but Digikam seems to run ok under X2Go.

Digikam starts, shows the splash screen, makes the initial checks, close the splash screen and DOESN'T open the main screen. It keeps running, however, as I can see via ps.

I am waiting for a reply from X2Go team (Brazil->Europe time zone problems) and in the mean time I would like to know if someone had a similar problem.

I compiled using a release switch, so my terminal doesn't have tons of messages. See below a terminal example. Both Xming and X2Go show quite the same messages but the last line just happens under X2Go.

Some clues? Should I recompile using debug options to get more information?

Thanks in advance.


Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
QDBusConnection: name 'org.freedesktop.UDisks2' had owner '' but we thought it was ':1.25'
QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in use, all queries will cease to work.
"/org/freedesktop/UDisks2/drives/VB0250EAVER_Z2ASDK4B" : property "DeviceNumber" does not exist 
"/org/freedesktop/UDisks2/drives/VB0250EAVER_Z2ASDK4B" : property "Device" does not exist 
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...
kbuildsycoca4(13077) KBuildSycoca::checkTimestamps: checking file timestamps
kbuildsycoca4(13077) KBuildSycoca::checkTimestamps: timestamps check ok
kbuildsycoca4(13077) kdemain: Emitting notifyDatabaseChanged ()
digikam(13028)/KIPI (loading) KIPI::PluginLoader::Info::plugin: Cannot create instance for plugin  "Calendar"  ( "kipiplugin_calendar" )  with error:  "Cannot load library /usr/lib/kde4/kipiplugin_calendar.so: (libkcalcore.so.4: cannot open shared object file: No such file or directory)" 
digikam(13028)/KIPI (loading) KIPI::PluginLoader::Info::plugin: Cannot create instance for plugin  "Calendar"  ( "kipiplugin_calendar" )  with error:  "Cannot load library /usr/lib/kde4/kipiplugin_calendar.so: (libkcalcore.so.4: cannot open shared object file: No such file or directory)" 
digikam(13028)/KIPI (loading) KIPI::PluginLoader::Info::plugin: Cannot create instance for plugin  "Calendar"  ( "kipiplugin_calendar" )  with error:  "Cannot load library /usr/lib/kde4/kipiplugin_calendar.so: (libkcalcore.so.4: cannot open shared object file: No such file or directory)" 
digikam(13028)/KIPI (general): Current image collection is not valid. 
Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
"/org/freedesktop/UDisks2/drives/VB0250EAVER_Z2ASDK4B" : property "DeviceNumber" does not exist 
"/org/freedesktop/UDisks2/drives/VB0250EAVER_Z2ASDK4B" : property "Device" does not exist 
QSocketNotifier: Invalid socket 15 and type 'Read', disabling...
_____________________
Piter Dias
piter.dias-dmjmWuXPryWakBO8gow8eQ@public.gmane.org

_______________________________________________
Digikam-users mailing list
Digikam-users@...
https://mail.kde.org/mailman/listinfo/digikam-users
Christoph Huckle | 25 Jul 20:39 2014
Picon

Albumview freezes - need help debugging

Hello,

on my latest  setup with digikam I am experiencing hangs on certain Albumviews.
I'm running 4.2 on Opensuse 13.1 on an Microsoft Surface Pro 3. All pictures are on a NAS the database runs on a server as MySQL.

With kdebugdialog enabled and gdb I get the following outputs if I let it freeze:

digikam(2337)/KGEOMAP KGeoMap::ItemMarkerTiler::slotSourceModelReset: ----
digikam(2337)/KGEOMAP KGeoMap::ItemMarkerTiler::slotSourceModelReset: ----
digikam(2337)/KGEOMAP KGeoMap::ItemMarkerTiler::slotSourceModelReset: ----
digikam(2337)/kio (Scheduler) KIO::SchedulerPrivate::doJob: KIO::SimpleJob(0x3a57180)
digikam(2337)/kio (KIOJob) KIO::TransferJob::slotFinished: KUrl("digikamalbums:/2011 22 Melb & Tasi/2011 09 26 Melb Central/?albumRoot=%2Fhome%2Fchris%2Fmnt%2FPhotos%2F2011&albumRootId=10&databaseType=QMYSQL&databaseName=digikam&connectOptions=&hostName=192.168.1.10&port=0&userName=digikam_sp3&password=***")
digikam(2337)/kio (Scheduler) KIO::SchedulerPrivate::jobFinished: KIO::SpecialJob(0x3a57180) KIO::Slave(0x4e9c840)
[Thread 0x7fffb7ffe700 (LWP 2416) exited]
[Thread 0x7fffb6ffc700 (LWP 2415) exited]
[Thread 0x7fffcf7fe700 (LWP 2411) exited]
[Thread 0x7fffb67fb700 (LWP 2417) exited]

this is then the backtrace output:
#0  0x00007fffeec3a006 in __memcpy_sse2_unaligned () from /lib64/libc.so.6
#1  0x00007ffff475aa23 in QConcatenable<QString>::appendTo (a=..., out= <at> 0x7fffffffc428: 0x6ec5fe0) at /usr/include/QtCore/qstringbuilder.h:277
#2  0x00007ffff47664f9 in QConcatenable<QStringBuilder<QStringBuilder<QString, char>, QString> >::appendTo<QChar> (p=..., out= <at> 0x7fffffffc428: 0x6ec5fe0) at /usr/include/QtCore/qstringbuilder.h:404
#3  0x00007ffff47617f5 in QStringBuilder<QStringBuilder<QString, char>, QString>::convertTo<QString> (this=0x7fffffffc4e0) at /usr/include/QtCore/qstringbuilder.h:126
#4  0x00007ffff475dc89 in QStringBuilder<QStringBuilder<QString, char>, QString>::operator QString (this=0x7fffffffc4e0) at /usr/include/QtCore/qstringbuilder.h:139
#5  0x00007ffff47f8c5a in Digikam::TagsCache::tagPath (this=0xf63b50, id=36, slashPolicy=Digikam::TagsCache::NoLeadingSlash) at /home/chris/dk/core/libs/database/tagscache.cpp:373
#6  0x00007ffff47f8e32 in Digikam::TagsCache::tagPaths (this=0xf63b50, ids=..., slashPolicy=Digikam::TagsCache::NoLeadingSlash, hiddenTagsPolicy=Digikam::TagsCache::NoHiddenTags)
    at /home/chris/dk/core/libs/database/tagscache.cpp:396
#7  0x00000000004b729b in Digikam::ImagePropertiesSideBarDB::setImagePropertiesInformation (this=0x1ee57e0, url=...) at /home/chris/dk/core/libs/imageproperties/imagepropertiessidebardb.cpp:627
#8  0x00000000004b5195 in Digikam::ImagePropertiesSideBarDB::slotChangedTab (this=0x1ee57e0, tab=0x1f02ef0) at /home/chris/dk/core/libs/imageproperties/imagepropertiessidebardb.cpp:274
#9  0x00000000004b4c36 in Digikam::ImagePropertiesSideBarDB::itemChanged (this=0x1ee57e0, infos=..., rect=..., img=0x0, history=...)
    at /home/chris/dk/core/libs/imageproperties/imagepropertiessidebardb.cpp:199
#10 0x00000000004b4ab5 in Digikam::ImagePropertiesSideBarDB::itemChanged (this=0x1ee57e0, infos=...) at /home/chris/dk/core/libs/imageproperties/imagepropertiessidebardb.cpp:175
#11 0x00000000006d4610 in Digikam::DigikamView::slotDispatchImageSelected (this=0x10a3a40) at /home/chris/dk/core/digikam/views/digikamview.cpp:1330
#12 0x00000000006ce2cf in Digikam::DigikamView::qt_static_metacall (_o=0x10a3a40, _c=QMetaObject::InvokeMetaMethod, _id=92, _a=0x7fffffffcde0)
    at /home/chris/dk/build/core/digikam/digikamview.moc:340
#13 0x00007ffff0ed0d68 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/libQtCore.so.4
#14 0x00007ffff0ed4f31 in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4
#15 0x00007fffefdbf8ac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#16 0x00007fffefdc5e70 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#17 0x00007ffff192618a in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#18 0x00007ffff0ebd0ad in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4
#19 0x00007ffff0eec83c in ?? () from /usr/lib64/libQtCore.so.4
#20 0x00007ffff0ee9b59 in ?? () from /usr/lib64/libQtCore.so.4
#21 0x00007fffe7acb316 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#22 0x00007fffe7acb668 in ?? () from /usr/lib64/libglib-2.0.so.0
#23 0x00007fffe7acb70c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#24 0x00007ffff0ee9d55 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#25 0x00007fffefe5c936 in ?? () from /usr/lib64/libQtGui.so.4
#26 0x00007ffff0ebbd0f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#27 0x00007ffff0ebc005 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#28 0x00007ffff0ec113b in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#29 0x0000000000754204 in main (argc=1, argv=0x7fffffffdd98) at /home/chris/dk/core/digikam/main/main.cpp:236

what else can I do to provide more useful information?
As said it only happens on certain folders.

BR
Chris.
_______________________________________________
Digikam-users mailing list
Digikam-users@...
https://mail.kde.org/mailman/listinfo/digikam-users
Del Andrew | 24 Jul 16:55 2014
Picon

Print assistant

Hello All!

I'm rather new to Digikam and I love it so far, but I have much to learn yet. 
I am presently having a problem with the Print Assistant. I go into the Print 
Assistant and do everything it says. I choose the size and all that, it goes 
to the next screen and I crop the picture the way I want, but when I hit 
finish it just goes back to the main program and doesn't print anything. I've 
tried using the print assistant as far as it goes, and then using the standard 
print command, but the print command doesn't do what I told the Print 
Assistant to do. Am I missing something here? I'm sorry for the newbie 
inexperience here.

Oh, FYI, I am using Digikam 4.1.0 on a laptop running Windows Vista

Thanks so much for any help
Veaceslav Munteanu | 23 Jul 19:06 2014
Picon

Tags and everything related to them

Hello,

I'm once again fighting with tags and this battle seem to have no ending.

I figured out that digiKam once again read data from 5 different
namespaces(IPTC, Xmp digikam, Xmp Microsoft, Xmp lightroom) and only
modify it to IPTC and own XMP namespace.

This is bad because:
If you wipe -> trigger write and then read -> all deleted tags are back.

Some users said that namespaces that are not from digiKam should not be touched.
Well this is impossible, you either:

1. grant digiKam to delete and modify all namespaces that it can read
2. remove the ability to read from that protected namespace

Any other combination result in total mess on read/write.

I'm waiting for suggestions about do you prefer the most: 1 or 2

Veaceslav
m5ernel | 22 Jul 20:38 2014
Picon

After update my Digikam keeps crashing

Hello.
I would need some help, please.
I use Linux Mint, version 17 Cinnamon 64. I've recently updated Digikam to
version 4.0.0. Since then, it keeps crashing every time I try to edit my
collection. It crashes after few steps, no matter what tool I use. It
usually happens when I click OK to confirm an action or when I click save.
Previous version worked just fine.

The bug message says the following:

/Application: digiKam (digikam), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7ff39d14fac0 (LWP 5014))]

Thread 5 (Thread 0x7ff3773f8700 (LWP 5017)):
#0  0x00007ff396295fbd in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x00007ff37bfa3248 in ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
#2  0x00007ff3922c9182 in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#3  0x00007ff3962a330d in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 4 (Thread 0x7ff369911700 (LWP 5018)):
#0  0x00007ff3922cd414 in pthread_cond_wait <at>  <at> GLIBC_2.3.2 () from
/lib/x86_64-linux-gnu/libpthread.so.0
#1  0x00007ff397084816 in QWaitCondition::wait(QMutex*, unsigned long) ()
from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#2  0x00000000005e3d9e in ?? ()
#3  0x00007ff39708432f in ?? () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#4  0x00007ff3922c9182 in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#5  0x00007ff3962a330d in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 3 (Thread 0x7ff369110700 (LWP 5019)):
#0  0x00007ff3922cc7f4 in pthread_mutex_unlock () from
/lib/x86_64-linux-gnu/libpthread.so.0
#1  0x00007ff38f14f9c1 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007ff38f10d0f0 in g_main_context_acquire () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007ff38f10dea5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007ff38f10e0ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007ff3971b37be in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
() from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#6  0x00007ff3971850af in
QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#7  0x00007ff3971853a5 in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#8  0x00007ff397081c5f in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#9  0x00007ff397166823 in ?? () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#10 0x00007ff39708432f in ?? () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#11 0x00007ff3922c9182 in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#12 0x00007ff3962a330d in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 2 (Thread 0x7ff36890f700 (LWP 5021)):
#0  0x00007ff3922cd414 in pthread_cond_wait <at>  <at> GLIBC_2.3.2 () from
/lib/x86_64-linux-gnu/libpthread.so.0
#1  0x00007ff397084816 in QWaitCondition::wait(QMutex*, unsigned long) ()
from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#2  0x00007ff39a7c78aa in ?? () from
/usr/lib/digikam/libdigikamcore.so.4.0.0
#3  0x00007ff39708432f in ?? () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#4  0x00007ff3922c9182 in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#5  0x00007ff3962a330d in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 1 (Thread 0x7ff39d14fac0 (LWP 5014)):
[KCrash Handler]
#5  0x00007ff3804a7da9 in ?? () from
/usr/lib/x86_64-linux-gnu/libsqlite3.so.0
#6  0x00007ff3804a7f63 in ?? () from
/usr/lib/x86_64-linux-gnu/libsqlite3.so.0
#7  0x00007ff3804bc579 in ?? () from
/usr/lib/x86_64-linux-gnu/libsqlite3.so.0
#8  0x00007ff3804e49c5 in ?? () from
/usr/lib/x86_64-linux-gnu/libsqlite3.so.0
#9  0x00007ff3804eced7 in sqlite3_step () from
/usr/lib/x86_64-linux-gnu/libsqlite3.so.0
#10 0x00007ff35bdfb11c in ?? () from
/usr/lib/x86_64-linux-gnu/qt4/plugins/sqldrivers/libqsqlite.so
#11 0x00007ff35bdfbe48 in ?? () from
/usr/lib/x86_64-linux-gnu/qt4/plugins/sqldrivers/libqsqlite.so
#12 0x00007ff39cd79b7d in QSqlQuery::exec() () from
/usr/lib/x86_64-linux-gnu/libQtSql.so.4
#13 0x00007ff39a780a46 in
Digikam::DatabaseCoreBackend::exec(Digikam::SqlQuery&) () from
/usr/lib/digikam/libdigikamcore.so.4.0.0
#14 0x00007ff39a780b72 in
Digikam::DatabaseCoreBackend::execQuery(Digikam::SqlQuery&, QVariant const&,
QVariant const&) () from /usr/lib/digikam/libdigikamcore.so.4.0.0
#15 0x00007ff39a781c2c in Digikam::DatabaseCoreBackend::execQuery(QString
const&, QVariant const&, QVariant const&) () from
/usr/lib/digikam/libdigikamcore.so.4.0.0
#16 0x00007ff39a781c7c in Digikam::DatabaseCoreBackend::execSql(QString
const&, QVariant const&, QVariant const&, QList<QVariant>*, QVariant*) ()
from /usr/lib/digikam/libdigikamcore.so.4.0.0
#17 0x00007ff39a146f6e in
Digikam::AlbumDB::findByNameAndCreationDate(QString const&, QDateTime
const&) () from /usr/lib/digikam/libdigikamdatabase.so.4.0.0
#18 0x00007ff39a1be764 in
Digikam::ImageScanner::resolveHistoryImageId(Digikam::HistoryImageId const&)
() from /usr/lib/digikam/libdigikamdatabase.so.4.0.0
#19 0x00007ff39a1ef254 in ?? () from
/usr/lib/digikam/libdigikamdatabase.so.4.0.0
#20 0x00007ff39a1ef424 in ?? () from
/usr/lib/digikam/libdigikamdatabase.so.4.0.0
#21 0x00007ff39a1f01da in ?? () from
/usr/lib/digikam/libdigikamdatabase.so.4.0.0
#22 0x00007ff39a1f05e7 in
Digikam::ImageHistoryGraph::addHistory(Digikam::DImageHistory const&,
Digikam::HistoryImageId const&) () from
/usr/lib/digikam/libdigikamdatabase.so.4.0.0
#23 0x00007ff39a1f063a in
Digikam::ImageHistoryGraph::addHistory(Digikam::DImageHistory const&,
Digikam::ImageInfo const&) () from
/usr/lib/digikam/libdigikamdatabase.so.4.0.0
#24 0x00007ff39a1f0dcd in
Digikam::ImageHistoryGraph::fromInfo(Digikam::ImageInfo const&,
QFlags<Digikam::ImageHistoryGraph::HistoryLoadingFlag>,
Digikam::ImageHistoryGraph::ProcessingMode) () from
/usr/lib/digikam/libdigikamdatabase.so.4.0.0
#25 0x00007ff39a201465 in
Digikam::ImageHistoryGraphModel::setHistory(Digikam::ImageInfo const&,
Digikam::ImageHistoryGraph const&) () from
/usr/lib/digikam/libdigikamdatabase.so.4.0.0
#26 0x00000000004c20e7 in ?? ()
#27 0x00000000004be133 in ?? ()
#28 0x00000000004a9e76 in ?? ()
#29 0x00007ff39719a87a in QMetaObject::activate(QObject*, QMetaObject
const*, int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#30 0x00007ff39a7f180f in Digikam::Sidebar::signalChangedTab(QWidget*) ()
from /usr/lib/digikam/libdigikamcore.so.4.0.0
#31 0x00007ff39a7f2705 in Digikam::Sidebar::deleteTab(QWidget*) () from
/usr/lib/digikam/libdigikamcore.so.4.0.0
#32 0x00007ff39a8a0183 in Digikam::EditorToolIface::unLoadTool() () from
/usr/lib/digikam/libdigikamcore.so.4.0.0
#33 0x00007ff39719a87a in QMetaObject::activate(QObject*, QMetaObject
const*, int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#34 0x00007ff39719a87a in QMetaObject::activate(QObject*, QMetaObject
const*, int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#35 0x00007ff39719a87a in QMetaObject::activate(QObject*, QMetaObject
const*, int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#36 0x00007ff3981c70d2 in QAbstractButton::clicked(bool) () from
/usr/lib/x86_64-linux-gnu/libQtGui.so.4
#37 0x00007ff397f2a9d3 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#38 0x00007ff397f2bb43 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#39 0x00007ff397f2bc2c in QAbstractButton::mouseReleaseEvent(QMouseEvent*)
() from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#40 0x00007ff397bc850a in QWidget::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQtGui.so.4
#41 0x00007ff397b78e2c in QApplicationPrivate::notify_helper(QObject*,
QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#42 0x00007ff397b7f5dd in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQtGui.so.4
#43 0x00007ff398883d1a in KApplication::notify(QObject*, QEvent*) () from
/usr/lib/libkdeui.so.5
#44 0x00007ff3971864dd in QCoreApplication::notifyInternal(QObject*,
QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#45 0x00007ff397b7ed93 in QApplicationPrivate::sendMouseEvent(QWidget*,
QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) ()
from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#46 0x00007ff397bf39cb in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#47 0x00007ff397bf3269 in QApplication::x11ProcessEvent(_XEvent*) () from
/usr/lib/x86_64-linux-gnu/libQtGui.so.4
#48 0x00007ff397c1ab02 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#49 0x00007ff38f10de04 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#50 0x00007ff38f10e048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#51 0x00007ff38f10e0ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#52 0x00007ff3971b37be in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
() from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#53 0x00007ff397c1abb6 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#54 0x00007ff3971850af in
QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#55 0x00007ff3971853a5 in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#56 0x00007ff39718ab79 in QCoreApplication::exec() () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#57 0x00000000004948f0 in ?? ()
#58 0x00007ff3961c9ec5 in __libc_start_main () from
/lib/x86_64-linux-gnu/libc.so.6
#59 0x0000000000496f1f in _start ()/

Any help? I am already thinking to switch to some alternative.

Regards

--
View this message in context: http://digikam.1695700.n4.nabble.com/After-update-my-Digikam-keeps-crashing-tp4670714.html
Sent from the digikam-users mailing list archive at Nabble.com.
Jeff Robinson | 22 Jul 14:11 2014
Picon

Hang while saving or updating JPEG on the network

Hi folks,

I'm trying to diagnose a problem I'm seeing with Digikam that has shown
up in the last month or two.  I don't exactly recall when the problem
first turned up, but it's seriously started to cramp my work-flow!

My current set-up is a desktop machine which contains my portfolio drive
and a laptop where I do a lot of my editing.

I primarily use the laptop to edit my photos, with the album directory
shared via a SMB connection (via smb4k).  I've used this set-up for
years, but the problems seem to have only started occurring recently,
and I'm trying to figure out where in my set-up the issue is occurring.

I use the sidecar files for both my RAW photos and JPEGs, in addition to
having the data written to the JPEGs as well.  In what seems like a
random event, I'll update the metadata on a JPEG and Digikam will stop
writing the information to a file, say at 80%.  If I click on the
thumbnail of the JPEG then the metadata commit will complete, but
otherwise Digikam will not seem to finish the write.

If I edit a RAW file in Digikam's Image Editor the editor will now
almost always hang while saving out the JPEG, where previously it worked
like a champ.

I enabled kdebugdialog and get the following output when I save the new
JPEG:
digikam(1760)/digikam (core) Digikam::DMetadata::setImageTitles: ""  ==>
Title:  QMap()
digikam(1760)/digikam (core) Digikam::DMetadata::setImageComments: ""
==> Comment:  QMap()
digikam(1760)/digikam (core) Digikam::DMetadata::setImagePickLabel: ""
==> Pick Label:  0
digikam(1760)/digikam (core) Digikam::DMetadata::setImageColorLabel: ""
 ==> Color Label:  0
digikam(1760)/digikam (core) Digikam::DMetadata::setImageRating: Rating
value to write is out of range!
digikam(1760)/digikam (core) Digikam::EditorWindow::startingSaveVersion:
Saving image KUrl("file:///home/portuser/album/Vacation/2013 British
Isles Cruise/UK Cruise/2013-08-03 - Le Havre/IMGP7090.PEF")
non-destructive, new version: true , saveAs: false format: ""
digikam(1760)/digikam (core)
Digikam::VersionNameCreator::setSaveFileName: need new version true
digikam(1760)/digikam (core)
Digikam::VersionNameCreator::setSaveFileName: analyzing file
"IMGP7090.PEF" QVariant(int, 1) QVariant(int, 1)
digikam(1760)/digikam (core)
Digikam::VersionNameCreator::checkIntermediates: Will replace false save
after each session false save after raw false save when not repro false
digikam(1760)/digikam (core)
Digikam::VersionNameCreator::checkIntermediates: initial history 1
current history 3 first step 1 last step 1
digikam(1760)/digikam (core)
Digikam::VersionNameCreator::checkIntermediates: Save intermediates
after steps ()
digikam(1760)/digikam (core) Digikam::EditorWindow::startingSaveVersion:
Writing file to  KUrl("file:///home/portuser/album/Vacation/2013 British
Isles Cruise/UK Cruise/2013-08-03 - Le Havre/IMGP7090_v1.JPG")
digikam(1760)/digikam (core) Digikam::EditorCore::Private::saveAs:
Saving to : "/home/portuser/album/Vacation/2013 British Isles Cruise/UK
Cruise/2013-08-03 - Le Havre/EditorWindow-Bc1760.digikamtempfile.JPG" (
"jpg" )
digikam(1760)/digikam (core) Digikam::EditorCore::Private::saveNext:
Saving file "/home/portuser/album/Vacation/2013 British Isles Cruise/UK
Cruise/2013-08-03 - Le Havre/EditorWindow-Bc1760.digikamtempfile.JPG" at -1
digikam(1760)/digikam (core) Digikam::AlbumWatch::rescanDirectory:
Detected change, triggering rescan of directory
"/home/portuser/album/Vacation/2013 British Isles Cruise/UK
Cruise/2013-08-03 - Le Havre"
digikam(1760)/digikam (core) Digikam::JPEGLoader::save: Using LibJPEG
medium chroma-subsampling (4:2:2)
digikam(1760)/digikam (core) Digikam::JPEGLoader::save: Using LibJPEG
quality compression value:  81
digikam(1760)/digikam (core) Digikam::AlbumWatch::rescanDirectory:
Detected change, triggering rescan of directory
"/home/portuser/album/Vacation/2013 British Isles Cruise/UK
Cruise/2013-08-03 - Le Havre"

Once I receive the last message about triggering a rescan Image Editor
is stuck at 89%.  If I try to cancel the save Image Editor does not
respond.  If I close Image Editor I receive a dialogue that asks to
"please wait for the image to be saved", but it never progresses.

I can cancel out of the dialogue and have three options: Save Changes,
Save Changes as a New Verion, and Discard Changes.

The only option that works is "Discard Changes".  This seems to close
Image Editor.  If I then close Digikam I receive the same "Please
wait..." dialogue.  If I hit "cancel" then Digikam disappears but a
second "Please wait..." dialogue appears.  Cancelling out of this one as
well makes the dialogue disappear, but Digikam is still running in the
background and I have to manually kill the process.

Any thoughts folks might have on troubleshooting my problem would be
greatly appreciated!

Jeff
Anders Lund | 21 Jul 16:07 2014
Picon

digikam 4.1 bugs

Hi,

I finally got an update to digikam 4.1, and it feels fast and nice.

However, within the editor, some bugs resist, notacibly the problem with 
preview sizes seems to persist.'

This problem is very odd, it does not affect all tools, and the behavior is not 
consistent, sometimes the order of tools used affects the behavior.

After conversion from RAW, using the curve tool, the initial preview is 
missized, on my screen it is set to 12%, which may be the preview size in the 
album view, with two sidebars visible.

In my opinion, if the size in the editor is "fit to window size", this setting 
should be sticky when activating tools (whatever setting in the editor window 
should stick, in fact).

Another problem is with the preview of the effect of a tool. I use consequently 
"mouse over" type preview, and Since 4.0, I have to move the mouse into the 
preview and out again to see the preview, which was not the case in 3.6 - a 
regression :0

Let me know, if I should rather file explicit bugs than explaining here!

--

-- 
kindly,
Anders
Dr. Martin Senftleben | 19 Jul 07:19 2014
Picon

digikam-doc cannot be installed


Hi,

with the upgrade to 4.1. I get the following error message:

error while attempting to overwrite
"usr/share/doc/kde/HTML/eu/kipi-plugins/rawconverter.docbook", which
is also in kipi-plugins-common 4.4.1.0-trusty~ppa1

I'm not sure if I translated the German error message as it would
appear in English, but the meaning should be the same. Any idea how I
can solve this?

Regards
Martin
Attachment (drmartinus.vcf): text/x-vcard, 396 bytes
_______________________________________________
Digikam-users mailing list
Digikam-users@...
https://mail.kde.org/mailman/listinfo/digikam-users
Remco Viëtor | 18 Jul 11:17 2014
Picon

Demosaicing doesn't use certain methods

Hi,

looking for something else, I noticed that Digikam versions 3.5 and 4.1 
(both the one from OpenSuse 13.1 and a local build) don't use several of 
the demosaicing options: AmaZe, LMMSE, VCD.

This might be a problem with my version of libraw or libkdcraw, but in any 
case, it would be nice to get a warning when certain methods aren't 
available.

regards, 

Remco
Am Tresen | 17 Jul 18:34 2014
Picon
Picon

Re: Digikam Face Detection does not work for me

Yeah, thank you for your ongoing support. I managed to have it run face 
detection properly by doing the following steps: (Debian Sid)

1.    Download the following repository and install it to 
/home/$YOURUSERNAME/.kde/share/apps/

https://projects.kde.org/projects/extragear/libs/libkface/repository/revisions/master/show/data

2. Create a haarcascades folder within the new 
/home/YOURUSERNAME/.kde/share/apps/libkface      so that you will get

     /home/YOURUSERNAME/.kde/share/apps/libkface/haarcascades/

The folder will be EMPTY.

3. Copy all files from
      /home/YOURUSERNAME/.kde/share/apps/libkface/data    to
/home/YOURUSERNAME/.kde/share/apps/libkface/haarcascades/ folder, data 
should contain the necessary .XML files.

At least it worked this way for me. It was a bit cumbersome since I 
copied every single file via terminal because I have no idea how to copy 
files into folders which my user has no write access to, but at least it 
worked after that.

Thanks again for the help, much appreciated!

Am 17.07.2014 14:00, schrieb digikam-users-request@...:
> Send Digikam-users mailing list submissions to
> 	digikam-users@...
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://mail.kde.org/mailman/listinfo/digikam-users
> or, via email, send a message with subject or body 'help' to
> 	digikam-users-request@...
>
> You can reach the person managing the list at
> 	digikam-users-owner@...
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Digikam-users digest..."
>
>
> Today's Topics:
>
>     1. Re: Digikam Face Detection does not work for me (Am Tresen)
>     2. Re: Digikam Face Detection does not work for me (maderios)
>     3. Re: Digikam Face Detection does not work for me (Gilles Caulier)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 16 Jul 2014 18:58:33 +0200
> From: Am Tresen <Am.Tresen@...>
> To: digikam-users@...
> Subject: Re: [Digikam-users] Digikam Face Detection does not work for
> 	me
> Message-ID: <53C6AF39.1010905@...>
> Content-Type: text/plain; charset=windows-1252; format=flowed
>
> Thanks for the reply, I checked for my opencv version and it is 2.4.9,
> which seems to be up to date according to the sourceforge website. Does
> anyone else have any ideas?
>
> Today I tried manually creating a face marker and then ran the scan
> again, still no result. When I use Detect & Recognize or just Recognize,
> the progress will finish within 1 second. To me this makes sense for the
> recognization (because i have only 1 face marker), but why does this
> happen with d&r, too? Maybe this could be a hint for anything?
>
> Anyone else have ideas?
>
> Am 16.07.2014 um 14:00 schrieb digikam-users-request@...:
>> Send Digikam-users mailing list submissions to
>> 	digikam-users@...
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>> 	https://mail.kde.org/mailman/listinfo/digikam-users
>> or, via email, send a message with subject or body 'help' to
>> 	digikam-users-request@...
>>
>> You can reach the person managing the list at
>> 	digikam-users-owner@...
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of Digikam-users digest..."
>>
>>
>> Today's Topics:
>>
>>      1. Re: Digikam Face Detection does not work for me
>>         (Henrique Santos Fernandes)
>>
>>
>> ----------------------------------------------------------------------
>>
>> Message: 1
>> Date: Tue, 15 Jul 2014 14:30:33 -0300
>> From: Henrique Santos Fernandes <sf.rique@...>
>> To: digiKam - Home Manage your photographs as a professional with the
>> 	power of open source <digikam-users@...>
>> Subject: Re: [Digikam-users] Digikam Face Detection does not work for
>> 	me
>> Message-ID:
>> 	<CAJpZ0xVRAnc1TdARgrYVr6D0PbLMeryy3s4s5=FM45h5bg+aww@...>
>> Content-Type: text/plain; charset="utf-8"
>>
>> Check for opencv!
>>
>> It need to be some version realy new!
>>
>> Have to compile it someway weird i guess too.
>>
>> something about it in the list archives..
>>
>> Sorry dont be more helpfull
>>
>> []'sf.rique
>> Henrique Santos Fernandes
>>
>>
>> On Tue, Jul 15, 2014 at 2:48 AM, Am Tresen <Am.Tresen@...> wrote:
>>
>>> I'm pretty sure I'm doing something wrong, so maybe somebody can help me.
>>>
>>> I'm running Digikam 4.1.0 on Debian Sid if that is of any matter.
>>>
>>> So, here is what I do: I start digikam, go to the Persons tab on the left,
>>> click on "search for faces", set it to "merge" (but I have tried all 3
>>> options already out of pure desperation). I set the search options to "all
>>> collections", "all tags", and the search quality to 100 (slow).
>>> Digikam does not show any results after scanning my images for about 2
>>> hours then, no matter if I ran face-detection or face-detection and
>>> recognition.
>>>
>>> Thanks in advance
>>> _______________________________________________
>>> Digikam-users mailing list
>>> Digikam-users@...
>>> https://mail.kde.org/mailman/listinfo/digikam-users
>>>
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20140715/9bb247c1/attachment-0001.html>
>>
>> ------------------------------
>>
>> _______________________________________________
>> Digikam-users mailing list
>> Digikam-users@...
>> https://mail.kde.org/mailman/listinfo/digikam-users
>>
>>
>> End of Digikam-users Digest, Vol 110, Issue 17
>> **********************************************
>
>
> ------------------------------
>
> Message: 2
> Date: Wed, 16 Jul 2014 20:51:27 +0200
> From: maderios <maderios@...>
> To: digikam-users@...
> Subject: Re: [Digikam-users] Digikam Face Detection does not work for
> 	me
> Message-ID: <53C6C9AF.3050408@...>
> Content-Type: text/plain; charset=utf-8; format=flowed
>
> On 07/15/2014 07:30 PM, Henrique Santos Fernandes wrote:
>> Check for opencv!
>>
>> It need to be some version realy new!
>>
> - In Debian Sid and Jessie,  Opencv version is the newest (2.4.9)
> - DK detection face is experimental
>
Christoph Huckle | 17 Jul 15:55 2014
Picon

Windows Version not working anymore

Hello there,

I cannot get the windows version to work anymore (3.5, 4.1 or 4.2)
First kio_thumbnail crashes a few times and then the Main Window just freezes.

Is there a way to update kio_thumbnail? Or any other work around?

BR
Christoph.
_______________________________________________
Digikam-users mailing list
Digikam-users@...
https://mail.kde.org/mailman/listinfo/digikam-users

Gmane