Description of problem: drag and dropped one folder from the desktop into an open window Version-Release number of selected component: Thunar-1.6.10-2.fc23 Additional info: reporter: libreport-2.6.4 backtrace_rating: 3 cmdline: /usr/bin/Thunar --daemon executable: /usr/bin/thunar global_pid: 3981 kernel: 4.3.5-300.fc23.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (4 frames) #0 ?? #4 exo_job_emit_valist_in_mainloop at exo-job.c:359 #5 mainloop_proxy_func at gioscheduler.c:200 #10 gtk_main at gtkmain.c:1268
Created attachment 1122911 [details] File: backtrace
Created attachment 1122913 [details] File: cgroup
Created attachment 1122918 [details] File: core_backtrace
Created attachment 1122920 [details] File: dso_list
Created attachment 1122922 [details] File: environ
Created attachment 1122923 [details] File: exploitable
Created attachment 1122925 [details] File: limits
Created attachment 1122928 [details] File: maps
Created attachment 1122931 [details] File: mountinfo
Created attachment 1122933 [details] File: open_fds
Created attachment 1122934 [details] File: proc_pid_status
Created attachment 1122935 [details] File: var_log_messages
Can you get the crash to happen again? If you upgrade to: http://koji.fedoraproject.org/koji/taskinfo?taskID=12359686 does it prevent the crash?
When I've reported the bug I could reproduce it yesterday. Tried again today after one reboot with same version 1.6.10-2.fc23 but could not get it to crash(5-10 tries). Installed version 1.6.10.4.fc24.x86_64 from rawhide, crashed at the first try. --- Running report_uReport --- This problem has already been reported. https://retrace.fedoraproject.org/faf/reports/933223/ https://bugzilla.redhat.com/show_bug.cgi?id=1279227 Adding you to CC List of the existing bugzilla bug Using Bugzilla ID '1279227' Logging into Bugzilla at https://bugzilla.redhat.com Logging out
Yeah, was wondering if this was a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1279070 and it seems so. ;( *** This bug has been marked as a duplicate of bug 1279070 ***