Bug 1494009 - [abrt] nautilus: gtk_stack_set_visible_child_name(): nautilus killed by SIGSEGV
Summary: [abrt] nautilus: gtk_stack_set_visible_child_name(): nautilus killed by SIGSEGV
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: nautilus
Version: 27
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:b4506ec3ac12ab2dd322a993f1f...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-09-21 10:14 UTC by František Zatloukal
Modified: 2018-11-30 23:15 UTC (History)
15 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-30 23:15:01 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (74.52 KB, text/plain)
2017-09-21 10:14 UTC, František Zatloukal
no flags Details
File: cgroup (321 bytes, text/plain)
2017-09-21 10:14 UTC, František Zatloukal
no flags Details
File: core_backtrace (53.17 KB, text/plain)
2017-09-21 10:14 UTC, František Zatloukal
no flags Details
File: cpuinfo (1.43 KB, text/plain)
2017-09-21 10:14 UTC, František Zatloukal
no flags Details
File: dso_list (14.25 KB, text/plain)
2017-09-21 10:14 UTC, František Zatloukal
no flags Details
File: environ (1.76 KB, text/plain)
2017-09-21 10:14 UTC, František Zatloukal
no flags Details
File: exploitable (95 bytes, text/plain)
2017-09-21 10:14 UTC, František Zatloukal
no flags Details
File: limits (1.29 KB, text/plain)
2017-09-21 10:14 UTC, František Zatloukal
no flags Details
File: maps (70.37 KB, text/plain)
2017-09-21 10:14 UTC, František Zatloukal
no flags Details
File: open_fds (8.98 KB, text/plain)
2017-09-21 10:14 UTC, František Zatloukal
no flags Details
File: proc_pid_status (1.27 KB, text/plain)
2017-09-21 10:14 UTC, František Zatloukal
no flags Details
File: var_log_messages (317 bytes, text/plain)
2017-09-21 10:14 UTC, František Zatloukal
no flags Details

Description František Zatloukal 2017-09-21 10:14:23 UTC
Description of problem:
Connected to a new SMB folder. Nautilus crashed immidiately after.

Version-Release number of selected component:
nautilus-3.26.0-1.fc27

Additional info:
reporter:       libreport-2.9.2
backtrace_rating: 4
cmdline:        /usr/bin/nautilus --gapplication-service
crash_function: gtk_stack_set_visible_child_name
executable:     /usr/bin/nautilus
journald_cursor: s=81b349ce73f246a4b99690d4d4bc1201;i=47253;b=34866086c9b1411ea95fa48c5e8391e5;m=2a3c52e86;t=559b04dd7c801;x=8b43fc5da43a3594
kernel:         4.13.2-300.fc27.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 gtk_stack_set_visible_child_name at gtkstack.c:1839
 #1 populate_servers at ../src/gtk/nautilusgtkplacesview.c:534
 #2 ffi_call_unix64 at ../src/x86/unix64.S:76
 #3 ffi_call at ../src/x86/ffi64.c:525
 #4 g_cclosure_marshal_generic_va at gclosure.c:1604
 #5 _g_closure_invoke_va at gclosure.c:867
 #8 g_file_monitor_emit_event at gfilemonitor.c:290
 #9 g_file_monitor_source_dispatch at glocalfilemonitor.c:546
 #13 g_main_context_iteration at gmain.c:3947
 #14 g_application_run at gapplication.c:2401

Potential duplicate: bug 1427446

Comment 1 František Zatloukal 2017-09-21 10:14:32 UTC
Created attachment 1328897 [details]
File: backtrace

Comment 2 František Zatloukal 2017-09-21 10:14:34 UTC
Created attachment 1328898 [details]
File: cgroup

Comment 3 František Zatloukal 2017-09-21 10:14:36 UTC
Created attachment 1328899 [details]
File: core_backtrace

Comment 4 František Zatloukal 2017-09-21 10:14:38 UTC
Created attachment 1328900 [details]
File: cpuinfo

Comment 5 František Zatloukal 2017-09-21 10:14:39 UTC
Created attachment 1328901 [details]
File: dso_list

Comment 6 František Zatloukal 2017-09-21 10:14:41 UTC
Created attachment 1328902 [details]
File: environ

Comment 7 František Zatloukal 2017-09-21 10:14:43 UTC
Created attachment 1328903 [details]
File: exploitable

Comment 8 František Zatloukal 2017-09-21 10:14:44 UTC
Created attachment 1328904 [details]
File: limits

Comment 9 František Zatloukal 2017-09-21 10:14:46 UTC
Created attachment 1328905 [details]
File: maps

Comment 10 František Zatloukal 2017-09-21 10:14:48 UTC
Created attachment 1328906 [details]
File: open_fds

Comment 11 František Zatloukal 2017-09-21 10:14:50 UTC
Created attachment 1328907 [details]
File: proc_pid_status

Comment 12 František Zatloukal 2017-09-21 10:14:51 UTC
Created attachment 1328908 [details]
File: var_log_messages

Comment 13 Chris Murphy 2017-11-28 04:26:15 UTC
Similar problem has been detected:

Try to connect to a Samba server.

Reproduce steps:
 Files > + Other Locations > enter address for server > Connect > authenticate

Crash.

