Menu
▾
▴
[gphoto-bugs] [ gphoto-Bugs-1492476 ] libgphoto2 does not preserve timestamps
|
From: SourceForge.net <no...@so...> - 2007-06-14 14:54:09
|
Bugs item #1492476, was opened at 2006-05-21 20:46 Message generated for change (Comment added) made by mdeegan You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=108874&aid=1492476&group_id=8874 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: libgphoto2 Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Michael (mdeegan) Assigned to: Hubert Figuiere (hfiguiere) Summary: libgphoto2 does not preserve timestamps Initial Comment: I'm sure it used to, but it sure doesn't preserve timestamps now. (Using a Canon A60, if that helps.) michael@wibble:/tmp$ date;gphoto2 -p 187;jhead IMG_8843.JPG|grep -i date Sun May 21 20:44:51 WST 2006 Detected a 'Canon:PowerShot A60'. Downloading 'IMG_8843.JPG' from folder '/DCIM/388CANON'... Saving file as IMG_8843.JPG File date : 2006:05:21 20:44:55 Date/Time : 2006:05:21 14:56:45 ---------------------------------------------------------------------- >Comment By: Michael (mdeegan) Date: 2007-06-14 22:54 Message: Logged In: YES user_id=1248468 Originator: YES Hmm, was that comment meant to be a repeat of the question I already answered in the affirmative? ---------------------------------------------------------------------- Comment By: Marcus Meissner (marcusmeissner) Date: 2007-06-13 12:54 Message: Logged In: YES user_id=48092 Originator: NO utime("MVI_6610.AVI", [2007/06/10-06:25:14, 2007/06/10-06:25:14]) = 0 the wrong mtime arrives there. hmm. Is this also happening with .JPG files? ---------------------------------------------------------------------- Comment By: Michael (mdeegan) Date: 2007-06-13 07:11 Message: Logged In: YES user_id=1248468 Originator: YES Yes, all files. I deliberately chose a non-JPEG file, to eliminate libexif from the equation. I am wondering if something that's a localtime is being treated as a utctime and is having a utc offset applied twice as a result. It occurred to me that it could be the timezone configured into the camera, but no, changing it (which does not change the camera's value of localtime) does not affect the resulting timestamps: michael@wibble:~/t$ jhead *JPG|grep -i date File date : 2007:06:13 14:53:09 Date/Time : 2007:06:13 06:53:09 File date : 2007:06:13 14:53:51 Date/Time : 2007:06:13 06:53:51 Next I tried fiddling the home-away timezone setting (the "away" timezone is UTC+11). No luck: File date : 2007:06:13 18:02:47 Date/Time : 2007:06:13 10:02:47 File date : 2007:06:13 15:03:15 Date/Time : 2007:06:13 07:03:15 And thirdly, $TZ doesn't seem to be an influence either: (eg. after "TZ=Australia/Melbourne strace -o gphoto-TZtest-strace.log gphoto2-2.3.1/gphoto2/gphoto2 -P --debug --debug-logfile gphoto-TZtest-debug.log"): michael@wibble:~/t$ jhead *JPG|grep -i date File date : 2007:06:13 18:02:46 Date/Time : 2007:06:13 10:02:47 File date : 2007:06:13 15:03:14 Date/Time : 2007:06:13 07:03:15 ie. still an 8 hour offset. ---------------------------------------------------------------------- Comment By: Marcus Meissner (marcusmeissner) Date: 2007-06-13 05:19 Message: Logged In: YES user_id=48092 Originator: NO utime("MVI_6610.AVI", [2007/06/10-06:25:14, 2007/06/10-06:25:14]) = 0 the wrong mtime arrives there. hmm. Is this also happening with .JPG files? ---------------------------------------------------------------------- Comment By: Michael (mdeegan) Date: 2007-06-09 23:50 Message: Logged In: YES user_id=1248468 Originator: YES I recorded a short movie. root@wibble:/home/michael/t# strace -o gphoto-strace.log ./gphoto2-2.3.1/gphoto2/gphoto2 -p 426 --debug --debug-logfile gphoto-debug.log Downloading 'MVI_6610.AVI' from folder '/store_00010001/DCIM/175CANON'... Saving file as MVI_6610.AVI root@wibble:/home/michael/t# stat MVI_6610.AVI File: `MVI_6610.AVI' Size: 8192516 Blocks: 16032 IO Block: 4096 regular file Device: 807h/2055d Inode: 1684279 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2007-06-10 06:25:14.000000000 +0800 Modify: 2007-06-10 06:25:14.000000000 +0800 Change: 2007-06-09 22:29:49.000000000 +0800 root@wibble:/home/michael/t# head -4 MVI_6610.AVI|strings -n 24|head -1 SAT JUN 09 22:25:14 2007 root@wibble:/home/michael/t# mount|grep /home /dev/sda7 on /home type ext3 (rw) root@wibble:/home/michael/t# uname -a Linux wibble 2.6.21.1-wibble #5 SMP PREEMPT Tue May 15 19:49:49 WST 2007 x86_64 GNU/Linux Naturally enough, I'll be keeping gphoto-debug.log in case you wish to look at that too. :P File Added: gphoto-strace.log.gz ---------------------------------------------------------------------- Comment By: Marcus Meissner (marcusmeissner) Date: 2007-06-09 22:21 Message: Logged In: YES user_id=48092 Originator: NO can you run strace -ologfile gphoto2 -p 187 and attach the strace logfile here? What filesystem are you saving on? What kernel version? ---------------------------------------------------------------------- Comment By: Michael (mdeegan) Date: 2007-06-07 18:03 Message: Logged In: YES user_id=1248468 Originator: YES Same result. root@wibble:/home/michael/t# ldd `ldd ./gphoto2-2.3.1/gphoto2/gphoto2 | awk '/libgphoto2.so.2/ {print $3}'`|grep exif libexif.so.12 => /usr/lib/libexif.so.12 (0x00002accff717000) ---------------------------------------------------------------------- Comment By: Marcus Meissner (marcusmeissner) Date: 2007-06-07 17:50 Message: Logged In: YES user_id=48092 Originator: NO please check libgphoto2, not the cmdline gphoto2. ldd /usr/lib/libgphoto2*so*|grep libexif ---------------------------------------------------------------------- Comment By: Michael (mdeegan) Date: 2007-06-07 17:45 Message: Logged In: YES user_id=1248468 Originator: YES It is. michael@wibble:~/t/gphoto2-2.3.1$ ldd ./gphoto2/gphoto2 |grep exif libexif.so.12 => /usr/lib/libexif.so.12 (0x00002ae885b85000) (that's Debian's libexif12 0.6.13) Is libexif used for non-JPEG files (eg. videos)? They have the same time offset problem. ---------------------------------------------------------------------- Comment By: Marcus Meissner (marcusmeissner) Date: 2007-06-07 16:02 Message: Logged In: YES user_id=48092 Originator: NO mdeegan: please make sure your libgphoto2 is built against libexif. ---------------------------------------------------------------------- Comment By: Michael (mdeegan) Date: 2007-06-03 16:57 Message: Logged In: YES user_id=1248468 Originator: YES AFAICT Canon S3 IS is PTP-only. It's not clear from the manuals how I would attempt to force usage of any particular driver... I've just tried libgphoto2 2.3.1 (from debian lenny) with no change in behaviour. On the other hand, updating the gphoto2 program itself from 2.2.0 to 2.3.1 -did-. Unfortunately, the timestamps are out by 8 hours (into the future). It may help to note that my timezone is UTC+8. ---------------------------------------------------------------------- Comment By: Hubert Figuiere (hfiguiere) Date: 2007-06-02 00:36 Message: Logged In: YES user_id=27487 Originator: NO 1/ which driver? 2/ what about trying with libgphoto2 2.3.1. ---------------------------------------------------------------------- Comment By: Michael (mdeegan) Date: 2007-06-02 00:05 Message: Logged In: YES user_id=1248468 Originator: YES Now using a Canon S3 IS and gphoto2 2.2.0 and libgphoto2 2.2.1 (Debian). Files still do not have the right timestamps (which is a problem for non-JPEG files...). ---------------------------------------------------------------------- Comment By: Hans Ulrich Niedermann (hun) Date: 2006-07-30 01:50 Message: Logged In: YES user_id=59853 I have just downloaded a bunch of files using gphoto2 trunk (r9037) and libgphoto2 trunk (r9030) and all files were stored with the correct timestamp. Canon PowerShot G2, canon.so ---------------------------------------------------------------------- Comment By: Hubert Figuiere (hfiguiere) Date: 2006-07-20 02:15 Message: Logged In: YES user_id=27487 problem is in PTP too was working fine with 2.1.6 ---------------------------------------------------------------------- Comment By: Niccolo Rigacci (niccolo_r) Date: 2006-07-19 22:21 Message: Logged In: YES user_id=1558369 Same problem here, with a Canon IXUS 40. I think that is a gphoto2 problem, not a libgphoto one, because if I mount the camera as a filesystem with gphotofs, I get the correct timestamps. I work on a Debian Testing (Etch) box, with the following programs version: gphoto2 2.2.0-3 gphotofs 0.2-2 libgphoto2-2 2.2.1-2 libgphoto2-port0 2.2.1-2 Feel free to contact me, I have a debug log of the download operation. ---------------------------------------------------------------------- Comment By: Marcus Meissner (marcusmeissner) Date: 2006-05-21 21:57 Message: Logged In: YES user_id=48092 Hmm. Likely a canon driver problem. Before it used the ptp2 driver I think. :/ ---------------------------------------------------------------------- Comment By: Michael (mdeegan) Date: 2006-05-21 21:26 Message: Logged In: YES user_id=1248468 Oh yeah. libgphoto2 2.1.6 with gphoto 2.1.5 also results in broken timestamps (therefore, bug likely in lib rather than app). Hopefully I'll stop replying to myself now. :P ---------------------------------------------------------------------- Comment By: Michael (mdeegan) Date: 2006-05-21 21:24 Message: Logged In: YES user_id=1248468 Oh yeah. This was tested under 2.1.6-8 and 2.1.6-10 under Debian testing/etch. Further experimentation (snapshot.debian.net FTW) seems to show that this is a libgphoto2 regression going from 2.1.5 to 2.1.6. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=108874&aid=1492476&group_id=8874 |