After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 733519 - crash fetching mail ...
crash fetching mail ...
Status: RESOLVED DUPLICATE of bug 732018
Product: evolution
Classification: Applications
Component: Mailer
3.12.x (obsolete)
Other Linux
: Normal major
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2014-07-21 19:42 UTC by Michael Meeks
Modified: 2014-11-21 11:33 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Michael Meeks 2014-07-21 19:42:02 UTC 
Left Evolution fetching mail (I think) or perhaps quiescent : bang ...

Thread 0x83939b40 (LWP 24966) exited]
[Thread 0x81774b40 (LWP 24967) exited]
[8265:8296:0721/153500:ERROR:raw_channel_posix.cc(139)] recvmsg: Connection reset by peer
[8265:8296:0721/153500:ERROR:channel.cc(297)] RawChannel fatal error (type 1)
[Thread 0x8f7e9b40 (LWP 22041) exited]
[8265:8296:0721/153614:ERROR:raw_channel_posix.cc(139)] recvmsg: Connection reset by peer
[8265:8296:0721/153614:ERROR:channel.cc(297)] RawChannel fatal error (type 1)

(evolution:21974): camel-imapx-WARNING **: stream_token called with literal 261671
**
GLib-Net:ERROR:gtlsconnection-gnutls.c:688:end_gnutls_io: assertion failed: (!error || !*error)

Program received signal SIGABRT, Aborted.

+ Trace 233853







Comment 1


Milan Crha





          2014-11-21 10:22:41 UTC
        



Thanks for a bug report. It's a pita to see the application crash, because the gnutl developers think it's a good idea to crash whole process when an "incorrect" argument is passed in, in this case only an already set GError to a function which requires it being NULL (either outer or the inner (*error) error. GError is able to cope with this gracefully, only claiming on the console that the GError would be overwritten and so on, but gnutls developers insist on the assert.

A similar bug report is filled for this already, there for POP3, while you have it with IMAPx. I'll merge the bugs into one.

*** This bug has been marked as a duplicate of bug 732018 ***






Comment 2


Milan Crha





          2014-11-21 11:33:37 UTC
        



(In reply to comment #1)
> ...because the gnutl developers...

Ehm, I'm sorry, the assert is part of glib-networking, gtlsconnection-gnutls.c, not the actual gnutls code, thus not a gnutls developers decision. I'm sorry for blaiming them incorrectly, due to my misread of the backtrace.