Changes have been made in Git (master):

commit 3d25bfab26f857f0cd44fb9aea29f85374dffcab
Author: Michael J Rubinsky <mrubinsk@horde.org>
Date:   Thu Apr 3 13:35:58 2014 -0400

     Bug: 11127 Gracefully handle errors during ajax calendar import.

  kronolith/data.php |    8 ++++----
  1 files changed, 4 insertions(+), 4 deletions(-)

http://github.com/horde/horde/commit/3d25bfab26f857f0cd44fb9aea29f85374dffcab

The traditional view does display the SQL error message at the top - 
the same style as the Turba import procedure errors. However, the 
Dynamic view just pops up the message (instantly, without waiting 
around):

'The calendar "[calendar name]" has been saved'

This is regardless of failure or success (in this case, it actually 
imported 30 out of 4800 events - I shrank the size of one of the 
fields in the back-end on purpose, to make it fail).

No error message or progress report in Dynamic mode. Actually, it has 
a success message every time - which is worse then no message.

There should be some feedback already. Do you get some if you use the 
traditional calendar view?

If the .ics import fails in Kronolith - there is no message in the 
interface. Turba spits back the SQL error message when importing .csv 
address books - which is useful in troubleshooting what went wrong. In 
Kronolith there is absolutely no indication of failure or success - or 
further details as to where things got jammed. It makes it impossible 
for users with no direct access to the back-end to troubleshoot 
calendar imports in .ics format (and by golly, they do go wrong a lot, 
in every calendar application I tried!)

Note that I've logged a different enhancement request regarding lack 
of progress feedback during import. I consider the two issues 
distinct: progress feedback during the import process and 
failure/success message at the end of the process.

Thank you