Version-Release number of selected component:
runlevel: N 5
Created attachment 1429888 [details]
Created attachment 1429889 [details]
Created attachment 1429890 [details]
Created attachment 1429891 [details]
Created attachment 1429892 [details]
Created attachment 1429893 [details]
Created attachment 1429894 [details]
Created attachment 1429895 [details]
Created attachment 1429896 [details]
Created attachment 1429897 [details]
Created attachment 1429898 [details]
I noticed the:
#1 0x00007f8a09ec17ac in g_log_default_handler (log_domain=log_domain@entry=0x7f8a09f02fae "GLib", log_level=log_level@entry=6, message=message@entry=0x7f899c0c8050 "Creating pipes for GWakeup: Too many open files\n", unused_data=unused_data@entry=0x0) at gmessages.c:3051
But is crashing really the best way to handle this?
Thanks for a bug report. It's the way glib (glib2 package) developers decided to behave. It usually points to a memory leak of some object which also contains that handle. That was the case in the past at least.
Your open_fds shows tons of "eventfd" handlers, which are usually tight to the GWeakup or such, if I recall correctly. The hardest thing is to figure out after what action the list of opened files increases. As your crash happened in the evolution-source-registry, then it'll be "slightly harder". And as 3.26.6 is out for quite some time, I'm unsure whether this is related to evolution-data-server (eds) itself, because I'd expect this strike sooner. But it's only my opinion, it can be all in eds, only the conditions for the reproducer didn't happen yet.
You can get the list of opened files with:
$ lsof -p `pidof evolution-source-registry` | sort >/tmp/a
then wait for a bit of time and rerun to the command, only to a different file:
$ lsof -p `pidof evolution-source-registry` | sort >/tmp/b
then you can "analyse" the changes with:
$ cat /tmp/a | wc -l
$ cat /tmp/b | wc -l
$ cat /tmp/a | grep -c eventfd
$ cat /tmp/b | grep -c eventfd
and when the counts increase, supposing what action had been done during the two calls, it can help to chase the issue.
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30 Fedora will stop maintaining and issuing updates for
Fedora 27. 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
EOL if it remains open with a Fedora 'version' of '27'.
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.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 27 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 this bug is closed as described in the policy above.
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 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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
Thank you for reporting this bug and we are sorry it could not be fixed.