digiKam › digikam-users

unsubscribe does not work propperly

classic Classic list List threaded Threaded
♦
♦
 3 messages Options
Martin Kaspar
Reply | Threaded
Open this post in threaded view
♦
♦
|

unsubscribe does not work propperly

Martin Kaspar
unsubscribe does not work propperly

On Tue, Jan 31, 2017 at 10:44 PM, <[hidden email]> wrote:
Send Digikam-users mailing list submissions to
        [hidden email]

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
        [hidden email]

You can reach the person managing the list at
        [hidden email]

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 5.5 froze on opening Settings (Gilles Caulier)
   2. Re: Scan for new items takes ages after syncing collection
      btw. two computers (Phil)
   3. Re: digiKam 5.4.0 crashes on Rebuilding Thumbnails
      ([hidden email])


----------------------------------------------------------------------

Message: 1
Date: Tue, 31 Jan 2017 18:39:55 +0100
From: Gilles Caulier <[hidden email]>
To: digiKam - Home Manage your photographs as a professional with the
        power of open source <[hidden email]>
Subject: Re: digiKam 5.5 froze on opening Settings
Message-ID:
        <CAHFG6sEtJJkPmLk9vZ3mxPFUr5U=TN8viyKxE41eZwX=[hidden email]>
Content-Type: text/plain; charset="utf-8"

It crash in exiv2 shared lib when Exif metadata viewer settings is
populated with tags to filters.

This must never expect of course.

Please report this problem in bugzilla, including the GDB backtrace

Thanks in advance

Gilles Caulier


2017-01-31 18:27 GMT+01:00 Andrey Goreev <[hidden email]>:

> On Monday, January 30, 2017 10:47:20 PM MST Gilles Caulier wrote:
> > ./digikam-5.5.0-01-x86-64.appimage debug
>
> digikam 5.5 froze on opening Settings.
>
> --
> Thread 1 "digikam" hit Catchpoint 1 (exception thrown), 0x00007fffebe788bd
> in
> __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
> (gdb) bt
> #0  0x00007fffebe788bd in __cxa_throw () from /usr/lib/x86_64-linux-gnu/
> libstdc++.so.6
> #1  0x00007ffff5e43b02 in Exiv2::ExifKey::ExifKey (this=<optimized out>,
> ti=...) at /b/ext_exiv2/ext_exiv2-prefix/src/ext_exiv2/src/tags.cpp:3157
> #2  0x00007ffff682aea0 in Digikam::MetaEngine::getStdExifTagsList
> (this=this@entry=0x7fffffffb100)
>     at /b/dktemp/digikam-master/core/libs/dmetadata/metaengine_
> exif.cpp:1087
> #3  0x00007ffff69a36c4 in Digikam::MetadataPanel::slotTabChanged
> (this=this@entry=0x3b65d40)
>     at /b/dktemp/digikam-master/core/libs/widgets/metadata/
> metadatapanel.cpp:
> 311
> #4  0x00007ffff69a402d in Digikam::MetadataPanel::MetadataPanel
> (this=0x3b65d40, tab=0x3b66970)
>     at /b/dktemp/digikam-master/core/libs/widgets/metadata/
> metadatapanel.cpp:
> 232
> #5  0x00007ffff768a70a in Digikam::SetupMetadata::SetupMetadata
> (this=0x3b30ee0, parent=<optimized out>)
>     at /b/dktemp/digikam-master/core/utilities/setup/metadata/
> setupmetadata.cpp:463
> #6  0x00007ffff766294a in Digikam::Setup::Setup (this=this@entry
> =0x3a1f520,
> parent=parent@entry=0x84ee70)
>     at /b/dktemp/digikam-master/core/utilities/setup/setup.cpp:186
> #7  0x00007ffff7664725 in Digikam::Setup::execDialog (parent=0x84ee70,
> page=Digikam::Setup::LastPageUsed)
>     at /b/dktemp/digikam-master/core/utilities/setup/setup.cpp:362
> #8  0x00007ffff7615d44 in Digikam::DigikamApp::qt_static_metacall
> (_o=0x84ee70, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>)
>     at /b/dktemp/digikam-master/build/core/app/moc_digikamapp.cpp:359
> #9  0x00000031e04af846 in QMetaObject::activate(QObject*, int, int,
> void**) ()
> from /tmp/.mount_vVX2pQ/usr/lib/libQt5Core.so.5
> #10 0x00007fffee338ba2 in QAction::triggered(bool) () from
> /tmp/.mount_vVX2pQ/
> usr/lib/libQt5Widgets.so.5
> #11 0x00007fffee33b57d in QAction::activate(QAction::ActionEvent) () from
> /
> tmp/.mount_vVX2pQ/usr/lib/libQt5Widgets.so.5
> #12 0x00007fffee4a3002 in ?? () from /tmp/.mount_vVX2pQ/usr/lib/
> libQt5Widgets.so.5
> #13 0x00007fffee4a9244 in ?? () from /tmp/.mount_vVX2pQ/usr/lib/
> libQt5Widgets.so.5
> #14 0x00007fffee4aa196 in QMenu::mouseReleaseEvent(QMouseEvent*) () from /
> tmp/.mount_vVX2pQ/usr/lib/libQt5Widgets.so.5
> #15 0x00007fffee3857c8 in QWidget::event(QEvent*) () from
> /tmp/.mount_vVX2pQ/
> usr/lib/libQt5Widgets.so.5
> #16 0x00007fffee4ac42b in QMenu::event(QEvent*) () from /tmp/.mount_vVX2pQ/
> usr/lib/libQt5Widgets.so.5
> #17 0x00007fffee33f8fc in QApplicationPrivate::notify_helper(QObject*,
> QEvent*) () from /tmp/.mount_vVX2pQ/usr/lib/libQt5Widgets.so.5
> #18 0x00007fffee3470db in QApplication::notify(QObject*, QEvent*) () from /
> tmp/.mount_vVX2pQ/usr/lib/libQt5Widgets.so.5
> #19 0x00000031e04880f0 in QCoreApplication::notifyInternal2(QObject*,
> QEvent*)
> () from /tmp/.mount_vVX2pQ/usr/lib/libQt5Core.so.5
> #20 0x00007fffee345dce in QApplicationPrivate::sendMouseEvent(QWidget*,
> QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) ()
>    from /tmp/.mount_vVX2pQ/usr/lib/libQt5Widgets.so.5
> #21 0x00007fffee3a1135 in ?? () from /tmp/.mount_vVX2pQ/usr/lib/
> libQt5Widgets.so.5
> #22 0x00007fffee3a39e3 in ?? () from /tmp/.mount_vVX2pQ/usr/lib/
> libQt5Widgets.so.5
> #23 0x00007fffee33f8fc in QApplicationPrivate::notify_helper(QObject*,
> QEvent*) () from /tmp/.mount_vVX2pQ/usr/lib/libQt5Widgets.so.5
> #24 0x00007fffee346808 in QApplication::notify(QObject*, QEvent*) () from /
> tmp/.mount_vVX2pQ/usr/lib/libQt5Widgets.so.5
> #25 0x00000031e04880f0 in QCoreApplication::notifyInternal2(QObject*,
> QEvent*)
> () from /tmp/.mount_vVX2pQ/usr/lib/libQt5Core.so.5
> #26 0x00007fffedd6a4ad in
> QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate:
> :MouseEvent*)
> () from /tmp/.mount_vVX2pQ/usr/lib/libQt5Gui.so.5
> #27 0x00007fffedd6c1c5 in
> QGuiApplicationPrivate::processWindowSystemEvent(
> QWindowSystemInterfacePrivate::WindowSystemEvent*)
> ()
>    from /tmp/.mount_vVX2pQ/usr/lib/libQt5Gui.so.5
> #28 0x00007fffedd4d023 in
> QWindowSystemInterface::sendWindowSystemEvents(QFlags<
> QEventLoop::ProcessEventsFlag>)
> () from /tmp/.mount_vVX2pQ/usr/lib/libQt5Gui.so.5
> #29 0x00007fffe4d62f30 in ?? () from /tmp/.mount_vVX2pQ/usr/lib/
> libQt5XcbQpa.so.5
> #30 0x00007fffea9c5197 in g_main_context_dispatch () from
> /lib/x86_64-linux-
> gnu/libglib-2.0.so.0
> #31 0x00007fffea9c53f0 in ?? () from /lib/x86_64-linux-gnu/libglib-
> 2.0.so.0
> ---Type <return> to continue, or q <return> to quit---
> #32 0x00007fffea9c549c in g_main_context_iteration () from
> /lib/x86_64-linux-
> gnu/libglib-2.0.so.0
> #33 0x00000031e04d5d87 in
> QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
> ()
> from /tmp/.mount_vVX2pQ/usr/lib/libQt5Core.so.5
> #34 0x00000031e04863da in
> QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /
> tmp/.mount_vVX2pQ/usr/lib/libQt5Core.so.5
> #35 0x00000031e048e1bd in QCoreApplication::exec() () from
> /tmp/.mount_vVX2pQ/
> usr/lib/libQt5Core.so.5
> #36 0x0000000000405054 in main (argc=1, argv=<optimized out>) at /b/dktemp/
> digikam-master/core/app/main/main.cpp:240
> (gdb)
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20170131/b4445ced/attachment-0001.html>

------------------------------

Message: 2
Date: Tue, 31 Jan 2017 13:30:34 +0100
From: Phil <[hidden email]>
To: digiKam - Home Manage your photographs as a professional with the
        power of open source <[hidden email]>
Subject: Re: Scan for new items takes ages after syncing collection
        btw. two computers
Message-ID: <[hidden email]>
Content-Type: text/plain; charset=windows-1252; format=flowed



On 30/01/17 20:03, Andrew Goodbody wrote:
>
>
> On 30/01/17 16:18, [hidden email] wrote:
>> Chris,
>>
>>> It's probably because Unison updates the 'last access' date field on
>>> the files and Digikam uses this to decide whether to resacn.
>>
>>> In Unix/Linux a file has three times associated with it:-
>>>
>>>     Modified time - last time the file contents were changes (write or
>>> append)
>>>     Accessed time - last time the file was accessed (read or write)
>>>     Status changed - last time the attributes (owner, permissions,
>>> etc.) were changed
>>
>> yeah, that's what I came up with, too -- the digikam4.db file will
>> probably have its access time changed during syncing.
>>
>>> Digikam will compare its database with one (or more) of the above file
>>> times I expect.  A Digikam expert will no doubt tell us.
>>
>> But if so, I still wonder where digikam keeps record of digikam4.db's
>> access time?
>
> It doesn't, that's not how it works.
>
> digiKam stores the path to the root of the collection in the database
> and this can look different on different systems, hence it will do a
> full rescan.

