GNOME Bugzilla – Bug 107262
[eel_pango_layout_set_font_desc_from_string] Application "gnome-terminal" (process 18409) has crashed due to a fatal error.
Last modified: 2005-09-29 11:29:19 UTC
Description of Problem: I had a terminal with 4 tabs. In the third of them I wrote at my zsh-prompt: cat <<SLUT > hello.java .... SLUT Pressing enter scrolled my window up half a window, where the upper half was in the background color (the one of the GTK-skin, not the white background of my terminal, i use AquaX) and then I got the standard gnome-crash-dialog.. Steps to reproduce the problem: 1. cat <<SLUT /** Hello prints two lines in the command window */ public class Hello { public static void main(String[] args) { System.out.println("Hello to you!"); System.out.println(49); } } SLUT Actual Results: segfaults, always. but only on this piece of code. not on other multiline strings. Expected Results: duh.. How often does this happen? Every time. Additional Information: Commands with cat <<BLAH-heredoc-multiline-strings results in setting a multiline title on the tab. So the tabs vertical size expands to fit the text. (but not on the window, in the window CRLF becomes those squares..), could that have something to do with it?
Thanks for the bug report. What version of gnome-terminal are you running? I can't duplicate this crash with gnome-terminal 2.0.1 (on Redhat 8 with either bash or zsh as the underlying shell). Without a stack trace from the crash we may not be able to determine what caused the crash. Can you provide us with one? Please see http://bugzilla.gnome.org/getting-traces.cgi for more information about getting a useful stack trace.
I run version 2.2.1 here is a stack trace (sorry, no debugging info..)
+ Trace 34386
and as it seems like a bug in a library.. here goes.. $ ldd `which gnome-terminal` libvte.so.4 => /usr/lib/libvte.so.4 (0x40023000) libXft.so.2 => /usr/X11R6/lib/libXft.so.2 (0x400f9000) libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x40109000) libXrender.so.1 => /usr/X11R6/lib/libXrender.so.1 (0x40157000) libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0x4015c000) libncurses.so.5 => /lib/libncurses.so.5 (0x4017f000) libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x401be000) libglade-2.0.so.0 => /usr/lib/libglade-2.0.so.0 (0x4027a000) libgnomeui-2.so.0 => /usr/lib/libgnomeui-2.so.0 (0x4028e000) libgnutls.so.5 => /usr/lib/libgnutls.so.5 (0x4030a000) libtasn1.so.0 => /usr/lib/libtasn1.so.0 (0x4033c000) libgcrypt.so.1 => /usr/lib/libgcrypt.so.1 (0x4034a000) libnsl.so.1 => /lib/libnsl.so.1 (0x40383000) libjpeg.so.62 => /usr/lib/libjpeg.so.62 (0x40397000) libSM.so.6 => /usr/X11R6/lib/libSM.so.6 (0x403b5000) libICE.so.6 => /usr/X11R6/lib/libICE.so.6 (0x403bd000) libbonoboui-2.so.0 => /usr/lib/libbonoboui-2.so.0 (0x403d2000) libgnomecanvas-2.so.0 => /usr/lib/libgnomecanvas-2.so.0 (0x4042a000) libgnome-2.so.0 => /usr/lib/libgnome-2.so.0 (0x40452000) libesd.so.0 => /usr/lib/libesd.so.0 (0x40465000) libaudiofile.so.0 => /usr/lib/libaudiofile.so.0 (0x4046c000) libart_lgpl_2.so.2 => /usr/lib/libart_lgpl_2.so.2 (0x4048a000) libpangoft2-1.0.so.0 => /usr/lib/libpangoft2-1.0.so.0 (0x4049f000) libgtk-x11-2.0.so.0 => /usr/lib/libgtk-x11-2.0.so.0 (0x404be000) libgdk-x11-2.0.so.0 => /usr/lib/libgdk-x11-2.0.so.0 (0x406c9000) libatk-1.0.so.0 => /usr/lib/libatk-1.0.so.0 (0x4072c000) libgdk_pixbuf-2.0.so.0 => /usr/lib/libgdk_pixbuf-2.0.so.0 (0x40742000) libpangoxft-1.0.so.0 => /usr/lib/libpangoxft-1.0.so.0 (0x40753000) libpangox-1.0.so.0 => /usr/lib/libpangox-1.0.so.0 (0x40771000) libpango-1.0.so.0 => /usr/lib/libpango-1.0.so.0 (0x4077d000) libbonobo-2.so.0 => /usr/lib/libbonobo-2.so.0 (0x407ac000) libORBitCosNaming-2.so.0 => /usr/lib/libORBitCosNaming-2.so.0 (0x407fb00 0) libgnomevfs-2.so.0 => /usr/lib/libgnomevfs-2.so.0 (0x407ff000) libgconf-2.so.4 => /usr/lib/libgconf-2.so.4 (0x40832000) libxml2.so.2 => /usr/lib/libxml2.so.2 (0x40857000) libz.so.1 => /lib/libz.so.1 (0x4092e000) librt.so.1 => /lib/librt.so.1 (0x4093b000) libbonobo-activation.so.4 => /usr/lib/libbonobo-activation.so.4 (0x4094d 000) libORBit-2.so.0 => /usr/lib/libORBit-2.so.0 (0x4095f000) libpopt.so.0 => /lib/libpopt.so.0 (0x4099b000) libm.so.6 => /lib/libm.so.6 (0x409a2000) liblinc.so.1 => /usr/lib/liblinc.so.1 (0x409c3000) libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0x409ca000) libdl.so.2 => /lib/libdl.so.2 (0x409cf000) libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0x409d2000) libgthread-2.0.so.0 => /usr/lib/libgthread-2.0.so.0 (0x40a01000) libpthread.so.0 => /lib/libpthread.so.0 (0x40a06000) libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0x40a55000) libstartup-notification-1.so.0 => /usr/lib/libstartup-notification-1.so. 0 (0x40ab7000) libc.so.6 => /lib/libc.so.6 (0x40ac0000) libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x40bd0000) libexpat.so.1 => /usr/lib/libexpat.so.1 (0x40bdd000) libXi.so.6 => /usr/X11R6/lib/libXi.so.6 (0x40bfb000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
Appears to be a unique stack trace, according to the simple-dup-finder. Marking priority->high (it's a crasher), changing GNOMEVER2.0->GNOMEVER2.2 (since tobbe said he ran version 2.2.1), adding bugsquad keyword, and reopening.
tobbe: Luis said that he "can't understand how that is a terminal trace, since terminal doesn't use eel, AFAIK". Are you sure you didn't cut and paste the wrong stack trace? Anyway, I'm reassigning this to eel, as per Luis' suggestion.
Yes I'm sure this is the one.. couldn't be I use AquaX-gtk-skin which uses xenophilia or something? I don't know :) I know very little of which components relates to eachother.. I don't code guis..
g-t contains eel cut-and-pastage. Can we check if this is specific to a particular theme or font?
Should also try without zshell, it looks like the crash is in trying to set the terminal tab title. So you'd have to have multiple tabs open to reproduce, and have to have the same title-setting setup as the bug reporter. Using this info maybe we can get complete reproduction instructions for what to set in the title that triggers a crash. Please reopen if reproduction instructions added.
*** Bug 111320 has been marked as a duplicate of this bug. ***
*** Bug 113197 has been marked as a duplicate of this bug. ***
Bug 111320 was a nautilus crash; bug 113197 was another gnome-terminal crash this time using RedHat 9. The reporter of bug 113197 had the following to say: Sometimes gnome-terminal crashes after a "cd ..". Steps to reproduce the problem: 1. Just type "cd .." 2. Just press "enter" How often does this happen? Twice in a few days, my usage of gnome-terminal is almost intensive. Additional Information: My gnome-terminal is the one given whit red-hat 9.0, I have changed the font. I've asked him to add a comment here saying which font it is that he changed to.
*** Bug 117308 has been marked as a duplicate of this bug. ***
*** Bug 119966 has been marked as a duplicate of this bug. ***
*** Bug 125685 has been marked as a duplicate of this bug. ***
I think I've found an easy way to reproduce this crash. The following crashes gnome-terminal, but I haven't compared stacktraces. To reproduce: 1. Start a new gnome-terminal 2. Create another tab (this is required so that gnome-terminal shows the tabbar) 3. Run: foo="abcdefghhijklmnopqrstuvwxyz" 4. Run: echo -ne "\016\033]0;$foo$foo$foo$foo$foo$foo\007";sleep 2 5. gnome-terminal crashes The weird characters are caused by the \016 before the xterm title update. Thats seems to crash gnome-terminal when setting a xterm title larger than the available space in the tabbar. The sleep 2 is required when PROMPT_COMMAND or PS1 also changes the xterm title.
bugzilla-gnome@bkor.dhs.org: The version on this bug is still 2.2. Does that mean you're still using gnome-terminal-2.2.x? If so, is there any way you could try out 2.4.x and see if the problem still exists under that version? Thanks.
newren@math.utah.edu: It was with gnome-terminal 2.4.0.1 and vte 0.11.10. I've finally managed to create gnome 2.4 and 2.5 stacktraces. They are both different, but the 2.4 stacktrace matches the one in bug 116108. The function from #0 (pango_layout_iter_get_char_extents) is the same, so it could be that it is same bug, but with a different stacktrace under gnome 2.2. Gnome 2.2 does not want to compile with jhbuild, so I'll just continue in bug 116108. removing newlines from summary
The \016 character, which in ASCII is called SO (Shift Out), causes an xterm terminal (and gnome-terminal, which emulates that) to switch to the alternate character set (whatever that may be...; see ami.univ-evry.fr/XFree86/4.0.1/doc/ctlseqs.TXT) This is reversed when the terminal sees a SI (Shift In) character, ie, a \017. One should *not* send \016 to terminals... I do not see this crashes using gtk+ HEAD and gnome-terminal 2.5, btw. Indeed, I see almost the same behaviour when I follow the above steps in gnome-terminal and xterm, except that gnome-terminal's title is garbled while xterm's is not. One reason for that I can think of is thayt vte is sending the text of the newly set title in the alternate charset, while gnome-terminal expects utf8; I'll have to check, tho.
hmmm, the url I meant to paste was http://www.lami.univ-evry.fr/XFree86/4.3.0/doc/ctlseqs.TXT
> One should *not* send \016 to terminals... Note that Midnight Commander (mc) does sometimes send \016 to the terminal. I found this out by redirecting the output of mc to tee + lots of trial and error. Catting the file created by tee sometimes crashes mc, but not reliably. Now that I have a gnome-terminal with debugging information I'll try to reproduce this stacktrace with gnome-terminal 2.4.
*** Bug 126290 has been marked as a duplicate of this bug. ***
Yeah, \016 is not that bad, actually ;) This bug is in pango, actually: I distilled a gnome-terminal-free little program, to be found in bug 120891, which exposes it. That bug in turn turns out to be part of the breakage in bug 89541, and, luckily, that part has been fixed there. There are other parts to it, though. I'll mark this as a duplicate of bug 120891, which is the closest one. *** This bug has been marked as a duplicate of 120891 ***
*** Bug 129372 has been marked as a duplicate of this bug. ***
*** Bug 129836 has been marked as a duplicate of this bug. ***
*** Bug 131144 has been marked as a duplicate of this bug. ***
*** Bug 121894 has been marked as a duplicate of this bug. ***
*** Bug 133767 has been marked as a duplicate of this bug. ***
*** Bug 134789 has been marked as a duplicate of this bug. ***
*** Bug 135048 has been marked as a duplicate of this bug. ***
*** Bug 135799 has been marked as a duplicate of this bug. ***
*** Bug 136051 has been marked as a duplicate of this bug. ***
*** Bug 136362 has been marked as a duplicate of this bug. ***
*** Bug 139620 has been marked as a duplicate of this bug. ***
*** Bug 139419 has been marked as a duplicate of this bug. ***
*** Bug 140242 has been marked as a duplicate of this bug. ***
This is being used as the original for all this bugs, so making the summary be more useful.
*** Bug 140761 has been marked as a duplicate of this bug. ***
*** Bug 140582 has been marked as a duplicate of this bug. ***
*** Bug 141076 has been marked as a duplicate of this bug. ***
*** Bug 141201 has been marked as a duplicate of this bug. ***
*** Bug 141573 has been marked as a duplicate of this bug. ***
*** Bug 143564 has been marked as a duplicate of this bug. ***
*** Bug 145699 has been marked as a duplicate of this bug. ***
*** Bug 145757 has been marked as a duplicate of this bug. ***
*** Bug 145921 has been marked as a duplicate of this bug. ***
*** Bug 146039 has been marked as a duplicate of this bug. ***
*** Bug 146040 has been marked as a duplicate of this bug. ***
*** Bug 146079 has been marked as a duplicate of this bug. ***
*** Bug 146189 has been marked as a duplicate of this bug. ***
*** Bug 153543 has been marked as a duplicate of this bug. ***
*** Bug 154288 has been marked as a duplicate of this bug. ***
*** Bug 146333 has been marked as a duplicate of this bug. ***
*** Bug 152554 has been marked as a duplicate of this bug. ***
*** Bug 155045 has been marked as a duplicate of this bug. ***
*** Bug 154148 has been marked as a duplicate of this bug. ***
*** Bug 160225 has been marked as a duplicate of this bug. ***
*** Bug 160661 has been marked as a duplicate of this bug. ***
*** Bug 165883 has been marked as a duplicate of this bug. ***
*** Bug 168343 has been marked as a duplicate of this bug. ***
*** Bug 166425 has been marked as a duplicate of this bug. ***
*** Bug 169303 has been marked as a duplicate of this bug. ***
*** Bug 300427 has been marked as a duplicate of this bug. ***
*** Bug 305249 has been marked as a duplicate of this bug. ***
*** Bug 306433 has been marked as a duplicate of this bug. ***
*** Bug 311699 has been marked as a duplicate of this bug. ***
*** Bug 317421 has been marked as a duplicate of this bug. ***