Bug 1273581

Summary: [abrt] Thunar: thunar_shortcuts_model_set_busy(): thunar killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Florian "der-flo" Lehner <dev>
Component: ThunarAssignee: Kevin Fenzi <kevin>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: christoph.wickert, kevin, nonamedotc
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/ad06b342da8aab4548699ca98cf51cae2acacc41
Whiteboard: abrt_hash:51fcfc1807679e01f7b2cc574b607e53a6dd7d71;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 18:16:50 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Florian "der-flo" Lehner 2015-10-20 18:03:16 UTC 
Version-Release number of selected component:
Thunar-1.6.10-1.fc22

Additional info:
reporter:       libreport-2.6.2
backtrace_rating: 4
cmdline:        Thunar --daemon
crash_function: thunar_shortcuts_model_set_busy
executable:     /usr/bin/thunar
global_pid:     2013
kernel:         4.2.3-200.fc22.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (6 frames)
 #0 thunar_shortcuts_model_set_busy at thunar-shortcuts-model.c:2163
 #1 thunar_browser_poke_device_finish at thunar-browser.c:588
 #2 thunar_device_operation_finish at thunar-device.c:275
 #3 g_simple_async_result_complete at gsimpleasyncresult.c:763
 #4 complete_in_idle_cb at gsimpleasyncresult.c:775
 #9 gtk_main at gtkmain.c:1268

Potential duplicate: bug 1018526
Comment 1 Florian "der-flo" Lehner 2015-10-20 18:03:22 UTC 
Created attachment 1084856 [details]
File: backtrace
Comment 2 Florian "der-flo" Lehner 2015-10-20 18:03:23 UTC 
Created attachment 1084858 [details]
File: cgroup
Comment 3 Florian "der-flo" Lehner 2015-10-20 18:03:25 UTC 
Created attachment 1084859 [details]
File: core_backtrace
Comment 4 Florian "der-flo" Lehner 2015-10-20 18:03:26 UTC 
Created attachment 1084860 [details]
File: dso_list
Comment 5 Florian "der-flo" Lehner 2015-10-20 18:03:28 UTC 
Created attachment 1084861 [details]
File: environ
Comment 6 Florian "der-flo" Lehner 2015-10-20 18:03:30 UTC 
Created attachment 1084862 [details]
File: limits
Comment 7 Florian "der-flo" Lehner 2015-10-20 18:03:32 UTC 
Created attachment 1084863 [details]
File: maps
Comment 8 Florian "der-flo" Lehner 2015-10-20 18:03:33 UTC 
Created attachment 1084864 [details]
File: mountinfo
Comment 9 Florian "der-flo" Lehner 2015-10-20 18:03:35 UTC 
Created attachment 1084865 [details]
File: namespaces
Comment 10 Florian "der-flo" Lehner 2015-10-20 18:03:36 UTC 
Created attachment 1084866 [details]
File: open_fds
Comment 11 Florian "der-flo" Lehner 2015-10-20 18:03:38 UTC 
Created attachment 1084867 [details]
File: proc_pid_status
Comment 12 Florian "der-flo" Lehner 2015-10-20 18:03:39 UTC 
Created attachment 1084868 [details]
File: var_log_messages
Comment 13 Kevin Fenzi 2015-10-20 20:08:20 UTC 
What were you doing when this happened?

Can you duplicate the crash?
Comment 14 Fedora End Of Life 2016-07-19 18:16:50 UTC 
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.