Yes. You're right. That was the problem. Disabling the mapping of organizer and attendees solves the problem. Eventually, I moved the calendar backing store from my exchange network folder to a local data file and switched on the organizer/attendees mapping again. It works. Thank you! Thank you for this cool piece of software! :-)
CalDav Sync failed: Can't respond to meeting invite.
merged patch from Dennis Nowak: added documentation of 'terminate' command line option
fixed warnings
merged patch from Dennis Nowak: added 'terminate' command line option
german translation: fixed missing newlines in license text
added 'missing' to .gitignore
updated e-mail address
updated po files
removed 'missing' file, it will be re-generated...
raised version to 0.6.4 (March, the 5th 2017)
updated po files
raised version to 0.6.4 (March, the 5th 2017)
removed it from full language support (docs sti...
added missing it + de translations
documentation update
minor changes to german docu
WIP: german translation of help file
reverted remains of commit 3863c1
german translation of documentation finished
PLEASE DISREGARD THIS PATCH, because the behaviour of the Mouse FSM was already correct...
(partially) reverted commit 3863c1, because the...
added images for german documentation and skele...
Reverted "(re-)added fr and ru documentation ba...
replaced again florence.png and switch.png imag...
also resurrected broken switch.png image in doc...
resurrected lost close.png and florence.png ima...
made desktop icon theme-aware
updated .gitignore
added install hook for updating the hicolor ico...
fixed default installation prefix back to /usr/...
(re-)added fr and ru documentation back to git
added 'compile' file to .gitignore
moved florence icon from /usr/share/pixmaps to ...
updated po files
prevent recursion (+ stack overflow) when bigge...
swapped LATCHED and LOCKED states of modifiier ...
swap order of latched and locked state of modifier keys
fix crash of resize buttons on Linux Mint 18
After some days of debugging, I'm pretty sure that printing to a Standard TCP/IP...
After some days of debugging, I'm pretty sure that printing to a Standard TCP/IP...
@Anton: which client did you use? Are you sure the problem arose when upgrading the...
After some days of debugging, I'm pretty sure that printing to a Standard TCP/IP...