gedit can't run in root terminal

This isn't a bug with the release upgrader, the software that provides release upgrades, rather with the system after the release upgrade. Subsequently, I am removing the package.

Status changed to 'Confirmed' because the bug affects multiple users.

Is there a workaround for this bug?

Yes, I just found a workaround yesterday.

I discovered that root is handed a definition of the environment variable XAUTHORITY that points to a non-existent directory:

    root@login:~# echo $XAUTHORITY
    /tmp/libgksu-OgwC1o/.Xauthority
    root@login:~# ls $XAUTHORITY
    ls: cannot access /tmp/libgksu-OgwC1o/.Xauthority: No such file or directory

 This makes it impossible to run any GUI-based program as root.

I worked around this by adding the following to root's .bashrc file:

    export XAUTHORITY=~/.Xauthority
    cp /home/<myhome>/.Xauthority $XAUTHORITY

It would appear that libgksu is the source of this problem.

Thanks Phil Wolff,

Your workaround works like a charm.

BTW, using Phil Wolff's workaround solved another problem I had trying to open android SDK from root's command line.

This is still a bug in Ubuntu 16.04. In my case, it comes from running a gui (synaptic package manager) as root inside a tiger vncserver session. It runs fine in the last vncserver it was run in, but from the real desktop console it conks out with the following error:

```root@ubuntu1604-p6720f:~# synaptic
No protocol specified
Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused

(synaptic:23495): Gtk-WARNING **: cannot open display: :1
root@ubuntu1604-p6720f:~# DISPLAY=:0 synaptic
No protocol specified
Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused

(synaptic:23624): Gtk-WARNING **: cannot open display: :0
root@ubuntu1604-p6720f:~# ```

As shown, even if I specify the exact display to open, it refuses to run in the main desktop. For whatever reason, Mir isn't running. I have no clue what that is. It also says "No protocol specified" -- is there a way to work around it by specifying a protocol?

Also, I tried Phil Wolff's workaround and it didn't work.

Here's an alternative method that works for me. Enter this to allow all local users to launch GUI windows: (Enter exactly as shown, including the final colon.)

xhost +local:

Or, more extreme (may not be secure without running a firewall):

xhost +

To undo, enter:

xhost -

I don't need to type sudo to run these commands when I enter them as my local user that has X authority (if I'm understanding the situation correctly).