That was a temporary disablement of gnome-shell-private-connection.patch The patch has since been rebased and re-applied (multiple times already)