Error constructing proxy for org gnome terminal

Remember how Windows applications mainly worked back in the Win16 days before Win32 came along and did away with it: where there were hInstance and hPrevInstance, attempting to run a second instance of many applications simply handed things over to the first instance, and this made things difficult for command scripting tools (like Take Command) because one would invoke an application a second time, it would visibly be there on the screen as an added window, but as far as the command interpreter was concerned the child process that it had just run immediately exited?

Well GNOME has brought the Win16 behaviour back for Linux.

GNOME Terminal is now a client-server application. The gnome-terminal program is just a client that constructs Desktop Bus messages to a server, passing along its command line options, environment, working directory, and arguments, and then simply exiting. The server is gnome-terminal-server which registers as org.gnome.Terminal on the Desktop Bus and which is responsible for all of the actual terminal emulation and displaying the window(s) on the GUI(s).

A Desktop Bus client like gnome-terminal locates the Desktop Bus broker via an environment variable, which usually points to socket in a per-user directory such as /run/user/1001. Alternatively, the environment variable specifies to look in «the current user’s runtime directory» and a path similar to the aforementioned is constructed from the client process’s effective user ID. This directory in either case is conventionally private to the individual user, and inaccessible to other (unprivileged) users.

Hilarity ensues when people attempt to run gnome-terminal as another user via sudo and suchlike. If the environment variable points to an explicitly-named runtime directory, an unprivileged client cannot connect to the per-user Desktop Bus. If the environment variable points to «the current user’s» runtime directory, it looks for the wrong Desktop Bus broker, often the one for a user that does not currently have a Desktop Bus broker running because the user has not logged in and started up that user account’s per-user services. (Per-user Desktop Bus brokers are run by a per-user service manager. The per-user service manager is either started explicitly or, in the case of some service management softwares, by some rather ugly hooks into the user authentication process employed by the likes of the login, su, and SSH server programs.)

The reason that dbus-launch worked for you as the superuser is that dbus-launch explicitly launched another Desktop Bus broker, running as the superuser, which gnome-terminal was able to talk to. Luckily, the system was also configured to demand-start the gnome-terminal-server server when the client attempted to connect to it via the broker. (This is not necessarily the case, and nowadays such demand-starting is seen as an inferior mechanism as it ends up with lots of Desktop Bus server processes that aren’t running under any kind of service management. Indeed, not having the broker itself under service management is considered inferior too. It’s also generally not considered a good idea for the superuser account to have these sorts of services running, as many of them do not expect to be running with superuser privileges because they expect to be running under the aegides of ordinary user accounts.)

Further hilarity ensuses if, as the questioner at «How can I launch gnome-terminal remotely on my headless server? (fails to launch over X11 forwarding)» does, people attempt to run gnome-terminal when even the original user does not have a Desktop Bus broker running. This happens when, for example, one has logged in via SSH but the SSH login process does not start up the per-user service manager, which in turn means that the per-user Desktop Bus broker is not run, and the gnome-terminal-server server cannot be reached over a Desktop Bus. (According to how the system is configured, graphical login could still trigger starting the per-user service manager, and hence one might observe that logging in graphically as the same user magically makes things work. And again dbus-launch would explicitly start a non-service-managed Desktop Bus broker.)

Yet more hilarity ensues when one has one of the service managers that has the hooks into login, su, and the SSH server. These hooks usually implement the semantics of starting up per-user service management, and all of the per-user services that it starts, at first log-on for that user; and stopping them all at last log-off for that user. If one has a lot of short-lived and non-overlapping SSH sessions, then there can be a lot of overhead generated uselessly starting up and shutting down the entire per-user service management system (and all of its auto-start services) at the starts and ends of each of those SSH sessions. systemd, one such service manager, has an imperfect «linger» mechanism that only really half addresses this. It means that per-user service management «lingers» after the final log-off, but it does not stop the per-user service management from being started at all.

Further reading

• Jonathan de Boyne Pollard (2016). /run/user/jim/dbus. «Gazetteer». nosh Guide. Softwares. jdebp.eu.
• Jonathan de Boyne Pollard (2016). «per-user user services». nosh Guide. Softwares. jdebp.eu.
• Run true multiple process instances of gnome-terminal
• Make user systemd service persistent
• https://unix.stackexchange.com/a/323700/5132

Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0

