Bug 1733814 - Attempting to benchmark disc terminates udisks2
Summary: Attempting to benchmark disc terminates udisks2
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: udisks2
Version: 30
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-07-28 22:07 UTC by James Ettle
Modified: 2019-07-30 07:31 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)

Description James Ettle 2019-07-28 22:07:14 UTC
Description of problem:
Attempting to benchmark a device using Gnome Disks causes udisks2 to SIGTERM.

Version-Release number of selected component (if applicable):
udisks2-2.8.2-1.fc30.x86_64
gnome-disk-utility-3.32.1-2.fc30.x86_64

How reproducible:
Always.

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.

Actual results:
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.

Expected results:
Benchmark begins. Other disks and udisks2 operations unaffected.

Comment 1 Tomáš Bžatek 2019-07-29 08:53:58 UTC
Please retest with https://bodhi.fedoraproject.org/updates/FEDORA-2019-65574a0e7a

Comment 2 James Ettle 2019-07-29 19:41:01 UTC
Still present with

udisks2-2.8.4-1.fc30.x86_64
libudisks2-2.8.4-1.fc30.x86_64
udisks2-iscsi-2.8.4-1.fc30.x86_64

Comment 3 Tomáš Bžatek 2019-07-30 07:16:52 UTC
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.

Comment 4 James Ettle 2019-07-30 07:31:31 UTC
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
Terminated

Nothing in coredumpctl. I tried under gdb but got nothing more than the above.


Note You need to log in before you can comment on or make changes to this bug.