Description of problem:
Attempting to benchmark a device using Gnome Disks causes udisks2 to SIGTERM.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Attach/insert device to benchmark (in this particular case an SD card on /dev/mmcblk0).
2. Open Gnome Disks.
3. Select the device, open Benchmark.
4. Click Start Benchmark, then Start Benchmarking.
5. Enter admin password when prompted.
Message box 'Remote peer disconnected (g-dbus-error-quark, 4)'.
In the system journal: 'udisks2.service: Main process exited, code=killed, status=15/TERM'
udisks2 is dead at this point -- newly-attached devices aren't noticed, at least until Gnome Disks is restarted.
Benchmark begins. Other disks and udisks2 operations unaffected.
Please retest with https://bodhi.fedoraproject.org/updates/FEDORA-2019-65574a0e7a
Still present with
Interesting, thanks for the test. Could you try finding related udisks2.service messages within the system journal? Something that would indicate an error. Alternatively please have a look at the output of coredumpctl if there's a coredump of udisksd and attach a backtrace here if so.
Can't see anything incriminating in journalctl -u udisks2. When I ran udisksd -d on the console all I got was:
udisks-Message: 08:21:51.191: udisks daemon version 2.8.4 starting
udisks-Message: 08:21:51.474: Acquired the name org.freedesktop.UDisks2 on the system message bus
Nothing in coredumpctl. I tried under gdb but got nothing more than the above.