On Thu, Mar 19, 2009 at 09:14:19PM -0400, Wendy Elmer wrote: > There is no difference when running it as you said. There is no output > to the terminal. I have used abiword before.
Thanks for trying. > Whenever I click on the X to kill the abiword window it doesn't > respond and a little while later a window pops up saying the > application is not responding do I want to force quit. Please get me a backtrace of where abiword hangs. You'll have to recompile abiword with debugging symbols and install debugging symbols for various libraries. In short (http://wiki.debian.org/HowToGetABacktrace has background information): $ cd /tmp [or somewhere else where you don't mind stuff lying around] $ sudo aptitude install build-essential fakeroot $ sudo apt-get build-dep abiword $ DEB_BUILD_OPTIONS=nostrip,noopt apt-get --build source abiword $ sudo dpkg -i abiword*.deb $ sudo aptitude install libglib2.0-0-dbg libgtk2.0-0-dbg $ gdb abiword [...] (gdb) set logging on (gdb) set pagination 0 (gdb) run [wait until abiword hangs, interrupt it by hitting Ctrl+C in the terminal] (gdb) thread apply all backtrace full (gdb) quit Do you really want to quit? yes ... and attach gdb.txt, which is located wherever you started gdb, in this case probably /tmp/gdb.txt. Kind regards, Patrik
signature.asc
Description: Digital signature
