Bug#412093: more info on #412093
Ana Guerrero wrote:
> severity 412093 important
> Hi Pedro,
> I'm downgroading the bug severity to important because i'm not sure this
> is even a problem of kpilot.
> Firstly, another etch's user has told me his palm works fine. Second, the bug
> you're reporting have appeared after an upgrade where kpilot was not changed
> at all (see Sune's mail above in this bug report).
> Could you check that your device is ok?
It seems to be working fine. I have even booted linux on it to check for
error messages and such, but there were none that I could catch.
I have tried to reproduce the problem without success this morning. I
usually sync the palm a couple of times a week, and since the problems I
had last year, I have a weekly backup with pilot-xfer. I had a restore
of my last backup to the palm (to play on the safe side), added the
missing events by hand, and had another backup with pilot-xfer.
Next I killed the kpilotDaemon proc, started kpilot and tried a sync. It
went fine as far as I can tell. Then I tried to add a few events to both
sides and synced again, and it went fine again AFAIK.
Summing up, I could not reproduce the problem this morning.
Please note that the problem described in the bug report caused the loss
of maybe 2 dozen entries on the palm. It may indeed be unrelated to
kpilot, but I would love a few suggestions on how to generate more
usefull info in case this happens again.