GNOME Bugzilla – Bug 705771
Improve error handling in POP3 code
Last modified: 2015-04-27 16:34:18 UTC
I have just seen this messages in journalctl output after broken the connection with pop3 server (fortunately, no mail has been lost :D): ago 10 21:19:56 belkin4 gnome-session[28773]: (evolution:31016): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory ago 10 21:19:56 belkin4 gnome-session[28773]: This indicates a bug in someone's code. You must ensure an error is NULL before it's set. ago 10 21:19:56 belkin4 gnome-session[28773]: The overwriting error message was: TCP connection reset by peer ago 10 21:20:04 belkin4 gnome-session[28773]: (evolution:31016): camel-pop3-provider-CRITICAL **: camel_pop3_engine_command_new: assertion `pe != NULL' failed ago 10 21:20:04 belkin4 gnome-session[28773]: (evolution:31016): camel-pop3-provider-CRITICAL **: camel_pop3_engine_iterate: assertion `pe != NULL' failed Not sure if it has any side effect, feel free to take care of this if you think so :/ Best regards!
*** Bug 729148 has been marked as a duplicate of this bug. ***
I tried to address as much as I was able to. I even cheated in the code to get some useful input. The code will behave better now, even not necessarily 100% "GError bug"-free. Created commit dbe1180 in eds master (3.17.2+) Created commit c7433db in eds gnome-3-16 (3.16.2+)