Bug 176483 – directory modification date falls back to 1970 after copying

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 176483 - directory modification date falls back to 1970 after copying

Summary:	directory modification date falls back to 1970 after copying

Status:	CLOSED RAWHIDE

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	nautilus (Show other bugs)
Sub Component:
Version:	4
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Alexander Larsson
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2005-12-23 03:31 EST by rob versluis
Modified:	2007-11-30 17:11 EST (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2006-01-12 10:39:39 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description rob versluis 2005-12-23 03:31:16 EST

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050922 Fedora/1.0.7-1.1.fc4 Firefox/1.0.7

Description of problem:
The new copy of a directory becomes always the modification date of 1970-01-01.
The system clock is up to date, and the directory copied has a current date.

Version-Release number of selected component (if applicable):
nautilus-2.10.0-4

How reproducible:
Always

Steps to Reproduce:
1. right click on a directory icon, choose copy
2. navigate to an other location and choose paste
3. 
  

Actual Results:  the new directory shows the '1970' date

Expected Results:  the new directory should show the date from the origianal or the current date.

Additional info:

Comment 1 Alexander Larsson 2006-01-12 10:39:39 EST

This should be fixed in gnome-vfs2 2.11.1

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