After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 722569 - Nautilus shows 'Me' as owner instead of user name
Nautilus shows 'Me' as owner instead of user name
Status: RESOLVED DUPLICATE of bug 680282
Product: nautilus
Classification: Core
Component: general
3.8.x
Other Linux
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2014-01-19 21:37 UTC by bryant.eadon
Modified: 2014-01-19 22:27 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description bryant.eadon 2014-01-19 21:37:08 UTC
re-opening from this ticket : https://bugzilla.gnome.org/show_bug.cgi?id=680282

What happens
============
Nautilus is displaying 'Me' as owner of my files, when 'Me' is not the owner of
my files.

What should happen
==================
I expect Nautilus to display the the owner of a file or folder in the 'Owner'
column (and other places like the 'Preferences > Permissions' tab).

Version info
============
GNOME nautilus 3.8.2

The owner field in nautilus should always refer to the named user, not a "soft" name : 'Me' or 'me'. Those people who need this field will enable it within nautilus and expect the actual named user be displayed.  Notably, displaying the Owner is not enabled by default.  Power users should be expected to handle real usernames and times.

Reasons include : users could be named 'Me' more often now that the installer is easier for the normal user :

>>"Since "me" could be a local username and usernames will probably not be capitalized."

I don't believe this is a strong argument to keep the behaviour of displaying "Me".
Comment 1 António Fernandes 2014-01-19 22:27:41 UTC
Thanks for taking the time to write this report.
This issue is not fundamentally different form the one which has been reported before. Could you please raise your concerns in the original reports rather than opening a duplicate in order to help us keep our bug tracking system organized?

*** This bug has been marked as a duplicate of bug 680282 ***