snap applications warn about XAUTHORITY path set by LightDM
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
snapd |
Triaged
|
Medium
|
Unassigned |
Bug Description
My $HOME resides on an NFS server with "root squash", therefore processes with effective user ID root(0) (and thus any application that I run with sudo) cannot access my ~/.Xauthority file, and as a result sudo or policy-kit rights elevation (e.g. for the gdebi-gtk package installer) fail for X11 GUI applications. As a workaround LightDM offers the option
user-
which I have set with
# echo -e '[LightDM]
as described in
https:/
As a result LightDM sets up my xauthority file instead at XAUTHORITY=
However, on Ubuntu {16,18,20}.04 /var/run -> /run is a symbolic link. As a result, each time I start a snap application (including non-X11 applications!), I get a warning of the form
# snap install pdftk
$ pdftk
2018/08/24 17:32:48.267771 cmd_run.go:442: WARNING: XAUTHORITY environment value is not a clean path: "/run/lightdm/
Why does snapd warn about the XAUTHORITY environment variable containing a symbolic link, even though a commonly used option (user-authority
What's wrong with symbolic links such as /var/run -> /run from snapd's point of view?
summary: |
- snapd complains about XAUTHORITY path set by LighDM + snapd complains about XAUTHORITY path set by LightDM |
summary: |
- snapd complains about XAUTHORITY path set by LightDM + snap applications complain about XAUTHORITY path set by LightDM |
summary: |
- snap applications complain about XAUTHORITY path set by LightDM + snap applications warn about XAUTHORITY path set by LightDM |
See also https:/ /github. com/canonical/ lightdm/ issues/ 151