[Bug 295263] New: When tagging, "Writing metadata to files" messages never clear from progress queue

[jon piesing]

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

--- Comment #20 from [hidden email] ---
Created attachment 70929
  --> https://bugs.kde.org/attachment.cgi?id=70929&action=edit
Log from digikam with patch applied

Log from digikam with patch applied. First a tag is applied and removed by
right-clicking on a thumbnail. Second a tag is applied by dragging a thumbnail
over to the tags list on the RHS of the screen. Each time an instance of the
"Writing metadata to files" pop-up was created and did not vanish. Lastly
digikam was exited and blocked due to pending writes.

--
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

[jon piesing]

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

--- Comment #21 from [hidden email] ---
Here's the information from "help" / "components information".

digiKam version 2.6.0-rc
Exiv2 can write to Jp2: Yes
Exiv2 can write to Jpeg: Yes
Exiv2 can write to Pgf: Yes
Exiv2 can write to Png: Yes
Exiv2 can write to Tiff: Yes
Exiv2 supports XMP metadata: Yes
LibCImg: 130
LibClapack: internal library
LibExiv2: 0.22
LibJPEG: 80
LibJasper: 1.900.1
LibKDE: 4.8.3 (4.8.3)
LibKExiv2: 2.3.0
LibKGeoMap: 2.0.0
LibKdcraw: 2.1.0
LibLCMS: 119
LibLensFun: 0.2.5-1 - internal library
LibLqr: internal library
LibPGF: 6.11.42 - internal library
LibPNG: 1.2.46
LibQt: 4.8.1
LibRaw: 0.14.6
LibTIFF: LIBTIFF, Version 3.9.5 Copyright (c) 1988-1996 Sam Leffler Copyright
(c) 1991-1996 Silicon Graphics, Inc.
Marble Widget: 0.13.3 (stable release)
Parallelized demosaicing: Yes
Database backend: QSQLITE
LibGphoto2: 2.4.13
LibKface: 2.0.0
LibKipi: 1.6.0
LibOpenCV: 2.3.1
Libface: 0.2

--
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

[jon piesing]

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

--- Comment #22 from [hidden email] ---
Created attachment 70934
  --> https://bugs.kde.org/attachment.cgi?id=70934&action=edit
Log from digikam with patch applied - without raw images

The previous log file included a lot of noise due to the image I was using
being a raw one. This 3rd log file uses TIFF/PNG.

--
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=295263

--- Comment #23 from Marcel Wiesweg <[hidden email]> ---
Thanks a lot.
To all who have confirmed this problem: Can we see a correlation with Qt
version?
Qt 4.7 -> no problem
Qt 4.8 -> problem?

--
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

[e-mail robert.m.davies]

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

--- Comment #24 from Rob D <[hidden email]> ---
The test sample is very small, so it's hard to say with certainty.
I would seem to strengthen the correlation though, as I am using Qt4.8.1

--
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

[jon piesing]

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

--- Comment #25 from [hidden email] ---
My desktop machine is Qt 4.7.4 (see below) and does not show this problem.
Still a very small sample but we have to start somewhere.

Jon

digiKam version 2.6.0-beta3
Exiv2 can write to Jp2: Yes
Exiv2 can write to Jpeg: Yes
Exiv2 can write to Pgf: Yes
Exiv2 can write to Png: Yes
Exiv2 can write to Tiff: Yes
Exiv2 supports XMP metadata: Yes
LibCImg: 130
LibClapack: internal library
LibExiv2: 0.22
LibJPEG: 62
LibJasper: 1.900.1
LibKDE: 4.7.4 (4.7.4)
LibKExiv2: 2.3.0
LibKGeoMap: 2.0.0
LibKdcraw: 2.1.0
LibLCMS: 119
LibLensFun: external shared library
LibLqr: internal library
LibPGF: 6.11.42 - internal library
LibPNG: 1.2.46
LibQt: 4.7.4
LibRaw: 0.14.5
LibTIFF: LIBTIFF, Version 3.9.5 Copyright (c) 1988-1996 Sam Leffler Copyright
(c) 1991-1996 Silicon Graphics, Inc.
Marble Widget: 0.12.2 (stable release)
Parallelised demosaicing: Yes
Database backend: QSQLITE
LibGphoto2: 2.4.13
LibKface: 2.0.0
LibKipi: 1.6.0
LibOpenCV: 2.1.0
Libface: 0.2

