Red Hat Bugzilla – Bug 1014652
[abrt] Thunar-1.6.3-2.fc20: exo_icon_view_get_cell_area: Process /usr/bin/thunar was killed by signal 11 (SIGSEGV)
Last modified: 2015-06-29 20:43:17 EDT
Description of problem:
Tried to access a remote ressource via smb which causes Thunar to freeze and afterwards to crash
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (10 frames)
#0 exo_icon_view_get_cell_area at exo-icon-view.c:3358
#1 exo_icon_view_paint_item at exo-icon-view.c:3633
#2 exo_icon_view_expose_event at exo-icon-view.c:1699
#3 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:86
#8 gtk_widget_event_internal at gtkwidget.c:5017
#9 gtk_widget_send_expose at gtkwidget.c:4846
#10 gtk_main_do_event at gtkmain.c:1610
#11 _gdk_window_process_updates_recurse at gdkwindow.c:5427
#14 _gdk_windowing_window_process_updates_recurse at gdkwindow-x11.c:5643
#15 gdk_window_process_updates_internal at gdkwindow.c:5594
Potential duplicate: bug 795380
Created attachment 806467 [details]
Created attachment 806468 [details]
Created attachment 806469 [details]
Created attachment 806470 [details]
Created attachment 806471 [details]
Created attachment 806472 [details]
Created attachment 806473 [details]
Created attachment 806474 [details]
Created attachment 806475 [details]
Created attachment 806476 [details]
Created attachment 806477 [details]
*** Bug 1013824 has been marked as a duplicate of this bug. ***
Yeah, I can confirm this here as well. ;(
Would you be willing to file a upstream bug on it? Or would you like me to do so?
I can't tell if this is really a Thunar bug or some issue in exo. The crash itself is in exo icon view... so it could be some change to icon handling that exo isn't dealing with right.
I've filed a bug report upstream. Hope this gets fixed soon
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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'
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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.