Hi,
with digikam 2.9.0 on Microsoft Windows 7 pro 64 bits and XP 32 bits I have big problems with a medium sized pictures collection (about 22000 pictures, 700 albums, with CR2 and JPG files). When I first start digiKam, I give it the root of the collection, it then scans the content for the first time and fills the database (SQLite). But once started, digiKam displays nothing, whatever the album I select (yet everything is OK in the database : the photos have a status of 1, the albums are there, the pictures are well related to an album, etc.).If I try to leave digiKam, I see that it stays in memory (probably a crashbecause dont seem to do anything). If I kill all processes (digiKam and KDE) and then restart digiKam, at worst digiKam crashes at best it shows nothing like the first time. If I close again all processes andthat I move admit half the collection apart from the root and I start digiKamagain, it displays all the images well and naturally creates thumbnails in the second file database ... (except for the files I moved outside the root of the collection of course). I also tried with another collection of pictures and had the same results... If a bug, it is really a critical one to me... Laurent. _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Hello Laurent,
i hvae the same Problem with Digikam 2.6 and also 2.9. from the anwers in the newsgroup nothing was helpful, the problem always exists. Wolfgang --- Laurent Espitallier <[hidden email]> schrieb am Sa, 17.11.2012: > Von: Laurent Espitallier <[hidden email]> > Betreff: [Digikam-users] Big problems with medium to large sized collections under Microsoft Windows > An: "digiKam - Home Manage your photographs as a professional with the power of open source" <[hidden email]> > Datum: Samstag, 17. November, 2012 11:14 Uhr > Hi, > > with digikam 2.9.0 on Microsoft Windows 7 pro 64 bits and XP > 32 bits I > have big problems with a medium sized pictures collection > (about 22000 > pictures, 700 albums, with CR2 and JPG files). When I first > start > digiKam, I give it the root of the collection, it then scans > the content > for the first time and fills the database (SQLite). But once > started, > digiKam displays nothing, whatever the album I select (yet > everything is > OK in the database : the photos have a status of 1, the > albums are > there, the pictures are well related to an album, etc.).If I > try to > leave digiKam, I see that it stays in memory (probably a > crashbecause > dont seem to do anything). If I kill all processes (digiKam > and KDE) and > then restart digiKam, at worst digiKam crashes at best it > shows nothing > like the first time. If I close again all processes andthat > I move admit > half the collection apart from the root and I start > digiKamagain, it > displays all the images well and naturally creates > thumbnails in the > second file database ... (except for the files I moved > outside the root > of the collection of course). I also tried with another > collection of > pictures and had the same results... > > If a bug, it is really a critical one to me... > > Laurent. > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users > Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Hi Wolfgang,
The good news is, I'm not totally crazy :D I filled a bug there https://bugs.kde.org/show_bug.cgi?id=310252 Laurent Le 19/11/2012 12:26, Wolfgang Strobel a écrit : > Hello Laurent, > > i hvae the same Problem with Digikam 2.6 and also 2.9. > from the anwers in the newsgroup nothing was helpful, the problem always exists. > > Wolfgang > > > > --- Laurent Espitallier <[hidden email]> schrieb am Sa, 17.11.2012: > >> Von: Laurent Espitallier <[hidden email]> >> Betreff: [Digikam-users] Big problems with medium to large sized collections under Microsoft Windows >> An: "digiKam - Home Manage your photographs as a professional with the power of open source" <[hidden email]> >> Datum: Samstag, 17. November, 2012 11:14 Uhr >> Hi, >> >> with digikam 2.9.0 on Microsoft Windows 7 pro 64 bits and XP >> 32 bits I >> have big problems with a medium sized pictures collection >> (about 22000 >> pictures, 700 albums, with CR2 and JPG files). When I first >> start >> digiKam, I give it the root of the collection, it then scans >> the content >> for the first time and fills the database (SQLite). But once >> started, >> digiKam displays nothing, whatever the album I select (yet >> everything is >> OK in the database : the photos have a status of 1, the >> albums are >> there, the pictures are well related to an album, etc.).If I >> try to >> leave digiKam, I see that it stays in memory (probably a >> crashbecause >> dont seem to do anything). If I kill all processes (digiKam >> and KDE) and >> then restart digiKam, at worst digiKam crashes at best it >> shows nothing >> like the first time. If I close again all processes andthat >> I move admit >> half the collection apart from the root and I start >> digiKamagain, it >> displays all the images well and naturally creates >> thumbnails in the >> second file database ... (except for the files I moved >> outside the root >> of the collection of course). I also tried with another >> collection of >> pictures and had the same results... >> >> If a bug, it is really a critical one to me... >> >> Laurent. >> _______________________________________________ >> Digikam-users mailing list >> [hidden email] >> https://mail.kde.org/mailman/listinfo/digikam-users >> > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by Wolfgang Strobel
is Laurent and myself the only users, which have problems with digikam under windows xp or windows 7? can somebody tell us a real way to use digicam with large size collections without to change unix? Is the problem directly in digicam or only in the interaction from digicam and the kde-plugins? Is it possibel to start digicam in "debugmodus" under windows to find the exact point of the error? in hope of a helpful answer wolfgang > Hello Laurent, > > i have the same Problem with Digikam 2.6 and also 2.9. > from the anwers in the newsgroup nothing was helpful, the problem always exists. > > Wolfgang > > > > --- Laurent Espitallier [hidden email] schrieb am Sa, 17.11.2012: > >> Von: Laurent Espitallier [hidden email] >> Betreff: [Digikam-users] Big problems with medium to large sized collections under Microsoft Windows >> An: "digiKam - Home Manage your photographs as a professional with the power of open source" [hidden email] >> Datum: Samstag, 17. November, 2012 11:14 Uhr >> Hi, >> >> with digikam 2.9.0 on Microsoft Windows 7 pro 64 bits and XP >> 32 bits I >> have big problems with a medium sized pictures collection >> (about 22000 >> pictures, 700 albums, with CR2 and JPG files). When I first >> start >> digiKam, I give it the root of the collection, it then scans >> the content >> for the first time and fills the database (SQLite). But once >> started, >> digiKam displays nothing, whatever the album I select (yet >> everything is >> OK in the database : the photos have a status of 1, the >> albums are >> there, the pictures are well related to an album, etc.).If I >> try to >> leave digiKam, I see that it stays in memory (probably a >> crashbecause >> dont seem to do anything). If I kill all processes (digiKam >> and KDE) and >> then restart digiKam, at worst digiKam crashes at best it >> shows nothing >> like the first time. If I close again all processes andthat >> I move admit >> half the collection apart from the root and I start >> digiKamagain, it >> displays all the images well and naturally creates >> thumbnails in the >> second file database ... (except for the files I moved >> outside the root >> of the collection of course). I also tried with another >> collection of >> pictures and had the same results... >> >> If a bug, it is really a critical one to me... >> >> Laurent. >> _______________________________________________ >> Digikam-users mailing list >> [hidden email] >> https://mail.kde.org/mailman/listinfo/digikam-users >> > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users > _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
On 04/12/12 19:43, Wolfgang Strobel wrote:
> Hello Digicam-users, digiKam with a K > is Laurent and myself the only users, which have problems with digikam > under windows xp or windows 7? No. I had problems as well, there were others as well I think. > can somebody tell us a real way to use digicam with large size > collections without to change unix? No. I changed to Linux. > Is the problem directly in digicam or only in the interaction from > digicam and the kde-plugins? I don't know what you are referring to as kde-plugins. AFAICT the problem is due to losing communication with the kioslave processes that are launched, digiKam then times out and assumes the kioslave is hung or dead (it is neither) and kills the kioslave. The result is no thumbnails etc are visible in the digiKam window. > Is it possibel to start digicam in "debugmodus" under windows to find > the exact point of the error? > > in hope of a helpful answer You can generally get to see the thumbnails by selecting an album and then waiting for the heavy disk access to finish and then quickly selecting a second album, again wait for the disk access to finish, now quickly going back to the first album should result in visible thumbnails. I think that once the data is in the disk cache the kioslave can load it quickly enough to resume talking to digiKam before digiKam times out and kills it. Unfortunately the kioslave processes get killed off after a period of inactivity so you have to go through the dance again after a little while. If you want to build digiKam from source, I can probably tell you the place to increase the time out. https://bugs.kde.org/show_bug.cgi?id=224038 Andrew _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
On Tue, 04 Dec 2012 20:59:53 +0000
Andrew Goodbody wrote: > If you want to build digiKam from source, I can probably tell you the > place to increase the time out. That might not be the correct way to fix it, the problem is more likely to be that the KDE libraries for Windows are not as stable as those on *nix because they are less developed and there isn't the effort available to improve the port. I don't know the current situation with this, it's possible that Ananta Palani knows more, he produces the installer for digiKam for Windows. -- Brian Morrison _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
2012/12/5 Brian Morrison <[hidden email]>
Yes this is the right status. KDELibs is lesser stable under Windows.
As Ananta work on KDE Windows project, he is the right guy to contact for more details. Gilles Caulier _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by Brian Morrison
On 05/12/12 16:52, Brian Morrison wrote:
> On Tue, 04 Dec 2012 20:59:53 +0000 > Andrew Goodbody wrote: > >> If you want to build digiKam from source, I can probably tell you the >> place to increase the time out. > > That might not be the correct way to fix it, the problem is more likely > to be that the KDE libraries for Windows are not as stable as those on > *nix because they are less developed and there isn't the effort > available to improve the port. No, it is not the correct way to fix it or I would have sent a patch years ago. Yes literally 2 years ago. It is however a pragmatic way to get it to work right now. I know it will make it work as I tried it out back in 2010. My bug report will be 3 years old in January and there has been no movement on it since. Laurent said it was a big issue for him and Wolfgang would also like a fix and there must be many others not even on this list. I will not hold my breath while waiting for someone to fix it the correct way. You can say 'not our problem' as much as you like but the fact is that this bug is our problem as digiKam seems to be the only application to be badly affected by it. It is negatively affecting the users of digiKam on Windows and therefore harming the reputation of digiKam as a whole. Andrew _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
On Thu, 06 Dec 2012 18:14:11 +0000
Andrew Goodbody wrote: > On 05/12/12 16:52, Brian Morrison wrote: > > On Tue, 04 Dec 2012 20:59:53 +0000 > > Andrew Goodbody wrote: > > > >> If you want to build digiKam from source, I can probably tell you > >> the place to increase the time out. > > > > That might not be the correct way to fix it, the problem is more > > likely to be that the KDE libraries for Windows are not as stable > > as those on *nix because they are less developed and there isn't > > the effort available to improve the port. > > No, it is not the correct way to fix it or I would have sent a patch > years ago. Yes literally 2 years ago. It is however a pragmatic way > to get it to work right now. I know it will make it work as I tried > it out back in 2010. My bug report will be 3 years old in January and > there has been no movement on it since. Laurent said it was a big > issue for him and Wolfgang would also like a fix and there must be > many others not even on this list. I will not hold my breath while > waiting for someone to fix it the correct way. > > You can say 'not our problem' as much as you like but the fact is > that this bug is our problem as digiKam seems to be the only > application to be badly affected by it. It is negatively affecting > the users of digiKam on Windows and therefore harming the reputation > of digiKam as a whole. Of course it is "our" problem, for some value of our. I'd like to see digiKam work well on Windows too, but I have no way of fixing it myself as I don't know the code at all. The question is, what is digiKam doing differently from other KDE programs ported to Windows and is the resulting problem something that needs fixing in the KDE ported libraries or can it be fixed in digiKam itself? Until the exact reasons are understood and a path to getting it fixed established then no one seems to know what to do. I shall copy this to Ananta and see if he has anything to add, he knows more than I do about this. -- Brian Morrison _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
I am pleased that others still are struggling with the windows problem. unfortunately still no one seems to really want to take the actual problem. it was certainly a lot of windows user gratifying when digikam even with large collections of images would work perfectly. with small pictures collections usually no one needs special management. I hope soon of a workable solution to the reuse of under windows digkam heard. wolfgang Am 06.12.2012 19:41, schrieb Brian Morrison: > On Thu, 06 Dec 2012 18:14:11 +0000 > Andrew Goodbody wrote: > >> On 05/12/12 16:52, Brian Morrison wrote: >>> On Tue, 04 Dec 2012 20:59:53 +0000 >>> Andrew Goodbody wrote: >>> >>>> If you want to build digiKam from source, I can probably tell you >>>> the place to increase the time out. >>> >>> That might not be the correct way to fix it, the problem is more >>> likely to be that the KDE libraries for Windows are not as stable >>> as those on *nix because they are less developed and there isn't >>> the effort available to improve the port. >> >> No, it is not the correct way to fix it or I would have sent a patch >> years ago. Yes literally 2 years ago. It is however a pragmatic way >> to get it to work right now. I know it will make it work as I tried >> it out back in 2010. My bug report will be 3 years old in January and >> there has been no movement on it since. Laurent said it was a big >> issue for him and Wolfgang would also like a fix and there must be >> many others not even on this list. I will not hold my breath while >> waiting for someone to fix it the correct way. >> >> You can say 'not our problem' as much as you like but the fact is >> that this bug is our problem as digiKam seems to be the only >> application to be badly affected by it. It is negatively affecting >> the users of digiKam on Windows and therefore harming the reputation >> of digiKam as a whole. > > Of course it is "our" problem, for some value of our. I'd like to see > digiKam work well on Windows too, but I have no way of fixing it myself > as I don't know the code at all. The question is, what is digiKam doing > differently from other KDE programs ported to Windows and is the > resulting problem something that needs fixing in the KDE ported > libraries or can it be fixed in digiKam itself? Until the exact reasons > are understood and a path to getting it fixed established then no one > seems to know what to do. > > I shall copy this to Ananta and see if he has anything to add, he knows > more than I do about this. > _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
I have been following the Windows digiKam discussion, and have run a large number of experiments with the program.
Sadly, I have given up trying to use the Windows digiKam version. It is way too buggy and unacceptably unstable. Maybe someday . . . . On Tue, Dec 18, 2012 at 1:21 PM, Wolfgang Strobel <[hidden email]> wrote:
_______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Free forum by Nabble | Edit this page |