Page 1 of 1

[Solved] M8 Beta1-Gnome-terminal issue

PostPosted: Aug 14th, '20, 17:02
by Kosh
I am running Mageia8Beta1 (the Gnome-flavour) and since the update of Gnome and Gnomeshell + extentions to 3.37.90 last week, my regular Gnome-teminal won't start anymore.
journalctl -ab -tail 100 gives:

Code: Select all
aug 14 16:49:43 localhost systemd[2424]: Started Application launched by gnome-shell.
aug 14 16:49:43 localhost dbus-daemon[2452]: [session uid=1000 pid=2452] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.97' (uid=1000 pid=14479 comm="gnome-terminal")
aug 14 16:49:43 localhost systemd[2424]: Starting GNOME Terminal Server...
aug 14 16:49:43 localhost gnome-terminal-server[14483]: Unable to init server: Could not connect: Connection refused
aug 14 16:49:43 localhost gnome-terminal-server[14483]: Failed to parse arguments: Cannot open display:
aug 14 16:49:43 localhost systemd[2424]: gnome-terminal-server.service: Main process exited, code=exited, status=10/n/a
aug 14 16:49:43 localhost systemd[2424]: gnome-terminal-server.service: Failed with result 'exit-code'.
aug 14 16:49:43 localhost systemd[2424]: Failed to start GNOME Terminal Server.

Odd is that the connection gets refused?
Both packages gnome-terminal and gnome-terminal-nautilus have version 3.36.2 and seem to be lagging behind the core version 3.37.90. Could this be the cause of the troubles?

I am using LXTerminal now as a wokaround.

Re: M8 Beta1-Gnome-terminal issue

PostPosted: Aug 14th, '20, 23:50
by martinw
Once you update, you're no longer running beta1 ;-)
Cauldron is still fairly unstable, so expect occasional breakages. GNOME in particular is tracking the upstream beta releases for GNOME 3.38. The gnome-terminal issue was reported on the dev mailing list, so I would expect it to be fixed soon (if not already).

Re: M8 Beta1-Gnome-terminal issue

PostPosted: Aug 15th, '20, 16:16
by Kosh
Thank you for the info. Cheers!

Re: M8 Beta1-Gnome-terminal issue

PostPosted: Aug 31st, '20, 18:28
by Kosh
Since the update to v3.37.90 today, all seems ok again.