[digikam] [Bug 357301] New: Album view is not updated automatically anymore

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

[digikam] [Bug 357301] New: Album view is not updated automatically anymore

bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=357301

            Bug ID: 357301
           Summary: Album view is not updated automatically anymore
           Product: digikam
           Version: 4.14.0
          Platform: Archlinux Packages
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: Albums View
          Assignee: [hidden email]
          Reporter: [hidden email]

digiKam stopped updating the album view automatically after file system related
operations such as copying, moving, renaming or deleting. Refreshing the album
view has to be triggered manually.

Reproducible: Always

Steps to Reproduce:
1. Do a file system related operation (rename, delete, copy, move, ...) within
a album view of digiKam
2.
3.

Actual Results:  
File dialog appears depending on operation (i.e. trash confirmation) and plasma
notification of operation appears, but album view is not updated.

Manual refresh (right click on album) has to be triggered to see updated album.

After deleting a file and without manual refresh, digiKam tries to load the
file anyway and shows that the image couldn't be loaded.

Workflow is disrupted.

Expected Results:  
Album view should be updated instantly.

Might be a duplicate of bug #352870.

Some terminal output after a deleting a file:

digikam(3305)/digikam (core) Digikam::DeleteDialog::slotUser1Clicked:
setShowTrashDeleteDialog  true
digikam(3305)/kio (Scheduler) KIO::SchedulerPrivate::doJob:
KIO::SimpleJob(0x56fcad0)
digikam(3305)/kio (Scheduler) KIO::SchedulerPrivate::protoQ: creating
ProtoQueue instance for "trash"
digikam(3305)/kio (Scheduler) KIO::ProtoQueue::ProtoQueue:
m_maxConnectionsTotal: 2 m_maxConnectionsPerHost: 2
digikam(3305)/kio (Slave) KIO::Slave::createSlave: createSlave "trash" for
KUrl("trash:/")
digikam(3305)/kio (KIOConnection) KIO::ConnectionServer::listenForRemote:
Listening on  "local:/run/user/1000/ksocket-USER/digikamnQ3305.slave-socket"
digikam(3305)/kio (Scheduler) KIO::SchedulerPrivate::jobFinished:
KIO::StatJob(0x56fcad0) KIO::Slave(0x5564d20)
digikam(3305)/kio (KIOJob) KIO::CopyJobPrivate::startRenameJob:
KUrl("file:///home/USER/fotos/album/PICTURE.jpg") -> KUrl("trash:/PICTURE.jpg")
trying direct rename first
digikam(3305)/kio (Scheduler) KIO::SchedulerPrivate::doJob:
KIO::SimpleJob(0x5c802b0)
digikam(3305)/kio (Scheduler) KIO::SchedulerPrivate::setJobPriority:
KIO::SimpleJob(0x5c802b0) 1
digikam(3305)/kio (KDirListerCache) KDirListerCache::slotFilesAdded:
KUrl("file:///home/USER/.local/share/Trash/files/PICTURE.jpg")
digikam(3305)/kio (KDirListerCache) KDirListerCache::updateDirectory:
KUrl("file:///home/USER/.local/share/Trash/files/PICTURE.jpg")
digikam(3305)/kio (Scheduler) KIO::SchedulerPrivate::jobFinished:
KIO::SimpleJob(0x5c802b0) KIO::Slave(0x5564d20)
digikam(3305)/kio (KIOJob) KIO::CopyJobPrivate::slotResultRenaming: Renaming
succeeded, move on
digikam(3305)/kio (KIOJob) KIO::CopyJobPrivate::statCurrentSrc: Stating
finished. To copy: 0 , available: 18446744073709551615
digikam(3305)/kio (KIOJob) KIO::CopyJob::emitResult: KDirNotify'ing
FilesRemoved ("file:///home/USER/fotos/album/PICTURE.jpg")
digikam(3305)/kio (KDirListerCache) KDirListerCache::slotFilesAdded:
KUrl("trash:/")
digikam(3305)/kio (KDirListerCache) KDirListerCache::updateDirectory:
KUrl("trash:/")


Component info:

digiKam version 4.14.0
Exiv2 kann in JP2 speichern: Ja
Exiv2 kann in JPEG speichern: Ja
Exiv2 kann in PGF speichern: Ja
Exiv2 kann in PNG speichern: Ja
Exiv2 kann in TIFF speichern: Ja
Exiv2 unterstützt XMP-Metadaten: Ja
LibCImg: 130
LibEigen: 3.2.7
LibExiv2: 0.25
LibJPEG: 80
LibJasper: 1.900.1
LibKDE: 4.14.15
LibKExiv2: 2.4.0
LibKGeoMap: 3.1.0
LibKdcraw: 2.4.2
LibLCMS: 2070
LibLensFun: 0.3.1-0
LibPGF: 6.14.12
LibPNG: 1.6.19
LibQt: 4.8.7
LibRaw: 0.17.0
LibTIFF: LIBTIFF, Version 4.0.6 Copyright (c) 1988-1996 Sam Leffler Copyright
(c) 1991-1996 Silicon Graphics, Inc.
Marble-Funktion: 0.21.80 (0.22 Beta 1)
Parallelisiertes Entfernen von Mosaikmustern: Unbekannt
Prozessorkerne: 4
Unterstützung für Demosaic GPL2: Unbekannt
Unterstützung für Demosaic GPL3: Unbekannt
Unterstützung für LibLqr: Ja
Unterstützung von RawSpeed-Codec: Unbekannt
Datenbanktreiber: QSQLITE
KIPI-Module: 4.14.0
LibGphoto2: 2.5.8
LibKface: 3.5.0
LibKipi: 2.2.0
LibOpenCV: 2.4.12.2
Unterstützung für Baloo: Ja
Unterstützung für Kdepimlibs: Nein
Unterstützung für Sqlite2: Nein

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 357301] Album view is not updated automatically anymore

bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=357301

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #1 from [hidden email] ---
*** Bug 352870 has been marked as a duplicate of this bug. ***

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 357301] Album view is not updated automatically anymore

bugzilla_noreply
In reply to this post by bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=357301

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]
   Version Fixed In|                            |5.0.0
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |FIXED

--- Comment #2 from [hidden email] ---
digiKam KIO-slave sound like broken on your computer. Probably due to a missing
or bad dependency.

In all cases, with 5.0.0, all digiKam KIO-slave have been replaced by a pure
multithreaded interface. This kind of problem will not appear anymore.

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel