GNOME Bugzilla – Bug 723345
[abrt] Crash under nntp_stream_fill()
Last modified: 2018-12-11 17:00:15 UTC
Moving this from a downstream bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1059740 Description of problem: I subscribed to two more NNTP groups and then added them to a vfolder. Version-Release number of selected component: evolution-3.8.5-2.fc19 Additional info: reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: evolution crash_function: memcpy executable: /usr/bin/evolution kernel: 3.11.9-200.fc19.x86_64 Core was generated by `evolution'. Program terminated with signal 11, Segmentation fault.
+ Trace 233104
Thread 22 (Thread 0x7f5c9bf4a700 (LWP 29113))
Thread 1 (Thread 0x7f5ca2ff3700 (LWP 29073))
I wonder if you can provide any advise. Since this segfault happens during startup even I am completely unable to use evolution.
Are you able to reproduce this crash reliably? I was not, unfortunately. What is your evolution version? If this is reliable, then it might depend on actual NNTP account state, like what messages are to be downloaded, thus I would be interested in your local cache for the NNTP account, together with the account setting, if it's a public server, without password. You can find the account setting in ~/.config/evolution/sources, basically all .source files which contain 'nntp' in it. The local cache is stored at ~/.cache/evolution/mail/<nntp-account-uid>, where nntp-account-uid is the file's name part of the .source files (the .source filename is "<nntp-account-uid>.source"). The <nntp-account-uid> string might be also included in other .source files (up to 2), where one is used for sending. One option to get past the crash is to start evolution in offline (evolution --offline), or even unplug the computer from the Internet completely, and disable/remove the NNTP account - of course, you'll lose the NNTP part of evolution, but you'll be able to run it. Getting rid of above-mentioned .source files, or the NNTP cache might do the trick too, I guess, just please do not delete them, if they lead to a reproducer.
(In reply to comment #2) > Are you able to reproduce this crash reliably? Hrm. I thought for sure my answer to this was going to be "of course" since I have not been using for a couple of days given that it crashed several times in a row when I originally reported the bug. So I was surprised when I started it up this morning just to make sure it was not going to make a liar out of me when I reported that and then lo and behold, it's working. > What > is your evolution version? evolution-3.8.5-2.fc19 > One option to get past the crash is to start evolution in offline (evolution > --offline), or even unplug the computer from the Internet completely, and > disable/remove the NNTP account Ahhh. Great idea. I had not thought of that. I will try to keep that in mind for next time. Thanks much!
(In reply to comment #3) > So I was surprised when I started it up this morning just to make sure it was > not going to make a liar out of me when I reported that and then lo and behold, > it's working. So it works for you the same way as for me, it crashes couple times, but once I eventually try to figure out what is wrong it starts working "properly" (not crashing). I'm pretty sure the fix will be small, it might be just about some overlook in reference counting, but getting it is so hard for me that I cannot figure out the reason of the crash.
(In reply to comment #4) > > So it works for you the same way as for me, it crashes couple times, but once I > eventually try to figure out what is wrong it starts working "properly" (not > crashing). I guess that's the case. I suppose I was just not persistent enough the first time I saw this a couple of times. > I'm pretty sure the fix will be small, it might be just about some > overlook in reference counting, Yeah. > but getting it is so hard for me that I cannot > figure out the reason of the crash. I will try to gather some data after the initial crash if I see this again.
Thanks for a bug report. I'm closing this as obsolete, but feel free to reopen or comment in case you can reproduce with the current 3.30.x stable series.