The default WebKit2Gtk "decide-destination" method used in MiniBrowser gets the default downloads destination using G_USER_DIRECTORY_DOWNLOAD and the XDG specification. XDG settings may not be present in very bare home directories like when using a chroot. This causes a failure when deciding the destination through the default method.
This problem can be corrected locally in MiniBrowser but it may be worth correcting actually in the default method implemented by the WebKit2Gtk library.
Created attachment 204427 [details] Patch
Added Enrique to CC.
Comment on attachment 204427 [details] Patch This looks good to me, but I think this is actually a bug in the default implementation of decide-destination. Let's fix it in WebKitDownload and all other apps using the API will benefit from it. Note that in this case we would be updating the internal destination to NULL and emitting the notify signal.
(In reply to comment #4) > (From update of attachment 204427 [details]) > This looks good to me, but I think this is actually a bug in the default implementation of decide-destination. Let's fix it in WebKitDownload and all other apps using the API will benefit from it. Note that in this case we would be updating the internal destination to NULL and emitting the notify signal. True. Moving then to the proper component.
Created attachment 205068 [details] Patch
Thanks for the patch. If this patch contains new public API please make sure it follows the guidelines for new WebKit2 GTK+ API. See http://trac.webkit.org/wiki/WebKitGTK/AddingNewWebKit2API
Comment on attachment 205068 [details] Patch Sorry for the delay reviewing it, it looks good to me, thanks!
Comment on attachment 205068 [details] Patch Clearing flags on attachment: 205068 Committed r152155: <http://trac.webkit.org/changeset/152155>
All reviewed patches have been landed. Closing bug.
(In reply to comment #8) > (From update of attachment 205068 [details]) > Sorry for the delay reviewing it, it looks good to me, thanks! Thanks to you for the review!