- Ubuntu sudo says no protocol specified how to#
- Ubuntu sudo says no protocol specified install#
- Ubuntu sudo says no protocol specified software#
- Ubuntu sudo says no protocol specified password#
- Ubuntu sudo says no protocol specified windows#
TLDR Is this standard practice and the way this should be done, to achieve separation between root and other user account? It seems like a "hack" to me. So if you started the X server under your own account (greg) then any other user (like root) doesn't have access to it."
Ubuntu sudo says no protocol specified windows#
You don't want just anybody opening windows on your screen, do you. Try running this command as non-root user: xhost + and then run the app with root. It looks like either the display port is not opened in your system or it is disabled. The DISPLAY variable pointing to the correct display (usually :0) Almost yours: 2 weeks, on us 100+ live channels are waiting for you with zero. xhost si:localuser:root sudo your-graphical-app Restore the default permissions: xhost -si:localuser:root Solution 2. "This has to do with access control to your X server. Accessing the X server requires two things: 1. What was the point in granting access to the other user if they can't open the program anyway? This separating is done for security reasons, so isn't making that above modification reverting the earlier comment 'export AUTHORITY=/home/greg/.Xauthority'."
Ubuntu sudo says no protocol specified software#
Or root can take it, because it can access your files: scottscott-MS-7596: sudo synaptic No protocol specified Unable to init server: Could not connect: Connection refused (synaptic:2675): Gtk-WARNING : cannot open display: :0 scottscott-MS-7596: They want you to use graphical userinterfaces designed to work with super user priveleges, like the software center. You (greg) can grant it by means of 'xhost local:root'. "You have two ways to get this working: grant it or have root take it. And the gtk-warning cannot open display seems to relate exactly to this issue. The "no protocol specified" part seems pretty straight forward.
Ubuntu sudo says no protocol specified how to#
Now, with the Admin screen displayed, here's how to set.
Ubuntu sudo says no protocol specified password#
I get the following error: no protocol specified For Ubuntu, you can enter your regular user name and password (assuming you have sudo privileges). But when I try to start wireshark as the wireshark user, using: sudo -s -u $USER wireshark Try running this command as non-root user: xhost + and then run the app with root. No protocol specified terminate called after throwing an instance of (anonymous namespace)::DisplayError what (): No display available. At the end, have a look at the Troubleshooting section to see commons issues and how to solve them. In subsequent sections, we see an explanation of the instructions so that you can easily port of other Linux distributions.
Ubuntu sudo says no protocol specified install#
Xsecurity manpage or the X Security extension spec.I am setting up wireshark to run as non root user, a la here, that is: sudo apt-get install wireshark It looks like either the display port is not opened in your system or it is disabled. Step 1 is only required if you run the deb package of LXD. If you want to know more about those things I suggest reading the Contains encrypted passwords for users who are defined in the passwd file. (make screenshots, do keylogging and other nasty stuff) and it is even Other graphical (X11) client could sniff data from the remote machine This last option can open security problems. Some security settings you'll receive an error instead.īut if you use ssh -Y remotemachine the remote machine is treated as Machine and receives the graphical output. So your local client sends a command to the remote If you use ssh -X remotemachine the remote machine is treated as an
or just ForwardX11 in /etc/ssh/ssh_config, then run $ ssh -Y, to enable trusted X11 forwarding, don't know the exact cause but I'm guessing with -X some features expire after some time, probably to increase security. If you have this problem after some time when running with -X arg. Note: IP is the local workstation’s IP where you want the GUI If not using sudo, then you can also just add xhost local:docker It worked for me at least, running on Elementary OS (Ubuntu 16.04). If you still get the “cannot open display” error, set the DISPLAY You can open any GUI application which will open it without any issue. Switch back to default user and execute xhost again. You can use xhost to limit access for X server for security reasons. $ ssh -XĮnable trusted X11 forwarding, by using the -Y option, $ ssh -YĪfter opening ssh connection to the remote host as explained above, 3 Answers Sorted by: 7 When executing the command xhost, you are probably receiving No protocol specified xhost: unable to open display ':0' Issue is your user is not allowed to access the X server. While doing ssh use the option -X to enable X11 forwarding. $ xhost +Īccess control disabled, clients can connect from any host
You can allow clients to connect from any host. From xhost+ : How to Fix “Cannot Open Display” Error While Launching GUI on Remote Server:Īnswer: You can fix the “cannot open display” error by following the xhost procedure mentioned in this article.Īllow clients to connect from any host using xhost+Įxecute the following command to disable the access control, by which
0 kommentar(er)
