Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
nautilus
nautilus
  • Project
    • Project
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 263
    • Issues 263
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 13
    • Merge Requests 13
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GNOME
  • nautilusnautilus
  • Issues
  • #423

Closed
Open
Opened May 11, 2018 by Ads20000@Ads200002 of 2 tasks completed2/2 tasks
  • Report abuse
  • New issue
Report abuse New issue

nautilus process takes a considerable time to exit after closing all Files windows

Steps to reproduce

  1. Run Files (nautilus or nautilus .) from Terminal.
  2. Notice that you're not dropped back to the Terminal prompt, even when you close Files.

Reproducible in:

  • Flatpak unstable
  • Other: Files 3.26.3-0ubuntu4 on Ubuntu 18.04

Current behavior

Files doesn't drop the user back to Terminal prompt after closing.

Expected behavior

Files should drop the user back to Terminal prompt after closing.

Additional information

Ubuntu bug
The original reporter said that it was a problem that Files didn't drop back to prompt immediately (apparently it did before 3.4.1, how come?) but I think it can be more reasonably be raised as a problem that it doesn't drop back to Terminal prompt after being closed. I know that it remains running in the background but can the process be 'forked' (I'm guessing this is the context the original bug title meant for it) so that the user can be dropped back to the Terminal prompt when Files is closed? How useful would it be to fix this bug? Not very? Maybe this can be marked Expected Behaviour and closed?

Edited Dec 17, 2018 by António Fernandes
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
No due date
2
Labels
1. Bug 5. CLI
Assign labels
  • View project labels
Reference: GNOME/nautilus#423