Public bug reported:
Description
When launching Nautilus (file manager) from the terminal embedded in
Visual Studio Code using the command `nautilus .`, closing Nautilus
causes it to fail to reopen via normal means (e.g., launcher or
terminal). A system restart is required to restore functionality.
Steps to Reproduce
1. Open Visual Studio Code.
2. Use Visual Studio Code to open a folder in any workspace.
3. Open the integrated terminal within Visual Studio Code (`Ctrl + ``).
4. In the terminal, run the following command:
```
nautilus .
```
5. Close the Nautilus window that opens.
6. Attempt to open Nautilus again via:
- The Ubuntu application launcher.
- A terminal command such as `nautilus .`.
7. Observe that Nautilus does not open.
8. Restarting the computer restores the ability to open Nautilus normally.
Expected Behavior
Nautilus should be able to reopen normally after being launched and closed from
the VSCode terminal.
Actual Behavior
Nautilus does not reopen after being closed when it was initially launched from
the VSCode terminal. No error message is displayed, and there is no apparent
recovery mechanism aside from restarting the system.
#### Additional Information
Ubuntu Version: 24.10 LTS
VSCode Version:
1.95.3
f1a4fb101478ce6ec82fe9627c43efbf9e98c813
x64
Nautilus Version: GNOME nautilus 47.0
Kernel Version: 6.11.0-9-generic
Workaround
Restarting the system resolves the issue temporarily.
Possible Cause
This issue might be related to how Nautilus handles its processes when launched
from VSCode. It is possible that a process remains running in the background,
preventing a new instance from starting.
ProblemType: Bug
DistroRelease: Ubuntu 24.10
Package: nautilus 1:47.0-1ubuntu1
ProcVersionSignature: Ubuntu 6.11.0-9.9-generic 6.11.0
Uname: Linux 6.11.0-9-generic x86_64
ApportVersion: 2.30.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov 26 13:33:47 2024
InstallationDate: Installed on 2024-05-01 (209 days ago)
InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64
(20240220)
ProcEnviron:
LANG=en_IN
LANGUAGE=en_IN:en
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=<set>
SourcePackage: nautilus
UpgradeStatus: Upgraded to oracular on 2024-11-24 (2 days ago)
usr_lib_nautilus:
file-roller 44.3-1
nautilus-extension-gnome-terminal 3.54.0-1ubuntu1
python3-nautilus 4.0.1-1
** Affects: nautilus (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug oracular
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/2089650
Title:
nautilus file manager crashes upon opening it with vscode terminal and
never opens again
Status in nautilus package in Ubuntu:
New
Bug description:
Description
When launching Nautilus (file manager) from the terminal embedded in
Visual Studio Code using the command `nautilus .`, closing Nautilus
causes it to fail to reopen via normal means (e.g., launcher or
terminal). A system restart is required to restore functionality.
Steps to Reproduce
1. Open Visual Studio Code.
2. Use Visual Studio Code to open a folder in any workspace.
3. Open the integrated terminal within Visual Studio Code (`Ctrl + ``).
4. In the terminal, run the following command:
```
nautilus .
```
5. Close the Nautilus window that opens.
6. Attempt to open Nautilus again via:
- The Ubuntu application launcher.
- A terminal command such as `nautilus .`.
7. Observe that Nautilus does not open.
8. Restarting the computer restores the ability to open Nautilus normally.
Expected Behavior
Nautilus should be able to reopen normally after being launched and closed
from the VSCode terminal.
Actual Behavior
Nautilus does not reopen after being closed when it was initially launched
from the VSCode terminal. No error message is displayed, and there is no
apparent recovery mechanism aside from restarting the system.
#### Additional Information
Ubuntu Version: 24.10 LTS
VSCode Version:
1.95.3
f1a4fb101478ce6ec82fe9627c43efbf9e98c813
x64
Nautilus Version: GNOME nautilus 47.0
Kernel Version: 6.11.0-9-generic
Workaround
Restarting the system resolves the issue temporarily.
Possible Cause
This issue might be related to how Nautilus handles its processes when
launched from VSCode. It is possible that a process remains running in the
background, preventing a new instance from starting.
ProblemType: Bug
DistroRelease: Ubuntu 24.10
Package: nautilus 1:47.0-1ubuntu1
ProcVersionSignature: Ubuntu 6.11.0-9.9-generic 6.11.0
Uname: Linux 6.11.0-9-generic x86_64
ApportVersion: 2.30.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov 26 13:33:47 2024
InstallationDate: Installed on 2024-05-01 (209 days ago)
InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64
(20240220)
ProcEnviron:
LANG=en_IN
LANGUAGE=en_IN:en
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=<set>
SourcePackage: nautilus
UpgradeStatus: Upgraded to oracular on 2024-11-24 (2 days ago)
usr_lib_nautilus:
file-roller 44.3-1
nautilus-extension-gnome-terminal 3.54.0-1ubuntu1
python3-nautilus 4.0.1-1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2089650/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
