* Egmont Koblinger <email address hidden>:
> > change to that new tab
>
> This is a no-op because the new tab is automatically swithed to,
> correct?
Indeed.
> ---
>
> Are you on Wayland or X11? This command should answer it:
>
> echo $XDG_SESSION_TYPE
$ echo $XDG_SESSION_TYPE
x11
I could check with wayland if you like
> I cannot reproduce the crash. The steps to reproduce are very simple, so
> I believe we should have received more crash reports. There must be
> something weird, unique going on in your machine, at least that's what I
> suspect.
>
> Have you customized your shell prompt, for example? It might be
> relevant.
* Egmont Koblinger <email address hidden>:
> > change to that new tab
>
> This is a no-op because the new tab is automatically swithed to,
> correct?
Indeed.
> ---
>
> Are you on Wayland or X11? This command should answer it:
>
> echo $XDG_SESSION_TYPE
$ echo $XDG_SESSION_TYPE
x11
I could check with wayland if you like
> I cannot reproduce the crash. The steps to reproduce are very simple, so
> I believe we should have received more crash reports. There must be
> something weird, unique going on in your machine, at least that's what I
> suspect.
>
> Have you customized your shell prompt, for example? It might be
> relevant.
Nope. It's vsw-it- nw-10:~ $
hildeb@
username @ hostname
> Or do you have unusually large or unusually small gnome-
> terminal windows, or anything nontypical in the terminal's default
> config?
No, definitely not (site is about a quarter of the screen)
> I'd like to see a stack trace of the crash. Could you please do the
> following?
Will work on that. Do I have to kill re-existing gnome-terminal- server
processes?