Bug 1076791

Summary: [abrt] nautilus: new_threadstate(): nautilus killed by SIGSEGV
Product: [Fedora] Fedora Reporter: francesco.segato
Component: nautilusAssignee: Matthias Clasen <mclasen>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: ccecchi, francesco.segato, lswoo89, mclasen, vedran
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/f5d8b210c6391b7468905e23fcc014224bdd1ec0
Whiteboard: abrt_hash:ed2e3d196f9c3771deabe210f40858905a2913fb
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 19:29:12 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: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description francesco.segato 2014-03-15 08:20:02 UTC 
Description of problem:
lanciato "File" appena aviiato il computer

Version-Release number of selected component:
nautilus-3.10.1-3.fc20

Additional info:
reporter:       libreport-2.2.0
backtrace_rating: 4
cmdline:        nautilus --new-window /home/casa/Scaricati
crash_function: new_threadstate
executable:     /usr/bin/nautilus
kernel:         3.13.5-202.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (6 frames)
 #0 new_threadstate at /usr/src/debug/Python-2.7.5/Python/pystate.c:202
 #1 PyThreadState_New at /usr/src/debug/Python-2.7.5/Python/pystate.c:213
 #2 PyGILState_Ensure at /usr/src/debug/Python-2.7.5/Python/pystate.c:600
 #3 _filter_message at ../../_dbus_bindings/conn-methods.c:142
 #9 g_main_context_iteration at gmain.c:3774
 #10 g_application_run at gapplication.c:1635
Comment 1 francesco.segato 2014-03-15 08:20:07 UTC 
Created attachment 874721 [details]
File: backtrace
Comment 2 francesco.segato 2014-03-15 08:20:10 UTC 
Created attachment 874722 [details]
File: cgroup
Comment 3 francesco.segato 2014-03-15 08:20:12 UTC 
Created attachment 874723 [details]
File: core_backtrace
Comment 4 francesco.segato 2014-03-15 08:20:15 UTC 
Created attachment 874724 [details]
File: dso_list
Comment 5 francesco.segato 2014-03-15 08:20:17 UTC 
Created attachment 874725 [details]
File: environ
Comment 6 francesco.segato 2014-03-15 08:20:20 UTC 
Created attachment 874726 [details]
File: exploitable
Comment 7 francesco.segato 2014-03-15 08:20:22 UTC 
Created attachment 874727 [details]
File: limits
Comment 8 francesco.segato 2014-03-15 08:20:26 UTC 
Created attachment 874728 [details]
File: maps
Comment 9 francesco.segato 2014-03-15 08:20:28 UTC 
Created attachment 874729 [details]
File: open_fds
Comment 10 francesco.segato 2014-03-15 08:20:30 UTC 
Created attachment 874730 [details]
File: proc_pid_status
Comment 11 francesco.segato 2014-03-15 08:20:32 UTC 
Created attachment 874731 [details]
File: var_log_messages
Comment 12 francesco.segato 2014-03-15 08:24:23 UTC 
Description of problem in English:
I have run "File" as soon as the computer was switched on and ready to work
Comment 13 Fedora End Of Life 2015-05-29 11:15:38 UTC 
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 '20'.

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 20 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 Fedora End Of Life 2015-06-29 19:29:12 UTC 
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.
Comment 15 Vedran Miletić 2018-11-02 10:05:40 UTC 
I get crashes in nautilus in Fedora 29. ABRT says backtrace is unusable, but points to this bug as a duplicate.
Comment 16 Vedran Miletić 2018-11-03 11:30:35 UTC 
Nevermind, I finally managed to report the record an usable backtrace and report it as bug 1645751.