GNOME Bugzilla – Bug 47054
Accessed date not shown in properties dialog for directories
Last modified: 2014-08-25 18:23:04 UTC
On the "basic" tab, files show 'modified' and 'accessed' date stamps for the file (that can be compared with the same-name fields from the 'stat' shell command). Directories never show the 'accessed' date stamp or its text label. See parent bug 40880 for historical reference. ------- Additional Comments From brett@eazel.com 2001-02-26 13:59:43 ---- I suggest that this is NOT a 1.0 bug .. ------- Additional Comments From sullivan@eazel.com 2001-02-26 15:08:34 ---- We should make sure we understand this clearly at some post-1.0 point. The code is deliberately not showing the accessed date for directories because to the best of my knowledge it was useless. But maybe it isn't useless; I or someone should investigate this further. ------- Additional Comments From eli@eazel.com 2001-03-26 11:13:33 ---- QA Assigning to self. ------- Bug moved to this database by unknown@bugzilla.gnome.org 2001-09-09 21:03 -------
Changing to "old" target milestone for all bugs laying around with no milestone set.
This is still valid for the properties dialog. For the tab/pane however in both cases only the modified date is shown. I tested this with version 2.1.2
*** Bug 140254 has been marked as a duplicate of this bug. ***
Created attachment 38693 [details] [review] This fixes the bug
Sdhakar: Thanks for your patch! Returning always TRUE in should_show_accessed_date makes the function useless. Therefore, you should just remove the function and adapt the caller code. I wonder why this code is there at all and whether "trash:" returns a correct access date.
Still occurs with Nautilus 2.16.1 on Ubuntu Edgy.
Created attachment 93515 [details] [review] Always show folders accessed date Trivial patch based on the previous attachment. should_show_accessed_date() and the conditional in create_basic_page() are simply removed. I don't know how to test the attributes of trash:, and none shows up in the Information tab. This was tested only on 2.18.3 and then adapted for trunk, so please test there.
What is the use case for this?
(In reply to comment #8) > What is the use case for this? Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!