Fedora Account System
Red Hat Associate
Red Hat Customer
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
Created attachment 1026245 [details] File: backtrace
Created attachment 1026246 [details] File: cgroup
Created attachment 1026247 [details] File: core_backtrace
Created attachment 1026248 [details] File: dso_list
Created attachment 1026249 [details] File: environ
Created attachment 1026250 [details] File: limits
Created attachment 1026251 [details] File: maps
Created attachment 1026252 [details] File: mountinfo
Created attachment 1026253 [details] File: namespaces
Created attachment 1026254 [details] File: open_fds
Created attachment 1026255 [details] File: proc_pid_status
Created attachment 1026256 [details] File: var_log_messages
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
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.