Version-Release number of selected component: Thunar-1.8.4-1.fc29 Additional info: reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: /usr/bin/Thunar --daemon crash_function: g_type_check_instance_cast executable: /usr/bin/thunar journald_cursor: s=0f858401ce6c40a5843b22627e8b5d7b;i=1eca1;b=7d89e4bb67324bb688bae3a1d9b3716c;m=13223d6b2;t=583992ddd205d;x=99b93f1ef2a420fc kernel: 4.20.5-200.fc29.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 g_type_check_instance_cast at gtype.c:4058 #1 thunar_thumbnailer_queue_async_reply at thunar-thumbnailer.c:340 #2 g_task_return_now at gtask.c:1148 #3 g_task_return at gtask.c:1206 #4 reply_cb at gdbusproxy.c:2596 #5 g_task_return_now at gtask.c:1148 #6 g_task_return at gtask.c:1206 #7 g_dbus_connection_call_done at gdbusconnection.c:5715 #8 g_task_return_now at gtask.c:1148 #9 complete_in_idle_cb at gtask.c:1162
Created attachment 1542206 [details] File: backtrace
Created attachment 1542207 [details] File: cgroup
Created attachment 1542208 [details] File: core_backtrace
Created attachment 1542209 [details] File: cpuinfo
Created attachment 1542210 [details] File: dso_list
Created attachment 1542211 [details] File: environ
Created attachment 1542212 [details] File: limits
Created attachment 1542213 [details] File: maps
Created attachment 1542214 [details] File: mountinfo
Created attachment 1542215 [details] File: open_fds
Created attachment 1542216 [details] File: proc_pid_status
Created attachment 1542217 [details] File: exploitable
Is there a specific action that triggers this?
Similar problem has been detected: Just opened thunar using a desktop shortcut reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: Thunar --daemon crash_function: g_type_check_instance_cast executable: /usr/bin/thunar journald_cursor: s=29472d188ab04b05a366d06ececfcd61;i=2a657;b=470b1a1fd8634517b6a7967b6ad1c786;m=4764f175d;t=58476d1bf0041;x=563a3ab05f850625 kernel: 4.20.15-200.fc29.x86_64 package: Thunar-1.8.4-1.fc29 reason: thunar killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1695945 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. 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 '29'. 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 29 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 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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.