[Kde-imaging] [Bug 207157] Regression: Can't transfer EXIF creation date to file date

[Kay Hayen]

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





--- Comment #6 from Kay Hayen <KayHayen gmx de>  2009-09-12 16:08:25 ---
Created an attachment (id=36896)
 --> (http://bugs.kde.org/attachment.cgi?id=36896)
Version information of kipi-plugin

Hello,

I updated it, but with no luck. I checked permissions of the files, but they
should allow it. Digikam imported them itself earlier. 

Then I tried to not use EXIF at all, and used that option where you can specify
the date, carefully disabling the checkboxes. Still no luck, the date doesn't
change.

I tried with "strace digikam" and "strace -f digikam", but I somehow Digikam
manages to escape. When trying to attach with strace to the running Digikam I
get something funny when I attempt to start the plugin:

*** glibc detected *** strace: munmap_chunk(): invalid pointer:
0x000000000240e7a0 ***                                            
======= Backtrace: =========                                                    
/lib/libc.so.6[0x30004716c8]                                                    
strace[0x4083df]                                                                
strace[0x4058de]                                                                
strace[0x404616]
/lib/libc.so.6(__libc_start_main+0xe6)[0x300041e5c6]
strace[0x401f69]
======= Memory map: ========
00400000-00447000 r-xp 00000000 08:12 140312                            
/usr/bin/strace
00647000-00648000 rw-p 00047000 08:12 140312                            
/usr/bin/strace
00648000-00656000 rw-p 00000000 00:00 0
0240e000-0242f000 rw-p 00000000 00:00 0                                  [heap]
3000000000-300001d000 r-xp 00000000 08:12 776736                        
/lib/ld-2.9.so
300021c000-300021d000 r--p 0001c000 08:12 776736                        
/lib/ld-2.9.so
300021d000-300021e000 rw-p 0001d000 08:12 776736                        
/lib/ld-2.9.so
3000400000-3000547000 r-xp 00000000 08:12 776742                        
/lib/libc-2.9.so
3000547000-3000747000 ---p 00147000 08:12 776742                        
/lib/libc-2.9.so
3000747000-300074b000 r--p 00147000 08:12 776742                        
/lib/libc-2.9.so
300074b000-300074c000 rw-p 0014b000 08:12 776742                        
/lib/libc-2.9.so
300074c000-3000751000 rw-p 00000000 00:00 0
3005e00000-3005e1a000 r-xp 00000000 08:12 776950                        
/lib/libgcc_s.so.1
3005e1a000-3006019000 ---p 0001a000 08:12 776950                        
/lib/libgcc_s.so.1
3006019000-300601a000 rw-p 00019000 08:12 776950                        
/lib/libgcc_s.so.1
7fc6100f2000-7fc6100f4000 rw-p 00000000 00:00 0
7fc610118000-7fc61011b000 rw-p 00000000 00:00 0
7fff1617e000-7fff16193000 rw-p 00000000 00:00 0                         
[stack]
7fff161c1000-7fff161c2000 r-xp 00000000 00:00 0                          [vdso]
ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0                 
[vsyscall]

So please advise. Can you reproduce the error?

Yours,
Kay

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.