On Tue, Apr 05, 2022 at 05:12:41PM +0200, s...@pandora.be wrote: > I think the most difficult thing is to setup a development system > (build system) to further test this issue (which is now fortunately > solved - for the moment - by the rollback of the glib2 version to > 2.62).
Not for me, it's not. I have half-a-dozen OI systems running on bare hardware: no virtualization here. The rollback is a temporary solution, until this bug is found. > I am not very familiar with dbus and hal but a good overview is at : > > https://iks.cs.ovgu.de/~elkner/s11/rmmount.html Yes, that web page looks useful. I haven't looked at it in detail yet. > On my OpenIndiana system, if I insert a USB device and monitor it with : > > $ dbus-monitor --session --profile | grep RemoteVolumeMonitor > > I see events on the dbus-monitor output like : > > 1. DriveConnected > 2. DriveChanged > 3. VolumeAdded > 4. VolumeMount > 5. VolumeChanged > 6. MountAdded > If a build system with glib2 and debug info is setup by someone > then perhaps it is possible to figure out where the "DriveConnected" > is happening when the USB removable drive is added. I haven't looked at "--session" output for some time, although I have looked at "--system" output. Running a BE where the USB automount fails, there is virtually no output from "dbus-monitor". -- -Gary Mills- -refurb- -Winnipeg, Manitoba, Canada- _______________________________________________ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev