Bug#296298: openoffice.org: OOo fails to detect itself having crashed
Package: openoffice.org
Version: 1.1.3-4
Severity: normal
If the user logs out without having quit OOo first (including cases like X crashed
etc.), OOo will remain running, unaware that it should quit itself.
When the user logs back in and tries to run OOo, no window appears because OOo
finds the "running session" and tries to open the new window there, but since that
X display no longer exists, nothing happens (from the user's viewpoint).
It is especially strange that if Ooo tries to open a new window in a non-existent
X display, it does not detect that X has crashed, as if the window can open
successfully without errors even without a functional X.
The user has to "killall -9 soffice.bin" to make OOo become responsive again.
Steps to reproduce:
1. Log in (e.g., to Xfce4)
2. Run oowriter (e.g.)
3. Log out without quitting oowriter first
4. Log back in and try to open some Ooo document
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.28-ow1
Locale: LANG=zh_TW.Big5, LC_CTYPE=zh_TW.Big5 (charmap=BIG5)
Versions of packages openoffice.org depends on:
ii dictionaries-common [openoffi 0.24.7 Common utilities for spelling dict
ii openoffice.org-bin 1.1.3-4 OpenOffice.org office suite binary
ii openoffice.org-debian-files 1.1.3-3+1 Debian specific parts of OpenOffic
ii openoffice.org-l10n-en [openo 1.1.3-4 English (US) language package for
ii ttf-opensymbol 1.1.3-4 The OpenSymbol TrueType font
-- no debconf information
Reply to: