On Wednesday 30 April 2008 08:32:45 pm Ralph Alvy wrote: >/ On Wednesday 30 April 2008 04:33:02 pm Ralph Alvy wrote: />/ > I notice that if I clean all data out of my ~/.jpilot folder and then do />/ > a sync with jpilot 0.99.9.22 (or just do a clean install of 0.99.9.22 and />/ > do a sync), I end up with a reset loop that I have to stop with a hard />/ > reset. />/ > />/ > This is repeatable under the latest Arch Linux. / >Further testing shows that if I do a clean compile and install of JPilot >0.99.9.18 on the same Arch Linux box, I do not get the reset loop. To perform >this test, I did what always causes the reset loop with 0.99.9.22 -- I >deleted my ~/.jpilot folder before running 0.99.9.18, starting fresh. This is >the way I can guarantee that 0.99.9.22 will cause the reset loop. 0.99.9.18 >desn't suffer this problem. I'm a developer for Jpilot and am obviously concerned about this bug. To make sure we are not chasing a temporary instability could you try compiling the latest code from CVS and verify that the bug is still there? If it is I'm going to have to ask for some more data. A recent bug report was filed on Bugzilla for this: http://bugs.jpilot.org/1918 but it would be useful to have your experience in excruciating detail as well. I'd like to know, in particular, whether you are using the new Contacts database and Memos database within Jpilot. Also, when you say it enters a reset loop are you getting the same message about an Invalid AppInfo Block that the bug reporter does?
More information about the jpilot mailing list