Всем добра.

Проблема в том, что иногда так случается( зависимости от каких либо действий я не обнаружил) что gnome terminal отказывается запускаться, при попытке запустить из другого терминала вылезает ошибка

org.gnome.Terminal.desktop[3794]: Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Ошибка вызова StartServiceByName для org.gnome.Terminal: Время ожидания истекло

От руда все запускается. Также все гномовские приложения переводятся с русского на английский язык.

Решения проблемы, которые есть в гугле, о всевозможных манипуляциях с локалями мне не помогли. Единственное что есть это запуск gnome-terminala из другого терминала командой dbus-launch gnome-terminal тогда он стартует. Хотелось бы полноценного решения.

# 6 лет, 4 месяца назад (отредактировано 6 лет, 4 месяца назад)

Смотрел, dbus-launch в принципе помогает, но если запускать так терминал то спамит кучу dbus сервисов. Хотелось бы более полноценного решения.
И ошибка у него другая.

Да и запуск без GDM, через exec dbus-launch gnome-session в xinitrc тоже не помогает, только что проверил.

Jeka76rus
Да и запуск без GDM, через exec dbus-launch gnome-session в xinitrc тоже не помогает, только что проверил.

Jeka76rus
Да и запуск без GDM, через exec dbus-launch gnome-session в xinitrc тоже не помогает, только что проверил.

А я только писал, хотел об этом спросить .
В указанной мной ссылке на BBS имеется еще ссылка на bug, связанный с dbus и gnome-terminal …. в подробности правда не вдавлся .

Иногда отпускает если выполнить dbus-update-activation-environment —all в другом терминале.

Jeka76rus
Тоже видел. Решение для себя там не нашел, в английском не достаточно силен.

# 6 лет, 4 месяца назад (отредактировано 6 лет, 4 месяца назад)

Jeka76rus
Тоже видел. Решение для себя там не нашел, в английском не достаточно силен.

Там мусолят несколько вариантов, но, по-моему, представляют интерес для проверки следующие два варианта
Второй вариант ты и используешь в другом терминале. Ближе к концу встретилось, что это вроде бы можно прописать на постоянку.
А вот 1-ый вариант для startx и дальше идет вопрос «Как это использовать» и ответ, что конкретно нужно добавить в .xinitrc
Можешь попробовать …
UPD …. и предлагается еще одно … и там даже есть ссылка на нашу Wiki .

Источник

Arch Linux

You are not logged in.

#1 2018-11-25 06:18:33

gnome-terminal Error constructing proxy for org.gnome.Terminal

hello guys, i cant launch the terminal.. i read in the forums that it might be cause of my locale.
i ran:

my locale.conf has

The error when i launch gnome-terminal is :

Last edited by InvisibleRasta (2018-11-25 06:46:27)

#2 2018-11-25 06:32:52

Re: gnome-terminal Error constructing proxy for org.gnome.Terminal

Registered Linux User #482438

#3 2018-11-25 06:46:42

Re: gnome-terminal Error constructing proxy for org.gnome.Terminal

i think i did set it up properly

#4 2018-11-25 06:47:24

Re: gnome-terminal Error constructing proxy for org.gnome.Terminal

Not according to your original locale output.

Registered Linux User #482438

#5 2018-11-25 06:51:25

Re: gnome-terminal Error constructing proxy for org.gnome.Terminal

gnome terminal doesnt start up anyways. still the same error

Last edited by InvisibleRasta (2018-11-25 07:05:33)

#6 2019-01-23 08:15:43

Re: gnome-terminal Error constructing proxy for org.gnome.Terminal

gnome terminal doesnt start up anyways. still the same error

Hello.
I have had the same exact problem. I tried every different technique until I found this one:

This command will almost certainly almost always work to open gnome-terminal. I also installed slim-unicode instead of slim, but I don’t know if I had any effect on the problem. (I was desperate to have a running station today, I did not have time to fine-tune my solution.)

(I love being able to use the Primary and the Clipboard systems with gnome-terminal, this is why I use it.)