Here the db is synced in one case, shared in the other case, so the
collection root paths are identical on the two machines.
Philip


------------------------------

Message: 3
Date: Tue, 31 Jan 2017 21:44:14 +0000
From: [hidden email]
To: digiKam - Home Manage your photographs as a professional with the
        power of open source <[hidden email]>
Subject: Re: digiKam 5.4.0 crashes on Rebuilding Thumbnails
Message-ID:
        <[hidden email]>
Content-Type: text/plain; charset="utf-8"; Format="flowed";
        DelSp="Yes"

Hi Gilles,

here's my log-file captured with the tee-command


Zitat von Gilles Caulier <[hidden email]>:

> Please use digiKam 5.5.0 pre-release AppImage linux bundle and try
> to reproduce the problem. File is here :       
>    https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM
>      
>     The bundle include debug symbols and can be executed into GDB like this :
>      
>     ./digikam-5.5.0-01-x86-64.appimage debug
>
> And when it crash, use gdb 'bt' command to get a backtrace..
>
>     
>    Gilles Caulier
>
>
>    2017-01-30 21:18 GMT+01:00 <[hidden email]>:
>
>> I have the same problem with
>> GLib-ERROR **: ....... Too many open files
>> under ArchLinux with this and other maintance modules especaly (but
>> not only) 
>> when allowing the use of al CPU kernels.
>>
>> Jürgen
>>
>> Zitat von Andrey Goreev <[hidden email]>:
>>
>>> digiKam crashes on me whenever I try to rebuild thumbnails.
>>> Here is what the terminal says:
>>> "
>>> digikam.general: stage1
>>> digikam.general: stage2
>>> digikam.general: Using  4  CPU core to run threads
>>> digikam.general: Using  1  CPU core to run threads
>>> QXcbConnection: XCB error: 3 (BadWindow), sequence: 3317, resource id:
>>> 44040800, major code: 40 (TranslateCoords), minor code: 0
>>>
>>> (process:11458): GLib-ERROR **: Creating pipes for GWakeup: Too
>>> many open files
>>>
>>> Trace/breakpoint trap
>>> "
>>>
>>> Any solution for that?
>>> Linux Mint 18.1 KDEsqlite
>>
>> --
>> Jürgen Blumenschein, eMail: [hidden email]
>> Homepage: http://members.dokom.net/blumenschein
>> Am Quartus 17
>> D-44149 Dortmund
>> Tel.: +49 231 7217321[1], Handy: +49 176 5591 4562[2]
>> public key:
>> http://members.dokom.net/blumenscheinJuergen_Blumenschein_(0xC9358EBB)_public_key.asc
>>  



Links:
------
[1] tel:%2B49%20231%207217321
[2] tel:%2B49%20176%205591%204562
--
Jürgen Blumenschein, eMail: [hidden email]
Homepage: http://members.dokom.net/blumenschein
Am Quartus 17
D-44149 Dortmund
Tel.: <a href="tel:%2B49%20231%207217321" value="+492317217321">+49 231 7217321, Handy: <a href="tel:%2B49%20176%205591%204562" value="+4917655914562">+49 176 5591 4562
public key:
http://members.dokom.net/blumenscheinJuergen_Blumenschein_(0xC9358EBB)_public_key.asc
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: digikam55.log
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20170131/13322a37/attachment.ksh>

------------------------------

Subject: Digest Footer

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users


------------------------------

End of Digikam-users Digest, Vol 140, Issue 150
***********************************************



--

   gplus_Seiten_Signatur
hajo
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: unsubscribe does not work propperly

hajo


-- 
Composed on my tablet. Apologies for typos.


On 1 Feb 2017, at 06:11, Martin Kaspar <[hidden email]> wrote:

unsubscribe does not work propperly

On Tue, Jan 31, 2017 at 10:44 PM, <[hidden email]> wrote:
Send Digikam-users mailing list submissions to
        [hidden email]

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
        [hidden email]

You can reach the person managing the list at
        [hidden email]

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 5.5 froze on opening Settings (Gilles Caulier)
   2. Re: Scan for new items takes ages after syncing collection
      btw. two computers (Phil)
   3. Re: digiKam 5.4.0 crashes on Rebuilding Thumbnails
      ([hidden email])


----------------------------------------------------------------------

Message: 1
Date: Tue, 31 Jan 2017 18:39:55 +0100
From: Gilles Caulier <[hidden email]>
To: digiKam - Home Manage your photographs as a professional with the
        power of open source <[hidden email]>
Subject: Re: digiKam 5.5 froze on opening Settings
Message-ID:
        <CAHFG6sEtJJkPmLk9vZ3mxPFUr5U=TN8viyKxE41eZwX=[hidden email]>
Content-Type: text/plain; charset="utf-8"

It crash in exiv2 shared lib when Exif metadata viewer settings is
populated with tags to filters.

This must never expect of course.

Please report this problem in bugzilla, including the GDB backtrace

Thanks in advance

Gilles Caulier


2017-01-31 18:27 GMT+01:00 Andrey Goreev <[hidden email]>:

> On Monday, January 30, 2017 10:47:20 PM MST Gilles Caulier wrote:
> > ./digikam-5.5.0-01-x86-64.appimage debug
>
> digikam 5.5 froze on opening Settings.
>
> --
> Thread 1 "digikam" hit Catchpoint 1 (exception thrown), 0x00007fffebe788bd
> in
> __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
> (gdb) bt
> #0  0x00007fffebe788bd in __cxa_throw () from /usr/lib/x86_64-linux-gnu/
> libstdc++.so.6
> #1  0x00007ffff5e43b02 in Exiv2::ExifKey::ExifKey (this=<optimized out>,
> ti=...) at /b/ext_exiv2/ext_exiv2-prefix/src/ext_exiv2/src/tags.cpp:3157
> #2  0x00007ffff682aea0 in Digikam::MetaEngine::getStdExifTagsList
> (this=this@entry=0x7fffffffb100)
>     at /b/dktemp/digikam-master/core/libs/dmetadata/metaengine_
> exif.cpp:1087
> #3  0x00007ffff69a36c4 in Digikam::MetadataPanel::slotTabChanged
> (this=this@entry=0x3b65d40)
>     at /b/dktemp/digikam-master/core/libs/widgets/metadata/
> metadatapanel.cpp:
> 311
> #4  0x00007ffff69a402d in Digikam::MetadataPanel::MetadataPanel
> (this=0x3b65d40, tab=0x3b66970)
>     at /b/dktemp/digikam-master/core/libs/widgets/metadata/
> metadatapanel.cpp:
> 232
> #5  0x00007ffff768a70a in Digikam::SetupMetadata::SetupMetadata
> (this=0x3b30ee0, parent=<optimized out>)
>     at /b/dktemp/digikam-master/core/utilities/setup/metadata/
> setupmetadata.cpp:463
> #6  0x00007ffff766294a in Digikam::Setup::Setup (this=this@entry
> =0x3a1f520,
> parent=parent@entry=0x84ee70)
>     at /b/dktemp/digikam-master/core/utilities/setup/setup.cpp:186
> #7  0x00007ffff7664725 in Digikam::Setup::execDialog (parent=0x84ee70,
> page=Digikam::Setup::LastPageUsed)
>     at /b/dktemp/digikam-master/core/utilities/setup/setup.cpp:362
> #8  0x00007ffff7615d44 in Digikam::DigikamApp::qt_static_metacall
> (_o=0x84ee70, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>)
>     at /b/dktemp/digikam-master/build/core/app/moc_digikamapp.cpp:359
> #9  0x00000031e04af846 in QMetaObject::activate(QObject*, int, int,
> void**) ()
> from /tmp/.mount_vVX2pQ/usr/lib/libQt5Core.so.5
> #10 0x00007fffee338ba2 in QAction::triggered(bool) () from
> /tmp/.mount_vVX2pQ/
> usr/lib/libQt5Widgets.so.5
> #11 0x00007fffee33b57d in QAction::activate(QAction::ActionEvent) () from
> /
> tmp/.mount_vVX2pQ/usr/lib/libQt5Widgets.so.5
> #12 0x00007fffee4a3002 in ?? () from /tmp/.mount_vVX2pQ/usr/lib/
> libQt5Widgets.so.5
> #13 0x00007fffee4a9244 in ?? () from /tmp/.mount_vVX2pQ/usr/lib/
> libQt5Widgets.so.5
> #14 0x00007fffee4aa196 in QMenu::mouseReleaseEvent(QMouseEvent*) () from /
> tmp/.mount_vVX2pQ/usr/lib/libQt5Widgets.so.5
> #15 0x00007fffee3857c8 in QWidget::event(QEvent*) () from
> /tmp/.mount_vVX2pQ/
> usr/lib/libQt5Widgets.so.5
> #16 0x00007fffee4ac42b in QMenu::event(QEvent*) () from /tmp/.mount_vVX2pQ/
> usr/lib/libQt5Widgets.so.5
> #17 0x00007fffee33f8fc in QApplicationPrivate::notify_helper(QObject*,
> QEvent*) () from /tmp/.mount_vVX2pQ/usr/lib/libQt5Widgets.so.5
> #18 0x00007fffee3470db in QApplication::notify(QObject*, QEvent*) () from /
> tmp/.mount_vVX2pQ/usr/lib/libQt5Widgets.so.5
> #19 0x00000031e04880f0 in QCoreApplication::notifyInternal2(QObject*,
> QEvent*)
> () from /tmp/.mount_vVX2pQ/usr/lib/libQt5Core.so.5
> #20 0x00007fffee345dce in QApplicationPrivate::sendMouseEvent(QWidget*,
> QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) ()
>    from /tmp/.mount_vVX2pQ/usr/lib/libQt5Widgets.so.5
> #21 0x00007fffee3a1135 in ?? () from /tmp/.mount_vVX2pQ/usr/lib/
> libQt5Widgets.so.5
> #22 0x00007fffee3a39e3 in ?? () from /tmp/.mount_vVX2pQ/usr/lib/
> libQt5Widgets.so.5
> #23 0x00007fffee33f8fc in QApplicationPrivate::notify_helper(QObject*,
> QEvent*) () from /tmp/.mount_vVX2pQ/usr/lib/libQt5Widgets.so.5
> #24 0x00007fffee346808 in QApplication::notify(QObject*, QEvent*) () from /
> tmp/.mount_vVX2pQ/usr/lib/libQt5Widgets.so.5
> #25 0x00000031e04880f0 in QCoreApplication::notifyInternal2(QObject*,
> QEvent*)
> () from /tmp/.mount_vVX2pQ/usr/lib/libQt5Core.so.5
> #26 0x00007fffedd6a4ad in
> QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate:
> :MouseEvent*)
> () from /tmp/.mount_vVX2pQ/usr/lib/libQt5Gui.so.5
> #27 0x00007fffedd6c1c5 in
> QGuiApplicationPrivate::processWindowSystemEvent(
> QWindowSystemInterfacePrivate::WindowSystemEvent*)
> ()
>    from /tmp/.mount_vVX2pQ/usr/lib/libQt5Gui.so.5
> #28 0x00007fffedd4d023 in
> QWindowSystemInterface::sendWindowSystemEvents(QFlags<
> QEventLoop::ProcessEventsFlag>)
> () from /tmp/.mount_vVX2pQ/usr/lib/libQt5Gui.so.5
> #29 0x00007fffe4d62f30 in ?? () from /tmp/.mount_vVX2pQ/usr/lib/
> libQt5XcbQpa.so.5
> #30 0x00007fffea9c5197 in g_main_context_dispatch () from
> /lib/x86_64-linux-
> gnu/libglib-2.0.so.0
> #31 0x00007fffea9c53f0 in ?? () from /lib/x86_64-linux-gnu/libglib-
> 2.0.so.0
> ---Type <return> to continue, or q <return> to quit---
> #32 0x00007fffea9c549c in g_main_context_iteration () from
> /lib/x86_64-linux-
> gnu/libglib-2.0.so.0
> #33 0x00000031e04d5d87 in
> QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
> ()
> from /tmp/.mount_vVX2pQ/usr/lib/libQt5Core.so.5
> #34 0x00000031e04863da in
> QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /
> tmp/.mount_vVX2pQ/usr/lib/libQt5Core.so.5
> #35 0x00000031e048e1bd in QCoreApplication::exec() () from
> /tmp/.mount_vVX2pQ/
> usr/lib/libQt5Core.so.5
> #36 0x0000000000405054 in main (argc=1, argv=<optimized out>) at /b/dktemp/
> digikam-master/core/app/main/main.cpp:240
> (gdb)
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20170131/b4445ced/attachment-0001.html>

