Am 01.04.22 um 19:31 schrieb [email protected]:
So this new upgrade is again in fact a downgrade or regression to

https://download.gnome.org/sources/glib/2.62/glib-2.62.6.tar.xz

In any case now the rmvolmgr rmmount seems to work (again) for me ...
Yes, I downgraded it again after your report. Also my system didn't work
anymore as expected after the latest illumos-gate updates.
As I have stated in another mail, I also have problems with this
version, only less often.


Regards
David Stes


----- Op 1 apr 2022 om 19:25 schreef Andreas Wacknitz [email protected]:

Am 01.04.22 um 19:00 schrieb [email protected]:
Good news ! I can update https://www.illumos.org/issues/14226 again ...

But this time to report success.

There was an update of "media-volume-manager" which now has glib2 2.70 as a
require.

# rmmount -l and # eject -l  report the removable media.

I just tried to insert a USB key in my system and it automounts immediately on
my OI workstation.

# pkg list media-volume-manager hal glib2 dbus
NAME (PUBLISHER)                                  VERSION                    IFO
library/glib2                                     2.70.0-2022.0.0.1          i--
This is the fake glib-2.70.0 version. You can check it with pkg info
glib2. It will show you which sources have been used to create it...

service/hal                                       0.5.11-2022.0.0.21026      i--
service/storage/media-volume-manager              0.5.11-2022.0.0.21026      i--
system/library/dbus                               1.12.20-2020.0.1.1         i--

# pkg contents -t depend media-volume-manager
TYPE    FMRI
require pkg:/system/library/[email protected]
require pkg:/shell/[email protected]
require pkg:/library/[email protected]
require pkg:/[email protected]
require pkg:/service/[email protected]
require pkg:/system/library/[email protected]
require pkg:/service/storage/[email protected]
require pkg:/system/[email protected]
require pkg:/system/library/[email protected]
require consolidation/osnet/osnet-incorporation


Perhaps some of the packages involved  (I suspect "media-volume-manager") was
not the right version.

When debugging this there seems to be a command :

     dbus-monitor --session

that can be used to follow what is going on.

Regards,
David Stes

_______________________________________________
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
_______________________________________________
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

Reply via email to