I'm assuming this is the
gnome-terminal started from your cronjob.
There is absolutely no need to run the cronjob scripts inside
gnome-terminal. Doing so would mean that the jobs would fail if
gnome-terminal could not be opened (which would probably happen if you weren't using the desktop at the time).
0 0,6,12,18 * * * "$HOME"/bin/updates.sh
0 0,6,12,18 * * * "$HOME"/bin/rclone.sh
Any output from the scripts will be emailed to you, assuming local email delivery was enabled. To save the output to a log file, use a redirection:
0 0,6,12,18 * * * "$HOME"/bin/updates.sh >>"$HOME"/updates.log"
0 0,6,12,18 * * * "$HOME"/bin/rclone.sh >>"$HOME"/rclone.log"
The environment that the cronjobs are running in is different from the one you usually have when logged in through a graphical desktop environment. For one thing, your default shell may not be set in the
SHELL environment variable, which is why
/bin/sh instead of
bash on your system, but runs in POSIX compatibility mode when invoked as
When logged in on the graphical desktop environment, opening
gnome-terminal as usual would give you your default shell. If it doesn't, it's because there's a
gnome-terminal-server process running which was started by the cron jobs. Terminate this process by either rebooting or by using
pkill -f gnome-terminal-server.
See also the comment posted by JdeBP below.