So it looks like basics are all in place and it should be possible to do this without an app crash.
FYI, I am using R28.1 release. I have run “sudo apt update” and “sudo apt-get upgrade”, followed by fixing any case of a broken libglx.so instance (this would show up under the “sha1sum -c /etc/nv_tegra_release” comamnd).
I removed my monitor and ran “ssh -Y ubuntu@<my_jetson_address>”. I ran this as user ubuntu on command line:
A GUI shows up on my host, and this GUI represents the previous settings…if I have edited screen lock settings before, then the GUI I see now correctly uses those settings. These are presumably the settings you are in need of changing.
On a TX2 (this is a TX1 forum) I get the same error (“Segmentation fault” and crash) you got if I have no monitor attached. Can I verify this is a TX1? I assume it probably is a TX1, and that the problem is some other difference between packages you have and packages I have.
The interesting thing on the TX2 is that the unity-control-center-dbgsym package cannot be installed (required for running in a debugger to see the exact cause of the seg fault)…not even by forcing. For whatever reason this is not allowed because it thinks the package which is already in place is the wrong package…but the package it requests is the package which is in place. Perhaps a stray character exists (such as a space) in some part of the dpkg file such that the package displays a different name than what other packages see it as.
Just FYI, if a package update breaks libglx.so, it will appear something like this in “sha1sum -c /etc/nv_tegra_release”:
If this happens, you have a backup at:
The way I fix libglx.so if it breaks is:
rm -f libglx.so
ln -sf /usr/lib/aarch64-linux-gnu/tegra/libglx.so .
# Then reboot...
I give this information because I want to make sure your packages are up to date for the packages we might have in common. Run the package updates for your TX1:
sudo apt update
sudo apt-get upgrade
# Verify files are correct...
sha1sum -c /etc/nv_tegra_release
With all files in place, and with all files updated, does your TX1 still fail “unity-control-center screen” after “ssh -Y” to the Jetson?
EDIT: strace seems to show this screen modifies through “/run/user/1000/dconf/”, but this is a temp file system without a real file. On the other hand, there is an app called “dconf-editor”. I’m thinking one of the values this editor can reach might be the same as using that GUI, though I don’t know which it would be.
YET ANOTHER EDIT: This might be it…dconf-editor is something you should explore. This app has a “search” function, and although lots of things have “lock” in their name (such as “clock”), I see this attribute which is a boolean toggle:
disable-...lots of things..
…these are under desktop->applications->lockdown. With my auto idle set to one hour, I see parameter desktop->applications->session:idle-delay set to 3600…in seconds this is one hour. Try “0”.