Skip to content
Thomas Gläßle edited this page Oct 2, 2017 · 2 revisions

When reporting an issue, please provide the following information - loosely sorted by likeliness of relevance:

udiskie

Start udiskie from the command line in verbose mode and watch the output, e.g.:

udiskie -v

udisks (device properties)

Snapshot of device properties reported by udisks2:

  • udisksctl dump (snapshot, all devices)
  • udisksctl info -b /dev/sda1 (single device)
  • udisksctl info -p block_devices/sda1 (by DBUS name)
  • udisksctl monitor (continuous monitoring)
  • journalctl -n 20 -f -u udisks2.service (Udisks system log)

See also: https://www.freedesktop.org/wiki/Software/udisks/#bugs

polkit (for permissions problems)

Add a rule in/etc/polkit-1/rules.d/10-udisks.rules that logs which polkit permissions are queried:

polkit.addRule(function(action, subject) {
  var prefix = "org.freedesktop.udisks";
  if (action.id.slice(0, prefix.length) == prefix)
    polkit.log(action.id);
});

and then monitor the polkit system log:

journalctl -n 20 -f -u polkit.service

List all installed actions:

pkaction | grep udisks

udev (lower level device info)

  • udevadm info /dev/sdb1 (snapshot)
  • udevadm monitor --env (monitoring)

dbus

Observe actual communication between udisks2 and clients:

gdbus monitor --system --dest org.freedesktop.UDisks2

Explore dbus tree (system bus: org.freedesktop.UDisks2):

  • d-feet
  • qdbusviewer