Nautilus will show two paritions as mounted for a USB even after that USB had a new image written to it.

Bug #1853860 reported by Seija K.
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
New
Low
Unassigned

Bug Description

When the startup disk creator writes a new image to the disk, it still displays the partitions of the USB prior to the image being written, which is problematic because after the image is written, nautilus changes all of the partitions on the sidebar to the first partition on the USB, and attempting to click on any mounted drive other than the first one listed causes nautilus to give a disk error saying there may be a bad superblock as the drive could not be opened.

Steps to Reproduce:
1. Insert a USB Drive with multiple partitions
2. Mount two of those partitions
3. Write an image to the USB drive via Startup Disk Creator
4. Notice how Nautilus shows the drives as accessible
5. Wait until the image writing is complete
6. Go back to Nautilus
7. Notice how there are two entries for the USB with the new image on it
8. Click on the second entry

Expected Results:
1. Nautilus should not show USB drives that are having its entire contents formatted and repartitioned
2. Even if 1. was intended behavior, nautilus should only have the first partition of the usb with the new image written open
3. There should be no superblock error, as nautilus should not have gotten to the point in which it reports the error in the first place.

Actual Results:
Nautilus says it is unable to access the 2nd partition even though it is not even mounted because it displayed the partitions of the usb prior to the ubuntu image being written to the USB and did not update its UI to show the USB has a new name and only has one partition mounted (the first one with the OS info on it).

Description: Ubuntu 19.10
Release: 19.10

nautilus:
  Installed: 1:3.34.1-1ubuntu1
  Candidate: 1:3.34.1-1ubuntu1
  Version table:
 *** 1:3.34.1-1ubuntu1 500
        500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
        100 /var/lib/dpkg/status
10:1
This issue occurred on November 25, 2019, at around 10:10 - 10:15 AM, EDT.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: nautilus 1:3.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
Uname: Linux 5.3.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 25 09:58:04 2019
GsettingsChanges:
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'260'
 b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
InstallationDate: Installed on 2019-11-20 (4 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.apport.crashdb.conf: 2019-11-24T17:17:29.098099
usr_lib_nautilus:

Revision history for this message
Seija K. (rose128) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report, that looks like an upstream. Could you report it to them on https://gitlab.gnome.org/GNOME/nautilus/issues/ ?

Changed in nautilus (Ubuntu):
importance: Undecided → Low
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.