Ubuntu
gtk+3.0 package

File save as dialog doesn't switch to keyed in path anymore when pressing enter

Bug #1577879 reported by ADFH on 2016-05-03

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	GTK+	Incomplete	Undecided	Unassigned
	gtk+3.0 (Ubuntu)	Incomplete	Low	Unassigned

Bug Description

Not sure if this is in Nautilus or a GTK package or something else..

I run Unity as my desktop environment at the moment. With a recent update, the file save dialog presented to me by Firefox appears to have changed. I'm pretty sure it's an OS dialog and not a Firefox specific control, but please feel free to bounce this to whichever package is responsible for the File Save As dialog generated by Firefox 46.0 in Ubuntu now.

In the past, when the save dialog came up, I was able to enter a path (absolute or relative) in the filename field:
* If it was a directory path that existed, the directory contents would be shown inside the window, allowing me to then specify a name
* If it was a directory path that didn't exist, it'd take me to the deepest part of the path that did match
* If it was a directory that did exist, and a filename that didn't, it'd save as that filename in that folder

The last is still true, but the others aren't anymore.. Say I have structure:

home
.../folder
....../sub2
....../sub3

... and I last saved into sub3 and I want to save into sub2, if I remove the filename from the name box, and I type ../sub2 and press enter, it doesn't navigate to the folder anymore.. The auto-complete function seems more reliable now, and it knows the folder exists, but the only way to actually show its contents now would be to click through the tree..

This feels like a functionality downgrade. I should be able to type a pathname into the filename area of the dialog, press enter, and have it take me to that particular folder.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: nautilus 1:3.14.2-0ubuntu13
ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
Uname: Linux 4.2.0-35-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Wed May 4 03:29:09 2016
GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'group', 'where', 'mime_type', 'owner', 'permissions', 'date_accessed']"
InstallationDate: Installed on 2016-01-21 (103 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)

See original description

Tags:

ADFH (adfh) on 2016-05-03

description:

updated

Revision history for this message

Sebastien Bacher (seb128) wrote on 2016-05-04:

unsure what firefox changed but it seems an issue on their side

affects:

nautilus (Ubuntu) → firefox (Ubuntu)

Revision history for this message

Sebastien Bacher (seb128) wrote on 2016-05-04:

could be a gtk issue in fact, do you get the bug using e.g gedit?

Revision history for this message

ADFH (adfh) wrote on 2016-05-06:

example.png Edit (133.8 KiB, image/png)

gvim does not do the same thing, and to create a new folder, it has "Create Folder" button.

gedit DOES do the same thing, and to create a new folder, it has a "+" button.

In the screenshot "example.png", you can see that the current folder is "folder1" and I've typed in ../folder2 and pressed enter and it hasn't switched to folder2, rather it's remained in the current folder.

This would seem to suggest the fact that it's not unique to Firefox and therefore something to do with underlying library.

Revision history for this message

ADFH (adfh) wrote on 2016-05-19:

... so this bug probably needs to be bounced to a GTK package.. but which one?

Revision history for this message

Sebastien Bacher (seb128) wrote on 2016-05-19:

The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

affects:	firefox (Ubuntu) → gtk+3.0 (Ubuntu)
Changed in gtk+3.0 (Ubuntu):
importance:	Undecided → Low

Revision history for this message

ADFH (adfh) wrote on 2016-05-20:

Done :)

Revision history for this message

Sebastien Bacher (seb128) wrote on 2016-05-20:

thanks!

Changed in gtk+3.0 (Ubuntu):
status:	New → Triaged

Bug Watch Updater (bug-watch-updater) on 2016-05-20

Changed in gtk:
importance:	Unknown → Medium
status:	Unknown → Confirmed

Revision history for this message

ADFH (adfh) wrote on 2016-05-26:

Upstream asking for my specific version of GTK, and says to contact Ubuntu maintainers first (I already have, and I linked this ticket too as per instructions).

I'm aware that distributions have their own version numbers for things - and I'm currently running an up to date Ubuntu Wily:

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 15.10
Release: 15.10
Codename: wily

How can I get them the specific version number they're after?

Revision history for this message

ADFH (adfh) wrote on 2016-05-26:

#10

hogan@AH01:~$ apt-cache show libgtk-3-0
Package: libgtk-3-0
Priority: optional
Section: libs
Installed-Size: 11573
Maintainer: Ubuntu Developers <email address hidden>
Original-Maintainer: Debian GNOME Maintainers <email address hidden>
Architecture: amd64
Source: gtk+3.0
Version: 3.16.7-0ubuntu3
Provides: gtk3-binver-3.0.0

... I'm assuming this means I'm running 3.16.7, they're talking about not having the issue in 3.20 or 3.21. That said, the issue didn't come about until relatively recently, and you've advised it's something upstream, so have they released a patch recently to older release that has a regression perhaps?

Revision history for this message

Sebastien Bacher (seb128) wrote on 2016-05-26:

#11

if you are on 15.10 you have 3.16.7 indeed, the issue is not new is just that firefox was using gtk2 and is using gtk3 now

Revision history for this message

ADFH (adfh) wrote on 2016-05-27:

#12

Ok.. reported GTK version to upstream.

Bug Watch Updater (bug-watch-updater) on 2017-09-14

Changed in gtk:
status:	Confirmed → Expired

Revision history for this message

Walter Garcia-Fontes (walter-garcia) wrote on 2017-09-15:

#13

I have tried this functionality in Ubuntu 17.10 with Unity and the original behavior seems to be back. Can anybody confirm if this is still an issue?

Changed in gtk:
importance:	Medium → Undecided
status:	Expired → New
status:	New → Incomplete
Changed in gtk+3.0 (Ubuntu):
status:	Triaged → Incomplete

Revision history for this message

naught101 (naught101) wrote on 2018-01-15:

#14

GTK's file dialogue is still annoying in 17.10, yes. It would be great if there was a way to always show the location bar, instead of the useless breadcrumb bar.

@ADFH, where is the bug you reported upstream? Can you please post a link?

Revision history for this message

ADFH (adfh) wrote on 2018-01-26:

#15

https://bugzilla.gnome.org/show_bug.cgi?id=766696
... but they basically put it back to Ubuntu saying packages I had from Ubuntu at the time weren't their bleeding edge, so it wasn't their issue.

It kiiinda sorta works now in 17.06 (I'm staying with 17.06 until they have remote desktop sorted out with Wayland for the moment) - but it can randomly tack on bits of filename, autocomplete style, at times... or pressing enter sometimes will or won't work.. it may be slightly confused by the fact in my folder heirarchy (which exists inside of a bind mount) I have things like:

Parent/
   A/
     apple/
     aardvark/
   B/
     badger -> ../../A/apple