Version-Release number of selected component: Thunar-1.3.0-6.fc17 Additional info: libreport version: 2.0.18 abrt_version: 2.0.18 backtrace_rating: 4 cmdline: /bin/Thunar crash_function: exo_icon_view_get_item_at_coords kernel: 3.6.9-2.fc17.x86_64 truncated backtrace: :Thread no. 1 (8 frames) : #0 exo_icon_view_get_item_at_coords at exo-icon-view.c:3764 : #1 exo_icon_view_motion_notify_event at exo-icon-view.c:1856 : #2 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:86 : #7 gtk_widget_event_internal at gtkwidget.c:5017 : #8 gtk_widget_event at gtkwidget.c:4814 : #9 gtk_propagate_event at gtkmain.c:2490 : #10 gtk_main_do_event at gtkmain.c:1685 : #16 gtk_main at gtkmain.c:1257
Created attachment 660855 [details] File: core_backtrace
Created attachment 660856 [details] File: environ
Created attachment 660857 [details] File: limits
Created attachment 660858 [details] File: backtrace
Created attachment 660859 [details] File: cgroup
Created attachment 660860 [details] File: smolt_data
Created attachment 660861 [details] File: executable
Created attachment 660862 [details] File: maps
Created attachment 660863 [details] File: dso_list
Created attachment 660864 [details] File: proc_pid_status
Created attachment 660865 [details] File: open_fds
Created attachment 660866 [details] File: var_log_messages
What were you doing when this happened? Can you duplicate it?
I's just booted the system up and logged in as normal (I hadn't done anything past that yet) - I think I'd left Thunar running when I'd shutdown before but trying that again didn't replicate the problem.
I encountered this bug, though in different situation. I opened a linked folder (I don't know whether I name it correctly - sorry for that) on desktop, then before Thunar managed to open window I grabbed this folder again to move it. When Thunars window opens, normally this linked folder is behind the window. When grabbed before it manages to start, Thunar opens a window, but does not load any content of it for a short while, then crashes. I managed to replicate for a few times it in this way, though it's really hard to do it when hard drive isn't loaded heavy enough, because Thunar opens too fast.
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 '17'. 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 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 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 17'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 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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. Thank you for reporting this bug and we are sorry it could not be fixed.