GNOME Bugzilla – Bug 116108
gnome-terminal crashes when dynamically setting xterm title
Last modified: 2004-12-22 21:47:04 UTC
Package: gnome-terminal Severity: normal Version: 2.2.2 Synopsis: gnome-terminal 2.2.2 crashes on changing directory Bugzilla-Product: gnome-terminal Bugzilla-Component: general BugBuddy-GnomeVersion: 2.0 (2.2.1) Description: Description of Problem: gnome-terminal 2.2.2 crashes on changing the directory - while trying to display the directory as the windows title Steps to reproduce the problem: 1. open new gnome-terminal 2. open 4-5 tabbed views 3. su - to different users in different views 4. every user starts mc and uses it to browse directories and enter RPM archives 5. after an hour of work, gnome-terminal crashes when I change directory (while I was browsing RPM package content, path - rather long - was displayed as window title. After using TAB to change mc panel - and current directory - terminal crashes) Actual Results: a lot of strange chars displayed as window title; terminal crashes Expected Results: new path displayed as the terminal window title How often does this happen? 3rd time today Additional Information: locale is pl_PL (ISO 8859-2) pango 1.2.3 and current GNOME 2.2.x libs are used Debugging Information: Backtrace was generated from '/usr/bin/gnome-terminal' (no debugging symbols found)...[New Thread 1087979360 (LWP 16476)] 0xffffe002 in ?? ()
+ Trace 38223
It appears that the stack trace didn't make it through. Can you resubmit it?
Created attachment 18038 [details] Crash data
Crashed again - backtrace above. New bug-buddy (2.2.106) does a lot better work saving it. I have a screenshot, too. It looks like all small letters from path are replaced by semigraphics and some strange chars - numbers and capital letters are intact. I will attach the screenshot if it helps.
Pasting the stack trace inline ot make searches easier: Backtrace was generated from '/usr/bin/gnome-terminal' (no debugging symbols found)...[New Thread 1087979360 (LWP 4016)] 0xffffe002 in ?? ()
+ Trace 38424
Thread 1 (Thread 1087979360 (LWP 4016))
This stack trace matches the one in bug 95786, but that was a crash in nautilus and Alex Larsson said the following in that bug: "I'm pretty sure i've fixed this on HEAD. It was a utf8 issue in the progress dialog." If it was due to a progress dialog, then it was probably only fixed for nautilus and means that this could still be an issue in gnome-terminal. I'm setting priority->high & severity->critical (it's a crasher) and adding GNOMEVER2.2 & bugsquad & STACKTRACE (has some debugging symobls) keywords. I believe my previous choice to move to pango (since the only function in the stack trace had "pango" in it) may have been wrong (mostly because of Alex's comment in bug 95786) so I'm moving back to gnome-terminal. I'm also marking as new.
New backtrace with symbols from gtk. Backtrace was generated from '/usr/bin/gnome-terminal' (no debugging symbols found)...[New Thread 1087979360 (LWP 2849)] 0xffffe002 in ?? ()
+ Trace 38486
Thread 1 (Thread 1087979360 (LWP 2849))
Cool, thanks. I'm adding the STACKTRACE keyword, as well as the GNOMEVER2.2 and bugsquad keywords and I'm also setting version to 2.2.x.
I can confirm the same type of crash, same type of work in terminal (mc, su). Additional info, wen crash occur: Get gnome-terminal focus after any memory consuming job and rapidly press twice down arrow or tab. Actual Results: Long nonsense text appears in window title then SEGFAULT How often does this happen? Twice daily Additional Information: LANG=cs_CZ Backtrace was generated from '/opt/gnome/bin/gnome-terminal' (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...[New Thread 16384 (LWP 30761)] (no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...0x40b90a86 in waitpid () from /lib/i686/libpthread.so.0
+ Trace 39892
Thread 1 (Thread 16384 (LWP 30761))
Update: I have experienced another crash, without double keypress.
Stanislav: With the info you've provided, it's hard to be sure you're experiencing the same crash. The stack trace you posted isn't very useful, as it looks trashed. It'd probably be good to verify that you're experiencing the same problem before posting further (since that might lead us down the wrong path for this problem or lead you in the wrong direction for a solution). Can you get a stack trace with debugging symbols and then attach it (please don't paste anymore stack traces inline, as we already have a good one and further stack traces will just make it harder to scroll through this report). Info on how to get one can be found at http://bugzilla.gnome.org/getting-traces.cgi. Thanks.
I know that I haven't debugging symbols, and backtrace is not much useful. But bug symptoms are identical. I have another idea, how to locate the bug. I am using two GNOME desktops. On first one (SuSE Linux 8.2, and now 9.0 beta1) I am experiencing crashes regularly (in 9.0 beta1 even daily). On second (Gentoo unstable) never. Now I have copied my gconf settings from second one to first one, reverted options, which (IMHO) cannot cause a problem and waiting for experience. If I succeed, I will send you problematic option. (Quick guess: On second system I have disabled all hotkeys, on first system sometimes accidentally appears yelp before crash {And I am nearly sure that I have not touch F1.}.) If I will not succeed, I will install debug packages and wait for crash.
I have compared my two systems: Crashing system has following differences: - Non-ASCII character in active profile name - scroll_on_output: false - no background picture, no transluency, different color scheme and font - theme Crux Waiting for another crash to be able more specific. To Robert Glowczynski: Can you verify these setups?
I have eliminated all gconf setups. I suspect the crash can be Crux theme specific (no crash in 3 days after theme change). Can one of reporters confirm it, eventually create backtrace again with debugging symbols in gnome-themes (I see some ?? in backtrace)?
Repeated with theme Grand Canyon. After theme change the bug seems to occur less often.
The bug was repeated with GNOME 2.2 in SuSE Linux 9.0 (gcc-3.3.1) and GNOME 2.4 in Gentoo Linux with gcc-3.3.1. Not yet experienced in Gentoo Linux with gcc-3.2.*.
Stanislav, maybe the problem you are seeing is the one reported in bug 122687. What is the profile name you are using which has non-ASCII characters in it?
It was one of my thoughts. Originally it was named "Tmavý". After renaming it to "Dark" crashes has appeared again.
The bug occur most frequently, if you have enabled and using "Lynx-like motion" feature in mc (i. e. left arrow to change directory). You need also check "Xterm window title" in mc layout to catch this bug. And my PS1 is \[\e]2;\u@\h:$(ppwd)\007\e]1;\h\007\]\u@\h:\w>.
(originally posted to bug 107262, but after getting a stacktrace adding the info to this bug) I think I've found an easy way to reproduce this crash. The following crashes gnome-terminal 2.4 (jhbuild gnome24 today) and 2.5 (jhbuild gnome26 today). 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. Stacktrace from 2.4:
+ Trace 41290
I can reproduce this bug independently of gnome-terminal. Since this is actually a dup of bug 120891, I'll post my findings there, and close this. *** This bug has been marked as a duplicate of 120891 ***