Issue 58334 - broken session management in Linux
Summary: broken session management in Linux
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: General
Classification: Code
Component: ui (show other issues)
Version: 680m140
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: thorsten.martens
QA Contact: issues@framework
URL:
Keywords: needmoreinfo
Depends on:
Blocks:
 
Reported: 2005-11-23 10:29 UTC by avagula
Modified: 2006-03-07 15:40 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description avagula 2005-11-23 10:29:30 UTC 
Open new file in OO.o, write some text, do not save - and log out from window 
manager - no warning about unsaved changes, oo.o just closes. 
When logging in again, OO.o shows splash screen and goes to invisible mode. No 
try to restore document. 
SuSE 10, tried with KDE and Gnome (dm as KDM).
Comment 1 lars 2005-11-23 22:15:55 UTC 
on Windows XP SP2 OOo-dev 2.0.139 asks to save changes before it is closed on 
log off .
Comment 2 thorsten.martens 2005-11-24 11:20:03 UTC 
Check auto-recovery settings in tools/options/load-save/general. If the checkbox
is checked, all done information should be saved in the background while the
Linux session manager closes the session. No dialog will appear. When logging in
again, OOo should start automatically, loading previous used documents.
Comment 3 avagula 2005-11-24 18:01:41 UTC 
Yes, I know all you say. This does not work in SuSE 10 and as an user said in
9.3 too. Tried with kde, gnome and xvwm, displaymanagers kdm and gdm. 
OO.o is community build by Pavel Janik (m140). 
In 9 cases from 10 oo.o started when logging in, showed splash and went to
background. In one case (Gnome/gdm) OO opened Writer window with empty document.
I'm trying to find user who can confirm this.
Comment 4 thorsten.martens 2005-11-25 10:09:56 UTC 
TM->vagula: Maybe the timeout, the session manager gives for closing
applications when shutting down, is too short. So OOo doesn´t have a chance to
save the needed information (same effect like cutting the wire).
Comment 5 Olaf Felka 2006-03-07 15:39:42 UTC 
I can't reproduce with OOo 2.0.2. Is it still a problem for you?
Comment 6 Olaf Felka 2006-03-07 15:40:59 UTC 
.