Last edited by nucleos (2019-01-23 08:16:57)

Источник

How do I report a bug, or request a new feature?

Since version 3.7, for new terminals to start in the working directory of the current terminal, it is necessary for the shell running in the terminal to cooperate. For this, vte since version 0.34.5 installs a /etc/profile.d/vte.sh script that when sourced will set this up automatically. It supports both bash(1) and zsh(1).

Some distributions (e.g. Fedora) source that script automatically for all interactive shells. Other distributions may only source it automatically for login shells, so you need to either source it manually from

/.bashrc, or check the «Run command as a login shell» checkbox on the «Command» tab in the profile preferences dialogue. For more information see this bug report.

Note that on bash(1), this feature relies on the PROMPT_COMMAND variable. The vte.sh script sets it automatically; if you want to make modifications to it, you need to make them after sourcing vte.sh, and only append to it instead of overwriting it completely.

Previous versions of vte required you to change your PS1 prompt yourself; this is no longer required.

Since version 3.7 this option has been moved from the per-profile preferences to the global Preferences dialogue.

How can I make middle-click paste the primary selection?

In GNOME versions since 3.9, pasting the primary selection with a middle click is disabled by default. To re-enable it (for all programmes, not just for gnome-terminal), create the file

/.config/gtk-3.0/settings.ini with these contents:

Or you can just use gnome-tweak-tool, which exposes this setting as a check box.

How can I change a profile setting from the command line?

First you need to find out the identifier of the profile you want to change. Open the Preferences dialogue, switch to the Profile tab, select the profile you want to change, and click Edit. The identifier is the string labelled «Profile ID». You don’t need to type it; you can simply right-click it, choose Select all, then right-click again, choose Copy; now you can paste into the terminal using Ctrl-Shift-V or right click, Paste.

Alternatively, if you want to change all profiles, you can use this command to get the list of all profile identifiers:

and this command to get the identifier of the default profile:

For each profile you want to change, replace the string UUID with the profile identifier in the command below:

For example values for the default profile can be changed like this:

Unfortunately, the gsettings tool can’t currently autocomplete the key names with relocatable schemas (that’s this bug), but you can just read the schema itself.

How can I stop the cursor from blinking?

You can disable the cursor blinking for all programmes by running this command:

However GNOME Terminal also has a setting of its own to en- or disable cursor blinking for each profile separately. Use the instructions above to change the cursor-blink-mode key; the allowed values are system (the default) to follow the global setting, and on or off to enable or disable blinking regardless of the global setting.

For example, disabling cursor blinking for the default profile can be done with this one-liner:

Since version 3.7 this option has been removed from the Preferences dialogue. You can however still get the same effect by adding the following lines to your

You will need to close all terminal windows for this change to take effect.

How can I make the terminal transparent?

Since version 3.7 this option has been removed from the Preferences dialogue. You can however still get the same effect by setting the _NET_WM_WINDOW_OPACITY X property, for example with the Devil’s Pie or Devil’s Pie II tools. E.g., set up Devil’s Pie to start automatically with the session, and create the file

/.devilspie/gnome-terminal.ds with these contents:

You can also use this shell script that however only works for existing terminal windows and not automatically for newly created ones.

Terminal fails to start

When gnome-terminal-server fails to start, it may print information about the problem. You can retrieve that information from the journal:

Also, the gnome-terminal client prints some information, that notably may contain the exit status of the server programme. (Note that since version 3.14.0, the exit status gives some information about the cause of the problem. Prior versions always exited with status 1. Exit status 9 or 10 only is reported since version 3.18.)

Exit status 7

Starting Terminal fails with this error message:

Reason: You are trying to run gnome-terminal with su, sudo or some similar mechanism. You cannot do so. Instead, run su, sudo, etc., inside the terminal. E.g.

Exit status 8

Starting Terminal fails with this error message:

Reason: The environment that gnome-terminal-server is started with does not correctly set the locale to a UTF-8 locale. Consult your distribution’s documentation on how to fix this. Note that is it not relevant to check the locale settings from a different terminal (e.g. xterm); what counts is the environment that the systemd —user instance passes to the processes it starts.

Exit status 9

Starting Terminal fails with this error message:

Reason: The locale settings in the environment that gnome-terminal-server is started with describe a nonexistent locale. Consult your distribution’s documentation on how to fix this. Note that is it not relevant to check the locale settings from a different terminal (e.g. xterm); what counts is the environment that the systemd —user instance passes to the processes it starts.

Exit status 10

Starting Terminal fails with this error message:

Reason: gtk_init() failed. The most likely cause is that the connection to the display could not be opened, for example because the environment that gnome-terminal-server is started with lacks a DISPLAY setting. Consult your distribution’s documentation on how to fix this. Note that is it not relevant to check the environment from a different terminal (e.g. xterm); what counts is the environment that the systemd —user instance passes to the processes it starts.

Apps/Terminal/FAQ (last edited 2022-05-29 08:23:49 by ChPe )

Источник

Thread: Can no longer run gnome-terminal

Thread Tools

Display

Can no longer run gnome-terminal

I suddenly began having this problem when I try to run gnome-terminal, I can’t figure out what caused this:

$ gnome-terminal
Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling StartServiceByName for org.gnome.Terminal: Timeout was reached
main19@system19:

This causes gnome—terminal not to start.

I have tried looking online, everyone says it is a locale problem, here is my locale output:

$ locale
LANG=en_US.UTF-8
LANGUAGE=
LC_CTYPE=»en_US.UTF-8″
LC_NUMERIC=»en_US.UTF-8″
LC_TIME=»en_US.UTF-8″
LC_COLLATE=»en_US.UTF-8″
LC_MONETARY=»en_US.UTF-8″
LC_MESSAGES=»en_US.UTF-8″
LC_PAPER=»en_US.UTF-8″
LC_NAME=»en_US.UTF-8″
LC_ADDRESS=»en_US.UTF-8″
LC_TELEPHONE=»en_US.UTF-8″
LC_MEASUREMENT=»en_US.UTF-8″
LC_IDENTIFICATION=»en_US.UTF-8″
LC_ALL=
main19@system19:

I have run out of ideas, if anyone can provide help with this that would be great.

Re: Can no longer run gnome-terminal

I haven’t seen that one in the terminal. Have you tried purging and reinstalling?

Re: Can no longer run gnome-terminal

I haven’t seen that one in the terminal. Have you tried purging and reinstalling?

I have done that. no improvement, still the exact same problem.

Re: Can no longer run gnome-terminal

Like you, my searches point to locale being the problem.

Re: Can no longer run gnome-terminal

Could you make keyboard shortcuts with

and give them a try?

Re: Can no longer run gnome-terminal

I am sorry to say this, but. I don’t know what you’re asking me to do. «Keyboard shortcuts» are what exactly?

Re: Can no longer run gnome-terminal

I ended up refreshing my HOME directory, that solved this problem.

Re: Can no longer run gnome-terminal

Ubuntu 17.10 (xorg), gnome 3.26.2.

I suddenly began having this problem when I try to run gnome-terminal, I can’t figure out what caused this:

$ gnome-terminal
Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling StartServiceByName for org.gnome.Terminal: Timeout was reached
main19@system19:

This causes gnome—terminal not to start.

I have tried looking online, everyone says it is a locale problem, here is my locale output:

$ locale
LANG=en_US.UTF-8
LANGUAGE=
LC_CTYPE=»en_US.UTF-8″
LC_NUMERIC=»en_US.UTF-8″
LC_TIME=»en_US.UTF-8″
LC_COLLATE=»en_US.UTF-8″
LC_MONETARY=»en_US.UTF-8″
LC_MESSAGES=»en_US.UTF-8″
LC_PAPER=»en_US.UTF-8″
LC_NAME=»en_US.UTF-8″
LC_ADDRESS=»en_US.UTF-8″
LC_TELEPHONE=»en_US.UTF-8″
LC_MEASUREMENT=»en_US.UTF-8″
LC_IDENTIFICATION=»en_US.UTF-8″
LC_ALL=
main19@system19:

I have run out of ideas, if anyone can provide help with this that would be great.

Источник

Поймал странную проблему после обновления debian (что то с gnome)

Сижу на debian testing

Обновился сегодня. и вдруг внезапно поотпадывали кое-какие gnome проги.

