Bug 887350

Created attachment 663714 [details]
File: backtrace

Created attachment 663715 [details]
File: build_ids

Created attachment 663716 [details]
File: cgroup

Created attachment 663717 [details]
File: core_backtrace

Created attachment 663718 [details]
File: dso_list

Created attachment 663719 [details]
File: environ

Created attachment 663720 [details]
File: limits

Created attachment 663721 [details]
File: maps

Created attachment 663722 [details]
File: open_fds

Created attachment 663723 [details]
File: proc_pid_status

Created attachment 663724 [details]
File: var_log_messages

Just trying to start evolution.  Previously though I did have a disk full on /home situation which may have caused some writes to fail.

backtrace_rating: 4
Package: evolution-data-server-3.6.2-2.fc18
OS Release: Fedora release 18 (Spherical Cow)

Thanks for a bug report. It seems the file
  /home/brian/.config/evolution/sources/1354513998.2438.22
is corrupt, or one before it, whatever ordering the evolution-source-registry process uses, thus it causes memory corruption. I suggest to move away whole:
  /home/brian/.config/evolution/sources
folder and then run evolution from scratch. It'll need to re-add all the accounts, but it should start without trouble. Other option is to try to find which .source files does the trouble, and remove only it. Note you can run the source registry process on its own, it resides in
   $ /usr/libexec/evolution-source-registry

Please let me know whether it helped. I would be interested in the broken .source file too, thus we might be able to fix the memory corruption bug. Thanks in advance.

I don't seem to be reproducing this.  I suspect that removing my .config/evolution/sources got rid of whatever corruption there was.  Any corruption should have been limited to just empty files as a result of trying to write with an ENOSPC condition.

Thanks for the update. Do you mean that you got out of disk space in one moment, then you freed some space, cleared the sources folder and everything is back normal?

That's correct, yes.

It seems you are right, the disk-full looks like a hard condition for this crash, because if I try to pass a zero-length file into evolution-source-registry, then it doesn't crash, neither valgrind claim any error. I also tried with a garbage file, which contained just part of a corect .source file, but no luck too, valgrind is quiet.

upgrade fedora 18 ,reboot.

backtrace_rating: 4
Package: evolution-data-server-3.6.3-2.fc18
OS Release: Fedora release 18 (Spherical Cow)

Hi all, I see more and more users being affected by this issue, but it's hard to believe that all of you are out of disk space, which makes me wonder what else can cause this to happen for you.

Could anybody of you try the comment #13 investigation, please? Of course it's not in brian's home on respective machine, but you might see the file path in your backtraces, when you search there for "/home" (quotes for clarity only). 

I'd like to ask for that broken file, to try to reproduce it here. Thanks in advance.

Tried to add Exchange server to Evolution.  Filled in all the necessary forms, and clicked on "OK".  Evolution hung for about 10 minutes before I had to do a kill -9 on its processes.

backtrace_rating: 4
cmdline:        /usr/libexec/evolution-source-registry
crash_function: magazine_chain_pop_head
executable:     /usr/libexec/evolution-source-registry
kernel:         3.8.8-202.fc18.x86_64
package:        evolution-data-server-3.6.4-3.fc18
reason:         Process /usr/libexec/evolution-source-registry was killed by signal 11 (SIGSEGV)
uid:            500
ureports_counter: 1

This might be addressed by the bug #974296.

This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.