Bugzilla – Bug 1065398
LibreOffice file chooser dialog does not remember last used size
Last modified: 2017-10-27 20:42:34 UTC
Created attachment 746118 [details] Default file chooser size for LO write Leap 42.2 x86_64 This isn't a showstopper, but it is annoying as all get-out. The file chooser dialog for libreoffice does not remember its last used size. Every time you open a file, you have to resize the dialog to be able to see your directory names and you have to resize the total width to be able to see your file information. I have used LO for years and it always remembered the last used size of the file dialogs. Now after the switch to gtk+3, that does not work. I end up having to resize that thing every time I use writer or calc. Before, that information was properly saved in ~/.config/gtk-2.0/gtkfilechooser.ini. There is no similar file in ~/.config/gtk-3.0 and nothing related to the file chooser. Is there another file that should capture the chooser width and height? I've included a couple of screenshots showing just how bad this is. The second will follows as a separate attachment.
Created attachment 746119 [details] Chooser dimensions after resize that allow use of the dialog
I can reproduce this but the issue is more for the upstream authors rather than issue only in the openSUSE. Please report this to upstream maintainers so they can resolve it: https://bugs.documentfoundation.org/
Tomas, Why are we closing bugs that need to be addressed upstream? I've been here for more than a decade and suse maintainers have always coordinated with upstream after the bug was filed here. That way if there were any additions that require packaging changes, the maintainers know and it gets fixed. I have never had a bug closed and the user told to just go file upstream -- that's how issues fall through the cracks. You have no way of knowing whether this reproducible bug will ever be reported anywhere other than here. This bug should stay open until it is resolved upstream. Your lucky today, because I did go further and did report the bug upstream: https://bugs.documentfoundation.org/show_bug.cgi?id=113487 They may also want to review this bug, and it very much helps if it is an open bug but pending upstream resolution.