Например gnome-terminal не запускается, пишет

Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Ошибка вызова StartServiceByName для org.gnome.Terminal: Время ожидания истекло

в тоже время dbus-launch gnome-terminal

Дайте намёк, что это такое поломано.

Перемещено leave из general

Боже, сраный терминал через дубас?! Они там совсем поехавшие в редхате?

Боже, сраный терминал через дубас?! Они там совсем поехавшие в редхате?

Ээ. после того, как systemd стал работать через DBust, почему бы через него не работать и терминалу?

Действительно, чего это я. А вот в ядро то что хотят запихнуть — это в т.ч. для терминала и прочего юзерспейса делают?

так это gnome-terminal

Для юзерспейса, конечно. Говорят, есть car infotainment быдлософт, который передает по DBust гигабайты. Походу, ради него и пилится.

Пойду, пожалуй, напьюсь и забудусь тяжелым сном.

Ретроград и прогрессофоб!

Вангую что такая „странная” проблема после апдейта не последняя, поэтому посоветую перекатиться с говнома на что-то более вменяемое с более адекватными разрабами.

Не терминал, а эмулятор терминала. И не просто эмулятор терминала, а часть единого DE. Безотносительно выполняемой программой задачи, это графическая программа, интегрированная в набор других графических и не очень программ, общающихся между собой по унифицированному способу IPC. Не скажу за gnome-terminal, гномом лет пятнадцать не пользуюсь (так, иногда ставлю на посмотреть), но konsole пару раз в скриптах переводил через dbus в полноэкранный режим, а есть ведь ещё всякие манипуляции с закладками и прочая работа с ним именно, как с эмулятором, а не терминалом.

Источник

GNOME Terminal Frequently Asked Questions

Please read through these common questions and answers before emailing the mailing list, asking on IRC or filing a bug report.

How do I report a bug, or request a new feature?

Look at these detailed instructions.

How can I make new terminals start in the working directory of the current terminal?

Since version 3.7, for new terminals to start in the working directory of the current terminal, it is necessary for the shell running in the terminal to cooperate. For this, vte since version 0.34.5 installs a /etc/profile.d/vte.sh script that when sourced will set this up automatically. It supports both bash(1) and zsh(1).

Some distributions (e.g. Fedora) source that script automatically for all interactive shells. Other distributions may only source it automatically for login shells, so you need to either source it manually from ~/.bashrc, or check the «Run command as a login shell» checkbox on the «Command» tab in the profile preferences dialogue. For more information see this bug report.

Note that on bash(1), this feature relies on the PROMPT_COMMAND variable. The vte.sh script sets it automatically; if you want to make modifications to it, you need to make them after sourcing vte.sh, and only append to it instead of overwriting it completely.

Previous versions of vte required you to change your PS1 prompt yourself; this is no longer required.

Since version 3.7 this option has been moved from the per-profile preferences to the global Preferences dialogue.

How can I make middle-click paste the primary selection?

In GNOME versions since 3.9, pasting the primary selection with a middle click is disabled by default. To re-enable it (for all programmes, not just for gnome-terminal), create the file ~/.config/gtk-3.0/settings.ini with these contents:

[Settings]
gtk-enable-primary-paste=true

Or you can just use gnome-tweak-tool, which exposes this setting as a check box.

How can I change a profile setting from the command line?

First you need to find out the identifier of the profile you want to change. Open the Preferences dialogue, switch to the Profile tab, select the profile you want to change, and click Edit. The identifier is the string labelled «Profile ID». You don’t need to type it; you can simply right-click it, choose Select all, then right-click again, choose Copy; now you can paste into the terminal using Ctrl-Shift-V or right click, Paste.

Alternatively, if you want to change all profiles, you can use this command to get the list of all profile identifiers:

gsettings get org.gnome.Terminal.ProfilesList list

and this command to get the identifier of the default profile:

gsettings get org.gnome.Terminal.ProfilesList default

For each profile you want to change, replace the string UUID with the profile identifier in the command below:

gsettings set org.gnome.Terminal.Legacy.Profile:/org/gnome/terminal/legacy/profiles:/:UUID/ KEY VALUE

