Bug 38472 - LibreOffice should offer a more sophisticated file dialog with shortcuts (places)
Summary: LibreOffice should offer a more sophisticated file dialog with shortcuts (pla...
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
(earliest affected)
Hardware: All Linux (All)
: medium enhancement
Assignee: Not Assigned
Depends on:
Blocks: File-Dialog
  Show dependency treegraph
Reported: 2011-06-19 10:06 UTC by ralf
Modified: 2018-01-02 10:18 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description ralf 2011-06-19 10:06:31 UTC
This was possible in a former version of openoffice.org.
Now, I don't find the option where to change the default 
file dialog to Qt or GTK components with more sophistication.

Especially the lack of shortcuts (places) is a big disadvantage.
It takes several clicks to get from




and back...

Comment 1 blendergeek 2017-04-19 17:55:18 UTC
I am using the current master (5.4 daily builds) on XUbuntu GNU/Linux 5.4
LibreOffice by default uses the system dialogs. And, LibreOffice's own dialog allows you to create shortcuts. 

I am changing to NEEDINFO.
Comment 2 QA Administrators 2017-12-04 12:46:03 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2018-01-02 10:18:50 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team