Bug 1222217

Summary: [abrt] nautilus: _g_log_abort(): nautilus killed by SIGTRAP
Product: [Fedora] Fedora Reporter: Mikhail <mikhail.v.gavrilov>
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, jan.public, mclasen
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/92dbe141aa2e227840168bf0fda2519d868d0b69
Whiteboard: abrt_hash:3772483f667d5a2a0f8d3a1cfce28a34e22461d9
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 14:07:17 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 Mikhail 2015-05-16 14:04:52 UTC 
Description of problem:
Nautilus crashed under wayland session

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

Additional info:
reporter:       libreport-2.5.1
backtrace_rating: 4
cmdline:        /usr/bin/nautilus --gapplication-service
crash_function: _g_log_abort
executable:     /usr/bin/nautilus
global_pid:     4045
kernel:         4.0.3-300.fc22.x86_64+debug
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (5 frames)
 #0 _g_log_abort at gmessages.c:315
 #3 gdk_event_source_prepare at gdkeventsource.c:55
 #4 g_main_context_prepare at gmain.c:3410
 #6 g_main_context_iteration at gmain.c:3869
 #7 g_application_run at gapplication.c:2308
Comment 1 Mikhail 2015-05-16 14:04:56 UTC 
Created attachment 1026245 [details]
File: backtrace
Comment 2 Mikhail 2015-05-16 14:04:57 UTC 
Created attachment 1026246 [details]
File: cgroup
Comment 3 Mikhail 2015-05-16 14:04:59 UTC 
Created attachment 1026247 [details]
File: core_backtrace
Comment 4 Mikhail 2015-05-16 14:05:00 UTC 
Created attachment 1026248 [details]
File: dso_list
Comment 5 Mikhail 2015-05-16 14:05:02 UTC 
Created attachment 1026249 [details]
File: environ
Comment 6 Mikhail 2015-05-16 14:05:03 UTC 
Created attachment 1026250 [details]
File: limits
Comment 7 Mikhail 2015-05-16 14:05:06 UTC 
Created attachment 1026251 [details]
File: maps
Comment 8 Mikhail 2015-05-16 14:05:07 UTC 
Created attachment 1026252 [details]
File: mountinfo
Comment 9 Mikhail 2015-05-16 14:05:09 UTC 
Created attachment 1026253 [details]
File: namespaces
Comment 10 Mikhail 2015-05-16 14:05:10 UTC 
Created attachment 1026254 [details]
File: open_fds
Comment 11 Mikhail 2015-05-16 14:05:11 UTC 
Created attachment 1026255 [details]
File: proc_pid_status
Comment 12 Mikhail 2015-05-16 14:05:13 UTC 
Created attachment 1026256 [details]
File: var_log_messages
Comment 13 Mikhail 2015-05-30 12:31:32 UTC 
Another user experienced a similar problem:

just try connect to sftp share

reporter:       libreport-2.5.1
backtrace_rating: 4
cmdline:        /usr/bin/nautilus --gapplication-service
crash_function: _g_log_abort
executable:     /usr/bin/nautilus
global_pid:     3272
kernel:         4.0.4-301.fc22.i686
package:        nautilus-3.16.2-1.fc22
reason:         nautilus killed by SIGTRAP
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 14 Fedora End Of Life 2016-07-19 14:07:17 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.