Red Hat Bugzilla – Bug 984717
[abrt] evolution-3.8.3-2.fc19: proxy_pixbuf_destroy: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
Last modified: 2015-02-17 11:10:31 EST
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (7 frames)
#4 proxy_pixbuf_destroy at gtkicontheme.c:3515
#5 gdk_pixbuf_finalize at gdk-pixbuf.c:259
#7 handle_stock_request at e-stock-request.c:139
#8 run_in_thread at gsimpleasyncresult.c:871
#9 io_job_thread at gioscheduler.c:89
#10 g_task_thread_pool_thread at gtask.c:1242
#12 g_thread_proxy at gthread.c:798
Created attachment 773879 [details]
Created attachment 773880 [details]
Created attachment 773881 [details]
Created attachment 773882 [details]
Created attachment 773883 [details]
Created attachment 773884 [details]
Created attachment 773885 [details]
Created attachment 773886 [details]
Created attachment 773887 [details]
Created attachment 773888 [details]
*** Bug 984761 has been marked as a duplicate of this bug. ***
Thanks for a bug report. The other bug suggests that this might be deeper than in evolution, the gdk-pixbuf2, gnome-icon-theme and gtk3 come on mind. Did you update any of these recently, please? I have installed these:
$ rpm -q gdk-pixbuf2 gnome-icon-theme gtk3
and I do not recall seeing any such crash in the past (though those mine seems to be the latest available).
Here's my versions of what's installed on my machine from the other bug:
*** Bug 986597 has been marked as a duplicate of this bug. ***
The backtrace in bug 986597 as different, but similar enough that it's probably the same issue.
Should be fixed with the 3.8.4 package which I think is in updates-testing already, although it probably doesn't list this bug as being fixed.
Right, this bug is not linked in the update. The update reached its stable karma threshold recently, I suppose it'll be in stable repos within today, more or less.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
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 19 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.