Summary: | MYSQL : Image window, extreme unstable under dates view. | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Gerard Dirkse <gerard.dirkse> |
Component: | Database-Mysql | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | caulier.gilles, gerard.dirkse, metzpinguin, simonandric5, swatilodha27 |
Priority: | NOR | ||
Version: | 4.11.0 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 5.0.0 | |
Attachments: |
terminal output
Kdebugdialog induced traces for digikam Second reprodution trace (unedited) Second kde trace Screenshot just after starting digikam and selecting a date Screenshot after change in window happened |
Description
Gerard Dirkse
2015-04-04 09:39:56 UTC
Of course this dysfunction is not reproducible here. This problem is specific to your computer. Run digiKam in a console with debug spaces enabled and report here the trace of messages printed. https://www.digikam.org/contrib Created attachment 91881 [details]
terminal output
text in red font at image and what happened (twice)
Created attachment 91882 [details]
Kdebugdialog induced traces for digikam
Reproduced and provided traces
Comment on attachment 91882 [details]
Kdebugdialog induced traces for digikam
digikam(11166)/digikam (core) Digikam::AlbumManager::scanTAlbums: Failed to find parent tag for tag "Irene" with pid 27
digikam(11166)/digikam (core) Digikam::AlbumManager::scanTAlbums: Failed to find parent tag for tag "Erik" with pid 27
digikam(11166)/digikam (core) Digikam::AlbumManager::scanTAlbums: Failed to find parent tag for tag "Geert" with pid 27
digikam(11166)/digikam (core) Digikam::AlbumManager::scanTAlbums: Failed to find parent tag for tag "ANZ" with pid 134
digikam(11166)/digikam (core) Digikam::AlbumManager::scanTAlbums: Failed to find parent tag for tag "Noordkaap" with pid 134
Sound like a DB file problem...
Gilles Caulier
Fixed the errors in the database, repeated the test, see attached files (stopped immediate after problem happened). Suspect the end result is caused by this: digikam(12444)/digikam (core) Digikam::DatabaseUrl::dateUrl: DatabaseUrl::dateUrl : "digikamdates://?databaseType=QMYSQL&databaseName=digikam&connectOptions=&hostName=dirksehome&port=3306&userName=digikam&password=fotos" digikam(12444)/digikam (core) Digikam::ImageLister::startListJob: Query Kioslave Url: "digikamdates://?databaseType=QMYSQL&databaseName=digikam&connectOptions=&hostName=dirksehome&port=3306&userName=digikam&password=fotos" and this digikam(12444)/KEXIV2 KExiv2Iface::KExiv2::getImageDateTime: DateTime => Exif.Photo.DateTimeOriginal => QDateTime("Mon Mar 9 09:03:14 2015") digikam(12444)/KEXIV2 KExiv2Iface::KExiv2::getImageOrientation: Orientation => Exif.Image.Orientation => 1 digikam(12444)/kio (Scheduler) KIO::SchedulerPrivate::doJob: KIO::SimpleJob(0x6cff720) digikam(12444)/kio (KIOConnection) KIO::SocketConnectionBackend::socketReadyRead: KIO::SocketConnectionBackend(0x4eb0bc0) Jumbo packet of 74156 bytes digikam(12444)/kio (KIOJob) KIO::TransferJob::slotFinished: KUrl("digikamdates://?databaseType=QMYSQL&databaseName=digikam&connectOptions=&hostName=dirksehome&port=3306&userName=digikam&password=fotos") digikam(12444)/kio (Scheduler) KIO::SchedulerPrivate::jobFinished: KIO::SpecialJob(0x6cff720) KIO::Slave(0x4fa40c0) But cant see what triggered the action in this case problem happened when going from last foto to next foto Created attachment 91884 [details]
Second reprodution trace (unedited)
Created attachment 91885 [details]
Second kde trace
Part of the problem sounds like this bug 344793. The bug report contains a video, it is comparable? Maik gerard, Did you seen comment #8 from Maik. He has fixed bug #344793 with digiKam 4.9.0. Can you reproduce the problem with this version ? Gilles Caulier No problem, within minutes. You want new traces ? I problem is reproducible yes. Typically debug statements on the console can help to see where is the problem... Gilles Caulier Nota : digiKam 4.10.0 will be released in few days... Gilles Caulier Was just checking out 4.11, and while in preview image from within 'dates' view (not doing anything at all), just reviewing a picture histogram, complete window was filled with the image and then fell back to thumbnail view. Will see if I can reproduce and take traces. Created attachment 94073 [details]
Screenshot just after starting digikam and selecting a date
Please note how the calender (left under) looks, all dates with photo’s are bold and the date selected is highlighted. The status bar (left under) indicates the selected and number of photo's are for that day.
Created attachment 94074 [details]
Screenshot after change in window happened
Please note how the calendar now looks !!!. Only the selected day is bold, the window has fallen back into thumbnail view and the number of selected images are all of them for that month.
Difference between the 2 last attachments is time, was working on a different screen (not window) in Linux. So I didn’t do absolutely nothing in Digikam (version is 4.12). I did note while working on that other screen that a small window popped up right under, on the screen I was working, with the digits '197' in it, tried it a couple of times, seem to give that number every time, window is only very short visible. Let me know if you need further traces, screen prints or whatever. Problem appears to be hard reproducible with the selections I currently use. Please try digikam5.0.0-Beta7 Problem is not reproducible here. Steps to reproduce: 1) Use MySQL backend and use digiKam in Dates view. 2) I tried viewing, deleting the images, added a new tag to image.... Result was produced as expected to be. |