Version-Release number of selected component: nautilus-3.6.3-4.fc18 Additional info: backtrace_rating: 4 cmdline: nautilus computer:// crash_function: pygobject_new_full executable: /usr/bin/nautilus kernel: 3.7.2-201.fc18.x86_64 remote_result: 740998 uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #4 pygobject_new_full at pygobject.c:990 #5 _pygi_marshal_to_py_interface_object at pygi-marshal-to-py.c:893 #6 _invoke_marshal_out_args at pygi-invoke.c:547 #7 pygi_callable_info_invoke at pygi-invoke.c:661 #8 ext_do_call at /usr/src/debug/Python-2.7.3/Python/ceval.c:4408 #9 PyEval_EvalFrameEx at /usr/src/debug/Python-2.7.3/Python/ceval.c:2779 #10 PyEval_EvalCodeEx at /usr/src/debug/Python-2.7.3/Python/ceval.c:3330 #11 fast_function at /usr/src/debug/Python-2.7.3/Python/ceval.c:4194 #12 call_function at /usr/src/debug/Python-2.7.3/Python/ceval.c:4119 #13 PyEval_EvalFrameEx at /usr/src/debug/Python-2.7.3/Python/ceval.c:2740
Created attachment 682995 [details] File: backtrace
Created attachment 682996 [details] File: cgroup
Created attachment 682997 [details] File: core_backtrace
Created attachment 682998 [details] File: dso_list
Created attachment 682999 [details] File: environ
Created attachment 683000 [details] File: limits
Created attachment 683001 [details] File: maps
Created attachment 683002 [details] File: open_fds
Created attachment 683003 [details] File: proc_pid_status
Created attachment 683004 [details] File: var_log_messages
I've juste removed nautilus and all its extensions and then reinstall nautilus and its minimal dependencies: now nautilus dosn't crash. Let's have a look extensions now...
Removing tortoisehg-nautilus solved this problem for me.
I can also confirm removing tortoisehg-nautilus allows nautilus to run as expected. Additional debug info: Before removing tortoisehg-nautilus-2.6.2-1, I ran nautilus from a terminal: ** (nautilus:4318): WARNING **: Can't load fallback CSS resource: Failed to import: The resource at '/org/gnome/adwaita/gtk-fallback.css' does not exist /usr/lib64/python2.7/site-packages/gobject/constants.py:24: Warning: g_boxed_type_register_static: assertion `g_type_from_name (name) == 0' failed import gobject._gobject Traceback (most recent call last): File "/usr/share/nautilus-python/extensions/postrExtension.py", line 21, in <module> import gobject, nautilus ImportError: No module named nautilus TypeError: metaclass conflict: the metaclass of a derived class must be a (non-strict) subclass of the metaclasses of all its bases ** ERROR:pygobject.c:990:pygobject_new_full: assertion failed: (tp != NULL) Aborted (core dumped) I uppdated to nautilus-3.6.3-5 and nautilus-extensions-3.6.3-5 without removing tortoisehg-nautilus-2.6.2-1 and reran nautilus from a terminal: ** (nautilus:3423): WARNING **: Can't load fallback CSS resource: Failed to import: The resource at '/org/gnome/adwaita/gtk-fallback.css' does not exist /usr/lib64/python2.7/site-packages/gobject/constants.py:24: Warning: g_boxed_type_register_static: assertion `g_type_from_name (name) == 0' failed import gobject._gobject Traceback (most recent call last): File "/usr/share/nautilus-python/extensions/postrExtension.py", line 21, in <module> import gobject, nautilus ImportError: No module named nautilus TypeError: metaclass conflict: the metaclass of a derived class must be a (non-strict) subclass of the metaclasses of all its bases ** ERROR:pygobject.c:990:pygobject_new_full: assertion failed: (tp != NULL) Aborted (core dumped)
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.