Trace/breakpoint trap (core dumped) after update to 22.04

[Ainar Garipov]

After updating to 22.04 recently, this command has stopped working:

  $ git difftool --tool=meld -y HEAD~1
  Viewing (1/15): 'file.txt'
  Launch 'meld' [Y/n]? y
  Trace/breakpoint trap (core dumped)
  fatal: external diff died, stopping at file.txt

I've already tried both reinstalling `meld` with `--reinstall` as well as removing it with `--purge` and `--auto-remove` and installing again. No use.

I've also tried to launch `meld` from the console, but it's breaking as well:

  $ meld ./file1.txt ./file2.txt
  Trace/breakpoint trap (core dumped)

Weirdly enough, it seems to be launching fine from the GUI, but that's not what I need. I need to use it with `git difftool`.

System info:

  $ lsb_release -d -r
  Description: Ubuntu 22.04.1 LTS
  Release: 22.04

  $ apt-cache policy meld
  meld:
    Installed: 3.20.4-2
    Candidate: 3.20.4-2
    Version table:
   *** 3.20.4-2 500
          500 http://mirror.yandex.ru/ubuntu jammy/universe amd64 Packages
          500 http://mirror.yandex.ru/ubuntu jammy/universe i386 Packages
          100 /var/lib/dpkg/status

  $ apt-cache policy git
  git:
    Installed: 1:2.34.1-1ubuntu1.5
    Candidate: 1:2.34.1-1ubuntu1.5
    Version table:
   *** 1:2.34.1-1ubuntu1.5 500
          500 http://mirror.yandex.ru/ubuntu jammy-updates/main amd64 Packages
          500 http://mirror.yandex.ru/ubuntu jammy-security/main amd64 Packages
          100 /var/lib/dpkg/status
       1:2.34.1-1ubuntu1 500
          500 http://mirror.yandex.ru/ubuntu jammy/main amd64 Packages

[Launchpad Janitor (janitor)]

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

[Decker (devdecker)]

I had a similar bug with Ubuntu 22.04.1 LTS (jammy) after I attempted to build and install meld from the GitLab repository. I removed all experiments / attempts and installed meld with `sudo apt install meld`, which caused an error "Trace/breakpoint trap (core dumped)". Further investigation led me to a back trace log:

#0 0x00007f0c22c95cef in g_log_structured_array () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1 0x00007f0c22c95fb9 in g_log_default_handler () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x00007f0c22c9741a in g_logv () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x00007f0c22c97703 in g_log () at /lib/x86_64-linux-gnu/libglib-2.0.so.0

I eventually fixed the problem when I searched the file system for all files containing `org.gnome.meld`:

- /usr/local/share/glib-2.0/schemas/gschemas.compiled
- /usr/local/share/icons/hicolor/icon-theme.cache
- /usr/local/share/applications/mimeinfo.cache

and removed them. The error was gone.