desktop-packages team mailing list archive

[Bug Watch Updater <1460602@xxxxxxxxxxxxxxxxxx>]

Launchpad has imported 3 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=85477.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2014-10-26T10:10:54+00:00 intrigeri wrote:

Hi,

I'm using GNOME Disks 3.12.1-1+b1 on current Debian unstable, with
udisks2 (2.1.3-5), gvfs (1.22.1-1) and libatasmart4 0.19-3.

Steps to reproduce:

1. Blank a USB drive (dd if=/dev/zero)

2. Format that USB drive with GNOME Disks (default options: quick and
MBR)

3. Attempt to create a new partition+filesystem on that USB drive using
the "+" icon in GNOME Disks (default options, again: don't overwrite,
FAT, no label)

* I always get this error in a dialog:

  Error creating partition
  Error wiping newly created partition /dev/sdb1: Command-line `wipefs -a "/dev/sdb1"' exited with non-zero exit status 1:
  wipefs: error: /dev/sdb1: probing initialization failed: No such file or directory
  (udisks-error-quark, 0)

* The sdb1 partition is always created.

* Sometimes the FAT filesystem is created on this partition, sometimes
not.

* In any case, I can then reliably "Format" the newly created partition
with GNOME Disks and get a filesystem created as expected.

Seems like udisks is trying to act on a device before the device node
appears. The affected code seems to live in
src/udiskslinuxpartitiontable.c, that pretends to "sit and wait for the
partition to show up" before wiping the newly created partition, but
apparently doesn't reliably wait for the device node to appear in /dev.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1460602/comments/0

------------------------------------------------------------------------
On 2014-10-26T10:31:16+00:00 intrigeri wrote:

I retried the same when running udisksd without --no-debug. The journal
(for the partition+FS creation) says:

Oct 26 11:29:02 sid-desktop kernel:  sda: sda1
Oct 26 11:29:03 sid-desktop udisksd[1790]: 11:29:03.286:[1790]:[DEBUG]: uevent change /sys/devices/pci0000:00/0000:00:01.2/usb1/1-2/1-2.2/1-2.2:1.0/host8/target8:0:0/8:0:0:0/block/sda [udiskslinuxprovider.c:902, udisks_linux_provider_handle_uevent()]
Oct 26 11:29:03 sid-desktop udisksd[1790]: 11:29:03.287:[1795]:[INFO]: Cleanup check start [udisksstate.c:419, udisks_state_check_in_thread()]
Oct 26 11:29:03 sid-desktop udisksd[1790]: 11:29:03.287:[1795]:[INFO]: Cleanup check end [udisksstate.c:457, udisks_state_check_in_thread()]
Oct 26 11:29:03 sid-desktop udisksd[1790]: 11:29:03.771:[1790]:[DEBUG]: uevent add /sys/devices/pci0000:00/0000:00:01.2/usb1/1-2/1-2.2/1-2.2:1.0/host8/target8:0:0/8:0:0:0/block/sda/sda1 [udiskslinuxprovider.c:902, udisks_linux_provider_handle_uevent()]
Oct 26 11:29:03 sid-desktop kernel:  sda: sda1
Oct 26 11:29:03 sid-desktop udisksd[1790]: 11:29:03.817:[1790]:[DEBUG]: uevent remove /sys/devices/pci0000:00/0000:00:01.2/usb1/1-2/1-2.2/1-2.2:1.0/host8/target8:0:0/8:0:0:0/block/sda/sda1 [udiskslinuxprovider.c:902, udisks_linux_provider_handle_uevent()]
Oct 26 11:29:03 sid-desktop udisksd[1790]: 11:29:03.817:[1795]:[INFO]: Cleanup check start [udisksstate.c:419, udisks_state_check_in_thread()]
Oct 26 11:29:03 sid-desktop udisksd[1790]: 11:29:03.818:[1795]:[INFO]: Cleanup check end [udisksstate.c:457, udisks_state_check_in_thread()]
Oct 26 11:29:04 sid-desktop udisksd[1790]: 11:29:04.416:[1790]:[DEBUG]: uevent change /sys/devices/pci0000:00/0000:00:01.2/usb1/1-2/1-2.2/1-2.2:1.0/host8/target8:0:0/8:0:0:0/block/sda [udiskslinuxprovider.c:902, udisks_linux_provider_handle_uevent()]
Oct 26 11:29:04 sid-desktop udisksd[1790]: 11:29:04.416:[1795]:[INFO]: Cleanup check start [udisksstate.c:419, udisks_state_check_in_thread()]
Oct 26 11:29:04 sid-desktop udisksd[1790]: 11:29:04.416:[1795]:[INFO]: Cleanup check end [udisksstate.c:457, udisks_state_check_in_thread()]
Oct 26 11:29:05 sid-desktop udisksd[1790]: 11:29:05.004:[1790]:[DEBUG]: uevent change /sys/devices/pci0000:00/0000:00:01.2/usb1/1-2/1-2.2/1-2.2:1.0/host8/target8:0:0/8:0:0:0/block/sda [udiskslinuxprovider.c:902, udisks_linux_provider_handle_uevent()]
Oct 26 11:29:05 sid-desktop udisksd[1790]: 11:29:05.004:[1795]:[INFO]: Cleanup check start [udisksstate.c:419, udisks_state_check_in_thread()]
Oct 26 11:29:05 sid-desktop udisksd[1790]: 11:29:05.004:[1795]:[INFO]: Cleanup check end [udisksstate.c:457, udisks_state_check_in_thread()]
Oct 26 11:29:05 sid-desktop udisksd[1790]: 11:29:05.482:[1790]:[DEBUG]: uevent add /sys/devices/pci0000:00/0000:00:01.2/usb1/1-2/1-2.2/1-2.2:1.0/host8/target8:0:0/8:0:0:0/block/sda/sda1 [udiskslinuxprovider.c:902, udisks_linux_provider_handle_uevent()]

Reply at:
https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1460602/comments/1

------------------------------------------------------------------------
On 2015-08-21T14:25:06+00:00 intrigeri wrote:

Reproduced with udisks 2.1.6-2 on current Debian sid, this time in
Python, with any of direct D-Bus calls (both sync and async), libudisks
(both sync and async) and gdbus. This tends to confirm that the bug is
in UDisks2 itself.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1460602/comments/5


** Changed in: udisks
       Status: Unknown => Confirmed

** Changed in: udisks
   Importance: Unknown => Medium

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/1460602

Title:
  Erasing disk failed: Error wiping newly created partition

Status in udisks:
  Confirmed
Status in udisks2 package in Ubuntu:
  Confirmed
Status in udisks2 package in Debian:
  Confirmed

Bug description:
  I tried to erase a normal 8GB USB stick on up to date Ubuntu 15.04.
  This dialog appeared:

  org.freedesktop.DBus.Python.GLib.Error: Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/dbus/service.py", line 707, in _message_cb
      retval = candidate_method(self, *args, **keywords)
    File "/usr/share/usb-creator/usb-creator-helper", line 287, in Format
      partition = table.call_create_partition_sync(0, size, '0x0c', '', no_options, None)
  GLib.Error: udisks-error-quark: GDBus.Error:org.freedesktop.UDisks2.Error.Failed: Error wiping newly created partition /dev/sdc1: Command-line `wipefs -a "/dev/sdc1"' exited with non-zero exit status 1: wipefs: error: /dev/sdc1: probing initialization failed: No such file or directory
   (0)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: usb-creator-gtk 0.2.67ubuntu0.1
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Mon Jun  1 13:20:30 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-02-12 (108 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: usb-creator
  UDisksDump: Error: [Errno 2] No such file or directory: 'udisks'
  UpgradeStatus: Upgraded to vivid on 2015-05-12 (19 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/udisks/+bug/1460602/+subscriptions