For example values for the default profile can be changed like this:

UUID=$(gsettings get org.gnome.Terminal.ProfilesList default | tr -d ')
gsettings set org.gnome.Terminal.Legacy.Profile:/org/gnome/terminal/legacy/profiles:/:${UUID}/ KEY VALUE

Unfortunately, the gsettings tool can’t currently autocomplete the key names with relocatable schemas (that’s this bug), but you can just read the schema itself.

How can I stop the cursor from blinking?

You can disable the cursor blinking for all programmes by running this command:

gsettings set org.gnome.desktop.interface cursor-blink false

However GNOME Terminal also has a setting of its own to en- or disable cursor blinking for each profile separately. Use the instructions above to change the cursor-blink-mode key; the allowed values are system (the default) to follow the global setting, and on or off to enable or disable blinking regardless of the global setting.

For example, disabling cursor blinking for the default profile can be done with this one-liner:

gsettings set org.gnome.Terminal.Legacy.Profile:/org/gnome/terminal/legacy/profiles:/:$(gsettings get org.gnome.Terminal.ProfilesList default | tr -d ')/ cursor-blink-mode off

Since version 3.7 this option has been removed from the Preferences dialogue. You can however still get the same effect by adding the following lines to your ~/.config/gtk-3.0/gtk.css file:

terminal-screen-container {
 -TerminalScreenContainer-window-placement: bottom-right;
 -TerminalScreenContainer-window-placement-set: true;
}

You will need to close all terminal windows for this change to take effect.

How can I make the terminal transparent?

Since version 3.7 this option has been removed from the Preferences dialogue. You can however still get the same effect by setting the _NET_WM_WINDOW_OPACITY X property, for example with the Devil’s Pie or Devil’s Pie II tools. E.g., set up Devil’s Pie to start automatically with the session, and create the file ~/.devilspie/gnome-terminal.ds with these contents:

(if
  (matches (window_name) "gnome-terminal-window-*")
  (opacity 90)
)

You can also use this shell script that however only works for existing terminal windows and not automatically for newly created ones.

Terminal fails to start

When gnome-terminal-server fails to start, it may print information about the problem. You can retrieve that information from the journal:

$ journalctl _EXE=/usr/libexec/gnome-terminal-server

Also, the gnome-terminal client prints some information, that notably may contain the exit status of the server programme. (Note that since version 3.14.0, the exit status gives some information about the cause of the problem. Prior versions always exited with status 1. Exit status 9 or 10 only is reported since version 3.18.)

Exit status 7

Starting Terminal fails with this error message:

Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling StartServiceByName for org.gnome.Terminal: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.Terminal exited with status 7

Reason: You are trying to run gnome-terminal with su, sudo or some similar mechanism. You cannot do so. Instead, run su, sudo, etc., inside the terminal. E.g.

gnome-terminal -- su ...

Exit status 8

Starting Terminal fails with this error message:

Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling StartServiceByName for org.gnome.Terminal: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.Terminal exited with status 8

Reason: The environment that gnome-terminal-server is started with does not correctly set the locale to a UTF-8 locale. Consult your distribution’s documentation on how to fix this. Note that is it not relevant to check the locale settings from a different terminal (e.g. xterm); what counts is the environment that the systemd —user instance passes to the processes it starts.

Exit status 9

Starting Terminal fails with this error message:

Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling StartServiceByName for org.gnome.Terminal: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.Terminal exited with status 9

Reason: The locale settings in the environment that gnome-terminal-server is started with describe a nonexistent locale. Consult your distribution’s documentation on how to fix this. Note that is it not relevant to check the locale settings from a different terminal (e.g. xterm); what counts is the environment that the systemd —user instance passes to the processes it starts.

Exit status 10

Starting Terminal fails with this error message:

Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling StartServiceByName for org.gnome.Terminal: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.Terminal exited with status 10

Reason: gtk_init() failed. The most likely cause is that the connection to the display could not be opened, for example because the environment that gnome-terminal-server is started with lacks a DISPLAY setting. Consult your distribution’s documentation on how to fix this. Note that is it not relevant to check the environment from a different terminal (e.g. xterm); what counts is the environment that the systemd —user instance passes to the processes it starts.