[evolution-kolab/ek-wip-porting: 21/22] KolabMailSynchronizer: folder hash table from InfoDb may be NULL



commit a6bc5352cd000c11934e0b1be41386ff42542d4b
Author: Christian Hilberg <hilberg kernelconcepts de>
Date:   Tue Sep 4 19:37:58 2012 +0200

    KolabMailSynchronizer: folder hash table from InfoDb may be NULL
    
    * InfoDb may be missing folder information (e.g. if an
      account with no IMAP folders is used)
    * we need to set an error in this case (and not use the
      NULL hash table)

 src/libekolab/kolab-mail-synchronizer.c |    7 +++++++
 1 files changed, 7 insertions(+), 0 deletions(-)
---
diff --git a/src/libekolab/kolab-mail-synchronizer.c b/src/libekolab/kolab-mail-synchronizer.c
index bdd30fe..86a0b30 100644
--- a/src/libekolab/kolab-mail-synchronizer.c
+++ b/src/libekolab/kolab-mail-synchronizer.c
@@ -1151,6 +1151,13 @@ mail_synchronizer_uids_update_infodb (KolabMailSynchronizer *self,
 		g_propagate_error (err, tmp_err);
 		return FALSE;
 	}
+	if (folders_lst == NULL) {
+		g_set_error (err,
+		             KOLAB_BACKEND_ERROR,
+		             KOLAB_BACKEND_ERROR_INFODB_NOFOLDER,
+		             _("No folder information in internal database"));
+		return FALSE;
+	}
 
 	if (foldername != NULL) {
 		GHashTable *folders_tbl = NULL;



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]