------------------------------

Message: 2
Date: Tue, 31 Jan 2017 13:30:34 +0100
From: Phil <[hidden email]>
To: digiKam - Home Manage your photographs as a professional with the
        power of open source <[hidden email]>
Subject: Re: Scan for new items takes ages after syncing collection
        btw. two computers
Message-ID: <[hidden email]>
Content-Type: text/plain; charset=windows-1252; format=flowed



On 30/01/17 20:03, Andrew Goodbody wrote:
>
>
> On 30/01/17 16:18, [hidden email] wrote:
>> Chris,
>>
>>> It's probably because Unison updates the 'last access' date field on
>>> the files and Digikam uses this to decide whether to resacn.
>>
>>> In Unix/Linux a file has three times associated with it:-
>>>
>>>     Modified time - last time the file contents were changes (write or
>>> append)
>>>     Accessed time - last time the file was accessed (read or write)
>>>     Status changed - last time the attributes (owner, permissions,
>>> etc.) were changed
>>
>> yeah, that's what I came up with, too -- the digikam4.db file will
>> probably have its access time changed during syncing.
>>
>>> Digikam will compare its database with one (or more) of the above file
>>> times I expect.  A Digikam expert will no doubt tell us.
>>
>> But if so, I still wonder where digikam keeps record of digikam4.db's
>> access time?
>
> It doesn't, that's not how it works.
>
> digiKam stores the path to the root of the collection in the database
> and this can look different on different systems, hence it will do a
> full rescan.

Here the db is synced in one case, shared in the other case, so the
collection root paths are identical on the two machines.
Philip


------------------------------

Message: 3
Date: Tue, 31 Jan 2017 21:44:14 +0000
From: [hidden email]
To: digiKam - Home Manage your photographs as a professional with the
        power of open source <[hidden email]>
Subject: Re: digiKam 5.4.0 crashes on Rebuilding Thumbnails
Message-ID:
        <[hidden email]>
Content-Type: text/plain; charset="utf-8"; Format="flowed";
        DelSp="Yes"

Hi Gilles,

here's my log-file captured with the tee-command


Zitat von Gilles Caulier <[hidden email]>:

> Please use digiKam 5.5.0 pre-release AppImage linux bundle and try
> to reproduce the problem. File is here :       
>    https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM
>      
>     The bundle include debug symbols and can be executed into GDB like this :
>      
>     ./digikam-5.5.0-01-x86-64.appimage debug
>
> And when it crash, use gdb 'bt' command to get a backtrace..
>
>     
>    Gilles Caulier
>
>
>    2017-01-30 21:18 GMT+01:00 <[hidden email]>:
>
>> I have the same problem with
>> GLib-ERROR **: ....... Too many open files
>> under ArchLinux with this and other maintance modules especaly (but
>> not only) 
>> when allowing the use of al CPU kernels.
>>
>> Jürgen
>>
>> Zitat von Andrey Goreev <[hidden email]>:
>>
>>> digiKam crashes on me whenever I try to rebuild thumbnails.
>>> Here is what the terminal says:
>>> "
>>> digikam.general: stage1
>>> digikam.general: stage2
>>> digikam.general: Using  4  CPU core to run threads
>>> digikam.general: Using  1  CPU core to run threads
>>> QXcbConnection: XCB error: 3 (BadWindow), sequence: 3317, resource id:
>>> 44040800, major code: 40 (TranslateCoords), minor code: 0
>>>
>>> (process:11458): GLib-ERROR **: Creating pipes for GWakeup: Too
>>> many open files
>>>
>>> Trace/breakpoint trap
>>> "
>>>
>>> Any solution for that?
>>> Linux Mint 18.1 KDEsqlite
>>
>> --
>> Jürgen Blumenschein, eMail: [hidden email]
>> Homepage: http://members.dokom.net/blumenschein
>> Am Quartus 17
>> D-44149 Dortmund
>> Tel.: +49 231 7217321[1], Handy: +49 176 5591 4562[2]
>> public key:
>> http://members.dokom.net/blumenscheinJuergen_Blumenschein_(0xC9358EBB)_public_key.asc
>>  



