GNOME Bugzilla – Bug 141194
Error Application gnome-terminal Crashed Unexpectedly
Last modified: 2009-08-15 18:40:50 UTC
While running gnopemicus with speech in the background ... 1. Bring up terminal window 2. Bring up any applications from terminal command line (i.e mozilla &) 3. Wait til application is up 4. Listen for Speech 5. Go back to terminal window 6. type ps -ef | grep mozilla (or whatever application just brought up) Error occured in Dialog Box: The Application "gnome-terminal" has quit unexpectedly. You can inform the developers of what happened to help them fix it. Or you can restart the application right now. <Restart Application> <Close> <Inform Developers> At this point, nothing works, can not switch windows back and forth. Can not "Restart" "Close" or "Inform Developers" . Cannot do anything. System hangs ... reboot needed.
I can't reproduce this because I donb't have any speech installed :-/ Maybe someone with the required tools can provide a stack trace? The "cannot do anything" part is probably due to a server grab, which you can disable doing ctrl-alt-keypad_/ or ctrl-alt-keypad_* if you add Option "AllowDeactivateGrabs" "true" Option "AllowClosedownGrabs" "true" to the ServerFlags section in your XF86Config file...
We really need a stack trace from gnome-terminal process to make any progress on this.
Stack trace, good idea. Please let me know how you want to capture stack trace, so I can provide exact information you requested (i.e. what commands, parameters, options, etc.). So far below is the only trace/error i have : The Application "gnome-terminal" has quit unexpectedly. You can inform the developers of what happened to help them fix it. Or you can restart the application right now. <Restart Application> <Close> <Inform Developers>
Clicking on the <Inform Developers> should guide you thru the steps. That assumes you can interact with you computer, though, of course. If you can't please try my suggestions on comment #1 to end grabs... That usually does help.
Use gdb to attach to the process and type where.
Any further information on this. Will have to close unless it is provided.
This problem is still exist. Gathering more info. Have anyone seen or duplicate this problem ?
Tony, we need a stack trace, and you seem to be the only one seeing this bug. Please see http://bugzilla.gnome.org/getting-traces.cgi for more information about getting a useful stack trace.
Mariano, I am having hard time getting a trace for you, since when this error occured, everything Crashed and Froze. The Only option Working out of the 3 ("Restart" "Close" or "Inform Developers") is "Restart" ... When "Restart" is pressed, all other applications and including terminal itself Closed. From your comment#4, "Clicking on the <Inform Developers>" this option does not work, when crash occured. Please tell me exact syntax/steps-by-steps how you want me to capture this problem (i.e Bug Buddy, core dump w/gdb, just gdb, or bug buddy & gdb). Please be specific ... thanks.
This is part of the trace ... It got "Segmentation fault" before it finished. Perhaps 'libgail-gnome' has something to do with it. Please advice. gdb gnome-terminal GNU gdb Red Hat Linux (5.3post-0.20021129.18rh) Copyright 2003 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-redhat-linux-gnu"... (no debugging symbols found)... (gdb) run Starting program: /usr/bin/gnome-terminal (gnome-terminal:3548): Gnome-WARNING **: Accessibility: failed to find module 'libgail-gnome' which is needed to make this application accessible GTK Accessibility Module initialized application finalize called Segmentation fault
Hi Tony: the missing libgail-gnome won't have any effect on gnome-terminal. However, it does cast some doubt on your gnome setup generally, since libgail-gnome should be bundled with your distro. Where did your gnome-2 stack come from?
Hi Bill, I obtained the trace using just GDB. Unless there are better ways and more succesful approach to capture, please let me know. Thanks.
I was asking where your "stack", i.e. your GNOME software modules, RPMS, etc. came from (not where your "stack trace" came from). The fact that libgail-gnome was not found suggests that your GNOME installation is incomplete or inconsistent in some way.
With Out Running Gnopernicus in the Background with speech enable, gnome- terminal is much more stable.
Tony: there is no stack trace attached to this bug, so I don't know what you are referring to. Can you also please tell us where your GNOME came from, i.e. is it RedHat Fedora 2, or Suse, etc. ? We will have to close this bug if we can't get any more specific information. The fact that libgail-gnome was not found suggests that there is something seriously wrong with the way your GNOME system is installed, so the problems may not be in gnome-terminal.
1. We're using Red Hat 9 2. Its hard to Capture trace because gnome-term Crashed left/right, at will. When it crashed, everything wiped out. All appls Closed. Below is additional trace. Again, if you like to see more specific items on a trace in addition to the trace below, please tell me exactly what you are looking for and provide the steps w/syntax to accomplish this task, so I can provide you more specific/custom trace, if need be. 3. lib-gail issue wise, I agreed with you (comment#11) that the missing libgail- gnome won't have any effect on gnome-terminal. It shouldnt be, but ...?? Trace: ------
+ Trace 47136
Thread 1 (Thread 1087918976 (LWP 3218))
Thanks Tony. So, if you are using RedHat 9, is that 9.0? Did all of the GNOME libraries you are using come packaged with your RedHat 9.0 distribution? The stack trace indicates that the gnome-terminal was exiting already when the "crash" occurred. So the actual problem is not the result of a segmentation fault or "crash" in the usual sense... the question is, why was the terminal exiting in the first place? I am assuming that the trace you sent is from the gnome-terminal process. I really think you should upgrade your GNOME desktop and see if this problem persists. In the meantime, if you can attach the output of "ldd `which gnome-terminal`" that would be helpful, it will tell us the versions of GNOME libraries which are being used.
1. It should be all Gnome Libs came packaged w/red hat 9 with kernel release 2.4.20-18.9 2. The trace is from gnome-term process. I'll see if i can capture more. 3. Gnome Desk top version is 2.7.1 . But this problem did occur with previous desktop version as well. 4. ldd wise, what's best way obtain this ? Please let me know.
Any progress or update status on this bug ?
Tony, can you please, as Bill suggested above, paste the output of running ldd `which gnome-terminal` in a shell?
libvte.so.4 => /opt/gnome2/lib/libvte.so.4 (0x40017000) libncurses.so.5 => /usr/lib/libncurses.so.5 (0x400ca000) libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x40127000) libglade-2.0.so.0 => /opt/gnome2/lib/libglade-2.0.so.0 (0x40207000) libgnomeui-2.so.0 => /opt/gnome2/lib/libgnomeui-2.so.0 (0x4021b000) libSM.so.6 => /usr/X11R6/lib/libSM.so.6 (0x4029f000) libICE.so.6 => /usr/X11R6/lib/libICE.so.6 (0x402a8000) libbonoboui-2.so.0 => /opt/gnome2/lib/libbonoboui-2.so.0 (0x402bf000) libxml2.so.2 => /opt/gnome2/lib/libxml2.so.2 (0x40318000) libz.so.1 => /usr/lib/libz.so.1 (0x40401000) libgnomecanvas-2.so.0 => /opt/gnome2/lib/libgnomecanvas-2.so.0 (0x4040f000) libgnome-2.so.0 => /opt/gnome2/lib/libgnome-2.so.0 (0x40438000) libart_lgpl_2.so.2 => /opt/gnome2/lib/libart_lgpl_2.so.2 (0x4044b000) libpangoft2-1.0.so.0 => /opt/gnome2/lib/libpangoft2-1.0.so.0 (0x40460000) libgtk-x11-2.0.so.0 => /opt/gnome2/lib/libgtk-x11-2.0.so.0 (0x40481000) libgdk-x11-2.0.so.0 => /opt/gnome2/lib/libgdk-x11-2.0.so.0 (0x406f7000) libatk-1.0.so.0 => /opt/gnome2/lib/libatk-1.0.so.0 (0x4075a000) libgdk_pixbuf-2.0.so.0 => /opt/gnome2/lib/libgdk_pixbuf- 2.0.so.0 (0x40772000) libpangoxft-1.0.so.0 => /opt/gnome2/lib/libpangoxft-1.0.so.0 (0x40785000) libpangox-1.0.so.0 => /opt/gnome2/lib/libpangox-1.0.so.0 (0x4078a000) libpango-1.0.so.0 => /opt/gnome2/lib/libpango-1.0.so.0 (0x40795000) libbonobo-2.so.0 => /opt/gnome2/lib/libbonobo-2.so.0 (0x407c7000) libgconf-2.so.4 => /opt/gnome2/lib/libgconf-2.so.4 (0x40818000) libgnomevfs-2.so.0 => /opt/gnome2/lib/libgnomevfs-2.so.0 (0x40848000) libbonobo-activation.so.4 => /opt/gnome2/lib/libbonobo- activation.so.4 (0x4089d000) libORBit-2.so.0 => /opt/gnome2/lib/libORBit-2.so.0 (0x408b1000) libm.so.6 => /lib/tls/libm.so.6 (0x40901000) liblinc.so.1 => /usr/lib/liblinc.so.1 (0x40924000) libgmodule-2.0.so.0 => /opt/gnome2/lib/libgmodule-2.0.so.0 (0x4092c000) libdl.so.2 => /lib/libdl.so.2 (0x40930000) libgobject-2.0.so.0 => /opt/gnome2/lib/libgobject-2.0.so.0 (0x40934000) libgthread-2.0.so.0 => /opt/gnome2/lib/libgthread-2.0.so.0 (0x40967000) libglib-2.0.so.0 => /opt/gnome2/lib/libglib-2.0.so.0 (0x4096b000) libstartup-notification-1.so.0 => /opt/gnome2/lib/libstartup- notification-1.so.0 (0x409e1000) libpthread.so.0 => /lib/tls/libpthread.so.0 (0x409e9000) libc.so.6 => /lib/tls/libc.so.6 (0x42000000) libpopt.so.0 => /usr/lib/libpopt.so.0 (0x409f7000) libXft.so.2 => /opt/gnome2/lib/libXft.so.2 (0x409ff000) libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x40a10000) libXrender.so.1 => /opt/gnome2/lib/libXrender.so.1 (0x40a62000) libfontconfig.so.1 => /opt/gnome2/lib/libfontconfig.so.1 (0x40a6a000) libgnome-keyring.so.0 => /opt/gnome2/lib/libgnome-keyring.so.0 (0x40a92000) libjpeg.so.62 => /usr/lib/libjpeg.so.62 (0x40a9a000) libesd.so.0 => /opt/gnome2/lib/libesd.so.0 (0x40ab9000) libaudiofile.so.0 => /opt/gnome2/lib/libaudiofile.so.0 (0x40ac2000) libXrandr.so.2 => /usr/X11R6/lib/libXrandr.so.2 (0x40ae0000) libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x40ae4000) libXcursor.so.1 => /usr/X11R6/lib/libXcursor.so.1 (0x40af2000) libORBitCosNaming-2.so.0 => /opt/gnome2/lib/libORBitCosNaming- 2.so.0 (0x40afc000) libssl.so.4 => /lib/libssl.so.4 (0x40b00000) libcrypto.so.4 => /lib/libcrypto.so.4 (0x40b35000) libresolv.so.2 => /lib/libresolv.so.2 (0x40c26000) libgssapi_krb5.so.2 => /usr/kerberos/lib/libgssapi_krb5.so.2 (0x40c38000) libkrb5.so.3 => /usr/kerberos/lib/libkrb5.so.3 (0x40c4c000) libk5crypto.so.3 => /usr/kerberos/lib/libk5crypto.so.3 (0x40caa000) libcom_err.so.2 => /lib/libcom_err.so.2 (0x40cba000) librt.so.1 => /lib/tls/librt.so.1 (0x40cbc000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000) libexpat.so.0 => /usr/lib/libexpat.so.0 (0x40cce000) libasound.so.2 => /usr/lib/libasound.so.2 (0x40cef000) libcom_err.so.3 => /usr/kerberos/lib/libcom_err.so.3 (0x40d88000)
Any update on this problem ?
Have tried on below configurations, problem is still exist. System configurations: Gnopernicus 0.9.7 Gnome Desktop 2.7.4 Fedora Core 2
Problem still exist in latest build below : System configurations: Gnopernicus 0.9.10 Gnome Desktop 2.7.9 Fedora Core 2
When the dialog box about gnome-terminal terminating appears, telnet into the systerm and attach gdb to the gnome-terminal process to get a stack trace. I assume that the original comments about how to reproduce the problem still ap-ply.
Stack trace have been captured in comment #16 ... Unless you want specific trace captured, please let me know.
As Bill stated this stack trace indicates that gnome-terminal was already exiting. Can you strace the gnome-terminal process to see if that gives us any useful information?
padraig - please tell me exactly how to obtain this strace and this particular useful information that you are looking for, steps by steps (as to bring what up 1st, run what command, look for what, a specific test case, etc.) This way we wont waste time looking for wrong things. I believed we went thru all these excercises already, unless something new. But I'll wait for your instructions ... So what if I did stack trace and I get the same thing as trace captured in comment #16, what next ?
The reason for asking for the strace output is to try and get some clue why gnome-terminal is terminating, i.e. the stack trace in comment #16 occurs. As for a specific test case, you must provide that. You should be able to figure out from the man page for strace how to call it.
padraig - Here is the trace again, when gnome-terminal and gnopernicus crashed ...
+ Trace 50315
I had asked for strace output not a stack trace. This stack trace is different from the one in comment #16. It does not help identify the problem as the function at the top of the stack is not identified.
If you know, Why dont you SHOW me the Exact steps by steps to capture what you looking for so we dont have to run around, waste time looking for wrong thing. I did what according to gdb doc said to use "thread apply all bt" ... and this is all i got from the trace ... Do you know better way ? Show me, so we can all save time. If you not familiar with the process, please point me to who does know.
I think there's some misunderstanding here. Padraig asked for output from the command strace which gives a trace of syscalls from the app. strace -o output-file.txt <app> will do nicely.
This problem seems to be resolved in : gnopernicus: 0.9.12 Gnome desktop : 2.8 Will close for now and re-open, if need be.