FreeBSD Plasma Integration
Open, Needs TriagePublic

Description

This task is for collecting FreeBSD Plasma integration issues, figuring out what needs to be done to get rid of HAL entirely, and generally making things better. It is prompted by the device notifier and attendant problems, but can probably be made much broader.

adridg created this task.Apr 15 2020, 8:52 AM

Bit of background, FreeBSD has HAL but is trying to get rid of it. It also has bsdisks, which is a FreeBSD implementation of the UDisks2 API -- this follows the "shim an appropriate API even if we don't like it" principle which was decided upon at the Devsummit at FOSDEM 2020. So in principle the Plasma (or Solid) code should just use the Linux API it needs from UDisks2 and FreeBSD will chase that.

Here's a screenshot of my device notifier. My machine has a CD-ROM drive. The drive contains an OpenBSD installer CD.

Should there be an "eject CD" button or option? Oh .. so the down-arrow button, with tooltip "click to make accessible from other applications", mounts the CD, and *then* changes to an eject button. So I can't eject an unmounted CD. When I click the eject button, the CD is unmounted, but does not eject.

If I mount the CD (e.g. by "make accessible from other applications") and then press the physical eject button (no applications are open on that mount), it does not eject. The disk stays mounted. I honestly don't know what behavior I expect, though.

arrowd added a subscriber: arrowd.Apr 15 2020, 9:23 AM

If I mount the CD (e.g. by "make accessible from other applications") and then press the physical eject button (no applications are open on that mount), it does not eject. The disk stays mounted. I honestly don't know what behavior I expect, though.

Hmmm. So, the filesystem gets mounted, but not unmounted? That's certainly strange.

Can you retry while running bsdisks in foreground? Any error messages? (You'd probably need to kill existing bsdisks process and then run it with sudo)