--
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

[e-mail robert.m.davies]

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

--- Comment #26 from Rob D <[hidden email]> ---
Probably should have provided complete component info:

digiKam version 2.6.0-beta3
Exiv2 can write to Jp2: Yes
Exiv2 can write to Jpeg: Yes
Exiv2 can write to Pgf: Yes
Exiv2 can write to Png: Yes
Exiv2 can write to Tiff: Yes
Exiv2 supports XMP metadata: Yes
LibCImg: 130
LibClapack: internal library
LibExiv2: 0.21.1
LibJPEG: 62
LibJasper: 1.900.1
LibKDE: 4.8.2 (4.8.2)
LibKExiv2: 2.1.0
LibKGeoMap: 2.0.0
LibKdcraw: 2.0.1
LibLCMS: 119
LibPGF: 6.11.42 - internal library
LibPNG: 1.2.46
LibQt: 4.8.1
LibRaw: 0.14.4
LibTIFF: LIBTIFF, Version 3.9.5 Copyright (c) 1988-1996 Sam Leffler Copyright
(c) 1991-1996 Silicon Graphics, Inc.
Marble Widget: 0.13.0 (stable release)
Parallelised demosaicing: Yes
Database backend: QSQLITE
LibGphoto2: 2.4.11
LibKface: 2.0.0
LibKipi: 1.3.0
LibOpenCV: 2.1.0
Libface: 0.2

--
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=295263

Varun Herale <[hidden email]> changed:

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

--- Comment #27 from Varun Herale <[hidden email]> ---
I can see this problem too - and my Qt version is 4.8.1.

It looks like nothing is being written into the metadata at all.

--
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=295263

Frederic Grelot <[hidden email]> changed:

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

--- Comment #28 from Frederic Grelot <[hidden email]> ---
I see this bug too, for quite a long time now.
I posted a bug report here :
https://bugs.kde.org/show_bug.cgi?id=295340
Actually, as I feared, the report described 2 bugs, one of them was fixed, but
the other one remains. Still, the backtrace included may be of some help...

My Qt is 4.8.1, and the only specific setting for me is that my database is
stored on mysql.
I have this bug on (at least) 2 computers, that share the same storage (one of
them locally, the other one accesses it through NFS) and the same database.
Digikam is built from source, so I may apply patches if necessary.

About the Qt version, here is my yum.log
Nov 09 23:03:49 Updated: 1:qt-4.8.0-0.23.rc1.fc16.x86_64
Dec 23 22:32:13 Updated: 1:qt-4.8.0-0.29.rc1.fc16.x86_64
Jan 05 19:00:21 Updated: 1:qt-4.8.0-5.fc16.x86_64
Jan 23 11:25:50 Updated: 1:qt-4.8.0-7.fc16.x86_64
Apr 21 14:04:14 Updated: 1:qt-4.8.1-5.fc16.x86_64

As you can see, I'm running qt-4.8 since november 2011, and the bug is far more
recent (I would say february or march), so the relation will not be immediate.

PS : I don't know who has the rights to do it, but it may be acceptable to set
this bug to "confirmed"

--
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=295263

Tudor M. Pristavu <[hidden email]> changed:

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

--- Comment #29 from Tudor M. Pristavu <[hidden email]> ---
I can confirm this issue.
I'm using kubuntu 12.04, kde 4.8.3 (tested on kde 4.8.2 as well), qt 4.8.1,
arch - 32bit amd 2 cores, digikam 2.6.0-rc compiled from sources.

--
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=295263

--- Comment #30 from Tudor M. Pristavu <[hidden email]> ---
  I've just tested this issue on a different computer with qt 4.7.4 (openSuse,
kde 4.7.2, digikam 2.6.0-rc) and the issue does not reproduce.
  The metadata is written to files and everything works as expected.

--
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

[cyh47]

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

cyh <[hidden email]> changed:

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

--- Comment #31 from cyh <[hidden email]> ---
I too am having the issue.

I don't know if proving results from"top" is of help but here you are.
I am using Fedora 1x86_64.

Following is the result from typing "top" in a console.
This was after asking Digikam to close.  The small window with progess bar was
warning about unfinished task.

If one chooses "cancel" Digikam does close as well as the small progress
window.

Upon restarting Digikam, the tags have been added to the photos and works well
it seems.

