[feisty] launching gnome-terminal w/geometry argument segfaults

[psylence519]

Binary package hint: gnome-terminal

Last night I could launch my gnome-terminal w/a larger geometry, this morning I updated (will attach update history) and now it segfaults immediately.

Even beryl's "command" launches have this problem, I had modified all gnome-terminal launches to have --geometry=110x50 after them, in the menu, one on the gnome panel and one in beryl. *ALL* segfault.

gdb tells me it's a segfault in libvte, but I don't have any debug packages (I don't seem to see any in the repos) so I can't dig further. It's telling me it's core'ing but I can't find the core either! :)

I'd gladly pursue this if you lead me down the right path, where can I get the proper debug packages?

[psylence519 (psylence519)]

bug 84587 seems possibly related as well

[C de-Avillez (hggdh2)]

you can add "deb http://people.ubuntu.com/~pitti/ddebs feisty main universe" to your /etc/apt/sources.list; then do a sudo apt-get update, and you will get the debug packages.

Not all of them are there, but still...

[C de-Avillez (hggdh2)]

I just tried it on my feisty (but its x86_64) and it does not core. gnome-terminal has been updated today. Did you update yours?

[C de-Avillez (hggdh2)]

duh. My gnome-terminal is 2.17.91-0ubuntu1,
 yours is 2.17.92-0ubuntu1.

Let me update mine, and check.

[Sebastien Bacher (seb128)]

Thanks for the bug report. This particular bug has already been reported, but feel free to report any other bugs you find.

[Sebastien Bacher (seb128)]

Marking the other bug duplicate. That's known upstream: http://bugzilla.gnome.org/show_bug.cgi?id=412717

[C de-Avillez (hggdh2)]

SB, I could not reproduce it on mine, even with windows maxed out. Feisty up-to-date, gnome-terminal 2.17.92-0ubuntu1, X86_64.

[psylence519 (psylence519)]

Following the upstream steps:
1. Launch gnome-terminal
2. Maximize the window
3. File -> Open tab or Ctrl+Shift+T

I don't have any problems, no crash. Are you sure this is a dup?

[psylence519 (psylence519)]

I stand corrected. My backtrace shows the same stack as upstream...

Thanks for the debug repo hggdh...

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1227274560 (LWP 29405)]
_vte_terminal_ensure_cursor (terminal=0x82c7800, current=0)
    at /build/buildd/vte-0.15.4/./src/vte.c:1892
1892 /build/buildd/vte-0.15.4/./src/vte.c: No such file or directory.
        in /build/buildd/vte-0.15.4/./src/vte.c
(gdb) bt
#0 _vte_terminal_ensure_cursor (terminal=0x82c7800, current=0)
    at /build/buildd/vte-0.15.4/./src/vte.c:1892
#1 0xb7d4861a in _vte_terminal_insert_char (terminal=0x82c7800,
    c=<value optimized out>, force_insert_mode=0, invalidate_now=0,
    paint_cells=1, forced_width=0) at /build/buildd/vte-0.15.4/./src/vte.c:2430
#2 0xb7d4cd72 in vte_terminal_process_incoming (terminal=0x82c7800)
    at /build/buildd/vte-0.15.4/./src/vte.c:3278
#3 0xb7d4d01a in time_process_incoming (terminal=0x82c7800)
    at /build/buildd/vte-0.15.4/./src/vte.c:11919
#4 0xb7d4d966 in process_timeout (data=0x0)
    at /build/buildd/vte-0.15.4/./src/vte.c:11964
#5 0xb771b216 in ?? () from /usr/lib/libglib-2.0.so.0
#6 0x00000000 in ?? ()
(gdb)

[Sebastien Bacher (seb128)]

That upload fixes the problem:

 vte (1:0.15.5-0ubuntu2) feisty; urgency=low
 .
   * debian/patches/90_from_svn_fix_crasher.patch:
     - patch from SVN, fix crasher when using the geometry option for example
       (Ubuntu: #88489)

[Alan Tam (at)]

I can confirmed that the new libvte fixes the crash.
But running "gnome-terminal --geomtery=80x20" has the following unexpected behavior - there are some new lines after first character of my shell prompt "only when the number of rows specified < 24 OR > 54".

[Sebastien Bacher (seb128)]

That's an another problem, please don't abuse a closed bug, it's creating confusion and sending mails to people who reported an another problem. That bug is already known upstream: http://bugzilla.gnome.org/show_bug.cgi?id=413068