"Open location" dialog should not close on invalid path

Bug #385785 reported by David on 2009-06-11
This bug affects 5 people
Affects Status Importance Assigned to Milestone
One Hundred Papercuts
nautilus (Ubuntu)
Ubuntu Desktop Bugs

Bug Description

In nautilus, the "Open location" window (showed with CTRL+L) should stay open when an invalid path is used. This will let the user correct it's mistake and retry faster the corrected path.

upstream bug report : http://bugzilla.gnome.org/show_bug.cgi?id=512171

Changed in nautilus:
status: Unknown → New
Sebastien Bacher (seb128) wrote :

That's something easy to change, can be targeted for karmic if the design team confirm what is the best option

Changed in nautilus (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
importance: Undecided → Wishlist
status: New → Confirmed
Changed in hundredpapercuts:
status: New → Confirmed
summary: - Nautilus open location should not close on invalid path
+ "Open location" dialog should not close on invalid path
Changed in hundredpapercuts:
milestone: none → round-2
Changed in hundredpapercuts:
milestone: round-2 → round-1

Ideally, we would check for existence before the user clicks "Open", and enable/disable the Open button accordingly.

A second-best solution is to leave the "Open Location" dialog open when the "Could not find <location>" dialog is shown so the user can correct the error.

Changed in hundredpapercuts:
status: Confirmed → Triaged
assignee: nobody → David Siegel (djsiegel)
Changed in hundredpapercuts:
assignee: David Siegel (djsiegel) → nobody
Changed in hundredpapercuts:
milestone: round-1 → round-6

Setting the bug to "triaged" since it has enough information for a developer to work on it.

Changed in nautilus (Ubuntu):
status: Confirmed → Triaged

I'm working on this and will probably have an initial patch later this week.

Changed in hundredpapercuts:
assignee: nobody → Marcus Carlson (0-launchpad-mejlamej-nu)

If you're running karmic you could try this out from my PPA [1].
 - Makes the open location a little bit smarter and does not allow you to open a local path that doesn't exists and shows this by disabling the Open button and adding the text "Location does not exist" under the entry.
 - Opening a remote folder that cannot open now results in that the location dialog gets back to the user with the same path entered from start (as this bug describes)

Comments are welcome, will talk to upstream in the coming days.

[1] https://launchpad.net/~0-launchpad-mejlamej-nu/+archive/ppa

A. Walton (awalton) wrote :

Patch does blocking I/O (g_file_query_exists()), which is strictly prohibited in Nautilus.

A. Walton, thanks for reviewing the patch!
How do I solve this? Will g_file_query_info_async () do the trick?

A. Walton (awalton) wrote :

Ideally you'd want to use the NautilusFile machinery, since there's a better-than-good chance that the location being entered has already been cached, but NautilusFile isn't exactly the best way to tell if a file /isn't/ there, so you're almost forced to having to roll your own lookup stuff there (with query_async() and friends).

I'm not particularly in favor of this as it adds a whole lot of complexity to something that's pretty simple as it is, and potentially causes some really odd interface bugs, but I guess I shouldn't complain too loudly if I'm not doing the ground work on this ;).

A. Walton, I'm not sure I'm the right person for all the async stuff.

But if we look at the other part of the patch, the one that brings the open location dialog back after unsuccessfully opening a location. Does that look good enough to send upstream?

Alejandro Vidal (mancvso) wrote :

@Marcus: i really think this is enough... why make this complex?

dael99, work is progressing upstream - I now focus on getting the Open Location dialog back after failure to open the location. The first patch was not accepted by upstream because it was using blocking I/O.

Changed in hundredpapercuts:
milestone: round-6 → lucid-round-3
Vish (vish) wrote :

Marcus , any idea why the upstream bug has stalled?

Changed in hundredpapercuts:
importance: Undecided → Low

I'm waiting for someone (eg Alex) to review the patch. I could ping him on Monday again.

Vish (vish) on 2010-06-11
Changed in hundredpapercuts:
milestone: lucid-round-3 → none
milestone: none → maverick-round-1-file-management
Vish (vish) on 2010-07-20
Changed in hundredpapercuts:
status: Triaged → In Progress
Changed in nautilus:
importance: Unknown → Low
Vish (vish) on 2010-11-23
Changed in hundredpapercuts:
milestone: maverick-round-1-file-management → nt4-nautilus
Timothy Arceri (t-fridey) wrote :

No progress in a year changing back to confirmed

Changed in hundredpapercuts:
status: In Progress → Confirmed
Changed in hundredpapercuts:
assignee: Marcus Carlson (0-launchpad-mejlamej-nu) → Timothy Arceri (t-fridey)
milestone: nt4-nautilus → precise-1-file-management
Changed in hundredpapercuts:
status: Confirmed → In Progress
Changed in hundredpapercuts:
milestone: precise-1-file-management → quantal-6-file-management

What's the progress on this fix?

Timothy Arceri (t-fridey) wrote :

I no long have time to work on ubuntu. Also someone might need to check if this option is still in the new nautilus I thought I read somewhere this was something that got removed from the latest version.

Changed in hundredpapercuts:
status: In Progress → Triaged
assignee: Timothy Arceri (t-fridey) → nobody
Changed in hundredpapercuts:
milestone: quantal-6-file-management → papercuts-nautilus
Changed in hundredpapercuts:
milestone: papercuts-nautilus → papercuts-s-nautilus
Changed in nautilus:
status: New → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.