[Bug 224038] New: Thumbnails not shown on launch of digikam

[Andrew Goodbody]

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

           Summary: Thumbnails not shown on launch of digikam
           Product: digikam
           Version: 1.1.0
          Platform: Compiled Sources
        OS/Version: MS Windows
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: [hidden email]
        ReportedBy: [hidden email]


Version:           1.1.0 (using Devel)
Compiler:          mingw4
OS:                MS Windows
Installed from:    Compiled sources

When I open digikam, the album location is restored to where it was when last
closed. However the middle panel of the screen, where the thumbnails should be
visible, is empty. It takes a couple of times of pressing F5 to refresh and
changing the directory a couple of times before the thumbnails are loaded. The
thumbnails can disappear from view sometimes while using digikam as well.

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- 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

[Gilles Caulier-4]

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


Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]
          Component|general                     |Kioslave




--- Comment #1 from Gilles Caulier <caulier gilles gmail com>  2010-01-24 15:26:36 ---
Sound like kioslave won't to start on your computer.

Do you have compiled digiKam yourself ?

Go Help/Compenents info to show all depencies

Gilles Caulier

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- 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

[Andrew Goodbody]

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





--- Comment #2 from Andrew Goodbody <ajg02 elfringham co uk>  2010-01-24 15:48:20 ---
I see multiple entries for kioslave in Task Manager as I start digikam.

I compiled using the emerge system on XP with SP3.

Component Information gives the following:-

digiKam version 1.1.0
Exiv2 can write to Jp2: Yes
Exiv2 can write to Jpeg: Yes
Exiv2 can write to Pgf: No
Exiv2 can write to Png: Yes
Exiv2 can write to Tiff: Yes
Exiv2 supports XMP metadata: Yes
LibCImg: 130
LibExiv2: 0.19
LibJPEG: 62
LibJasper: 1.900.1
LibKDE: 4.4.59 (KDE 4.4.59 (KDE 4.5 >= 20100107))
LibKExiv2: 1.0.0
LibKdcraw: 1.0.0
LibLCMS: 118
LibPGF: 6.09.44
LibPNG: 1.2.35
LibQt: 4.6.1
LibRaw: 0.8.5
LibTIFF: LIBTIFF, Version 3.8.2 Copyright (c) 1988-1996 Sam Leffler Copyright
(c) 1991-1996 Silicon Graphics, Inc.
Marble widget: 0.10.0 SVN
Parallelized demosaicing: Yes
LibKipi: 1.0.0

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- 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

[Andrew Goodbody]

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





--- Comment #3 from Andrew Goodbody <ajg02 elfringham co uk>  2010-01-24 18:20:47 ---
It seems like the F5 is not needed. All I need to do is to wait for some time
and then change directory in order to get the thumbnails visible. I have over
27,000 pictures in this album, I don't know if that is a factor or not.

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- 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

[Johannes Wienke-3]

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





--- Comment #4 from Johannes Wienke <languitar semipol de>  2010-01-24 18:23:23 ---
Does digikam use the full cpu while you wait for the thumbnails?

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- 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

[Andrew Goodbody]

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





--- Comment #5 from Andrew Goodbody <ajg02 elfringham co uk>  2010-01-24 18:42:41 ---
No, the CPU is not at 100%, at least not once the digikam window is rendered.
The thumbnails will never appear unless I change the directory viewed some time
after the window has appeared. Changing directory too soon does not result in
the thumbnails being shown. The CPU is not at 100% at this stage.

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- 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

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


Julien Narboux <[hidden email]> changed:

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




--- Comment #6 from Julien Narboux <Julien narboux fr>  2010-01-25 09:00:33 ---
After compiling Digikam 1.0.0 under MaxOSX 10.6 using mac ports, I also can not
see the thumbnails. I guess it is more an installation problem than a bug in
Digikam.
It seems to be a quite common problem of wrong Digikam installations. I have
seen the same problem under linux in the past as well. Sometimes after updating
Digikam, I had to log out / log in to see the thumbnails again.

It would be nice if there were some graphical feedback/error message stating
that there is a problem with kioslave.

Julien

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- 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

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


David Eriksson <[hidden email]> changed:

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




--- Comment #7 from David Eriksson <meldavid acc umu se>  2010-01-27 20:15:25 ---
I have the same problem. It sometimes happens also after running digikam for
some time. This is what I get as debug output:

