This could have been forwarded to upstream evolution->conduits as an
improvement suggestion... It would be better if bogus data from the
palm didn't cause the app to throw an assert failure, but resulted in a
log message and skipping of the record, or some such. It's a rare
enough case, I guess.
Thanks for following up. Closing the bug report.
** Changed in: gnome-pilot (Ubuntu)
Status: Needs Info => Rejected
--
Sync failes - Evolution/T5 - Ubuntu Edgy
https://launchpad.net/bugs/65513
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/list
I think I solved my problem. I found some broken entries in my palm calender
database. They were dated to 01.01.1919!
After deleting them gnome-pilot works perfect.
Thanks,
Gerhard
PS: Sorry for the false bug report!
--
Sync failes - Evolution/T5 - Ubuntu Edgy
https://launchpad.net/bugs/65513
Thanks for your bug report. If this is reproducable can you try to get
another backtrace with the help of
http://wiki.ubuntu.com/DebuggingProgramCrash and get the debug symbols
for gnome-pilot, libglib2.0-0, libgtk2.0-0, libc6, libpisock9?
** Changed in: gnome-pilot (Ubuntu)
Importance: Undecid
