Description of problem: I Dragged some *.pdf and *.pptx files from one thunar window into another, then I tried to create a new folder using the "another" window, at this point the application crashed. Version-Release number of selected component: Thunar-1.6.15-1.fc28 Additional info: reporter: libreport-2.9.5 backtrace_rating: 4 cmdline: Thunar --daemon crash_function: poll_for_event executable: /usr/bin/thunar journald_cursor: s=7a58bd34b4d54ced98e241216ba1c0b3;i=159a;b=4001b8bbdd534be999ee7f1e928bc8ed;m=626cc5b0f;t=576eecce6a326;x=eca93301f56a3f2e kernel: 4.18.9-200.fc28.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000
Created attachment 1488094 [details] File: backtrace
Created attachment 1488095 [details] File: cgroup
Created attachment 1488096 [details] File: core_backtrace
Created attachment 1488097 [details] File: cpuinfo
Created attachment 1488098 [details] File: dso_list
Created attachment 1488099 [details] File: environ
Created attachment 1488100 [details] File: limits
Created attachment 1488101 [details] File: maps
Created attachment 1488102 [details] File: mountinfo
Created attachment 1488103 [details] File: open_fds
Created attachment 1488104 [details] File: proc_pid_status
Did you notice the application crash or was it only a ABRT prompt?
(In reply to Mukundan Ragavan from comment #12) > Did you notice the application crash or was it only a ABRT prompt? It was long ago. but as I remember, there was no prompt. all thunar windows just vanished and then, yes there was a prompt from the system stating that the application has crashed.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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 bug. Thank you for reporting this bug and we are sorry it could not be fixed.