I'm seeing the same. 

I have tried the newer version from gnome:factory but I still get segmentation fault.

Created attachment 867653 [details]
gdb backtrace of crash

I see the same. Managed to get a gdb backtrace in case that helps.

The latest TW update has broken Nautilus on my laptop. I get this error:
** Message: 11:06:40.235: Connecting to org.freedesktop.Tracker3.Miner.Files
fish: Job 1, 'nautilus' terminated by signal SIGSEGV (Address boundary error)

I had the same error since I've updated on Jun 16th

Current version:
NAME="openSUSE Tumbleweed"
# VERSION="20230616"
ID="opensuse-tumbleweed"
ID_LIKE="opensuse suse"
VERSION_ID="20230616"
PRETTY_NAME="openSUSE Tumbleweed"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:tumbleweed:20230616"
BUG_REPORT_URL="https://bugzilla.opensuse.org"
SUPPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://www.opensuse.org"
DOCUMENTATION_URL="https://en.opensuse.org/Portal:Tumbleweed"
LOGO="distributor-logo-Tumbleweed"

I managed to resolve this issue by removing: nautilus-extension-tilix
Once that nautilus extension has been removed from my system, I can start nautilus again

(In reply to Harald van Bree from comment #4)
> I had the same error since I've updated on Jun 16th
> 
> Current version:
> NAME="openSUSE Tumbleweed"
> # VERSION="20230616"
> ID="opensuse-tumbleweed"
> ID_LIKE="opensuse suse"
> VERSION_ID="20230616"
> PRETTY_NAME="openSUSE Tumbleweed"
> ANSI_COLOR="0;32"
> CPE_NAME="cpe:/o:opensuse:tumbleweed:20230616"
> BUG_REPORT_URL="https://bugzilla.opensuse.org"
> SUPPORT_URL="https://bugs.opensuse.org"
> HOME_URL="https://www.opensuse.org"
> DOCUMENTATION_URL="https://en.opensuse.org/Portal:Tumbleweed"
> LOGO="distributor-logo-Tumbleweed"
> 
> I managed to resolve this issue by removing: nautilus-extension-tilix
> Once that nautilus extension has been removed from my system, I can start
> nautilus again

Thank you. Solved

(In reply to Harald van Bree from comment #4)
> 
> I managed to resolve this issue by removing: nautilus-extension-tilix
> Once that nautilus extension has been removed from my system, I can start
> nautilus again

Does not work for me, unfortunately. Removed all nautilus extensions, but still no luck.

Also, for the problem is not solved this way. On a fresh installation of openSUSE the problem does not exist even with nautilus-extension-tilix installed. So there must be conflict with something.

Also, this is not connected with user specific extension. The same problem on a new created user

I first tried to simply reinstall tilix and the extension, but that did not help. Right now I also have to remove the extension.

(In reply to Stefan Sauer from comment #9)
> I first tried to simply reinstall tilix and the extension, but that did not
> help. Right now I also have to remove the extension.

Seems that any python-nautilus extension currently causes nautilus to crash. It could be the tilix extension, or as in my case nautilus-gsconnect.py installed to ~/.local/share/nautilus-python/extension/. Deleting all extensions installed to that latter dir, alongside using zypper to uninstall nautilus-extension-* helped nautilus start in my case.

Indeed after getting it to start, just copy pasting the TestExtension.py example [1] to ~/.local/share/nautilus-python/extension/ will once again cause nautilus to crash. Here is the debugging output on terminal:


> ~> NAUTILUS_PYTHON_DEBUG=misc nautilus                                                                                                             > ** Message: 22:19:26.177: Connecting to org.freedesktop.Tracker3.Miner.Files
> nautilus_module_initialize: entered
> nautilus_python_load_dir: entered dirname=/home/badshah/.local/share/nautilus-python/extensions
> nautilus-python:g_module_open /usr/lib64/libpython3.11.so.1.0
> nautilus-python:Py_Initialize
> nautilus-python:PySys_SetArgv
> nautilus-python:Sanitize the python search path
> nautilus-python:init_pygobject
> Segmentation fault (core dumped)

[1] https://gitlab.gnome.org/GNOME/nautilus-python/-/blob/master/examples/TestExtension.py

I had the same issue, and I confirm that comment#4 solved the issue.

on my end I had to remove all Python extensions - which is a real bummer as they are among the core features I use on Nautilus on a daily basis (titlix, gsconnect and sublimetext extensions).
This seems to have appeared with a bump to Python 3.11 .

A different solution, which has less impact on the user is to remove/block
  libpython3_11-1_0-x86-64-v3
for the time being. 

Seems either python gets mis-optimized on v3 hardware or nautilus does something weird there.

But with this removed from the system, nautilus can be used with python extensions.

Assigning to python as component

(In reply to Dominique Leuenberger from comment #13)
> A different solution, which has less impact on the user is to remove/block
>   libpython3_11-1_0-x86-64-v3
> for the time being. 
> 
> Seems either python gets mis-optimized on v3 hardware or nautilus does
> something weird there.
> 
> But with this removed from the system, nautilus can be used with python
> extensions.
> 

Many thanks. I can confirm that that works very well.

I had to remove nautilus-extension-nextcloud to get nautilus running again.

(In reply to Johannes Weberhofer from comment #15)
> I had to remove nautilus-extension-nextcloud to get nautilus running again.

Even with libpython3_11-1_0-x86-64-v3 uninstalled? I also had to get rid of nautilus-extension-nextcloud, but with libpython3_11-1_0-x86-64-v3 now out my system, I have installed it back and it works.

(In reply to Atri Bhattacharya from comment #16)
> (In reply to Johannes Weberhofer from comment #15)
> > I had to remove nautilus-extension-nextcloud to get nautilus running again.
> 
> Even with libpython3_11-1_0-x86-64-v3 uninstalled? I also had to get rid of
> nautilus-extension-nextcloud, but with libpython3_11-1_0-x86-64-v3 now out
> my system, I have installed it back and it works.

I have libpython3_11-1_0 and libpython3_11-1_0-x86-64-v3 installed and only removed nautilus-extension-nextcloud.

The only extensions left are nautilus-extension-seahorse and nautilus-extension-terminal (didn't install much)

(In reply to Johannes Weberhofer from comment #17)
> 
> I have libpython3_11-1_0 and libpython3_11-1_0-x86-64-v3 installed and only
> removed nautilus-extension-nextcloud.
> 
> The only extensions left are nautilus-extension-seahorse and
> nautilus-extension-terminal (didn't install much)

No, please see comment 13; the bug is in libpython3_11-1_0-x86-64-v3. Remove that package and you can install back all your necessary nautilus-extension-* packages without a problem.

Confirmed. Uninstalling libpython3_11-1_0-x86-64-v3 solves the problem

(In reply to Atri Bhattacharya from comment #18)
> (In reply to Johannes Weberhofer from comment #17)
> > 
> > I have libpython3_11-1_0 and libpython3_11-1_0-x86-64-v3 installed and only
> > removed nautilus-extension-nextcloud.
> > 
> > The only extensions left are nautilus-extension-seahorse and
> > nautilus-extension-terminal (didn't install much)
> 
> No, please see comment 13; the bug is in libpython3_11-1_0-x86-64-v3. Remove
> that package and you can install back all your necessary
> nautilus-extension-* packages without a problem.

I've now done that and it works. Thanks!

Also for me removing libpython3_11-1_0-x86-64-v3 resolves the issue.

This solution also worked for me.

I've been debugging and trying different approximations to detect what's happening here and I've discovered something. Looks like the python-nautilus extension looks for the libpython.so [1] in the default libdir and is using a different version from the loaded v3.

I've tested building with the PYTHON_LIBPATH pointing to the v3 and in that case it works. Now I just need to patch to make it sure that it picks the correct version depending on the installed libpython.

[1] https://gitlab.gnome.org/GNOME/nautilus-python/-/blob/master/src/nautilus-python.c#L158

This patch fixes the issue [1]. I'm not sure if it's the best solution, but at least this works for me, with and without the libpython3_11-1_0-x86-64-v3 installed.

[1] https://build.opensuse.org/request/show/1096629

This simplest patch also fixes the issue in TW:

https://build.opensuse.org/request/show/1096798

There's also a discussion happening upstream about it, and as far as I can tell, this fix will be problematic with using a python interpreter different from the system python, that's something that I think doesn't affect the TW package.

https://gitlab.gnome.org/GNOME/nautilus-python/-/issues/21#note_1783240

*** Bug 1212482 has been marked as a duplicate of this bug. ***

Fix published in TW