Nautilus crashes when opening folders that contain files with js or json extensions

[Arash Farr]

After attempting to open a folder that contains js or json files the app crashes.
when testing from terminal I get a segmentation fault and no other error info.
even enabling G_MESSAGES_DEBUG=all did not provide additional info.
removing nautilus extensions, resetting xdg-mime for js/json, and disabling nautilus features (search, file count, etc ...) did not fix the problem either.

additional info
$ lsb_release -rd
Description: Ubuntu 22.04.3 LTS
Release: 22.04

$ apt-cache policy nautilus
nautilus:
  Installed: 1:42.6-0ubuntu1
  Candidate: 1:42.6-0ubuntu1
  Version table:
 *** 1:42.6-0ubuntu1 500
        500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     1:42.2-0ubuntu2.1 500
        500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
     1:42.0-1ubuntu2 500
        500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: nautilus 1:42.6-0ubuntu1
ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-39-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Dec 30 14:50:09 2023
InstallationDate: Installed on 2023-02-14 (319 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:
 evince 42.3-0ubuntu3.1
 file-roller 3.42.0-1
 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1
 nautilus-share 0.7.3-2ubuntu6

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:

1. Run these commands:
    journalctl -b0 > journal.txt
    journalctl -b-1 > prevjournal.txt
and attach the resulting text files here.

2. Look in /var/crash for crash files and if found run:
    ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

3. If step 2 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.

[Sebastien Bacher (seb128)]

Could you perhaps attach an example of file showing the issue?

[airtonix (airtonix-gmail)]

This isn't specific to ubuntu btw. it happens on Fedora 38 too.

so far i've found that any `.json` or `.js` file will cause any instance of the gnome filebrowser (nautilus, a file picker modal, etc) to crash itself and any app that uses it.

[Valentin Bersier (vbersier)]

I can confirm this happens to me too on a fresh install of Ubuntu 23.10. I specifically re-installed Ubuntu (I was on 22.04 LTS) because of the problem but it's still present.

[Paul Peregud (paulperegud)]

On my machine crash will occur if nautilus opens a directory containing a .json file (haven't experimented with .js) which is not empty. Files with trivial body, such as '""' or '"{}"' do trigger segfault. Empty (zero sized) .json files does not trigger segfault.

```
segfault at 7fed30041ff8 ip 00007fed50109bad sp 00007fed30042000 error 6 in libgio-2.0.so.0.7200.4[7fed50000000+111000] likely on CPU 6 (core 2, socket 0)
```

[Paul Peregud (paulperegud)]

/var/crash$ sudo cat _usr_bin_nautilus.1000.uploaded
07f47ab6-c1bc-11ee-9cd1-fa163ec44ecd

[Paul Peregud (paulperegud)]

According to Nautilus devs, the solution is bumping the library version: https://gitlab.gnome.org/GNOME/nautilus/-/issues/3273

[Sebastien Bacher (seb128)]

Thanks, that's a glib issue fixed upstream in 2.78.4 which isn't in Ubuntu yet