3

I use a machine remotely on which several people have remote access. One of them messed around with the Python versions, installed a newer version maybe, not exactly sure. Assume I have no access to him. Now, the main pythonic thing I'm using on that machine is running meld - a python utility for diff'ing and merging files.

For a while, meld wasn't running at all. Then that other user fixed/changed things again, and meld now works. However - it's taking > 20 seconds to start (!)

After startup, meld is quite responsive, so it's not networking issues AFAICT.

How can I determine what causes this startup delay?

Notes:

  • I'm not an expert in Python.
  • The Linux distribution is SLES 15.
  • I can become root if necessary.
einpoklum
  • 10,666

3 Answers3

5

I experience this very slow start of meld on a headless Debian 11 server accessed through SSH with -X forwarding enabled.

The problem seems to be described in this bug report: https://gitlab.gnome.org/GNOME/meld/-/issues/484

Not sure if your problem is the same, but the suggested solution or workaround seems to work for me. Before using Meld, start

dbus-launch --exit-with-session /bin/bash
mivk
  • 4,015
1

Starting without DBUS helps:

$ DBUS_SESSION_BUS_ADDRESS= meld
mmm
  • 11
0

The advice from the other answer (https://superuser.com/a/1729262/21952) didn't work for me on Debian bookworm. I suspect this has something to do with changes in DBus.

For some reason, the following commands helped. I'm not sure what the side-effects are; I hope somebody will share a better workaround:

sudo apt remove dbus-user-session
sudo apt install dbus-x11

I got the idea from reading apt info dbus-user-session.

user21952-is-a-great-name
  • 209