File chooser not working in current folder

This seems like it may be a GTK bug and not a Deluge bug.

I couldn't decide what it was, I was in on Gnome, Nautilus or something similar but I guessed. Should I move it to GTK instead?

Thank you for your bug. Your description is not clear and lacks details. What version of Ubuntu do you use? Why can't you choose that directory? Do you get an error dialog? Which one? Could you describe easy steps to trigger the issue?

I use Ubuntu Gutsy Gibbon (7.10).

I can only guess why, the last directory used gets listed. I can't choose that directory if it is on an external drive. I have to activly choose a directory to be able to select that directory as my target. My workaround is that I select the previous directory and then click on the folder in the folderstructure. It can't be done if you only use the "history" or whatever that is above the directory tree.

I don't get an error, nothing happens. I've tried to see if the console spits something out but it doesn't.

My way of reproducing:
Using Deloge-torrent.
Loading torrent.
Last dir is on the external, so just OK.
Nothing happens.

Workaround:
Press on parent directory.
Choose the directory from the tree.
Press OK.

the description is not clear but that doesn't look like a gtk bug or other applications would have similar issues

Is this symptom still reproducible in 8.10 or 9.04?

I've seen this bug in file-roller too.
http://bugzilla.gnome.org/show_bug.cgi?id=556376

reassigning to file-roller and linking the upstream report, thanks.

This isn't a deluge-specific issue. I've experienced this myself with the file chooser in many applications. Linked more relevant upstream report.

This bug is indeed quite annoying. I have built a version using the upstream patch from http://bugzilla.gnome.org/show_bug.cgi?id=516714 available in my ppa:
https://edge.launchpad.net/~atreju-tauschinsky/+archive/ppa/
That version works fine for me, maybe someone else can test it as well?
Attached also a debdiff of this change.

thank you for your work there but unsubscribing the sponsor team for now we want to get the patch reviewed by the GNOME upstream before using it there

I believe bug #388074 is a duplicate of this bug, although they are described differently.

I think gnome-bugs #540788 (<http://bugzilla.gnome.org/show_bug.cgi?id=540788>) is related, if not exactly the same. If anybody's grovelling around in the code, could they take a peek at this as well?

From my comment on gnome-bugs:

"This bug drives me nuts on a fairly regular basis, I think the usual scenario
is when you want to save a file in the parent directory of the default
directory (the one which is displayed when the file selector is first shown):
clicking on the parent in the path bar (is that the right terminology?) changes
directory but leaves the subdir selected, so clicking save changes to the
subdir instead.

However, this doesn't happen consistently - it's only a problem if the focus is
on the file list and not the file name entry box, and I don't understand why
this is sometimes different. Is it something to do with the application
behaviour?"

So I know GNOME hasn't looked at the bug, but can't we get it into Karmic anyway until there is an "official" fix? I don't think we need GNOME to tell us that this fix is kosher. The bug is simply annoying and needs to be eradicated! When they implement it in their upstream is irrelevant to the Ubuntu operating system as a whole. And frankly if they've got a more "proper" fix for it, that's great, it can be implemented later. For now, let's put a bandaid over this papercut. It has been haunting the userbase for the past few versions of Ubuntu.

Here is a debdiff for Karmic based on the above patch. I have not tested it yet, but it looks very similar to a patch I came up with.

> Here is a debdiff for Karmic based on the above patch. I have not tested it yet, but it looks very similar to a patch I came up with.

Uploading non tested changes to a basis component as gtk is just not the way to do things no

Bug #390306: "file-roller extracts files to wrong directory when choosing a parent directory of the current one" might be related.
I reported it upstream as http://bugzilla.gnome.org/show_bug.cgi?id=586565

Please test patch at my PPA: https://launchpad.net/~xt-knight/+archive/ppa

Any hopes that this annoying usability bug will get patched in Karmic?

At least in Karmic Alpha6 (amd64), this bug is still found at least when using file-roller. I consider this bug actually quite fatal usability problem (and it has survived for years now...). How on earth user could possibly know that in order to get his/her files extracted to default location (usually /home/hername) he/she has to go up one directory and then back again? There is absolutely no feedback, it just does nothing when you hit "Extract".

Importance should definitely be "low" for severe usability problems like this.

Sorry, I meant "should definetly NOT be "low" for..."

This bug was fixed in the package gtk+2.0 - 2.19.7-0ubuntu2

---------------
gtk+2.0 (2.19.7-0ubuntu2) lucid; urgency=low

  * debian/patches/063_treeview_almost_fixed.patch:
    - change by Michael Vogt to add an ubuntu-almost-fixed-height-mode property,
      the change is required for software-center, adding as an ubuntu specific
      change for now until somebody comment on the upstream bug (lp: #514879)
  * debian/patches/064_initial_fileselector_select.patch:
    - change by Cody Russell to fix the default action not working in the
      gtkfileselector until you selected a directory (lp: #80755, #181788)
 -- Sebastien Bacher <email address hidden> Mon, 22 Mar 2010 14:23:46 +0100

My #1 papercut bug fixed, all praise you wizards! Hopefully upstream will also reach some conclusion.

Am I the only one who still (or again) has this bug in Lucid? Did work fine in Karmic though.

Not a bug in file-roller. Fix has landed in gtk+