[38896] Debug:digikam(38896)/kio (Slave) KIO::Slave::createSlave: createSlave
"digikamalbums" for KUrl("digikamalbums:/Små bilder/?albumRoot=C:/Documents and
Settings/David/Mina dokument/Mina
bilder&albumRootId=2&databaseType=QSQLITE&databaseName=C:/Documents and
Settings/David/Mina dokument/Mina bilder/digikam4.db")
[38896] Debug:digikam(38896)/kio (KIOConnection)
KIO::ConnectionServer::listenForRemote: Listening on  "tcp://127.0.0.1:3477"
[7448] Debug:klauncher(7448)/kio (KLauncher) KLauncher::requestSlave:
KLauncher: launching new slave  "D:/KDE2/bin/kioslave.exe"  with protocol=
"digikamalbums"  args= ("kio_digikamalbums", "digikamalbums",
"tcp://127.0.0.1:4780", "tcp://127.0.0.1:3477")
[7448] Debug:klauncher(7448)/kio (KLauncher) KLauncher::processRequestReturn:
"D:/KDE2/bin/kioslave.exe" (pid 32720) up and running.
[32720] Debug:trying to load 'kio_digikamalbums'
[38896] Debug:digikam(38896)/kio (Slave) KIO::Slave::timeout: slave failed to
connect to application pid= 32720  protocol= "digikamalbums"
[38896] Debug:digikam(38896)/kio (Slave) KIO::Slave::timeout: Houston, we lost
our slave, pid= 32720
[38896] Debug:digikam(38896)/kio (Slave) KIO::Slave::timeout: slave died pid =
32720
[32720] Debug:kio_digikamalbums(32720)
KIO::SocketConnectionBackend::connectToRemote: could not connect to
KUrl("tcp://127.0.0.1:3477")
[32720] Debug:kio_digikamalbums(32720)/kio (kioslave)
KIO::SlaveBase::connectSlave: SlaveBase: failed to connect to
"tcp://127.0.0.1:3477"
[32720] Debug:Reason: ""
[7448] Debug:klauncher(7448)/kio (KLauncher) KLauncher::slotFinished: process
finished exitcode= 255 exitStatus= 0
[37020] Warning:QSqlDatabasePrivate::removeDatabase: connection
'digikamDatabase-4080440' is still in use, all queries will cease to work.
[7448] Debug:klauncher(7448)/kio (KLauncher) KLauncher::slotGotOutput: Family
none
[7448] Family none
[7448] Debug:klauncher(7448)/kio (KLauncher) KLauncher::slotFinished: process
finished exitcode= 0 exitStatus= 0

I can see that a kioslave process is started with the correct pid but it
disappears quickly.

David

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- 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

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





--- Comment #8 from David Eriksson <meldavid acc umu se>  2010-02-03 15:33:46 ---
I have to correct myself. The kioslave processes don't disappear quickly. They
stay open for some time, ranging from a few second to several minutes. I also
have kioslave processes that never disappears, even though no digikam process
is running.

I also can trigger the problem with the new albummodeltest. It sometimes runs
nicely and finishes without any problems but sometimes it just freezes and I
have to kill it. The debug output then is similar to the above:

QDEBUG : AlbumModelTest::testPAlbumModel() qttest(1988)/digikam (core)
AlbumModelTest::ensureItemCounts: Waiting for Alb
umManager and the IOSlave to create DAlbums...
QDEBUG : AlbumModelTest::testPAlbumModel() qttest(1988)/kio (Slave)
KIO::Slave::createSlave: createSlave "digikamdates"
for
KUrl("digikamdates:?databaseType=QSQLITE&databaseName=C:/DOCUME~1/David/LOKALA~1/Temp/albummodeltest-15_19_57/digika
m4.db")
QDEBUG : AlbumModelTest::testPAlbumModel() qttest(1988)/kio (KIOConnection)
KIO::ConnectionServer::listenForRemote: List
ening on  "tcp://127.0.0.1:1436"
QDEBUG : AlbumModelTest::testPAlbumModel() qttest(1988)/kio (Slave)
KIO::Slave::createSlave: createSlave "digikamalbums"
 for
KUrl("digikamalbums:?databaseType=QSQLITE&databaseName=C:/DOCUME~1/David/LOKALA~1/Temp/albummodeltest-15_19_57/digi
kam4.db")
QDEBUG : AlbumModelTest::testPAlbumModel() qttest(1988)/kio (KIOConnection)
KIO::ConnectionServer::listenForRemote: List
ening on  "tcp://127.0.0.1:1437"
QDEBUG : AlbumModelTest::testPAlbumModel() qttest(1988)/kio (Slave)
KIO::Slave::createSlave: createSlave "digikamtags" f
or
KUrl("digikamtags:?databaseType=QSQLITE&databaseName=C:/DOCUME~1/David/LOKALA~1/Temp/albummodeltest-15_19_57/digikam4
.db")
QDEBUG : AlbumModelTest::testPAlbumModel() qttest(1988)/kio (KIOConnection)
KIO::ConnectionServer::listenForRemote: List
ening on  "tcp://127.0.0.1:1438"
QDEBUG : AlbumModelTest::testPAlbumModel() qttest(1988)/kio (Slave)
KIO::Slave::timeout: slave failed to connect to appl
ication pid= 5520  protocol= "digikamdates"
QDEBUG : AlbumModelTest::testPAlbumModel() qttest(1988)/kio (Slave)
KIO::Slave::timeout: Houston, we lost our slave, pid
= 5520
QDEBUG : AlbumModelTest::testPAlbumModel() qttest(1988)/kio (Slave)
KIO::Slave::timeout: slave died pid =  5520
QDEBUG : AlbumModelTest::testPAlbumModel() qttest(1988)/kio (Slave)
KIO::Slave::timeout: slave failed to connect to appl
ication pid= 5524  protocol= "digikamalbums"
QDEBUG : AlbumModelTest::testPAlbumModel() qttest(1988)/kio (Slave)
KIO::Slave::timeout: Houston, we lost our slave, pid
= 5524
QDEBUG : AlbumModelTest::testPAlbumModel() qttest(1988)/kio (Slave)
KIO::Slave::timeout: slave died pid =  5524
QDEBUG : AlbumModelTest::testPAlbumModel() qttest(1988)/kio (Slave)
KIO::Slave::timeout: slave failed to connect to appl
ication pid= 2640  protocol= "digikamtags"
QDEBUG : AlbumModelTest::testPAlbumModel() qttest(1988)/kio (Slave)
KIO::Slave::timeout: Houston, we lost our slave, pid
= 2640
QDEBUG : AlbumModelTest::testPAlbumModel() qttest(1988)/kio (Slave)
KIO::Slave::timeout: slave died pid =  2640

Can it be some timeout that is to short? Since the process lives for sometime
after the debug message that it has died can it be that it some how starts to
slow on Windows?

This bug is quite annoying since it can happen anytime during working with
digikam that you all of a sudden don't see any pictures. I have not figured out
a way of getting the pictures back quickly. Instead you have to click around
and hope that it will come back, which it does eventually.

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- 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

[Andrew Goodbody]

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





--- Comment #9 from Andrew Goodbody <ajg02 elfringham co uk>  2010-02-03 22:14:40 ---
Yes I think it may be a timeout issue. After I start digikam and have the main
window up, the hard disk is still being accessed a lot. It's only after the hdd
accesses have slowed down or stopped that I can change directories and then get
the thumbnails shown. So I am guessing that kioslave is busy accessing the hdd
and is thus unresponsive to digikam for too long, but I don't know how that
stuff works in reality. Once the disk cache contains the right data kioslave
manages to respond in time and all is well until the disk cache is evicted and
the process starts again.
David, if the bug annoys you, please vote for it if you have any votes spare.

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- 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

[Marcel Wiesweg]

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





--- Comment #10 from Marcel Wiesweg <marcel wiesweg gmx de>  2010-02-04 18:25:47 ---
In any case it's a kdelibs kio issue. We just tell KIO to start a job and wait
for results.
If you are both working on Windows, it's most probably a Windows issue.

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- 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

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





--- Comment #11 from David Eriksson <meldavid acc umu se>  2010-02-04 22:13:44 ---
So that means that this report should be reassigned? To where?

As far as I can tell what happens is that the job never reports any result just
debug output that the slave died.

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- 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

[Gilles Caulier-4]

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


Gilles Caulier <[hidden email]> changed:

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




--- Comment #12 from Gilles Caulier <caulier gilles gmail com>  2010-02-05 12:19:21 ---
Patrick Spendrin, who maintain KDE windows project is the best people to
respond here...

Gilles Caulier

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- 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

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





--- Comment #13 from David Eriksson <meldavid acc umu se>  2010-02-08 14:12:08 ---
There are at least two different problems here.

One is that the slaves dies, or is regarded as dead because they start slowly.
This problem maybe a generic kdelibs KIO problem or related to the
implementation of the digikamslaves.

The other problem is related to digikams handling of errors with KIO jobs. I
have done some more investigations and the job sends the signal result with the
error code that the slave died. However as far as I can see the only thing done
about it on the digikam end is to issue a kWarning with the error. The
albummodeltest stops since it is waiting for a signalAllDAlbumsLoaded which is
never emitted. I don't know if digikam also waits for this signal or if it
waits for the data signal from the job, which is never emitted since the slave
is dead. It would be nice to have some sort of notification that the reason no
pictures are shown is that the slave died and a refresh button or something to
try restart the slave/job. I am willing to help with this but I don't know
where in the code to start looking.

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- 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

[Marcel Wiesweg]

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





--- Comment #14 from Marcel Wiesweg <marcel wiesweg gmx de>  2010-02-08 18:22:49 ---
This problem must be fixed in kdelibs on Windows! This has never been a problem
on Linux. For you a workaround in the UI looks like a good solution for your
problem at hand, but it is not maintainable to add workarounds to the UI for
platform bugs which troubled us on a specific system for a specific version.
And you will agree that we cannot require users to restart ioslaves
manually...you dont use a hand crank to start your car? ;-)

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- 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

[Patrick Spendrin]

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





--- Comment #15 from Saro Engels <ps_ml gmx de>  2010-02-08 18:39:29 ---
I haven't yet seen any logic within these bugs. Similar bugs could occur in
kate e.g. in the file view there (the kioslave just dies away). The real
problem might not even be kioslave, but rather dbus as well. For those users on
windows here: Please report your operating system and the compiler with which
your packages had been compiled (the one you chose when installing
KDE/digikam). Also since kioslaves are handled via dbus ipc, please check your
firewalls for any issues or checks.

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- 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

[Andrew Goodbody]

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





--- Comment #16 from Andrew Goodbody <ajg02 elfringham co uk>  2010-02-08 22:00:31 ---
My OS is XP Home with SP3. As stated in the summary the compiler was set to
mingw4 when I used emerge to build it. I tried launching digikam with my
firewall turned off, it made no difference. Let me know if there are any other
diagnostics I can do.

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- 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

[Gilles Caulier-4]

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


Gilles Caulier <[hidden email]> changed:

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




--- Comment #17 from Gilles Caulier <caulier gilles gmail com>  2010-02-19 10:55:49 ---
*** Bug 227640 has been marked as a duplicate of this bug. ***

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- 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

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





--- Comment #18 from Julien Narboux <Julien narboux fr>  2010-12-30 09:19:37 ---
Can you please test with digikam 1.7.0/kde 4.4.4 if bug is still there ?
There is an installer available here:
http://sourceforge.net/projects/digikam/files/digikam/1.7.0/digiKam-installer-1.7-win32.exe/download

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- 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

[Andrew Goodbody]

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





--- Comment #19 from Andrew Goodbody <ajg02 elfringham co uk>  2010-12-31 01:12:38 ---
Yes it does still occur with that version. It also occurs in the version I had
built from SVN using kde 4.6.70.
From the logs above and looking at the source kdelibs/kio/kio/slave.cpp you can
see that the kioslave launcher is failing to hear back from the
kio_digikamalbums even though it exists. Also the retry mechanism to wait for a
slow slave is not being triggered (no 'slave is slow' messages). So
kio_digikamalbums appears to be unresponsive for some time after its creation
and the launcher cannot even tell that it exists let alone communicate with it.
I would guess that the time kio_digikamalbums is unresponsive is related to the
size of the database (number of photos?) as there is heavy disk activity at
this time. Waiting a short time (enough to get db into disk cache?) allows the
slave to start if you do something such as change directory. If you wait too
long it will fail again (db evicted from cache?). Increasing
SLAVE_CONNECTION_TIMEOUT_MIN does allow the slave to start but I don't think
that is an acceptable solution.

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- 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