I'm using an FC3 box up-to-date. Recently, Abiword started crashing my X server upon start-up.
These messages popup in Xorg.0.log.old:
AUDIT: Tue May 17 21:46:42 2005: 5099 X: client 2 rejected from local host Auth name: MIT-MAGIC-COOKIE-1 ID: -1 AUDIT: Tue May 17 21:46:42 2005: 5099 X: client 4 rejected from local host Auth name: MIT-MAGIC-COOKIE-1 ID: -1 AUDIT: Tue May 17 21:46:42 2005: 5099 X: client 3 rejected from local host Auth name: MIT-MAGIC-COOKIE-1 ID: -1
*** If unresolved symbols were reported above, they might not *** be the reason for the server aborting.
Fatal server error: Caught signal 11. Server aborting
Versions info:
[ovidiu@Iris ~]$ rpm -qa 'xorg*' xorg-x11-font-utils-6.8.2-1.FC3.13 xorg-x11-deprecated-libs-6.8.2-1.FC3.13 xorg-x11-xauth-6.8.2-1.FC3.13 xorg-x11-twm-6.8.2-1.FC3.13 xorg-x11-libs-6.8.2-1.FC3.13 xorg-x11-xfs-6.8.2-1.FC3.13 xorg-x11-deprecated-libs-devel-6.8.2-1.FC3.13 xorg-x11-Mesa-libGL-6.8.2-1.FC3.13 xorg-x11-6.8.2-1.FC3.13 abiword-2.0.12-9 xorg-x11-Mesa-libGLU-6.8.2-1.FC3.13 xorg-x11-Xnest-6.8.2-1.FC3.13 xorg-x11-devel-6.8.2-1.FC3.13 xorg-x11-tools-6.8.2-1.FC3.13 [ovidiu@Iris ~]$ rpm -q abiword abiword-2.0.12-9
Any hints on what might cause it and put Abiword back on its feet? I fall asleep waiting for Oo.org Writer to start.
-- Ovidiu Lixandru linux360
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