reporter:       libreport-2.9.3
backtrace_rating: 4
cmdline:        /usr/bin/nautilus --gapplication-service
crash_function: gtk_stack_set_visible_child_name
executable:     /usr/bin/nautilus
journald_cursor: s=cee91d8fbaeb4d609042fda49f6dd4c8;i=9cd;b=fda679c9f029478f86dd744e96200875;m=58f0f192;t=55eefd1edccf3;x=f5cc857d6329710c
kernel:         4.13.15-300.fc27.x86_64
package:        nautilus-3.26.2-1.fc27
reason:         nautilus killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 14 Patrick Truebe 2018-01-02 16:00:34 UTC
Similar problem has been detected:

Connect to smb share via direct URL. Was at "Other Locations". Credentials already saved in Keychain.

reporter:       libreport-2.9.3
backtrace_rating: 4
cmdline:        /usr/bin/nautilus --gapplication-service
crash_function: gtk_stack_set_visible_child_name
executable:     /usr/bin/nautilus
journald_cursor: s=c0b37bf3f08b43b095630d2f73f982dc;i=2fe22;b=ff75a070eb7d41999b933263af2e5e51;m=8f15f20ec;t=561cd187668fd;x=6e0fee5f0426ed1a
kernel:         4.14.8-300.fc27.x86_64
package:        nautilus-3.26.2-1.fc27
reason:         nautilus killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 15 John Webb 2018-01-20 23:45:34 UTC
Similar problem has been detected:

I was attempting to attach to a samba server running on my dd-wrt router using the nautilus "+Other Locations" and then the dropdown for smb://192.168.12.2/.

reporter:       libreport-2.9.3
backtrace_rating: 4
cmdline:        /usr/bin/nautilus --gapplication-service
crash_function: gtk_stack_set_visible_child_name
executable:     /usr/bin/nautilus
journald_cursor: s=709c14232fd7421093abf5d0ef48971b;i=c9262;b=5c0719427dc941f6916f7f1c80c88450;m=3f42a5c632;t=5633d9f408897;x=49c354f9b4838be6
kernel:         4.14.13-300.fc27.x86_64
package:        nautilus-3.26.2-1.fc27
reason:         nautilus killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 16 Mike 2018-01-22 22:00:36 UTC
Similar problem has been detected:

I was attempting to make a "remote connection" with the Nautilus "Files" application. I was typing in:  sftp://mharris.23.123/

reporter:       libreport-2.9.3
backtrace_rating: 4
cmdline:        /usr/bin/nautilus --gapplication-service
crash_function: gtk_stack_set_visible_child_name
executable:     /usr/bin/nautilus
journald_cursor: s=2c80261c1b1b472b8a3a709e9edb1fe5;i=56de;b=6d546c8f13484c108f8ad240abaf83d1;m=4c36920c65;t=563647db0d99b;x=eef00bac68de6fe6
kernel:         4.14.13-300.fc27.x86_64
package:        nautilus-3.26.2-1.fc27
reason:         nautilus killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 17 汪明衡 2018-02-08 12:39:33 UTC
Similar problem has been detected:

I ran server ultimate pro ftp on my android phone, and used nautilus to connect to it. Nautilus first reported http proxy error of some sort, though seemed not reasonable, I did use privoxy as system-wide http/https proxy. It crashed on second successful attempt.

reporter:       libreport-2.9.3
backtrace_rating: 4
cmdline:        /usr/bin/nautilus --gapplication-service
crash_function: gtk_stack_set_visible_child_name
executable:     /usr/bin/nautilus
journald_cursor: s=56e2032653ab41a595b4d84d21865877;i=65ffb;b=cf7b536e0fab427aa989d38e282c7a28;m=c19afdc;t=564b294ac899b;x=bfa1b5c5ac1f1670
kernel:         4.14.16-300.fc27.x86_64
package:        nautilus-3.26.2-1.fc27
reason:         nautilus killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 18 Mike 2018-03-08 19:24:47 UTC
Similar problem has been detected:

Was launching the "files" application, chose the option to open a new tab, and then was attempting to connect, via sftp to another system in my home.

reporter:       libreport-2.9.3
backtrace_rating: 4
cmdline:        /usr/bin/nautilus --gapplication-service
crash_function: gtk_stack_set_visible_child_name
executable:     /usr/bin/nautilus
journald_cursor: s=360a8d294bc44bab99c92106182c6685;i=6ee71;b=fb0c2b75031a4d839c42059808836282;m=17143a3c2b;t=566eb9419c667;x=4e7c838c09fd9986
kernel:         4.15.6-300.fc27.x86_64
package:        nautilus-3.26.2-1.fc27
reason:         nautilus killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 19 Mike 2018-10-14 03:37:54 UTC
Similar problem has been detected:

Was making an sftp connection to another host to share files.

reporter:       libreport-2.9.3
backtrace_rating: 4
cmdline:        /usr/bin/nautilus --gapplication-service
crash_function: gtk_stack_set_visible_child_name
executable:     /usr/bin/nautilus
journald_cursor: s=5cf68896667a4d388e93dcd66158e912;i=155bf95;b=972659c6447a4b67ae916cf4dd917f46;m=12351f5989;t=5782797749aaa;x=2c25f9393803f1ae
kernel:         4.18.12-100.fc27.x86_64
package:        nautilus-3.26.3.1-1.fc27
reason:         nautilus killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 20 Ben Cotton 2018-11-27 14:01:52 UTC
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora  'version' of '27'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 27 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 21 Ben Cotton 2018-11-30 23:15:01 UTC
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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.


Note You need to log in before you can comment on or make changes to this bug.