Links:
------
[1] <a href="tel:%2B49%20231%207217321">tel:%2B49%20231%207217321
[2] <a href="tel:%2B49%20176%205591%204562">tel:%2B49%20176%205591%204562
--
Jürgen Blumenschein, eMail: [hidden email]
Homepage: http://members.dokom.net/blumenschein
Am Quartus 17
D-44149 Dortmund
Tel.: <a href="tel:%2B49%20231%207217321" value="+492317217321">+49 231 7217321, Handy: <a href="tel:%2B49%20176%205591%204562" value="+4917655914562">+49 176 5591 4562
public key:
http://members.dokom.net/blumenscheinJuergen_Blumenschein_(0xC9358EBB)_public_key.asc
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: digikam55.log
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20170131/13322a37/attachment.ksh>

------------------------------

Subject: Digest Footer

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users


------------------------------

End of Digikam-users Digest, Vol 140, Issue 150
***********************************************



--

   gplus_Seiten_Signatur
hajo
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: unsubscribe does not work propperly

hajo
In reply to this post by Martin Kaspar
Martin,

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.

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.

Thx,
Hajo

-- 
Composed on my tablet. Apologies for typos.


On 1 Feb 2017, at 06:11, Martin Kaspar <[hidden email]> wrote:

unsubscribe does not work propperly

On Tue, Jan 31, 2017 at 10:44 PM, <[hidden email]> wrote:
Send Digikam-users mailing list submissions to
        [hidden email]

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
        [hidden email]

You can reach the person managing the list at
        [hidden email]

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 5.5 froze on opening Settings (Gilles Caulier)
   2. Re: Scan for new items takes ages after syncing collection
      btw. two computers (Phil)
   3. Re: digiKam 5.4.0 crashes on Rebuilding Thumbnails
      ([hidden email])


----------------------------------------------------------------------

Message: 1
Date: Tue, 31 Jan 2017 18:39:55 +0100
From: Gilles Caulier <[hidden email]>
To: digiKam - Home Manage your photographs as a professional with the
        power of open source <[hidden email]>
Subject: Re: digiKam 5.5 froze on opening Settings
Message-ID:
        <CAHFG6sEtJJkPmLk9vZ3mxPFUr5U=TN8viyKxE41eZwX=[hidden email]>
Content-Type: text/plain; charset="utf-8"

It crash in exiv2 shared lib when Exif metadata viewer settings is
populated with tags to filters.

This must never expect of course.

Please report this problem in bugzilla, including the GDB backtrace

Thanks in advance

Gilles Caulier


2017-01-31 18:27 GMT+01:00 Andrey Goreev <[hidden email]>:

