Issue 10753

Summary: Ctrl-Alt-Del shows Soffice not responding
Product: ui Reporter: farhiz <farhiz>
Component: uiAssignee: stefan.baltzer
Status: CLOSED DUPLICATE QA Contact: issues@ui <issues>
Severity: Trivial    
Priority: P3 CC: dan.strome, issues, oooqa
Version: OOo 1.0.1Keywords: oooqa
Target Milestone: ---   
Hardware: PC   
OS: Windows 98   
Issue Type: DEFECT Latest Confirmation in: ---
Developer Difficulty: ---
Description Flags
ctrl-alt-del screen shot none

Description farhiz 2003-01-18 09:58:38 UTC

I have noticed that after working in OOo for a while the ctrl-alt-del close 
program box shows 'Soffice not responding'.

If I don't end this task before quitting Windows then the machine goes into a 
hang state.

Not that big a problem but sure is when I'm trying to get other users to switch 
over to OOo.

Can anybody help?
Comment 1 farhiz 2003-01-18 10:03:11 UTC
Created attachment 4340 [details]
ctrl-alt-del screen shot
Comment 2 Frank Schönheit 2003-02-05 16:32:23 UTC
Farhiz, with the current description, the bug is hardly ro reproduce
(and thus hardly to fix). Please try to find common things which you
do before the problem happens - e.g. that you always have to open a
certain file or whatever. Or do you leave simply
unattended for a certain time? What do you do in this time with your
machine? Does the behaviour depend on the workload? Anything like this

(PS: There are rumors that the quickstarter on windows interferes with
e.g. Mozilla/Netscape, with the same effect as you describe -
soffice.exe hanging. Is it possible that this is what you encounter?)
Comment 3 farhiz 2003-02-06 10:40:51 UTC
Hi Frank, Could quite possibly be the reason as you mention. I 
haven't been able to quite catch what causes it to hang on my machine 
but I know for a fact that Eudora Pro makes OOo hang on other users 
Comment 4 danstrome 2003-02-07 20:32:02 UTC
I've just added a comment to issue 6809
that the QuickStarter for OOo 1.0.1 (Win98)
must be closed before the Eudora Pro email 
program will open completely.

It seems possible that these two issues are related.
Comment 5 prgmgr 2003-06-17 17:45:00 UTC
See issue 7037.

*** This issue has been marked as a duplicate of 7037 ***
Comment 6 prgmgr 2003-06-17 17:45:16 UTC