<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix"><font face="FreeSerif">On 04/15/2018
09:41 PM, Karl Kleinpaste wrote:<br>
</font></div>
<blockquote type="cite"
cite="mid:f7b9d9df-ed82-d0da-256c-c4b6e23404b8@kleinpaste.org"><font
face="FreeSerif">I am in serious need of a huge clue. Anyone?</font></blockquote>
<font face="FreeSerif"><br>
I did git reset back to the 4.0.7 release. I still get no prefs
dialog. Whatever has gone wrong is somehow environmental in my
system.<br>
<br>
If I stuff up my own dummy routine in preferences_dialog.c...<br>
<br>
GVolumeMonitor *g_volume_monitor_get(void) { return NULL; }<br>
<br>
...I get lots of...<br>
<br>
(xiphos:16044): GLib-GObject-WARNING **: invalid (NULL) pointer
instance<br>
(xiphos:16044): GLib-GObject-CRITICAL **: g_signal_connect_object:
assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed<br>
<br>
...plus a bunch of...<br>
<br>
(xiphos:16044): GLib-GIO-CRITICAL **: g_volume_monitor_get_mounts:
assertion 'G_IS_VOLUME_MONITOR (volume_monitor)' failed<br>
(xiphos:16044): GLib-GIO-CRITICAL **:
g_volume_monitor_get_connected_drives: assertion
'G_IS_VOLUME_MONITOR (volume_monitor)' failed<br>
<br>
...but no functional change.<br>
<br>
If I take that out and instead insert a similar dummy for
g_unix_volume_monitor_init(), I stop getting all the warnings but
the behavior (no dialog) is the same.<br>
<br>
What has started asking for "volume monitoring," why has it begun
in the last 48 hours, how does it affect signal connections, and
why can't I get around it to see a prefs dialog? And why doesn't
it affect any other window's creation?<br>
<br>
This is the Xiphos developers' list. <i><b>Are there any actual
developers here, or am I talking to a wall?</b></i></font><br>
</body>
</html>