Apache OpenOffice (AOO) Bugzilla – Issue 56302
deadlock after opening non-existent document while modal dialog is present
Last modified: 2017-05-20 11:29:47 UTC
Here is how to reproduce the bug. 1. start openoffice from shell in background: /opt/openoffice.org2.0/program/soffice & 2. Wait until the 'OOo-writer' window appears and select menu item 'File - Open'. This opens a modal dialog. Leave this dialog open. 3. Go back to the shell and start openoffice with a non-existent file: /opt/openoffice.org2.0/program/soffice some-non-exiting-file 4. Now we have another dialog telling that the file could not be found. Try closing either of the dialogs. On my system neither dialog reacts on mouse clicks (to be precise: the fial dialog still reacts on button clicks and allows browing around in the file system; but any clicks on the Ok or Cancel buttons are ignored). This looks like a classic event-loop in the event-loop problem. IMHO the second invocation of openoffice should be blocked until the running openoffice program is in its idle loop (back in the main event loop).
Partly reproducible on Suse Linux 9.3. As long as the second dialog is shown, the file-picker doesn´t work. But the second dialog (the errormessage) can be closed and then, the file-picker works again. TM->HRO: please have a look, thanks !
Thanks for looking into this. Note that I am using the system dialogs (gtk). If I select preferences item 'Use openoffice.org dialogs' then I get the behavior you describe (2nd dialog can be closed). With the system dialogs, the 2nd dialog does not respond and the only way to quit openoffice is by a kill -9 pid. I think the problem is more general; any modal dialog that runs in its own event loop could probably cause this problem.
Guess this is rather P4. hro->pl: Can't please have a look on this ?
This seems to be an interaction between vcl modal dialogues and the gtk filepicker; could you please have a look ? Perhaps we need to arrange something regarding modality.
cmc->mmeeks: any bright ideas before I go into the hell that this is likely to lurk here.
Well - I'd like to see a stack trace to rule out multi-threaded evilness 1st :-) - though I guess that that's not an issue - since we actually see the warning dialog itself. I would imagine that it's a case of gtk+'s idea of handling modality fighting VCL's idea of how to handle modality ;-)
Created attachment 34110 [details] relevent bits of stacktrace
reassigning
Reset assigne to the default "issues@openoffice.apache.org".