Bug 1039856

Summary: [abrt] nautilus-3.11.2-1.fc21: _g_log_abort: Process /usr/bin/nautilus was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Alexander <nireus>
Component: nautilusAssignee: Matthias Clasen <mclasen>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: cam.avarley, ccecchi, hotmusicfan, kenshin936, marmarosi.jozsef, mclasen, namyrb, vicsiol
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/b86f740378664a413bdc7a44511473373cb478bc
Whiteboard: abrt_hash:338b7886dfa96a3334b8decd8f7a76af86260c0e
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 10:46:45 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: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Alexander 2013-12-10 07:59:09 UTC 
Version-Release number of selected component:
nautilus-3.11.2-1.fc21

Additional info:
reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        nautilus
crash_function: _g_log_abort
executable:     /usr/bin/nautilus
kernel:         3.13.0-0.rc2.git5.1.fc21.x86_64
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 _g_log_abort at gmessages.c:281
 #5 nautilus_window_get_slots at nautilus-window.c:2096
 #6 get_window_slot_for_location at nautilus-application.c:571
 #7 open_windows at nautilus-application.c:641
 #8 nautilus_application_open at nautilus-application.c:706
 #9 ffi_call_unix64 at ../src/x86/unix64.S:76
 #10 ffi_call at ../src/x86/ffi64.c:522
 #11 g_cclosure_marshal_generic_va at gclosure.c:1550
 #12 _g_closure_invoke_va at gclosure.c:840
 #15 g_application_open at gapplication.c:1466
Comment 1 Alexander 2013-12-10 07:59:18 UTC 
Created attachment 834652 [details]
File: backtrace
Comment 2 Alexander 2013-12-10 07:59:20 UTC 
Created attachment 834653 [details]
File: cgroup
Comment 3 Alexander 2013-12-10 07:59:24 UTC 
Created attachment 834654 [details]
File: core_backtrace
Comment 4 Alexander 2013-12-10 07:59:27 UTC 
Created attachment 834655 [details]
File: dso_list
Comment 5 Alexander 2013-12-10 07:59:29 UTC 
Created attachment 834656 [details]
File: environ
Comment 6 Alexander 2013-12-10 07:59:32 UTC 
Created attachment 834657 [details]
File: limits
Comment 7 Alexander 2013-12-10 07:59:35 UTC 
Created attachment 834658 [details]
File: maps
Comment 8 Alexander 2013-12-10 07:59:37 UTC 
Created attachment 834659 [details]
File: open_fds
Comment 9 Alexander 2013-12-10 07:59:39 UTC 
Created attachment 834660 [details]
File: proc_pid_status
Comment 10 Alexander 2013-12-10 07:59:42 UTC 
Created attachment 834661 [details]
File: var_log_messages
Comment 11 Jaroslav Reznik 2015-03-03 15:19:07 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Comment 12 Fedora End Of Life 2016-07-19 10:46:45 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.