nautilus lacking 'new document' in context menu on GNOME

Bug #1437502 reported by David González
This bug affects 27 people
Affects Status Importance Assigned to Milestone
Ubuntu GNOME
nautilus (Ubuntu)

Bug Description

As the title mentions nautilus is provided in its default state and there is no 'New Document' in the context menu.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: nautilus 1:3.14.2-0ubuntu6
ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
Uname: Linux 3.19.0-10-generic x86_64
ApportVersion: 2.16.2-0ubuntu5
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Mar 27 17:49:01 2015
GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']"
InstallationDate: Installed on 2015-03-27 (0 days ago)
InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Beta amd64 (20150326)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)

Related branches

Revision history for this message
David González (allenskd) wrote :
Revision history for this message
Tim Lunn (darkxst) wrote :

The exisitng patch for this is set to only show under Unity, probably can drop that check, since this would be useful under GNOME also.

Changed in ubuntu-gnome:
milestone: none → vivid
Revision history for this message
Sebastien Bacher (seb128) wrote :

Shouldn't Ubuntu GNOME report a bug upstream if they think it makes sense on all environment including GNOME?

Changed in nautilus (Ubuntu):
importance: Undecided → Wishlist
Changed in ubuntu-gnome:
status: New → Triaged
importance: Undecided → Low
milestone: vivid → xenial
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in nautilus (Ubuntu):
status: New → Confirmed
Changed in ubuntu-gnome:
assignee: nobody → Nikita Yerenkov-Scott (yerenkov-scott)
Changed in ubuntu-gnome:
assignee: Nikita Yerenkov-Scott (yerenkov-scott) → nobody
Changed in ubuntu-gnome:
milestone: xenial → yakkety
Changed in nautilus (Ubuntu):
status: Confirmed → Triaged
summary: - nautilus lacking 'new document' in context menu
+ nautilus lacking 'new document' in context menu on GNOME
Norbert (nrbrtx)
tags: added: yakkety
removed: amd64
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu Package testing tracker.

A list of all reports related to this bug can be found here:

tags: added: package-qa-testing
tags: added: zesty
removed: vivid
Revision history for this message
Anders Hall (a.hall) wrote :

For anyone ending up here, i lost this feature in 17.04 and need it: quick fix found at

    1. See if you have ~/Templates folder. Create one if it is missing using command:

        mkdir ~/Templates

    2. Now create an empty file from command prompt:

        touch ~/Templates/Text\ File.txt1

"Create Document" option is back again and you can create a new text file or a new document.

1the backslash is used to tell the shell that the space following it is part of the filename. Since the shell recognizes spaces are delimiters between commands/options/arguments, unless you "quote it" 'quote it' or quote\ it, the shell will treat whatever comes after the space as a separate argument.

Revision history for this message
Jeremy Soller (jackpot51) wrote :

I believe this applies again to Ubuntu 17.10.

Revision history for this message
Norbert (nrbrtx) wrote :

Bug exists in Ubuntu 17.10 final.

tags: added: artful
Revision history for this message
JLuc (jluc-q) wrote :

I confirm : Bug exists in released Ubuntu 17.10

Revision history for this message
Jeremy Bícha (jbicha) wrote :

I'm marking this a duplicate of bug 1632027, the bug for Ubuntu 16.10+. It is highly unlikely that we would make a UI change this late for 16.04 LTS without fixing the current development release first anyway.

Revision history for this message
hasan.magdy (hasan-magdy) wrote :
Revision history for this message
Charlie Daly (cdaly) wrote :

The workaround as suggested by Anders Hall is not very satisfactory because the first thing that you want to do after creating a new document is change the name. Previously, after creating the document you were immediately in a text field changing the name. Using the workaround, you have to select the document and select that you are changing the name before entering the name. It is pointless extra work.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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