Issue 97854 - kdefilepicker is not closing, when oo is closed
Summary: kdefilepicker is not closing, when oo is closed
Alias: None
Product: gsl
Classification: Code
Component: code (show other issues)
Version: OOo 2.4.1
Hardware: Unknown All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2009-01-07 22:50 UTC by gokcen
Modified: 2013-07-29 17:55 UTC (History)
1 user (show)

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


Note You need to log in before you can comment on or make changes to this issue.
Description gokcen 2009-01-07 22:50:52 UTC
Since kdefilepicker does not provide a modal dialog, when dialog is open, users
can close the application, and if is closed, kdefilepicker is not
closed and still exists. In addition, if you select a file in this case,
document recovery screen comes up.

Steps to reproduce:
1- Open a new Writer document
2- Issue ctrl+o to open a kdefilepicker dialog.
3- Close the Writer application and kdefilepicker still exists.

kdefilepicker must be a modal dialog that doesn't allow users to make any
changes in the window behind, or all applications should kill any
kdefilepicker during exit.
Comment 1 philipp.lohmann 2009-01-08 09:02:35 UTC
This is peculiar since OOo does not use the kde file picker; do you perhaps mean
the gtk file picker ? Or are you using a modified version which perhaps uses the
kde file picker like e.g. go-oo which comes with SuSE or debian ?
Comment 2 gokcen 2009-01-08 09:24:04 UTC
Yes, in Pardus Linux we use a go-oo build of[1] which uses ooh680-m17.
Since we are a KDE distro, it's very useful to use KDE style dialogs. 

If gtk dialogs are started in a similar way (as a new process), perhaps this bug
is valid for gtk dialogs, too. But I've not tried.

Comment 3 philipp.lohmann 2009-01-08 09:32:31 UTC
@kendy: this seems to be a gooo special, would you handle the kde file picker ?
Comment 4 kendy 2009-01-08 13:29:19 UTC
gokcen: Well, from various reasons, the KDE fpicker is an external application 
which causes the problems you mentioned & will not be that easy to fix, 
unfortunately...  The best way would be to re-do it to an internal 
implementation, but it's not that easy :-(