Bug 1259065

Summary: [abrt] nautilus: handlers_find(): nautilus killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Kamil Páral <kparal>
Component: nautilusAssignee: Matthias Clasen <mclasen>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: ccecchi, mclasen
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/7b07d516c0d7d8af9cd88e93f4b9440f995a0fe4
Whiteboard: abrt_hash:e6c759c796f760621f7fbd9ad185185f6d5a7196
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 17:45:35 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 Kamil Páral 2015-09-01 21:28:33 UTC 
Description of problem:
searching in nautilus

Version-Release number of selected component:
nautilus-3.16.2-2.fc22

Additional info:
reporter:       libreport-2.6.2
backtrace_rating: 4
cmdline:        /usr/bin/nautilus --gapplication-service
crash_function: handlers_find
executable:     /usr/bin/nautilus
global_pid:     3944
kernel:         4.1.6-200.fc22.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 handlers_find at gsignal.c:522
 #1 signal_handlers_foreach_matched_R at gsignal.c:2714
 #2 g_signal_handlers_disconnect_matched at gsignal.c:2864
 #3 reset_file_list at nautilus-search-directory.c:105
 #4 search_force_reload at nautilus-search-directory.c:608
 #5 begin_location_change at nautilus-window-slot.c:937
 #6 nautilus_window_slot_force_reload at nautilus-window-slot.c:1761
 #7 sync_search_directory at nautilus-window-slot.c:218
 #8 query_editor_changed_callback at nautilus-window-slot.c:285
 #9 ffi_call_unix64 at ../src/x86/unix64.S:76
Comment 1 Kamil Páral 2015-09-01 21:28:36 UTC 
Created attachment 1069205 [details]
File: backtrace
Comment 2 Kamil Páral 2015-09-01 21:28:37 UTC 
Created attachment 1069206 [details]
File: cgroup
Comment 3 Kamil Páral 2015-09-01 21:28:39 UTC 
Created attachment 1069207 [details]
File: core_backtrace
Comment 4 Kamil Páral 2015-09-01 21:28:40 UTC 
Created attachment 1069208 [details]
File: dso_list
Comment 5 Kamil Páral 2015-09-01 21:28:41 UTC 
Created attachment 1069209 [details]
File: environ
Comment 6 Kamil Páral 2015-09-01 21:28:43 UTC 
Created attachment 1069210 [details]
File: limits
Comment 7 Kamil Páral 2015-09-01 21:28:45 UTC 
Created attachment 1069211 [details]
File: maps
Comment 8 Kamil Páral 2015-09-01 21:28:46 UTC 
Created attachment 1069212 [details]
File: mountinfo
Comment 9 Kamil Páral 2015-09-01 21:28:47 UTC 
Created attachment 1069213 [details]
File: namespaces
Comment 10 Kamil Páral 2015-09-01 21:28:49 UTC 
Created attachment 1069214 [details]
File: open_fds
Comment 11 Kamil Páral 2015-09-01 21:28:50 UTC 
Created attachment 1069215 [details]
File: proc_pid_status
Comment 12 Kamil Páral 2015-09-01 21:28:51 UTC 
Created attachment 1069216 [details]
File: var_log_messages
Comment 13 Fedora End Of Life 2016-07-19 17:45:35 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.