Unknown gedit fstab failure

Recently I entered;

sudo gedit /etc/fstab

In responce I got,

(gedit:66385): dconf-WARNING **: 22:49:56.775: failed to commit changes to dconf: Failed to execute child process “dbus-launch” (No such file or directory)

(gedit:66385): dconf-WARNING **: 22:49:56.778: failed to commit changes to dconf: Failed to execute child process “dbus-launch” (No such file or directory)

(gedit:66385): dconf-WARNING **: 22:49:56.890: failed to commit changes to dconf: Failed to execute child process “dbus-launch” (No such file or directory)

(gedit:66385): dconf-WARNING **: 22:49:56.890: failed to commit changes to dconf: Failed to execute child process “dbus-launch” (No such file or directory)

(gedit:66385): dconf-WARNING **: 22:49:56.890: failed to commit changes to dconf: Failed to execute child process “dbus-launch” (No such file or directory)

** (gedit:66385): WARNING **: 08:22:33.104: Set document metadata failed: Setting attribute metadata::gedit-position not supported

(gedit:66385): dconf-WARNING **: 08:22:33.113: failed to commit changes to dconf: Failed to execute child process “dbus-launch” (No such file or directory)*

Only physical change to machine, since I last used successfully, is shifting my home folder to an SSD drive partition. An effort to save data should my system melt down.

Should this have affected this or is it something else. New install of Ubuntu 22.04 fully updated, upgraded & refreshed.

Casual observation is that I have noticed some latency in apps opening and cursor responses even text highlighting delays till after I release the mouse button.

Looking for avenues to investigate as to cause of fstab edit?

Cheers

Virtual novice, Brucie...

In your ~/.bashrc, add

export EDITOR=$(type -p gedit)
export VISUAL=$(type -p gedit)

Then, source .bashrc.

Now, you can sudoedit /etc/fstab. Read man sudoedit.

Here's what sudoedit does:

1. Authenticate the user (like sudo).
2. As root make a temporary copy of the file, that the user can edit.
3. As the user, invoke $VISUAL to edit the temporary file.
4. When the editor exits, if the file was changed, as root, sudoedit copies the temporary file back to target file.

I've successfully used sudoedit with emacsclient, vim, vi, nano, and ed as the $VISUAL.