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.
This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '30'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 30 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
This bug persists in Fedora 32 Live ISO when attempting to benchmark an internal drive on an M-Book Speedmind netbook.
(In reply to Alex Villacís Lasso from comment #6)
> This bug persists in Fedora 32 Live ISO when attempting to benchmark an
> internal drive on an M-Book Speedmind netbook.
Great! Can you please grab a backtrace and post it here? Please check `coredumpctl` if there were any crashes. Also ABRT I think could be useful here.
I'm not currently seeing this with udisks2-2.8.4-4.fc32 -- how about you Alex?
I am still experiencing this with udisks2-2.8.4-4.fc32 . In my case, the block device is an internal flash device that shows up as a SD card reader, yet is the device from which the system boots up.
BTW, there is absolutely no mention of udiskd crashing at all from the coredumpctl listing, or any ABRT report. It looks as if the program simply decides to terminate normally.
I have reproduced this with a different card reader, that shows up as /dev/mmcblk1. The boot device shows up as /dev/mmcblk0. But card readers exposed via USB that show up as /dev/sdX do NOT trigger the bug.