top - 13:23:39 up  6:54,  3 users,  load average: 2.56, 2.59, 2.68
Tasks: 178 total,   2 running, 176 sleeping,   0 stopped,   0 zombie
Cpu(s): 47.0%us, 19.8%sy,  0.0%ni, 22.7%id, 10.1%wa,  0.0%hi,  0.5%si,  0.0%st
Mem:   4050492k total,  3933556k used,   116936k free,     9392k buffers
Swap:  7186424k total,  2426216k used,  4760208k free,   424124k cached

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND            
 1736 cyh47     20   0 6287m 2.6g  23m S 52.9 68.4 152:14.10 digikam            
 9251 cyh47     20   0  630m 6992 5440 R 26.4  0.2   0:00.16 kio_digikamtags    
   46 root      20   0     0    0    0 S  1.7  0.0   2:00.74 kswapd0            
 1220 cyh47     20   0  724m  16m 1256 S  1.7  0.4   0:34.87 mysqld            
 2451 root      20   0     0    0    0 S  1.7  0.0   2:57.66 btrfs-endio-3      
 9250 root      20   0 15252 1168  824 R  1.7  0.0   0:00.05 top                
    1 root      20   0 61392 1328  808 S  0.0  0.0   0:03.10 systemd            
    2 root      20   0     0    0    0 S  0.0  0.0   0:00.01 kthreadd          
    3 root      20   0     0    0    0 S  0.0  0.0   0:09.77 ksoftirqd/0        
    6 root      RT   0     0    0    0 S  0.0  0.0   0:00.00 migration/0        
    7 root      RT   0     0    0    0 S  0.0  0.0   0:00.79 watchdog/0        
    8 root       0 -20     0    0    0 S  0.0  0.0   0:00.00 cpuset            
    9 root       0 -20     0    0    0 S  0.0  0.0   0:00.00 khelper            
   10 root      20   0     0    0    0 S  0.0  0.0   0:00.00 kdevtmpfs          
   11 root       0 -20     0    0    0 S  0.0  0.0   0:00.00 netns              
   12 root      20   0     0    0    0 S  0.0  0.0   0:00.25 sync_supers        
   13 root      20   0     0    0    0 S  0.0  0.0   0:00.00 bdi-default        
   14 root       0 -20     0    0    0 S  0.0  0.0   0:00.00 kintegrityd        
   15 root       0 -20     0    0    0 S  0.0  0.0   0:00.00 kblockd            
   16 root       0 -20     0    0    0 S  0.0  0.0   0:00.00 ata_sff            
   17 root      20   0     0    0    0 S  0.0  0.0   0:00.12 khubd              
   18 root       0 -20     0    0    0 S  0.0  0.0   0:00.00 md                
   47 root      25   5     0    0    0 S  0.0  0.0   0:00.00 ksmd

--
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=295263

--- Comment #32 from Marcel Wiesweg <[hidden email]> ---
Can someone with Qt 4.8 attach the file core/digikam/fileworkeriface.moc from
the build dir? Just to rule out some possible causes.
I believe for a proper debugging I will need to upgrade to Qt4.8 which is not
done in ten minutes. Therefore I guess for 2.6 final, we need a workaround
which will only disable the feature that load is distributed over all CPU cores
for the relevant tasks (rotation, file metadata editing).

Btw: Those of you who can confirm this issue have also a problem when rotating
multiple pictures at once?

--
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=295263

--- Comment #33 from Tudor M. Pristavu <[hidden email]> ---
Created attachment 71077
  --> https://bugs.kde.org/attachment.cgi?id=71077&action=edit
fileworkeriface.moc for qt 4.8.1

I attached the fileworkeriface.moc file (qt 4.8.1).

As for rotating images, I tried to rotate a raw image (.nef) but the progress
bar didn't move from 0%.

--
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=295263

--- Comment #34 from Tudor M. Pristavu <[hidden email]> ---
  I've just done an experiment with moc files.
  I used the moc file generated on computer with qt 4.7.4 to build digikam with
qt 4.8.1 (after disabling the #ifdef protection). And everything seems to work
fine. :)  Both operations (writing metadata and rotating images) finish with
success.
  It's probably not the best idea but might give you some clues about the
problem.

--
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

[Veaceslav Munteanu]

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

Veaceslav Munteanu <[hidden email]> changed:

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

