OpenOffice.org崩溃，望老鸟相助

不熟的瓜 · 发表于 2009-9-1 15:04:26

今天遇到个情况，发现自己的openoffice打开时会出现一个
The KDE Crash Handler的对话框，上面具体内容如下：
General:
Short description
The application OpenOffice.org(soffice.bin) carshed and caused the signal 6(SIGABRT)

What is this?
An application terminates with a SIGABRT signal when it detects an internal inconsistency caused by a bug in the program

What can I do?
You might want to send a bug report for this application. Chedk if it is listed on http://bugs.kde.org,otherwise mail the author. Please includes as mush information as possible, maybe the original documents. If you have a way to reproduce the eeror, include this also

其跟踪错误记录如下：
System configuration startup check disabled.

[?1034h(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)
[Thread debugging using libthread_db enabled]
[New Thread 0x7f0f857a1700 (LWP 3301)]
(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)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#5  0x00007f0f80d115c5 in raise () from /lib64/libc.so.6
#6  0x00007f0f80d12bb3 in abort () from /lib64/libc.so.6
#7  0x00007f0f80d0a1e9 in __assert_fail () from /lib64/libc.so.6
#8  0x00007f0f81c20397 in _XRead () from /usr/lib64/libX11.so.6
#9  0x00007f0f78e7498a in ?? () from /usr/lib64/libGL.so.1
#10 0x00007f0f78e52aff in ?? () from /usr/lib64/libGL.so.1
#11 0x00007f0f78e4ebc3 in glXGetConfig () from /usr/lib64/libGL.so.1
#12 0x00007f0f7b368b66 in ?? ()
from /usr/lib64/ooo-2.0/program/libvclplug_gen680lx.so
#13 0x00007f0f7b38e2ce in SalDisplay::BestVisual ()
from /usr/lib64/ooo-2.0/program/libvclplug_gen680lx.so
#14 0x00007f0f7b390f8b in SalDisplay::initScreen ()
from /usr/lib64/ooo-2.0/program/libvclplug_gen680lx.so
#15 0x00007f0f7b39dab9 in vcl_sal::WMAdaptor::WMAdaptor ()
from /usr/lib64/ooo-2.0/program/libvclplug_gen680lx.so
#16 0x00007f0f7b39eecb in ?? ()
from /usr/lib64/ooo-2.0/program/libvclplug_gen680lx.so
#17 0x00007f0f7b39f5ae in vcl_sal::WMAdaptor::createWMAdaptor ()
from /usr/lib64/ooo-2.0/program/libvclplug_gen680lx.so
#18 0x00007f0f7b3930ea in SalDisplay::Init ()
from /usr/lib64/ooo-2.0/program/libvclplug_gen680lx.so
#19 0x00007f0f7b393fb5 in SalX11Display::SalX11Display ()
from /usr/lib64/ooo-2.0/program/libvclplug_gen680lx.so
#20 0x00007f0f7cae57e9 in ?? ()
from /usr/lib64/ooo-2.0/program/libvclplug_kde680lx.so
#21 0x00007f0f7cae5ace in ?? ()
from /usr/lib64/ooo-2.0/program/libvclplug_kde680lx.so
#22 0x00007f0f7cae5455 in create_SalInstance ()
from /usr/lib64/ooo-2.0/program/libvclplug_kde680lx.so
#23 0x00007f0f8532298f in ?? () from /usr/lib64/ooo-2.0/program/libvcl680lx.so
#24 0x00007f0f85323aea in ?? () from /usr/lib64/ooo-2.0/program/libvcl680lx.so
#25 0x00007f0f850d92c0 in InitVCL ()
from /usr/lib64/ooo-2.0/program/libvcl680lx.so
#26 0x00007f0f850d9667 in ?? () from /usr/lib64/ooo-2.0/program/libvcl680lx.so
#27 0x00007f0f850d9865 in SVMain ()
from /usr/lib64/ooo-2.0/program/libvcl680lx.so
#28 0x000000000042612d in main ()

不只是什么原因，望高手相助！

不熟的瓜 · 发表于 2009-9-1 15:06:12

对了，忘说了，关键是openoffice从此就打不开了，怎么修复啊

糊涂 · 发表于 2009-9-1 15:25:27

知道OOo的启动命令具体是哪个文件么？从一个终端窗口里运行，就在前台别加＆放后台，然后在终端窗口里看有输出什么报错或不正常的地方

马大瞎子 · 发表于 2009-9-1 23:13:30

在/opt/openoffice.org3/program>下，用“./soffice.bin”可以打开，用“.scalc”打开表格功能、用“.swriter”打开字处理。

不熟的瓜 · 发表于 2009-9-2 08:48:34

一般是在什么地方，叫什么名啊，刚接触这东西，不是很了解。

不熟的瓜 · 发表于 2009-9-2 08:50:55

Post by 糊涂;2022698
知道OOo的启动命令具体是哪个文件么？从一个终端窗口里运行，就在前台别加＆放后台，然后在终端窗口里看有输出什么报错或不正常的地方

在什么地方下，刚接触这东西，不是很清楚。

不熟的瓜 · 发表于 2009-9-2 08:55:47

Post by 马大瞎子;2022881
在/opt/openoffice.org3/program>下，用“./soffice.bin”可以打开，用“.scalc”打开表格功能、用“.swriter”打开字处理。

／opt／底下根本就没openoffice的这个文件夹，另外，我用的是2。0的，好像问题不是openoffice本身的问题，可能是KDE出现问题了，因为我在GNOME的环境下能够打开openoffice的，更奇怪的是在安全模式下也能打开openoffice。

yourfriend · 发表于 2009-9-2 09:17:25

对对，用终端命令行打开，提示会更友好。

马大瞎子 · 发表于 2009-9-2 16:36:55

find -name openoffice试试？或者find -name soffice.bin试试？不同版本的OOo可能安装目录不同，我用的是OOo3.0的一个改装版本，SuSE11.1+Gnome环境。

LinuxIsHard · 发表于 2009-9-2 20:20:52

检查下是不是缺了openoffice-kde包吧

		自动登录	找回密码
密码			注册