Bug 576461 - Cannot Create New Directories from GNOME's "Save As" Dialogue Box
Summary: Cannot Create New Directories from GNOME's "Save As" Dialogue Box
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gtk2
Version: 13
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-24 05:53 UTC by David Le Sage
Modified: 2011-06-27 15:16 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-27 15:16:15 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description David Le Sage 2010-03-24 05:53:01 UTC
Description of problem:
GNOME's "Save As" dialogue box cannot be used to create a new directory on the Desktop at present.

Version-Release number of selected component (if applicable):
GNOME 2.29.92 (Fedora 13 Alpha)

How reproducible:
100%

Steps to Reproduce:
1.  Load a web page in Firefox or Epiphany.
2.  File->Save As (GNOME's default "Save As" dialogue box appears.)
3. Navigate to Desktop.
4.  Click "Create Folder"
  
Actual results:
New folder momentarily appears, name selected so that user can rename it but then disappears again almost instantly.

Expected results:
New folder should not disappear again almost immediately.

Additional info:
This problem only occurs if using the dialogue box to create a new directory on the Desktop.  In other locations, it works correctly.

Comment 1 David 2010-05-29 22:42:56 UTC
I found this bug also effecting file-roller.

Its also in gnome 2.30

https://bugzilla.redhat.com/show_bug.cgi?id=597640

Comment 2 Fedora Admin XMLRPC Client 2010-06-23 09:22:35 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 3 Jiri Popelka 2010-06-23 10:17:05 UTC
As in bug #597640, comment #1, I'm also not able to reproduce this problem.
David, can you confirm that this problem is "fixed" and this bug can be closed ?

Comment 4 David 2010-06-23 12:54:51 UTC
Yes its been fixed by an update in updates-testing I have not seen it since

Comment 5 Bug Zapper 2011-06-02 15:58:11 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 6 Bug Zapper 2011-06-27 15:16:15 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.