ERROR:terminal-tabs-menu.c:133:free_tab_id: assertion failed: (id >= 0 && id < tabs_id_array->len * 8)

[Andrew Bennetts]

Binary package hint: gnome-terminal

$ apt-cache policy gnome-terminal | head -2
gnome-terminal:
  Installed: 2.24.0-0ubuntu2

gnome-terminal just crashed for the second time today. Both times I closed a single tab to find that all terminal windows had vanished.

~/.xsession-errors contains this line:

ERROR:terminal-tabs-menu.c:133:free_tab_id: assertion failed: (id >= 0 && id < tabs_id_array->len * 8)

I upgraded to intrepid about a week ago. gnome-terminal never crashed for me in hardy.

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instuctions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

[Andrew Bennetts (spiv)]

I am using Ubuntu with Gnome.

However, I can't use apport to submit this bug, because no .crash file is generated that I can find. There's certainly no gnome-terminal crash files in /var/crash. No "report a bug" dialog appeared for either crash (unlike when e.g. epiphany-browser crashes). The only detail I could find about it was that line in ~/.xsession-errors.

If you can tell me how to configure things so that I more information will be captured next time it crashes, I'll be glad to do so. But at the moment, this bug report is the best report I can provide, so I'm reopening it. I appreciate that it's not much to work with, but it's a real problem, and without a crash file I cannot use apport to file a better one.

[Pedro Villavicencio (pedro)]

Try to get one with gdb then, the report is no use without a backtrace. instructions on how to get one here: https://wiki.ubuntu.com/DebuggingProgramCrash and also tell us a few steps in order to reproduce the bug so we can also try to reproduce it, thanks.

[Christoph Lechleitner (lech)]

I have the same problem and I think the crash only happens if gnome is started with multiple windows (--window parameter) and tabs, and if one closes a tab (or the most-right tab?) in another than the first window.

[GiuseppeVerde (launchpad-digitasaru)]

I'm in the process of collecting a backtrace.

The problem is >10 windows open simultaneously, then exiting one.

[GiuseppeVerde (launchpad-digitasaru)]

This is all I can get so far. I can't seem to find a package with debugging symbols for gnome-terminal.

[GiuseppeVerde (launchpad-digitasaru)]

There we go. Thanks for the instructions

[Pedro Fragoso (ember)]

Thanks for your info, but this bug is fixed under gnome-terminal 2.24.1 who will soon hit Intrepid.

If you want to test it you can download 2.24.1 from my PPA and give some feedback, thanks!

[GiuseppeVerde (launchpad-digitasaru)]

Where is the bug report on bugs.gnome.org?

[GiuseppeVerde (launchpad-digitasaru)]

Linked to the (probable) upstream report. I just got the 2.24.1-0ubuntu1 package, and it no longer crashes for me.

LCL/;borkborkbork:~:1$ dpkg -l gnome-terminal
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
+++-==============-==============-============================================
ii gnome-terminal 2.24.1-0ubuntu The GNOME 2 terminal emulator application
L

[Pedro Fragoso (ember)]

Closing it then. Thanks again.

[Christoph Lechleitner (lech)]

Just for the record:
I confirm that upgrading to the latest intrepid packages (as of today) solved the problem for me, too.
Thanks for the fast upstream upgrade.