--- Comment #35 from Veaceslav Munteanu <[hidden email]> ---
I still can't rotate images, with latest git, clean install. Progress stuck at
0%.

--
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

[DrSlony-3]

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

DrSlony <[hidden email]> changed:

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

--- Comment #36 from DrSlony <[hidden email]> ---
I get the same problem.

I'm cleaning up my tags, so I create new tag hierarchies and then drag-and-drop
whole albums on the new tag and click "Assign tag" from the popup. Sometimes
this happens with no progress bar, other times I get the "Writing metadata to
files" progress bar. It stays at 0%. When I try to close digiKam, a new window
pops up, "Finishing tasks" and it also stays up perpetually. I have to click
"Cancel".

Upon restarting digiKam usually my changes have been applied, but yesterday I
came across one main tag /subject/* whose files I tried re-tagging with other
tags (e.g. from drag photos from the /subject/flora/fern tag and drop them on
the /plants/fern tag), the perpetual progress bar would appear, I would have to
"cancel" it to close digiKam, upon restarting the new tags were gone, and the
old deletes ones were back. So after restarting, all changes I made to these
files from /subject/* (deleting the old tags, settings new ones) would not get
applied - time lost. I ended up deleting that whole main tag /subject.

I tested just now - created a new tag "foo", dropped seven JPEG photos from tag
"mushrooms" on to tag "foo", the perpetual 0% progress bar appeared, I clicked
X to close digiKam, clicked "cancel", restarted it, and the new tag "foo" was
set.
Screenshot here: http://i.imgur.com/6YnUM.png

digiKam version 2.6.0-rc
Exiv2 can write to Jp2: Yes
Exiv2 can write to Jpeg: Yes
Exiv2 can write to Pgf: Yes
Exiv2 can write to Png: Yes
Exiv2 can write to Tiff: Yes
Exiv2 supports XMP metadata: Yes
LibCImg: 130
LibClapack: external shared library
LibExiv2: 0.21.1
LibJPEG: 80
LibJasper: 1.900.1
LibKDE: 4.8.1 (4.8.1)
LibKExiv2: 2.1.0
LibKGeoMap: 2.0.0
LibKdcraw: 2.0.1
LibLCMS: 119
LibLensFun: external shared library
LibLqr: internal library
LibPGF: 6.11.32 - external shared library
LibPNG: 1.5.10
LibQt: 4.8.1
LibRaw: 0.14.4
LibTIFF: LIBTIFF, Version 4.0.1 Copyright (c) 1988-1996 Sam Leffler Copyright
(c) 1991-1996 Silicon Graphics, Inc.
Marble Widget: 0.12.97 (0.13 Release Candidate 2)
Parallelized demosaicing: Yes
Database backend: QSQLITE
LibKface: 2.0.0
LibKipi: 1.3.0
LibOpenCV: 2.3.0
Libface: 0.2

--
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

[Nicolas Pomarede]

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

Nicolas Pomarede <[hidden email]> changed:

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

--- Comment #37 from Nicolas Pomarede <[hidden email]> ---
to comment #32 :

Hello, I have the same problem under Mandriva cooker, using qt 4.8.1 and
digikam 2.6.0.rc2

I tried to disable all cores/cpus at boot using kernel option maxcpus=1, but in
that case the problem is still present, the "writing metadata to file" message
is still present on screen and never goes away.

Are you sure the problem is related to the number of cpu in QT 4.8 ?

Nicolas

--
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

[DrSlony-3]

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

--- Comment #38 from DrSlony <[hidden email]> ---
i7 820QM (mobile quad-core)

--
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=295263

--- Comment #39 from Marcel Wiesweg <[hidden email]> ---
Git commit e254d1b8e53fa513f1433b1c73adb4859874f2f1 by Marcel Wiesweg.
Committed on 19/05/2012 at 12:37.
Pushed by mwiesweg into branch 'master'.

Try to make slot interception work with Qt4.8

4.8's moc makes use of the extraData field of QMetaObject to pass the
static_qt_metacall pointer.
I know this is a hack (but binary compatibility vows are on our side)

M  +18   -3    libs/threads/parallelworkers.cpp
M  +19   -7    libs/threads/parallelworkers.h

http://commits.kde.org/digikam/e254d1b8e53fa513f1433b1c73adb4859874f2f1

--
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