> On Monday, January 30, 2017 10:47:20 PM MST Gilles Caulier wrote:
> > ./digikam-5.5.0-01-x86-64.appimage debug
>
> digikam 5.5 froze on opening Settings.
>
> --
> Thread 1 "digikam" hit Catchpoint 1 (exception thrown), 0x00007fffebe788bd
> in
> __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
> (gdb) bt
> #0  0x00007fffebe788bd in __cxa_throw () from /usr/lib/x86_64-linux-gnu/
> libstdc++.so.6
> #1  0x00007ffff5e43b02 in Exiv2::ExifKey::ExifKey (this=<optimized out>,
> ti=...) at /b/ext_exiv2/ext_exiv2-prefix/src/ext_exiv2/src/tags.cpp:3157
> #2  0x00007ffff682aea0 in Digikam::MetaEngine::getStdExifTagsList
> (this=this@entry=0x7fffffffb100)
>     at /b/dktemp/digikam-master/core/libs/dmetadata/metaengine_
> exif.cpp:1087
> #3  0x00007ffff69a36c4 in Digikam::MetadataPanel::slotTabChanged
> (this=this@entry=0x3b65d40)
>     at /b/dktemp/digikam-master/core/libs/widgets/metadata/
> metadatapanel.cpp:
> 311
> #4  0x00007ffff69a402d in Digikam::MetadataPanel::MetadataPanel
> (this=0x3b65d40, tab=0x3b66970)
>     at /b/dktemp/digikam-master/core/libs/widgets/metadata/
> metadatapanel.cpp:
> 232
> #5  0x00007ffff768a70a in Digikam::SetupMetadata::SetupMetadata
> (this=0x3b30ee0, parent=<optimized out>)
>     at /b/dktemp/digikam-master/core/utilities/setup/metadata/
> setupmetadata.cpp:463
> #6  0x00007ffff766294a in Digikam::Setup::Setup (this=this@entry
> =0x3a1f520,
> parent=parent@entry=0x84ee70)
>     at /b/dktemp/digikam-master/core/utilities/setup/setup.cpp:186
> #7  0x00007ffff7664725 in Digikam::Setup::execDialog (parent=0x84ee70,
> page=Digikam::Setup::LastPageUsed)
>     at /b/dktemp/digikam-master/core/utilities/setup/setup.cpp:362
> #8  0x00007ffff7615d44 in Digikam::DigikamApp::qt_static_metacall
> (_o=0x84ee70, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>)
>     at /b/dktemp/digikam-master/build/core/app/moc_digikamapp.cpp:359
> #9  0x00000031e04af846 in QMetaObject::activate(QObject*, int, int,
> void**) ()
> from /tmp/.mount_vVX2pQ/usr/lib/libQt5Core.so.5
> #10 0x00007fffee338ba2 in QAction::triggered(bool) () from
> /tmp/.mount_vVX2pQ/
> usr/lib/libQt5Widgets.so.5
> #11 0x00007fffee33b57d in QAction::activate(QAction::ActionEvent) () from
> /
> tmp/.mount_vVX2pQ/usr/lib/libQt5Widgets.so.5
> #12 0x00007fffee4a3002 in ?? () from /tmp/.mount_vVX2pQ/usr/lib/
> libQt5Widgets.so.5
> #13 0x00007fffee4a9244 in ?? () from /tmp/.mount_vVX2pQ/usr/lib/
> libQt5Widgets.so.5
> #14 0x00007fffee4aa196 in QMenu::mouseReleaseEvent(QMouseEvent*) () from /
> tmp/.mount_vVX2pQ/usr/lib/libQt5Widgets.so.5
> #15 0x00007fffee3857c8 in QWidget::event(QEvent*) () from
> /tmp/.mount_vVX2pQ/
> usr/lib/libQt5Widgets.so.5
> #16 0x00007fffee4ac42b in QMenu::event(QEvent*) () from /tmp/.mount_vVX2pQ/
> usr/lib/libQt5Widgets.so.5
> #17 0x00007fffee33f8fc in QApplicationPrivate::notify_helper(QObject*,
> QEvent*) () from /tmp/.mount_vVX2pQ/usr/lib/libQt5Widgets.so.5
> #18 0x00007fffee3470db in QApplication::notify(QObject*, QEvent*) () from /
> tmp/.mount_vVX2pQ/usr/lib/libQt5Widgets.so.5
> #19 0x00000031e04880f0 in QCoreApplication::notifyInternal2(QObject*,
> QEvent*)
> () from /tmp/.mount_vVX2pQ/usr/lib/libQt5Core.so.5
> #20 0x00007fffee345dce in QApplicationPrivate::sendMouseEvent(QWidget*,
> QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) ()
>    from /tmp/.mount_vVX2pQ/usr/lib/libQt5Widgets.so.5
> #21 0x00007fffee3a1135 in ?? () from /tmp/.mount_vVX2pQ/usr/lib/
> libQt5Widgets.so.5
> #22 0x00007fffee3a39e3 in ?? () from /tmp/.mount_vVX2pQ/usr/lib/
> libQt5Widgets.so.5
> #23 0x00007fffee33f8fc in QApplicationPrivate::notify_helper(QObject*,
> QEvent*) () from /tmp/.mount_vVX2pQ/usr/lib/libQt5Widgets.so.5
> #24 0x00007fffee346808 in QApplication::notify(QObject*, QEvent*) () from /
> tmp/.mount_vVX2pQ/usr/lib/libQt5Widgets.so.5
> #25 0x00000031e04880f0 in QCoreApplication::notifyInternal2(QObject*,
> QEvent*)
> () from /tmp/.mount_vVX2pQ/usr/lib/libQt5Core.so.5
> #26 0x00007fffedd6a4ad in
> QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate:
> :MouseEvent*)
> () from /tmp/.mount_vVX2pQ/usr/lib/libQt5Gui.so.5
> #27 0x00007fffedd6c1c5 in
> QGuiApplicationPrivate::processWindowSystemEvent(
> QWindowSystemInterfacePrivate::WindowSystemEvent*)
> ()
>    from /tmp/.mount_vVX2pQ/usr/lib/libQt5Gui.so.5
> #28 0x00007fffedd4d023 in
> QWindowSystemInterface::sendWindowSystemEvents(QFlags<
> QEventLoop::ProcessEventsFlag>)
> () from /tmp/.mount_vVX2pQ/usr/lib/libQt5Gui.so.5
> #29 0x00007fffe4d62f30 in ?? () from /tmp/.mount_vVX2pQ/usr/lib/
> libQt5XcbQpa.so.5
> #30 0x00007fffea9c5197 in g_main_context_dispatch () from
> /lib/x86_64-linux-
> gnu/libglib-2.0.so.0
> #31 0x00007fffea9c53f0 in ?? () from /lib/x86_64-linux-gnu/libglib-
> 2.0.so.0
> ---Type <return> to continue, or q <return> to quit---
> #32 0x00007fffea9c549c in g_main_context_iteration () from
> /lib/x86_64-linux-
> gnu/libglib-2.0.so.0
> #33 0x00000031e04d5d87 in
> QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
> ()
> from /tmp/.mount_vVX2pQ/usr/lib/libQt5Core.so.5
> #34 0x00000031e04863da in
> QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /
> tmp/.mount_vVX2pQ/usr/lib/libQt5Core.so.5
> #35 0x00000031e048e1bd in QCoreApplication::exec() () from
> /tmp/.mount_vVX2pQ/
> usr/lib/libQt5Core.so.5
> #36 0x0000000000405054 in main (argc=1, argv=<optimized out>) at /b/dktemp/
> digikam-master/core/app/main/main.cpp:240
> (gdb)
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20170131/b4445ced/attachment-0001.html>

