[digiKam-users] dk 5.9 freezes under certain conditions
Locked
[digiKam-users] dk 5.9 freezes under certain conditions
 
|
Hello,
I am here with digikam 5.9 from opensuse repos on opensuse 42.3, KDE. When I try color->black and white (or auto-correction), move a file to another folder, and try again a colorcolor->black and white, digikam freezes, I have to kill and restart it... To explain more detailled: I have folders like digikam -myFotos --theNewOnes ---blackAndWhite ---color The folder "color" contains 100 jpg-images, each of approx. 70 MB. Now I go through this folder in album view, one by one, click on a thumbnail to open in editor. In editor I chose colors->black and white, then cancel it (it's just to see how it would look). If I think it looks better in bw I move the file to the folder "blackAndWhite" in album view, drag and drop thumbnail on folder in album tree, choose move. Now when I click on the next image in the folder "color" (where I still am, and the previous image has been moved to the other folder) and try again colors->black and white, digikam freezes. I cannot close the editor window. After a while KDE says "digikam doesn't react, kill it?". It must have something to do with moving the files and choosing the next one (that now is in the sequential album position where the moved one was before). If I do /not/ move a file I can open editor and check bw effect as many times as I wish (well, I tried 10 times to test...)... Is this a known or reproducible bug? Kind regards Daniel -- Daniel Bauer photographer Basel Málaga https://www.patreon.com/danielbauer http://www.daniel-bauer.com |
Re: dk 5.9 freezes under certain conditions - addition
|
|
On 14.10.18 13:16, Daniel Bauer wrote: > Hello, > > I am here with digikam 5.9 from opensuse repos on opensuse 42.3, KDE. > > When I try color->black and white (or auto-correction), move a file to > another folder, and try again a colorcolor->black and white, digikam > freezes, I have to kill and restart it... > > To explain more detailled: > > I have folders like > > digikam > -myFotos > --theNewOnes > ---blackAndWhite > ---color > > The folder "color" contains 100 jpg-images, each of approx. 70 MB. Now I > go through this folder in album view, one by one, click on a thumbnail > to open in editor. In editor I chose colors->black and white, then > cancel it (it's just to see how it would look). > > If I think it looks better in bw I move the file to the folder > "blackAndWhite" in album view, drag and drop thumbnail on folder in > album tree, choose move. > > Now when I click on the next image in the folder "color" (where I still > am, and the previous image has been moved to the other folder) and try > again colors->black and white, digikam freezes. I cannot close the > editor window. After a while KDE says "digikam doesn't react, kill it?". > > It must have something to do with moving the files and choosing the next > one (that now is in the sequential album position where the moved one > was before). > > If I do /not/ move a file I can open editor and check bw effect as many > times as I wish (well, I tried 10 times to test...)... > > Is this a known or reproducible bug? > > Kind regards > > Daniel I was wrong: the error occurs also without moving a file, but it seems it takes longer to appear and it shows different: Instead of moving the files I now marked them with a star (to move them later), but after some click to open in editor - colors->bw - cancel, clicking on the next image... etc... the next image is not loaded in editor, it shows the one of before. The cursor turns into "wait" when hovering the menu. I can now close the window. But I can't do anything more. Opening an image always still shows the last one... However I don't have to kill digikam, I can close it normally and restart it... -- Daniel Bauer photographer Basel Málaga https://www.patreon.com/danielbauer http://www.daniel-bauer.com |
Re: dk 5.9 freezes under certain conditions - addition
|
|
Hi, Best Gilles Caulier Le dim. 14 oct. 2018 à 13:29, Daniel Bauer <[hidden email]> a écrit :
|
Re: dk 5.9 freezes under certain conditions - addition
|
|
Hi Gilles,
here's the output: https://www.daniel-bauer.com/test/digikam.txt (I replaced path's and uuid's because the file is public, if you need the original file I can send it to you in a private email) - started digikam - went to the folder [loop] - opened an image from album into editor - chosed colors->black and white - canceled the converter - moved the file to another folder [/loop] (I think 3 times) [loop] - the same as before, but - selected the next image to open without moving the previous one [/loop] (I think 2 times, iirc once I clicked on colors->autocorrection and canceled it) Now in the editor the image of before is shown (not the actually clicked one), the menu is grayed out, hovering the menu shows the "wait-cursor". I tried two or three times (closing bw-coverter with close-button up on the right, clicking on other thumbnail in album...). Finally I close digikam with close-button up on the right in album. But: digikam disappeared (window closed) but it's still in the process list with 0 CPU, 758'532 K memory and 147'672 K shared memory. This for quite a while now without changing any numbers (since I closed digikam, uploaded the txt file and wrote this mail). Now I killed the process... Let's see if the output is helpful :-) kind regards Daniel On 17.10.18 05:29, Gilles Caulier wrote: > Hi, > > If you run digiKam on a console, it will be instructuve to see all debug > traces printed while this kind of operation. > > Best > > Gilles Caulier > > Le dim. 14 oct. 2018 à 13:29, Daniel Bauer <[hidden email] > <mailto:[hidden email]>> a écrit : > > > > On 14.10.18 13:16, Daniel Bauer wrote: > > Hello, > > > > I am here with digikam 5.9 from opensuse repos on opensuse 42.3, KDE. > > > > When I try color->black and white (or auto-correction), move a > file to > > another folder, and try again a colorcolor->black and white, digikam > > freezes, I have to kill and restart it... > > > > To explain more detailled: > > > > I have folders like > > > > digikam > > -myFotos > > --theNewOnes > > ---blackAndWhite > > ---color > > > > The folder "color" contains 100 jpg-images, each of approx. 70 > MB. Now I > > go through this folder in album view, one by one, click on a > thumbnail > > to open in editor. In editor I chose colors->black and white, then > > cancel it (it's just to see how it would look). > > > > If I think it looks better in bw I move the file to the folder > > "blackAndWhite" in album view, drag and drop thumbnail on folder in > > album tree, choose move. > > > > Now when I click on the next image in the folder "color" (where I > still > > am, and the previous image has been moved to the other folder) > and try > > again colors->black and white, digikam freezes. I cannot close the > > editor window. After a while KDE says "digikam doesn't react, > kill it?". > > > > It must have something to do with moving the files and choosing > the next > > one (that now is in the sequential album position where the moved > one > > was before). > > > > If I do /not/ move a file I can open editor and check bw effect > as many > > times as I wish (well, I tried 10 times to test...)... > > > > Is this a known or reproducible bug? > > > > Kind regards > > > > Daniel > > > I was wrong: the error occurs also without moving a file, but it seems > it takes longer to appear and it shows different: > > Instead of moving the files I now marked them with a star (to move them > later), but after some click to open in editor - colors->bw - cancel, > clicking on the next image... etc... the next image is not loaded in > editor, it shows the one of before. The cursor turns into "wait" when > hovering the menu. I can now close the window. But I can't do anything > more. Opening an image always still shows the last one... However I > don't have to kill digikam, I can close it normally and restart it... > -- > Daniel Bauer photographer Basel Málaga > https://www.patreon.com/danielbauer > http://www.daniel-bauer.com > -- Daniel Bauer photographer Basel Málaga https://www.patreon.com/danielbauer http://www.daniel-bauer.com |
Re: dk 5.9 freezes under certain conditions - addition
|
|
On 17.10.18 13:06, Daniel Bauer wrote: ... > > Now in the editor the image of before is shown (not the actually clicked > one), the menu is grayed out, hovering the menu shows the "wait-cursor". > > I tried two or three times (closing bw-coverter with close-button up on > the right, clicking on other thumbnail in album...). This should be: closing /editor-window/ with close-button... . -- Daniel Bauer photographer Basel Málaga https://www.patreon.com/danielbauer http://www.daniel-bauer.com |
Re: dk 5.9 freezes under certain conditions - addition
|
|
Did you seen that :
digikam.dbengine: Database is locked. Waited 0 digikam.dbengine: Database is locked. Waited 250 digikam.dbengine: Database is locked. Waited 500 digikam.dbengine: Database is locked. Waited 750 digikam.dbengine: Database is locked. Waited 1000 digikam.dbengine: Database is locked. Waited 1250 digikam.dbengine: Database is locked. Waited 1500 digikam.dbengine: Database is locked. Waited 1750 digikam.dbengine: Database is locked. Waited 2000 digikam.dbengine: Database is locked. Waited 2250 digikam.dbengine: Database is locked. Waited 2500 digikam.dbengine: Database is locked. Waited 2750 digikam.dbengine: Database is locked. Waited 3000 digikam.dbengine: Database is locked. Waited 3250 digikam.dbengine: Database is locked. Waited 3500 digikam.dbengine: Database is locked. Waited 3750 digikam.dbengine: Database is locked. Waited 4000 digikam.dbengine: Database is locked. Waited 4250 digikam.dbengine: Database is locked. Waited 4500 digikam.dbengine: Database is locked. Waited 4750 digikam.dbengine: Database is locked. Waited 5000 digikam.dbengine: Database is locked. Waited 5250 digikam.dbengine: Database is locked. Waited 5500 digikam.dbengine: Database is locked. Waited 5750 digikam.dbengine: Database is locked. Waited 6000 digikam.dbengine: Database is locked. Waited 6250 digikam.dbengine: Database is locked. Waited 6500 digikam.dbengine: Database is locked. Waited 6750 digikam.dbengine: Database is locked. Waited 7000 digikam.dbengine: Database is locked. Waited 7250 digikam.dbengine: Database is locked. Waited 7500 digikam.dbengine: Database is locked. Waited 7750 digikam.dbengine: Database is locked. Waited 8000 digikam.dbengine: Database is locked. Waited 8250 digikam.dbengine: Database is locked. Waited 8500 digikam.dbengine: Database is locked. Waited 8750 digikam.dbengine: Database is locked. Waited 9000 digikam.dbengine: Database is locked. Waited 9250 digikam.dbengine: Database is locked. Waited 9500a digikam.dbengine: Database is locked. Waited 9750 digikam.dbengine: Database is locked. Waited 10000 digikam.dbengine: Detected locked database file. There is an active transaction. Waited but giving up now. digikam.dbengine: Failure executing query: "SELECT latitude, latitudeNumber, longitude, longitudeNumber, altitude, orientation, tilt, roll, accuracy, description FROM ImagePositions WHERE imageid=?;" Error messages: "Der Datensatz konnte nicht abgeholt werden" "database table is locked: ImagePositions" 6 1 Bound values: (QVariant(qlonglong, 236104)) This can explain the time latency Also, there are a lots of screen warnings from Qt : QXcbConnection: XCB error: 3 (BadWindow), sequence: 46222, resource id: 71303465, major code: 2 (ChangeWindowAttributes), minor code: 0 QXcbConnection: XCB error: 3 (BadWindow), sequence: 46535, resource id: 71303465, major code: 2 (ChangeWindowAttributes), minor code: 0 QXcbConnection: XCB error: 3 (BadWindow), sequence: 46923, resource id: 71303465, major code: 2 (ChangeWindowAttributes), minor code: 0 QXcbConnection: XCB error: 3 (BadWindow), sequence: 47380, resource id: 71303465, major code: 2 (ChangeWindowAttributes), minor code: 0 QXcbConnection: XCB error: 3 (BadWindow), sequence: 47717, resource id: 71303465, major code: 2 (ChangeWindowAttributes), minor code: 0 QXcbConnection: XCB error: 3 (BadWindow), sequence: 48035, resource id: 71303465, major code: 2 (ChangeWindowAttributes), minor code: 0 QXcbConnection: XCB error: 3 (BadWindow), sequence: 50242, resource id: 71303465, major code: 2 (ChangeWindowAttributes), minor code: 0 Typically, something is badly configured somewhere with your X11 server. This can also introduce time latency to draw application widget on screen. Q : did you use color management with ICM profiles ? Gilles Caulier Le mer. 17 oct. 2018 à 13:11, Daniel Bauer <[hidden email]> a écrit : > > > > On 17.10.18 13:06, Daniel Bauer wrote: > ... > > > > Now in the editor the image of before is shown (not the actually clicked > > one), the menu is grayed out, hovering the menu shows the "wait-cursor". > > > > I tried two or three times (closing bw-coverter with close-button up on > > the right, clicking on other thumbnail in album...). > > This should be: closing /editor-window/ with close-button... > . > -- > Daniel Bauer photographer Basel Málaga > https://www.patreon.com/danielbauer > http://www.daniel-bauer.com |
Re: dk 5.9 freezes under certain conditions - addition
|
|
On 17.10.18 17:05, Gilles Caulier wrote: > Did you seen that : > > digikam.dbengine: Database is locked. Waited 0 > ... > digikam.dbengine: Detected locked database file. There is an active > transaction. Waited but giving up now. Yes, I have seen it, but I don't know what to do about it... Don't know why the database is locked. It was the only digikam process (I checked before starting the test) and there should be nobody else accessing that database... > digikam.dbengine: Failure executing query: > "SELECT latitude, latitudeNumber, longitude, longitudeNumber, > altitude, orientation, tilt, roll, accuracy, description FROM > ImagePositions WHERE imageid=?;" These images I used for the test today are from a canon 5 Mk 2 that doesn't have geo data. But it also happens with images from a Mk 4, that has gps data. > Error messages: "Der Datensatz konnte nicht abgeholt werden" "database > table is locked: ImagePositions" 6 1 > Bound values: (QVariant(qlonglong, 236104)) > > This can explain the time latency > Also, there are a lots of screen warnings from Qt : > > QXcbConnection: XCB error: 3 (BadWindow), sequence: 46222, resource id: > 71303465, major code: 2 (ChangeWindowAttributes), minor code: 0 > ... > > Typically, something is badly configured somewhere with your X11 server. > This can also introduce time latency to draw application widget on screen. I've seen this. I thought "BadWindow" was a Linux-message about bad, bad microsoft (joke, :-) ). Of course I don't know what this could mean, where it comes from and what I can do about it... I do have problems with my graphics card. It is an asus laptop with this nvidia/intel optimus thing, something that Linux obviously can't handle. I tried many things with hints from opensuse mailing lists and it is possible that my display things are f***ed-up for the many changes and back-changes - but I have no idea where to look and how to find out. Actually it only runs with the poor power of intel graphics, nvidia is there for nothing... I guess trying with a fresh user wouldn't change anything??? > > Q : did you use color management with ICM profiles ? No, these are old photos, just the jpg's as they came out of the camera and without color management. > > Gilles Caulier > > Le mer. 17 oct. 2018 à 13:11, Daniel Bauer <[hidden email] > <mailto:[hidden email]>> a écrit : > > > > > > > > On 17.10.18 13:06, Daniel Bauer wrote: > > ... > > > > > > Now in the editor the image of before is shown (not the actually > clicked > > > one), the menu is grayed out, hovering the menu shows the > "wait-cursor". > > > > > > I tried two or three times (closing bw-coverter with close-button up on > > > the right, clicking on other thumbnail in album...). > > > > This should be: closing /editor-window/ with close-button... > > . > > -- > > Daniel Bauer photographer Basel Málaga > > https://www.patreon.com/danielbauer > > http://www.daniel-bauer.com -- Daniel Bauer photographer Basel Málaga https://www.patreon.com/danielbauer http://www.daniel-bauer.com |
Re: dk 5.9 freezes under certain conditions - addition
|
|
I also have the "BadWindow" messages, they are not relevant. OpenSUSE has
enabled a little too much Qt debug messages. These messages I had with NVidia and now with AMD graphics card. I switched from NVidia to AMD because I use openSUSE Tumbleewed and there are very frequent kernel updates. Each time the driver had to be recompiled, and not always succeeds with a current kernel until NVidia follows. The Radion driver works stably and OpenGL works without problems and for me fast enough. Maik Am Mittwoch, 17. Oktober 2018, 17:41:01 CEST schrieb Daniel Bauer: > On 17.10.18 17:05, Gilles Caulier wrote: > > Did you seen that : > > > > digikam.dbengine: Database is locked. Waited 0 > > ... > > digikam.dbengine: Detected locked database file. There is an active > > transaction. Waited but giving up now. > > Yes, I have seen it, but I don't know what to do about it... Don't know > why the database is locked. It was the only digikam process (I checked > before starting the test) and there should be nobody else accessing that > database... > > > digikam.dbengine: Failure executing query: > > "SELECT latitude, latitudeNumber, longitude, longitudeNumber, > > > > altitude, orientation, tilt, roll, accuracy, description FROM > > ImagePositions WHERE imageid=?;" > > These images I used for the test today are from a canon 5 Mk 2 that > doesn't have geo data. But it also happens with images from a Mk 4, that > has gps data. > > > Error messages: "Der Datensatz konnte nicht abgeholt werden" "database > > table is locked: ImagePositions" 6 1 > > Bound values: (QVariant(qlonglong, 236104)) > > > > This can explain the time latency > > > > > > Also, there are a lots of screen warnings from Qt : > > > > QXcbConnection: XCB error: 3 (BadWindow), sequence: 46222, resource id: > > 71303465, major code: 2 (ChangeWindowAttributes), minor code: 0 > > ... > > > > Typically, something is badly configured somewhere with your X11 server. > > This can also introduce time latency to draw application widget on screen. > > I've seen this. I thought "BadWindow" was a Linux-message about bad, bad > microsoft (joke, :-) ). Of course I don't know what this could mean, > where it comes from and what I can do about it... > > I do have problems with my graphics card. It is an asus laptop with this > nvidia/intel optimus thing, something that Linux obviously can't handle. > > I tried many things with hints from opensuse mailing lists and it is > possible that my display things are f***ed-up for the many changes and > back-changes - but I have no idea where to look and how to find out. > Actually it only runs with the poor power of intel graphics, nvidia is > there for nothing... > > I guess trying with a fresh user wouldn't change anything??? > > > Q : did you use color management with ICM profiles ? > > No, these are old photos, just the jpg's as they came out of the camera > and without color management. > > > Gilles Caulier > > > > Le mer. 17 oct. 2018 à 13:11, Daniel Bauer <[hidden email] > > > > <mailto:[hidden email]>> a écrit : > > > On 17.10.18 13:06, Daniel Bauer wrote: > > > ... > > > > > > > Now in the editor the image of before is shown (not the actually > > > > clicked > > > > > > one), the menu is grayed out, hovering the menu shows the > > > > "wait-cursor". > > > > > > I tried two or three times (closing bw-coverter with close-button up > > > > on > > > > the right, clicking on other thumbnail in album...). > > > > > > This should be: closing /editor-window/ with close-button... > > > . > > > -- > > > Daniel Bauer photographer Basel Málaga > > > https://www.patreon.com/danielbauer > > > http://www.daniel-bauer.com |
«
Return to digikam-users
|
1 view|%1 views
| Free forum by Nabble | Edit this page |