Bug 1047439 - [abrt] nautilus: PyObject_IsSubclass(): nautilus killed by SIGSEGV
Summary: [abrt] nautilus: PyObject_IsSubclass(): nautilus killed by SIGSEGV
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: nautilus
Version: 20
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:fbb763a2db4457eeee21ddfaef9...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-31 06:54 UTC by Steve Foster
Modified: 2015-06-29 13:58 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-29 13:58:48 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (40.28 KB, text/plain)
2013-12-31 06:54 UTC, Steve Foster
no flags Details
File: cgroup (172 bytes, text/plain)
2013-12-31 06:54 UTC, Steve Foster
no flags Details
File: core_backtrace (15.37 KB, text/plain)
2013-12-31 06:55 UTC, Steve Foster
no flags Details
File: dso_list (17.89 KB, text/plain)
2013-12-31 06:55 UTC, Steve Foster
no flags Details
File: environ (3.26 KB, text/plain)
2013-12-31 06:55 UTC, Steve Foster
no flags Details
File: exploitable (82 bytes, text/plain)
2013-12-31 06:55 UTC, Steve Foster
no flags Details
File: limits (1.29 KB, text/plain)
2013-12-31 06:55 UTC, Steve Foster
no flags Details
File: maps (83.74 KB, text/plain)
2013-12-31 06:55 UTC, Steve Foster
no flags Details
File: open_fds (1.50 KB, text/plain)
2013-12-31 06:55 UTC, Steve Foster
no flags Details
File: proc_pid_status (942 bytes, text/plain)
2013-12-31 06:55 UTC, Steve Foster
no flags Details
File: var_log_messages (2.96 KB, text/plain)
2013-12-31 06:55 UTC, Steve Foster
no flags Details

Description Steve Foster 2013-12-31 06:54:54 UTC
Description of problem:
trying to use other nautilus extensions in ."local/share/nautilus-python/extensions".  This causing the

$ nautilus
Initializing nautilus-open-terminal extension
Initializing nautilus-search-tool extension
ImportError: could not import gobject (could not find _PyGObject_API object)
Segmentation fault (core dumped)

Does not matter which extensions..  It just breaks nautilus, and prevents some of normal extensions
I use from functioning.   I consider the to be badly broken.

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

Additional info:
reporter:       libreport-2.1.10
backtrace_rating: 4
cmdline:        nautilus
crash_function: PyObject_IsSubclass
executable:     /usr/bin/nautilus
kernel:         3.12.5-302.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 PyObject_IsSubclass at /usr/src/debug/Python-2.7.5/Objects/abstract.c:3013
 #1 nautilus_python_load_file at nautilus-python.c:91
 #2 nautilus_python_load_dir at nautilus-python.c:149
 #3 nautilus_module_load at nautilus-module.c:116
 #4 g_type_module_use at gtypemodule.c:256
 #5 nautilus_module_load_file at nautilus-module.c:193
 #6 load_module_dir at nautilus-module.c:220
 #7 nautilus_module_setup at nautilus-module.c:250
 #8 nautilus_application_startup at nautilus-application.c:1601
 #9 _g_closure_invoke_va at gclosure.c:840

Comment 1 Steve Foster 2013-12-31 06:54:58 UTC
Created attachment 843623 [details]
File: backtrace

Comment 2 Steve Foster 2013-12-31 06:54:59 UTC
Created attachment 843624 [details]
File: cgroup

Comment 3 Steve Foster 2013-12-31 06:55:00 UTC
Created attachment 843625 [details]
File: core_backtrace

Comment 4 Steve Foster 2013-12-31 06:55:02 UTC
Created attachment 843626 [details]
File: dso_list

Comment 5 Steve Foster 2013-12-31 06:55:03 UTC
Created attachment 843627 [details]
File: environ

Comment 6 Steve Foster 2013-12-31 06:55:05 UTC
Created attachment 843628 [details]
File: exploitable

Comment 7 Steve Foster 2013-12-31 06:55:06 UTC
Created attachment 843629 [details]
File: limits

Comment 8 Steve Foster 2013-12-31 06:55:07 UTC
Created attachment 843630 [details]
File: maps

Comment 9 Steve Foster 2013-12-31 06:55:09 UTC
Created attachment 843631 [details]
File: open_fds

Comment 10 Steve Foster 2013-12-31 06:55:10 UTC
Created attachment 843632 [details]
File: proc_pid_status

Comment 11 Steve Foster 2013-12-31 06:55:12 UTC
Created attachment 843633 [details]
File: var_log_messages

Comment 12 Fedora End Of Life 2015-05-29 10:15:15 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 13 Fedora End Of Life 2015-06-29 13:58:48 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.


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