------------------------------

Message: 2
Date: Tue, 31 Jan 2017 13:30:34 +0100
From: Phil <[hidden email]>
To: digiKam - Home Manage your photographs as a professional with the
        power of open source <[hidden email]>
Subject: Re: Scan for new items takes ages after syncing collection
        btw. two computers
Message-ID: <[hidden email]>
Content-Type: text/plain; charset=windows-1252; format=flowed



On 30/01/17 20:03, Andrew Goodbody wrote:
>
>
> On 30/01/17 16:18, [hidden email] wrote:
>> Chris,
>>
>>> It's probably because Unison updates the 'last access' date field on
>>> the files and Digikam uses this to decide whether to resacn.
>>
>>> In Unix/Linux a file has three times associated with it:-
>>>
>>>     Modified time - last time the file contents were changes (write or
>>> append)
>>>     Accessed time - last time the file was accessed (read or write)
>>>     Status changed - last time the attributes (owner, permissions,
>>> etc.) were changed
>>
>> yeah, that's what I came up with, too -- the digikam4.db file will
>> probably have its access time changed during syncing.
>>
>>> Digikam will compare its database with one (or more) of the above file
>>> times I expect.  A Digikam expert will no doubt tell us.
>>
>> But if so, I still wonder where digikam keeps record of digikam4.db's
>> access time?
>
> It doesn't, that's not how it works.
>
> digiKam stores the path to the root of the collection in the database
> and this can look different on different systems, hence it will do a
> full rescan.

Here the db is synced in one case, shared in the other case, so the
collection root paths are identical on the two machines.
Philip


------------------------------

Message: 3
Date: Tue, 31 Jan 2017 21:44:14 +0000
From: [hidden email]
To: digiKam - Home Manage your photographs as a professional with the
        power of open source <[hidden email]>
Subject: Re: digiKam 5.4.0 crashes on Rebuilding Thumbnails
Message-ID:
        <[hidden email]>
Content-Type: text/plain; charset="utf-8"; Format="flowed";
        DelSp="Yes"

Hi Gilles,

here's my log-file captured with the tee-command


Zitat von Gilles Caulier <[hidden email]>:

> Please use digiKam 5.5.0 pre-release AppImage linux bundle and try
> to reproduce the problem. File is here :       
>    https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM
>      
>     The bundle include debug symbols and can be executed into GDB like this :
>      
>     ./digikam-5.5.0-01-x86-64.appimage debug
>
> And when it crash, use gdb 'bt' command to get a backtrace..
>
>     
>    Gilles Caulier
>
>
>    2017-01-30 21:18 GMT+01:00 <[hidden email]>:
>
>> I have the same problem with
>> GLib-ERROR **: ....... Too many open files
>> under ArchLinux with this and other maintance modules especaly (but
>> not only) 
>> when allowing the use of al CPU kernels.
>>
>> Jürgen
>>
>> Zitat von Andrey Goreev <[hidden email]>:
>>
>>> digiKam crashes on me whenever I try to rebuild thumbnails.
>>> Here is what the terminal says:
>>> "
>>> digikam.general: stage1
>>> digikam.general: stage2
>>> digikam.general: Using  4  CPU core to run threads
>>> digikam.general: Using  1  CPU core to run threads
>>> QXcbConnection: XCB error: 3 (BadWindow), sequence: 3317, resource id:
>>> 44040800, major code: 40 (TranslateCoords), minor code: 0
>>>
>>> (process:11458): GLib-ERROR **: Creating pipes for GWakeup: Too
>>> many open files
>>>
>>> Trace/breakpoint trap
>>> "
>>>
>>> Any solution for that?
>>> Linux Mint 18.1 KDEsqlite
>>
>> --
>> Jürgen Blumenschein, eMail: [hidden email]
>> Homepage: http://members.dokom.net/blumenschein
>> Am Quartus 17
>> D-44149 Dortmund
>> Tel.: +49 231 7217321[1], Handy: +49 176 5591 4562[2]
>> public key:
>> http://members.dokom.net/blumenscheinJuergen_Blumenschein_(0xC9358EBB)_public_key.asc
>>  



Links:
------
[1] <a href="tel:%2B49%20231%207217321">tel:%2B49%20231%207217321
[2] <a href="tel:%2B49%20176%205591%204562">tel:%2B49%20176%205591%204562
--
Jürgen Blumenschein, eMail: [hidden email]
Homepage: http://members.dokom.net/blumenschein
Am Quartus 17
D-44149 Dortmund
Tel.: <a href="tel:%2B49%20231%207217321" value="+492317217321">+49 231 7217321, Handy: <a href="tel:%2B49%20176%205591%204562" value="+4917655914562">+49 176 5591 4562
public key:
http://members.dokom.net/blumenscheinJuergen_Blumenschein_(0xC9358EBB)_public_key.asc
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: digikam55.log
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20170131/13322a37/attachment.ksh>

------------------------------

Subject: Digest Footer

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users


------------------------------

End of Digikam-users Digest, Vol 140, Issue 150
***********************************************



--

   gplus_Seiten_Signatur
Free forum by Nabble Edit this page