Bug 1569711

Summary: [abrt] nautilus: nautilus_window_slot_get_location(): nautilus killed by SIGABRT
Product: [Fedora] Fedora Reporter: Theodor van Nahl <theodor+rh>
Component: nautilusAssignee: Matthias Clasen <mclasen>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 28CC: alexl, cosimo.cecchi, john.j5live, mclasen, mlinchits, rhughes, sandmann
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/a304c8945fdac1f9bd23323b418aba0b8aa0441f
Whiteboard: abrt_hash:bf9ca82c4f9d70ebf7dcddedf86cfb91ae20843e;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-05-28 22:03:07 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: cpuinfo
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status none

Description Theodor van Nahl 2018-04-19 21:08:40 UTC 
Description of problem:
I tried to "star" a folder within my home directory. Since that didn't work previously I've reset tracker using `tracker reset -e` and started this new nautilus.

Version-Release number of selected component:
nautilus-3.28.1-1.fc28

Additional info:
reporter:       libreport-2.9.4
backtrace_rating: 4
cmdline:        /usr/bin/nautilus --gapplication-service
crash_function: nautilus_window_slot_get_location
executable:     /usr/bin/nautilus
journald_cursor: s=623735e0352a48cba93ebc8f7b950d26;i=1e200;b=729c1c0eab5e4e3e91fcb61f53a8d09d;m=10a02af2d;t=56a39d610b567;x=f3794a6823a5984a
kernel:         4.16.2-300.fc28.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (2 frames)
 #4 nautilus_window_slot_get_location at ../src/nautilus-window-slot.c:2942
 #5 nautilus_window_on_undo_changed at ../src/nautilus-window.c:1864
Comment 1 Theodor van Nahl 2018-04-19 21:08:47 UTC 
Created attachment 1424293 [details]
File: backtrace
Comment 2 Theodor van Nahl 2018-04-19 21:08:48 UTC 
Created attachment 1424294 [details]
File: cgroup
Comment 3 Theodor van Nahl 2018-04-19 21:08:50 UTC 
Created attachment 1424295 [details]
File: core_backtrace
Comment 4 Theodor van Nahl 2018-04-19 21:08:51 UTC 
Created attachment 1424296 [details]
File: cpuinfo
Comment 5 Theodor van Nahl 2018-04-19 21:08:53 UTC 
Created attachment 1424297 [details]
File: dso_list
Comment 6 Theodor van Nahl 2018-04-19 21:08:54 UTC 
Created attachment 1424298 [details]
File: environ
Comment 7 Theodor van Nahl 2018-04-19 21:08:56 UTC 
Created attachment 1424299 [details]
File: limits
Comment 8 Theodor van Nahl 2018-04-19 21:08:58 UTC 
Created attachment 1424300 [details]
File: maps
Comment 9 Theodor van Nahl 2018-04-19 21:08:59 UTC 
Created attachment 1424301 [details]
File: mountinfo
Comment 10 Theodor van Nahl 2018-04-19 21:09:01 UTC 
Created attachment 1424302 [details]
File: open_fds
Comment 11 Theodor van Nahl 2018-04-19 21:09:02 UTC 
Created attachment 1424303 [details]
File: proc_pid_status
Comment 12 piglist 2018-08-05 06:16:34 UTC 
Similar problem has been detected:

I was setting some preferences - namely enabling context menu option to enable symplic creation.

reporter:       libreport-2.9.5
backtrace_rating: 4
cmdline:        /usr/bin/nautilus --gapplication-service
crash_function: nautilus_window_slot_get_location
executable:     /usr/bin/nautilus
journald_cursor: s=5e053fec5ef845efa805df98b7159cf4;i=16054;b=f91b0bc05dd54e4586693eb54389a55e;m=7e736ced2d;t=572a9efd3e639;x=f7ff5213629b0fef
kernel:         4.17.7-200.fc28.x86_64
package:        nautilus-3.28.1-1.fc28
reason:         nautilus killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 13 Ben Cotton 2019-05-02 21:12:02 UTC 
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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 '28'.

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 28 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 14 Ben Cotton 2019-05-28 22:03:07 UTC 
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.