View Single Post
Old 10-11-2011, 07:45 PM   #162
Robert22
Zealot
Robert22 has exceeded all limitations known to mankindRobert22 has exceeded all limitations known to mankindRobert22 has exceeded all limitations known to mankindRobert22 has exceeded all limitations known to mankindRobert22 has exceeded all limitations known to mankindRobert22 has exceeded all limitations known to mankindRobert22 has exceeded all limitations known to mankindRobert22 has exceeded all limitations known to mankindRobert22 has exceeded all limitations known to mankindRobert22 has exceeded all limitations known to mankindRobert22 has exceeded all limitations known to mankind
 
Robert22's Avatar
 
Posts: 108
Karma: 17102
Join Date: Sep 2010
Location: San Diego, CA
Device: PRS-505 600 300 350 T1 T2 Kindle PW1 PW2 KV Clara 2E Libra 2 Leaf 2
Quote:
Originally Posted by Kolenka View Post
It would be (GMT+1, so east of UTC). It's a really stupid bug on the part of Sony too.

If I change my device's timezone to be east of where it was before (say GMT-7 to GMT-6), it will trigger a rescan of the entire library (and undo the work of my device_db plugboards). It makes me a little dead inside that something like this made it through, and there are easy ways on *nix systems to go from localtime to a valid Unix Epoch timestamp. They had to go out of their way to create a bug like this.

It's weird that you aren't seeing the path bug others are seeing, though.
Will this affect the change from DST to Standard time?
Robert22 is offline   Reply With Quote