To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=75578
------- Additional comments from [EMAIL PROTECTED] Thu Apr 19 12:54:49 +0000 2007 ------- whitehat101: if you get the rpm in tar.gz from www.openoffice.org you can install those anywhere using the install_linux.sh script from mirrors OpenOffice.org/developer/install_scripts In my case I use my own build on GNU/Linux SPARC but the principle is the same. Now this bug happens on various linux platforms - intel x86, x86_64, sparc, SMP etc. It also affects different builds. There are 3 main builds now: (a) ooo-build (www.go-oo.org) builds (b) vanilla (community) builds (c) sun builds The main differences are: ooo-build - has some patches, quickstart enabled, online update built but not activated vanilla - no patches - includes enabled, online update is built but not activated sun - quickstart not enabled, online update is activated This bug seems to affect all three builds. The various distributions (debian, fedora etc) use the ooo-build. To get a backtrace - I was just lucky to catch the process at the right moment, or maybe the backtrace is not relevant, I dont know... Assume the office is froazen, and you ssh in from another machine. (1) get the process number $ ps ax | grep soffice.bin 20794 pts/0 Sl+ 1:31 /opt/o208/program/soffice.bin -enableautomation -norestore -nolockcheck -autocrashreport -accept=socket,host=localhost,port=65535;urp (2) attach gdb to the process $ gdb soffice.bin 20794 (3) get the backtrace (gdb) bt #0 0xf68100bc in poll () from /lib/libc.so.6 #1 0xf5369e48 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0xf5369e48 in ?? () from /usr/lib/libglib-2.0.so.0 Backtrace stopped: previous frame identical to this frame (corrupt stack?) Normally that is what will be seen when the process has NOT frozen. gdb seems to interfere with the running process. I was very lucky to catch something, or maybe it is not relevant. Also I ran gdb as root because a different user was running soffice.bin, but maybe you can do this without being root. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
