Comment 5 for bug 2049923

> change to that new tab

This is a no-op because the new tab is automatically swithed to, correct?

---

Are you on Wayland or X11? This command should answer it:

echo $XDG_SESSION_TYPE

---

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. Or do you have unusually large or unusually small gnome-terminal windows, or anything nontypical in the terminal's default config?

---

I'd like to see a stack trace of the crash. Could you please do the following?

Open two terminals that are _not_ gnome-terminal. For example xterm. Make sure gnome-terminal is _not_ running.

In the first xterm, execute two:

ulimit -c unlimited
/usr/libexec/gnome-terminal-server

In the second xterm, within 10 seconds, execute:

gnome-terminal

You should see a gnome-terminal window appear as usual. Make it crash according to the aforementioned steps.

In the first window you should see a brief message including "core dumped".

In the directory /var/lib/apport/coredump you should see a freshly created file, mentioning gnome-terminal-server in its name. Verify its timestamp that it's indeed a freshly created one.

Run this command

gdb /usr/libexec/gnome-terminal-server /var/lib/apport/coredupmp/[the new filename of that core dump]

You might then need to press Enter a few times until you get a "(gdb)" prompt. There execute the command

bt full

You might again need to press Enter a few times to continue its output (if it asks to "Type <RET> for more"), until you get a "(gdb)" prompt again.

Then please copy-paste gdb's output here.

(There might be an easier way of getting this info using apport, but I'm not familiar with that. If you are then you can do that.)

Thanks in advance!