I get a segmentation fault when I open directories containing a non-empty json
file using file managers such as Caja, Nautilus and Thunar. GDB reports the
segfault is in libgio-2.0.so.0.

Debian version: 12.7, everything up to date

Possibly related:
https://gitlab.gnome.org/GNOME/glib/-/issues/3191
https://gitlab.gnome.org/GNOME/nautilus/-/issues/3273

After some more debugging, it turns out this happens only with certain
mime types, in my case those installed by homebrew.

So full steps to reproduce are:

- Install homebrew (https://brew.sh/)
- brew install shared-mime-info
- Ensure /home/linuxbrew/.linuxbrew/share is in $XDG_DATA_DIRS
- Run a file manager like Thunar and navigate to a directory with a
non-empty json file

Control: retitle -1 libglib2.0-0: segfault after installing shared-mime-info from Homebrew
Control: tags -1 + moreinfo

Does this happen for literally any JSON file (for example
`echo "{}" > object.json`) or does the JSON file that is required to
reproduce the crash have non-trivial contents?

Is there a single file or combination of files that reproduce this without
installing arbitrary software from outside Debian?

For example as a starting point you could try excluding
/home/linuxbrew/.linuxbrew/share from XDG_DATA_DIRS, and copying
some file installed by Homebrew (possibly
/home/linuxbrew/.linuxbrew/share/mime/packages/freedesktop.org.xml?)
into ~/.local/share/mime/packages?

If that probably-multi-megabyte XML file reproduces the crash, it would
also be very useful if you're able to narrow it down to some smaller part
of the file as the trigger for this crash. Extracting the MIME type
definitions for formats that match the glob *.json, like application/json
and application/schema+json, might be a good first step.

    smcv

Any non-empty file that ends in ".json" causes a segfault. It doesn't
even have to be valid json.

Yes! I've attached a minimal version of freedesktop.org.xml that causes
a segfault. It seems it has something to do with the interaction between
multiple mime-type definitions, since the problem goes away after
removing a single json or javascript related mime-type.

Best,

Lennart

Hi,

I get this segmentation fault when opening a NFS-Share with Nautilus
that contains any kind of file with .js or .json extension since my
system was updated on May 20 2025.

When I remove the files no crash happens.

I have found these bug-reports

  -https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2047737/comments/10
  -https://gitlab.gnome.org/GNOME/nautilus/-/issues/3273#note_1989525
  -https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2097496

and these bugs https://gitlab.gnome.org/GNOME/glib/-/issues/3601/
https://gitlab.gnome.org/GNOME/glib/-/issues/3191



Start-Date: 2025-05-20  19:47:25
Commandline: /usr/bin/unattended-upgrade
Upgrade: libglib2.0-dev-bin:amd64 (2.74.6-2+deb12u5, 2.74.6-2+deb12u6),
libglib2.0-bin:amd64 (2.74.6-2+deb12u5, 2.74.6-2+deb12u6),
libglib2.0-dev:amd64 (2.74.6-2+deb12u5, 2.74.6-2+deb12u6),
libglib2.0-data:amd64 (2.74.6-2+deb12u5, 2.74.6-2+deb12u6),
libglib2.0-0:amd64 (2.74.6-2+deb12u5, 2.74.6-2+deb12u6),
libglib2.0-0:i386 (2.74.6-2+deb12u5, 2.74.6-2+deb12u6)
End-Date: 2025-05-20  19:47:28


Debian 6.1.140-1 (2025-05-22) x86_64 GNU/Linux

Debian version: 12.11

libc6 Version: 2.36-9+deb12u10

libglib2.0-0:
   Installiert:           2.74.6-2+deb12u6
   Installationskandidat: 2.74.6-2+deb12u6
   Versionstabelle:
  *** 2.74.6-2+deb12u6 500
         500 http://deb.debian.org/debian bookworm/main amd64 Packages
         100 /var/lib/dpkg/status
      2.74.6-2+deb12u2 500
         500 http://deb.debian.org/debian-security
bookworm-security/main amd64 Packages