GNOME Bugzilla – Bug 728974
camel-WARNING **: CamelPOP3Folder::get_message_sync() reported failure without setting its GError
Last modified: 2021-05-19 12:28:43 UTC
Using Debian Sid/unstable with Evolution 3.12.0 from experimental the following warnings are printed to the terminal when starting Evolution. (evolution:6465): camel-WARNING **: CamelPOP3Folder::get_message_sync() reported failure without setting its GError (evolution:6465): GLib-CRITICAL **: g_propagate_error: assertion 'src != NULL' failed I am pretty sure these have been present since at least Evolution 3.4.x.
This is still there in Evolution-Data-Server 3.12.2.
Thanks for a bug report. These are new to me. I'm wondering why it says so. It probably failed to read the message from your server for some reason. Could you run evolution with debugging for pop3 on and see what it says, please? The command is: $ CAMEL_DEBUG=pop3 evolution &>log.txt I suppose you get the error whenever you click Send/Receive-><the pop3 account>.
Thanks for the log (you sent me it in private). If I read it correctly, then you connected to an account with 919 messages which are later downloaded and deleted (while there also seem to be one left (or new) message, thus it retrieved and deleted 920 messages). What confuses me the most is that the warning came in the middle of nowhere, during the UIDL command processing. It can be that the POP3 account was asked for a message which wasn't downloaded yet, but that also feels odd. Another weird thing is that the POP3 account connects to your server twice, while I would expect only one connection. After a brief code reading it looks to me like the POP3 stream read zero bytes from the server, which leads to an error state report without setting corresponding GError. Whether it is it or not I cannot tell for sure, the log doesn't show that much information as I hoped. I may investigate this later, it seems the messages are properly downloaded afterwards, thus it should be "only" annoying to see it on the console. Mine POP3 account doesn't show this runtime warning, but I do not have that that large traffic as you do.
Paul, I guess this didn't magically cleanup on its own, right?
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines and create a new bug report ticket at https://gitlab.gnome.org/GNOME/evolution/-/issues/ Thank you for your understanding and your help.