<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Martin,</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">Can you please stop spamming the whole list with this? Please take it up with the list owner directly instead, I do not need to read your mails about this all the time.</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">A shot in the dark: You subscribed with a different email address. See whether you can manage it through the WWW interface instead. But please leave me out of it.</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">Thx,</div><div id="AppleMailSignature">Hajo<br><br>-- <div>Composed on my tablet. Apologies for typos.</div><div><br></div><div>PGP key: <a href="http://tinyurl.com/neswujo" style="font-size: 13pt;">http://tinyurl.com/2016pgpkey</a></div></div><div><br>On 1 Feb 2017, at 06:11, Martin Kaspar <<a href="mailto:martin.kaspar@campus-24.com">martin.kaspar@campus-24.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr">unsubscribe does not work propperly<br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jan 31, 2017 at 10:44 PM, <span dir="ltr"><<a href="mailto:digikam-users-request@kde.org" target="_blank">digikam-users-request@kde.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send Digikam-users mailing list submissions to<br>
<a href="mailto:digikam-users@kde.org">digikam-users@kde.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://mail.kde.org/mailman/listinfo/digikam-users" rel="noreferrer" target="_blank">https://mail.kde.org/mailman/<wbr>listinfo/digikam-users</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:digikam-users-request@kde.org">digikam-users-request@kde.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:digikam-users-owner@kde.org">digikam-users-owner@kde.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of Digikam-users digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: digiKam 5.5 froze on opening Settings (Gilles Caulier)<br>
2. Re: Scan for new items takes ages after syncing collection<br>
btw. two computers (Phil)<br>
3. Re: digiKam 5.4.0 crashes on Rebuilding Thumbnails<br>
(<a href="mailto:blumenschein@dokom.net">blumenschein@dokom.net</a>)<br>
<br>
<br>
------------------------------<wbr>------------------------------<wbr>----------<br>
<br>
Message: 1<br>
Date: Tue, 31 Jan 2017 18:39:55 +0100<br>
From: Gilles Caulier <<a href="mailto:caulier.gilles@gmail.com">caulier.gilles@gmail.com</a>><br>
To: digiKam - Home Manage your photographs as a professional with the<br>
power of open source <<a href="mailto:digikam-users@kde.org">digikam-users@kde.org</a>><br>
Subject: Re: digiKam 5.5 froze on opening Settings<br>
Message-ID:<br>
<CAHFG6sEtJJkPmLk9vZ3mxPFUr5U=<wbr>TN8viyKxE41eZwX=<a href="mailto:pZp%2Bhg@mail.gmail.com">pZp+hg@mail.<wbr>gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
It crash in exiv2 shared lib when Exif metadata viewer settings is<br>
populated with tags to filters.<br>
<br>
This must never expect of course.<br>
<br>
Please report this problem in bugzilla, including the GDB backtrace<br>
<br>
Thanks in advance<br>
<br>
Gilles Caulier<br>
<br>
<br>
2017-01-31 18:27 GMT+01:00 Andrey Goreev <<a href="mailto:aegoreev@gmail.com">aegoreev@gmail.com</a>>:<br>
<br>
> On Monday, January 30, 2017 10:47:20 PM MST Gilles Caulier wrote:<br>
> > ./digikam-5.5.0-01-x86-64.<wbr>appimage debug<br>
><br>
> digikam 5.5 froze on opening Settings.<br>
><br>
> --<br>
> Thread 1 "digikam" hit Catchpoint 1 (exception thrown), 0x00007fffebe788bd<br>
> in<br>
> __cxa_throw () from /usr/lib/x86_64-linux-gnu/<wbr>libstdc++.so.6<br>
> (gdb) bt<br>
> #0 0x00007fffebe788bd in __cxa_throw () from /usr/lib/x86_64-linux-gnu/<br>
> libstdc++.so.6<br>
> #1 0x00007ffff5e43b02 in Exiv2::ExifKey::ExifKey (this=<optimized out>,<br>
> ti=...) at /b/ext_exiv2/ext_exiv2-prefix/<wbr>src/ext_exiv2/src/tags.cpp:<wbr>3157<br>
> #2 0x00007ffff682aea0 in Digikam::MetaEngine::<wbr>getStdExifTagsList<br>
> (this=this@entry=<wbr>0x7fffffffb100)<br>
> at /b/dktemp/digikam-master/core/<wbr>libs/dmetadata/metaengine_<br>
> exif.cpp:1087<br>
> #3 0x00007ffff69a36c4 in Digikam::MetadataPanel::<wbr>slotTabChanged<br>
> (this=this@entry=0x3b65d40)<br>
> at /b/dktemp/digikam-master/core/<wbr>libs/widgets/metadata/<br>
> metadatapanel.cpp:<br>
> 311<br>
> #4 0x00007ffff69a402d in Digikam::MetadataPanel::<wbr>MetadataPanel<br>
> (this=0x3b65d40, tab=0x3b66970)<br>
> at /b/dktemp/digikam-master/core/<wbr>libs/widgets/metadata/<br>
> metadatapanel.cpp:<br>
> 232<br>
> #5 0x00007ffff768a70a in Digikam::SetupMetadata::<wbr>SetupMetadata<br>
> (this=0x3b30ee0, parent=<optimized out>)<br>
> at /b/dktemp/digikam-master/core/<wbr>utilities/setup/metadata/<br>
> setupmetadata.cpp:463<br>
> #6 0x00007ffff766294a in Digikam::Setup::Setup (this=this@entry<br>
> =0x3a1f520,<br>
> parent=parent@entry=0x84ee70)<br>
> at /b/dktemp/digikam-master/core/<wbr>utilities/setup/setup.cpp:186<br>
> #7 0x00007ffff7664725 in Digikam::Setup::execDialog (parent=0x84ee70,<br>
> page=Digikam::Setup::<wbr>LastPageUsed)<br>
> at /b/dktemp/digikam-master/core/<wbr>utilities/setup/setup.cpp:362<br>
> #8 0x00007ffff7615d44 in Digikam::DigikamApp::qt_<wbr>static_metacall<br>
> (_o=0x84ee70, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>)<br>
> at /b/dktemp/digikam-master/<wbr>build/core/app/moc_digikamapp.<wbr>cpp:359<br>
> #9 0x00000031e04af846 in QMetaObject::activate(QObject*<wbr>, int, int,<br>
> void**) ()<br>
> from /tmp/.mount_vVX2pQ/usr/lib/<wbr>libQt5Core.so.5<br>
> #10 0x00007fffee338ba2 in QAction::triggered(bool) () from<br>
> /tmp/.mount_vVX2pQ/<br>
> usr/lib/libQt5Widgets.so.5<br>
> #11 0x00007fffee33b57d in QAction::activate(QAction::<wbr>ActionEvent) () from<br>
> /<br>
> tmp/.mount_vVX2pQ/usr/lib/<wbr>libQt5Widgets.so.5<br>
> #12 0x00007fffee4a3002 in ?? () from /tmp/.mount_vVX2pQ/usr/lib/<br>
> libQt5Widgets.so.5<br>
> #13 0x00007fffee4a9244 in ?? () from /tmp/.mount_vVX2pQ/usr/lib/<br>
> libQt5Widgets.so.5<br>
> #14 0x00007fffee4aa196 in QMenu::mouseReleaseEvent(<wbr>QMouseEvent*) () from /<br>
> tmp/.mount_vVX2pQ/usr/lib/<wbr>libQt5Widgets.so.5<br>
> #15 0x00007fffee3857c8 in QWidget::event(QEvent*) () from<br>
> /tmp/.mount_vVX2pQ/<br>
> usr/lib/libQt5Widgets.so.5<br>
> #16 0x00007fffee4ac42b in QMenu::event(QEvent*) () from /tmp/.mount_vVX2pQ/<br>
> usr/lib/libQt5Widgets.so.5<br>
> #17 0x00007fffee33f8fc in QApplicationPrivate::notify_<wbr>helper(QObject*,<br>
> QEvent*) () from /tmp/.mount_vVX2pQ/usr/lib/<wbr>libQt5Widgets.so.5<br>
> #18 0x00007fffee3470db in QApplication::notify(QObject*, QEvent*) () from /<br>
> tmp/.mount_vVX2pQ/usr/lib/<wbr>libQt5Widgets.so.5<br>
> #19 0x00000031e04880f0 in QCoreApplication::<wbr>notifyInternal2(QObject*,<br>
> QEvent*)<br>
> () from /tmp/.mount_vVX2pQ/usr/lib/<wbr>libQt5Core.so.5<br>
> #20 0x00007fffee345dce in QApplicationPrivate::<wbr>sendMouseEvent(QWidget*,<br>
> QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) ()<br>
> from /tmp/.mount_vVX2pQ/usr/lib/<wbr>libQt5Widgets.so.5<br>
> #21 0x00007fffee3a1135 in ?? () from /tmp/.mount_vVX2pQ/usr/lib/<br>
> libQt5Widgets.so.5<br>
> #22 0x00007fffee3a39e3 in ?? () from /tmp/.mount_vVX2pQ/usr/lib/<br>
> libQt5Widgets.so.5<br>
> #23 0x00007fffee33f8fc in QApplicationPrivate::notify_<wbr>helper(QObject*,<br>
> QEvent*) () from /tmp/.mount_vVX2pQ/usr/lib/<wbr>libQt5Widgets.so.5<br>
> #24 0x00007fffee346808 in QApplication::notify(QObject*, QEvent*) () from /<br>
> tmp/.mount_vVX2pQ/usr/lib/<wbr>libQt5Widgets.so.5<br>
> #25 0x00000031e04880f0 in QCoreApplication::<wbr>notifyInternal2(QObject*,<br>
> QEvent*)<br>
> () from /tmp/.mount_vVX2pQ/usr/lib/<wbr>libQt5Core.so.5<br>
> #26 0x00007fffedd6a4ad in<br>
> QGuiApplicationPrivate::<wbr>processMouseEvent(<wbr>QWindowSystemInterfacePrivate:<br>
> :MouseEvent*)<br>
> () from /tmp/.mount_vVX2pQ/usr/lib/<wbr>libQt5Gui.so.5<br>
> #27 0x00007fffedd6c1c5 in<br>
> QGuiApplicationPrivate::<wbr>processWindowSystemEvent(<br>
> QWindowSystemInterfacePrivate:<wbr>:WindowSystemEvent*)<br>
> ()<br>
> from /tmp/.mount_vVX2pQ/usr/lib/<wbr>libQt5Gui.so.5<br>
> #28 0x00007fffedd4d023 in<br>
> QWindowSystemInterface::<wbr>sendWindowSystemEvents(QFlags<<br>
> QEventLoop::ProcessEventsFlag><wbr>)<br>
> () from /tmp/.mount_vVX2pQ/usr/lib/<wbr>libQt5Gui.so.5<br>
> #29 0x00007fffe4d62f30 in ?? () from /tmp/.mount_vVX2pQ/usr/lib/<br>
> libQt5XcbQpa.so.5<br>
> #30 0x00007fffea9c5197 in g_main_context_dispatch () from<br>
> /lib/x86_64-linux-<br>
> gnu/libglib-2.0.so.0<br>
> #31 0x00007fffea9c53f0 in ?? () from /lib/x86_64-linux-gnu/libglib-<br>
> 2.0.so.0<br>
> ---Type <return> to continue, or q <return> to quit---<br>
> #32 0x00007fffea9c549c in g_main_context_iteration () from<br>
> /lib/x86_64-linux-<br>
> gnu/libglib-2.0.so.0<br>
> #33 0x00000031e04d5d87 in<br>
> QEventDispatcherGlib::<wbr>processEvents(QFlags<<wbr>QEventLoop::ProcessEventsFlag><wbr>)<br>
> ()<br>
> from /tmp/.mount_vVX2pQ/usr/lib/<wbr>libQt5Core.so.5<br>
> #34 0x00000031e04863da in<br>
> QEventLoop::exec(QFlags<<wbr>QEventLoop::ProcessEventsFlag><wbr>) () from /<br>
> tmp/.mount_vVX2pQ/usr/lib/<wbr>libQt5Core.so.5<br>
> #35 0x00000031e048e1bd in QCoreApplication::exec() () from<br>
> /tmp/.mount_vVX2pQ/<br>
> usr/lib/libQt5Core.so.5<br>
> #36 0x0000000000405054 in main (argc=1, argv=<optimized out>) at /b/dktemp/<br>
> digikam-master/core/app/main/<wbr>main.cpp:240<br>
> (gdb)<br>
><br>
><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://mail.kde.org/pipermail/digikam-users/attachments/20170131/b4445ced/attachment-0001.html" rel="noreferrer" target="_blank">http://mail.kde.org/<wbr>pipermail/digikam-users/<wbr>attachments/20170131/b4445ced/<wbr>attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Tue, 31 Jan 2017 13:30:34 +0100<br>
From: Phil <<a href="mailto:philtuckey@free.fr">philtuckey@free.fr</a>><br>
To: digiKam - Home Manage your photographs as a professional with the<br>
power of open source <<a href="mailto:digikam-users@kde.org">digikam-users@kde.org</a>><br>
Subject: Re: Scan for new items takes ages after syncing collection<br>
btw. two computers<br>
Message-ID: <<a href="mailto:2d18ec8b-b8cd-07c9-8dbe-faf7ef1f25fa@free.fr">2d18ec8b-b8cd-07c9-8dbe-<wbr>faf7ef1f25fa@free.fr</a>><br>
Content-Type: text/plain; charset=windows-1252; format=flowed<br>
<br>
<br>
<br>
On 30/01/17 20:03, Andrew Goodbody wrote:<br>
><br>
><br>
> On 30/01/17 16:18, <a href="mailto:news@tcrass.de">news@tcrass.de</a> wrote:<br>
>> Chris,<br>
>><br>
>>> It's probably because Unison updates the 'last access' date field on<br>
>>> the files and Digikam uses this to decide whether to resacn.<br>
>><br>
>>> In Unix/Linux a file has three times associated with it:-<br>
>>><br>
>>> Modified time - last time the file contents were changes (write or<br>
>>> append)<br>
>>> Accessed time - last time the file was accessed (read or write)<br>
>>> Status changed - last time the attributes (owner, permissions,<br>
>>> etc.) were changed<br>
>><br>
>> yeah, that's what I came up with, too -- the digikam4.db file will<br>
>> probably have its access time changed during syncing.<br>
>><br>
>>> Digikam will compare its database with one (or more) of the above file<br>
>>> times I expect. A Digikam expert will no doubt tell us.<br>
>><br>
>> But if so, I still wonder where digikam keeps record of digikam4.db's<br>
>> access time?<br>
><br>
> It doesn't, that's not how it works.<br>
><br>
> digiKam stores the path to the root of the collection in the database<br>
> and this can look different on different systems, hence it will do a<br>
> full rescan.<br>
<br>
Here the db is synced in one case, shared in the other case, so the<br>
collection root paths are identical on the two machines.<br>
Philip<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Tue, 31 Jan 2017 21:44:14 +0000<br>
From: <a href="mailto:blumenschein@dokom.net">blumenschein@dokom.net</a><br>
To: digiKam - Home Manage your photographs as a professional with the<br>
power of open source <<a href="mailto:digikam-users@kde.org">digikam-users@kde.org</a>><br>
Subject: Re: digiKam 5.4.0 crashes on Rebuilding Thumbnails<br>
Message-ID:<br>
<<a href="mailto:20170131214414.Horde.lpDI2HmTVUcytQld0MexffT@www.dokom21-webagent.de">20170131214414.Horde.<wbr>lpDI2HmTVUcytQld0MexffT@www.<wbr>dokom21-webagent.de</a>><br>
Content-Type: text/plain; charset="utf-8"; Format="flowed";<br>
DelSp="Yes"<br>
<br>
Hi Gilles,<br>
<br>
here's my log-file captured with the tee-command<br>
<br>
<br>
Zitat von Gilles Caulier <<a href="mailto:caulier.gilles@gmail.com">caulier.gilles@gmail.com</a>>:<br>
<br>
> Please use digiKam 5.5.0 pre-release AppImage linux bundle and try<br>
> to reproduce the problem. File is here : <br>
> <a href="https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM" rel="noreferrer" target="_blank">https://drive.google.com/<wbr>drive/folders/0BzeiVr-<wbr>byqt5Y0tIRWVWelRJenM</a><br>
> <br>
> The bundle include debug symbols and can be executed into GDB like this :<br>
> <br>
> ./digikam-5.5.0-01-x86-64.<wbr>appimage debug<br>
><br>
> And when it crash, use gdb 'bt' command to get a backtrace..<br>
><br>
> <br>
> Gilles Caulier<br>
><br>
><br>
> 2017-01-30 21:18 GMT+01:00 <<a href="mailto:blumenschein@dokom.net">blumenschein@dokom.net</a>>:<br>
><br>
>> I have the same problem with<br>
>> GLib-ERROR **: ....... Too many open files<br>
>> under ArchLinux with this and other maintance modules especaly (but<br>
>> not only) <br>
>> when allowing the use of al CPU kernels.<br>
>><br>
>> Jürgen<br>
>><br>
>> Zitat von Andrey Goreev <<a href="mailto:aegoreev@gmail.com">aegoreev@gmail.com</a>>:<br>
>><br>
>>> digiKam crashes on me whenever I try to rebuild thumbnails.<br>
>>> Here is what the terminal says:<br>
>>> "<br>
>>> digikam.general: stage1<br>
>>> digikam.general: stage2<br>
>>> digikam.general: Using 4 CPU core to run threads<br>
>>> digikam.general: Using 1 CPU core to run threads<br>
>>> QXcbConnection: XCB error: 3 (BadWindow), sequence: 3317, resource id:<br>
>>> 44040800, major code: 40 (TranslateCoords), minor code: 0<br>
>>><br>
>>> (process:11458): GLib-ERROR **: Creating pipes for GWakeup: Too<br>
>>> many open files<br>
>>><br>
>>> Trace/breakpoint trap<br>
>>> "<br>
>>><br>
>>> Any solution for that?<br>
>>> Linux Mint 18.1 KDEsqlite<br>
>><br>
>> --<br>
>> Jürgen Blumenschein, eMail: <a href="mailto:blumenschein@dokom.net">blumenschein@dokom.net</a><br>
>> Homepage: <a href="http://members.dokom.net/blumenschein" rel="noreferrer" target="_blank">http://members.dokom.net/<wbr>blumenschein</a><br>
>> Am Quartus 17<br>
>> D-44149 Dortmund<br>
>> Tel.: +49 231 7217321[1], Handy: +49 176 5591 4562[2]<br>
>> public key:<br>
>> <a href="http://members.dokom.net/blumenscheinJuergen_Blumenschein_(0xC9358EBB)_public_key.asc" rel="noreferrer" target="_blank">http://members.dokom.net/<wbr>blumenscheinJuergen_<wbr>Blumenschein_(0xC9358EBB)_<wbr>public_key.asc</a><br>
>> <br>
<br>
<br>
<br>
Links:<br>
------<br>
[1] <a href="tel:%2B49%20231%207217321">tel:%2B49%20231%207217321</a><br>
[2] <a href="tel:%2B49%20176%205591%204562">tel:%2B49%20176%205591%204562</a><br>
--<br>
Jürgen Blumenschein, eMail: <a href="mailto:blumenschein@dokom.net">blumenschein@dokom.net</a><br>
Homepage: <a href="http://members.dokom.net/blumenschein" rel="noreferrer" target="_blank">http://members.dokom.net/<wbr>blumenschein</a><br>
Am Quartus 17<br>
D-44149 Dortmund<br>
Tel.: <a href="tel:%2B49%20231%207217321" value="+492317217321">+49 231 7217321</a>, Handy: <a href="tel:%2B49%20176%205591%204562" value="+4917655914562">+49 176 5591 4562</a><br>
public key:<br>
<a href="http://members.dokom.net/blumenscheinJuergen_Blumenschein_(0xC9358EBB)_public_key.asc" rel="noreferrer" target="_blank">http://members.dokom.net/<wbr>blumenscheinJuergen_<wbr>Blumenschein_(0xC9358EBB)_<wbr>public_key.asc</a><br>
-------------- next part --------------<br>
An embedded and charset-unspecified text was scrubbed...<br>
Name: digikam55.log<br>
URL: <<a href="http://mail.kde.org/pipermail/digikam-users/attachments/20170131/13322a37/attachment.ksh" rel="noreferrer" target="_blank">http://mail.kde.org/<wbr>pipermail/digikam-users/<wbr>attachments/20170131/13322a37/<wbr>attachment.ksh</a>><br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
______________________________<wbr>_________________<br>
Digikam-users mailing list<br>
<a href="mailto:Digikam-users@kde.org">Digikam-users@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/digikam-users" rel="noreferrer" target="_blank">https://mail.kde.org/mailman/<wbr>listinfo/digikam-users</a><br>
<br>
<br>
------------------------------<br>
<br>
End of Digikam-users Digest, Vol 140, Issue 150<br>
******************************<wbr>*****************<br>
</blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"></span><p><span style="font-size:10.5pt;font-family:Consolas;color:#1f497d"> </span><a href="http://www.facebook.com/martin.kaspar.547" target="_blank"><span style="font-size:10.5pt;font-family:Consolas;color:#1f497d;text-decoration:none"><img src="cid:image002.png@01CDBC4A.438DCA20" width="20" height="20" border="0"></span></a><span style="font-size:10.5pt;font-family:Consolas;color:#1f497d"> </span><span style="font-size:10.5pt;font-family:Consolas;color:#1f497d"> </span><a href="https://plus.google.com/u/0/104428351748591530426" target="_blank"><span style="font-size:10.5pt;font-family:Consolas;color:blue;text-decoration:none"><img src="cid:image004.png@01CDBC4A.438DCA20" alt="gplus_Seiten_Signatur" width="20" height="20" border="0"></span></a></p></div>
</div></div>
</div></blockquote></body></html>