Bug 1634434

Summary: [abrt] nautilus: g_strfreev(): nautilus killed by SIGABRT
Product: [Fedora] Fedora Reporter: Baptiste Mille-Mathias <baptiste.millemathias>
Component: nautilusAssignee: Matthias Clasen <mclasen>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 29CC: 9jYqEjAGii7bauq6tAFv, AboveTrain448+redhat, adriano.svieira, alexl, burni, cosimo.cecchi, john.j5live, kparal, mclasen, rhughes, sandmann, twaugh
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/c25030e0e2de85513d8a3b296d51714d2d4b5ad1
Whiteboard: abrt_hash:34f46888f8d899a3eba678c2b1f466e4a5cf7122;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-27 22:06:02 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 Baptiste Mille-Mathias 2018-09-30 18:05:07 UTC
Description of problem:
crash at session start

Version-Release number of selected component:
nautilus-3.30.0-2.fc29

Additional info:
reporter:       libreport-2.9.5
backtrace_rating: 4
cmdline:        /usr/bin/nautilus --gapplication-service
crash_function: g_strfreev
executable:     /usr/bin/nautilus
journald_cursor: s=8b6ad8041a7b4d16a522d6f4a180c7d8;i=6d88e1;b=864f51943034425ea4342e856a7b6d9e;m=315bf38bc;t=5771a7282f03e;x=4300cae85eedcd4f
kernel:         4.18.10-300.fc29.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 1 Baptiste Mille-Mathias 2018-09-30 18:05:14 UTC
Created attachment 1488655 [details]
File: backtrace

Comment 2 Baptiste Mille-Mathias 2018-09-30 18:05:15 UTC
Created attachment 1488656 [details]
File: cgroup

Comment 3 Baptiste Mille-Mathias 2018-09-30 18:05:18 UTC
Created attachment 1488657 [details]
File: core_backtrace

Comment 4 Baptiste Mille-Mathias 2018-09-30 18:05:19 UTC
Created attachment 1488658 [details]
File: cpuinfo

Comment 5 Baptiste Mille-Mathias 2018-09-30 18:05:21 UTC
Created attachment 1488659 [details]
File: dso_list

Comment 6 Baptiste Mille-Mathias 2018-09-30 18:05:23 UTC
Created attachment 1488660 [details]
File: environ

Comment 7 Baptiste Mille-Mathias 2018-09-30 18:05:25 UTC
Created attachment 1488661 [details]
File: limits

Comment 8 Baptiste Mille-Mathias 2018-09-30 18:05:27 UTC
Created attachment 1488662 [details]
File: maps

Comment 9 Baptiste Mille-Mathias 2018-09-30 18:05:29 UTC
Created attachment 1488663 [details]
File: mountinfo

Comment 10 Baptiste Mille-Mathias 2018-09-30 18:05:31 UTC
Created attachment 1488664 [details]
File: open_fds

Comment 11 Baptiste Mille-Mathias 2018-09-30 18:05:32 UTC
Created attachment 1488665 [details]
File: proc_pid_status

Comment 12 Sebastian 2018-10-04 14:42:09 UTC
Similar problem has been detected:

I typed "disk" into the search bar, Filelight was found, so i opened it to have a look at the screenshot what the program looks like. And then, this crash appeared.

reporter:       libreport-2.9.5
backtrace_rating: 4
cmdline:        /usr/bin/nautilus --gapplication-service
crash_function: g_strfreev
executable:     /usr/bin/nautilus
journald_cursor: s=dbd035a0e9904f1d94daf1d549aab192;i=3b14;b=74bd1b6e79f142bcb49fa2e247ecbc02;m=7f40f8ff;t=57767cfb8e005;x=f3d8f1d5c99c34d3
kernel:         4.19.0-0.rc4.git4.1.vanilla.knurd.1.fc29.x86_64
package:        nautilus-3.30.0-2.fc29
reason:         nautilus killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 13 9jYqEjAGii7bauq6tAFv 2019-01-02 08:56:40 UTC
*** Bug 1662860 has been marked as a duplicate of this bug. ***

Comment 14 Kamil Páral 2019-04-07 06:39:54 UTC
Similar problem has been detected:

Searching for files

reporter:       libreport-2.10.0
backtrace_rating: 4
cmdline:        /usr/bin/nautilus --gapplication-service
crash_function: g_strfreev
executable:     /usr/bin/nautilus
journald_cursor: s=ec7c300726e249ea832d448b66a4cd3e;i=1da59;b=d7491555876841cb9729ffda0eec9aa6;m=8eb5d83;t=585eaf01523e4;x=c94f6f55cfbf87b
kernel:         5.0.6-200.fc29.x86_64
package:        nautilus-3.30.5-1.fc29
reason:         nautilus killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 15 Adriano Vieira 2019-04-24 02:58:03 UTC
*** Bug 1702523 has been marked as a duplicate of this bug. ***

Comment 16 Ben Cotton 2019-10-31 19:34:03 UTC
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
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 '29'.

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 29 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 17 Ben Cotton 2019-11-27 22:06:02 UTC
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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.