[OpenIndiana-discuss] More 2021.04.30 strangeness

[Reginald Beardsley]

I've started to transition all my computing to 2021.04.30 on the Z840.  I created a pair of pools, one with primary-cache=all and one with primary-cache=metadata.  The first is 4.3 TB RAIDZ2 and the second 3.8 TB RAIDZ1.  It's a 4x 4 TB disk set with a 1 TB NVMe SSD for the L2ARC, split 980 GB and 20 GB.  That all seems fine with the L2 persisting across a reboot.

I was getting logged out running as root so I did "unset autologout"  and hit return.  The mouse cursor then hid behind the mate-term and became inoperative.  I was forced to reboot via the soft power switch.

After the reboot .xsession-errors has this at the start:

root at hipster:~# more .xs*ors
mate-session-check-accelerated: Failed to run GL helper: Failed to execute child process “/usr/
lib/amd64/mate/mate-session-check-accelerated-gl-helper” (No such file or directory)
mate-session-check-accelerated: Failed to run GLES helper: Failed to execute child process “/us
r/lib/amd64/mate/mate-session-check-accelerated-gles-helper” (No such file or directory)

(mate-settings-daemon:1419): MateDesktop-WARNING **: 07:35:40.297: Call to screen_info_new is too
 frequent, skipping...

(mate-settings-daemon:1419): MateDesktop-WARNING **: 07:35:40.308: Call to screen_info_new is too
 frequent, skipping...
Window manager warning: Log level 128: unsetenv() is not thread-safe and should not be used after
 threads are created

(mate-settings-daemon:1419): MateDesktop-WARNING **: 07:35:41.528: Call to screen_info_new is too
 frequent, skipping...

(mate-settings-daemon:1419): MateDesktop-WARNING **: 07:35:41.531: Call to screen_info_new is too
 frequent, skipping...

(mate-settings-daemon:1419): MateDesktop-WARNING **: 07:35:41.531: Call to screen_info_new is too
 frequent, skipping...
Connection failure: Connection refused
pa_context_connect() failed: Connection refused
** Message: 07:35:42.669: Initializing gksu extension...
** Message: 07:35:42.984: Initializing gksu extension...
** Message: 07:35:43.158: Initializing gksu extension...


it then repeats the gksu messages 5-6 times per second

Does anyone know what is going on?  I've never seen this before.  GPU is an nVidia K5000 using the 390.141 driver.

Thanks,
Reg