Hi Gary, 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).
So that all tools like 'eject' and 'rmmount' and hal and dbus, and media-volume-manager (rmvolmgr) can be built with some debug info. I am not very familiar with dbus and hal but a good overview is at : https://iks.cs.ovgu.de/~elkner/s11/rmmount.html Right now thanks to the 'rollback' or downgrade of glib2 to glib 2.62 the automount of USB devices works fine. 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. The issue is important I think for users of OpenIndiana who use USB keyboard/mouse as obviously it is not funny if you loose keyboard or mouse access via USB because of this issue ... Anyway I am not really hit by this issue as I use PS/2 mouse/keyboard and because I am not familiar with the dbus/hal/rmvolmgr code my help is minimal I'm afraid, I'm glad to test out future updates on my system ... Regards, David Stes ----- Op 5 apr 2022 om 16:29 schreef gary mills [email protected]: > On Sun, Apr 03, 2022 at 07:13:45PM -0500, Gary Mills wrote: >> > [...] >> Here's the result with a BE where the USB automount did not work. >> Notice that there are two signals about 60 microseconds apart, and >> nothing more. Notice also that the columns do not align with the >> header: >> >> Script started on April 3, 2022 at 03:05:42 PM CDT >> <root@z400># dbus-monitor --system --profile >> #type timestamp serial sender destination path interface >> member >> # in_reply_to >> sig 1649016387.639814 2 org.freedesktop.DBus :1.60 >> /org/freedesktop/DBus org.freedesktop.DBus NameAcquired >> sig 1649016387.639882 4 org.freedesktop.DBus :1.60 >> /org/freedesktop/DBus org.freedesktop.DBus NameLost > > I suppose the original message contained too much information for > anyone to digest. Consider this instead: The output for a BE where > the USB automount succeeded began with a signal message: > > sig 1648934895.356888 306 :1.2 <none> > /org/freedesktop/Hal/Manager org.freedesktop.Hal.Manager DeviceAdded > > This is not an actual signal, but a bus message derived from the > signal. Note that the "DeviceAdded" message is entirely absent in the > output from the BE where USB automount did not work. I wonder if a > missing signal is responsible for the failure. > > -- > -Gary Mills- -refurb- -Winnipeg, Manitoba, Canada- > > _______________________________________________ > oi-dev mailing list > [email protected] > https://openindiana.org/mailman/listinfo/oi-dev _______________________________________________ oi-dev mailing list [email protected] https://openindiana.org/mailman/listinfo/oi-dev
