X11 logout on display :0 messes the behaviour of other X11 displays running at the same time
Working on any of the conventional desktop environments (KDE, mate, cinnamon, etc, wich usually run on the display :0 ), I am able to successfully launch a vnc xserver on display :1, and connect to it using a vncclient. As the vncserver works in the background, it continues to work even if I log out the (ie. KDE) session on display :0 .
After such a log out, :1 is still running, and I can connect to it again. However this time, trying to launch any graphical program inside the vncsession is not possible, and every application complains saying that they cannot connect to the :1 display:
$ xterm
No protocol specified
xterm: Xt error: Can't open display: :1
$ terminator
No protocol specified
/usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:57: GtkWarning: could not open display
warnings.warn(str(e), _gtk.Warning)
You need to run terminator in an X environment. Make sure $DISPLAY is properly set
Albeit they say that the $DISPLAY envvar is not set, it is correctly set indeed:
echo $DISPLAY
:1
I especulate that the logout procedure on :0 messed something (perhaps the X11 sockets for :1) in the vncserver, preventing newer applications to connect to :1, however, but I have not been able to figure it out.
This happens regardless the vncserver implementation (vncserver, vnc4server, tightvncserver.. etc).
Similarly, other remote display solutions as xpra get messed after logout, for instance display :100 get inaccessible, and xpra attach cannot connect, despite it still continues running in background.
Any ideas of what is causing this?
xorg display kde vnc xpra
asked 1 hour ago
aizquieraizquier
1763
add a comment |
Working on any of the conventional desktop environments (KDE, mate, cinnamon, etc, wich usually run on the display :0 ), I am able to successfully launch a vnc xserver on display :1, and connect to it using a vncclient. As the vncserver works in the background, it continues to work even if I log out the (ie. KDE) session on display :0 .
After such a log out, :1 is still running, and I can connect to it again. However this time, trying to launch any graphical program inside the vncsession is not possible, and every application complains saying that they cannot connect to the :1 display:
$ xterm
No protocol specified
xterm: Xt error: Can't open display: :1
$ terminator
No protocol specified
/usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:57: GtkWarning: could not open display
warnings.warn(str(e), _gtk.Warning)
You need to run terminator in an X environment. Make sure $DISPLAY is properly set
Albeit they say that the $DISPLAY envvar is not set, it is correctly set indeed:
echo $DISPLAY
:1
I especulate that the logout procedure on :0 messed something (perhaps the X11 sockets for :1) in the vncserver, preventing newer applications to connect to :1, however, but I have not been able to figure it out.
This happens regardless the vncserver implementation (vncserver, vnc4server, tightvncserver.. etc).
Similarly, other remote display solutions as xpra get messed after logout, for instance display :100 get inaccessible, and xpra attach cannot connect, despite it still continues running in background.
Any ideas of what is causing this?
xorg display kde vnc xpra
asked 1 hour ago
aizquieraizquier
1763
In each environment, run(echo "=== set ===";set;echo "===env ==="; env | sort;echo "=== alias ===";alias), redirecting the output to diferent files. Inspect these files withless, compare them withdiff. I haveat.environment batch.environment cron.environment interactive.environment interactive.ssh.environment non-gui.environment ssh.environment term.environmentfiles that help.
– waltinator
1 hour ago
add a comment |
Working on any of the conventional desktop environments (KDE, mate, cinnamon, etc, wich usually run on the display :0 ), I am able to successfully launch a vnc xserver on display :1, and connect to it using a vncclient. As the vncserver works in the background, it continues to work even if I log out the (ie. KDE) session on display :0 .
After such a log out, :1 is still running, and I can connect to it again. However this time, trying to launch any graphical program inside the vncsession is not possible, and every application complains saying that they cannot connect to the :1 display:
$ xterm
No protocol specified
xterm: Xt error: Can't open display: :1
$ terminator
No protocol specified
/usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:57: GtkWarning: could not open display
warnings.warn(str(e), _gtk.Warning)
You need to run terminator in an X environment. Make sure $DISPLAY is properly set
Albeit they say that the $DISPLAY envvar is not set, it is correctly set indeed:
echo $DISPLAY
:1
I especulate that the logout procedure on :0 messed something (perhaps the X11 sockets for :1) in the vncserver, preventing newer applications to connect to :1, however, but I have not been able to figure it out.
This happens regardless the vncserver implementation (vncserver, vnc4server, tightvncserver.. etc).
Similarly, other remote display solutions as xpra get messed after logout, for instance display :100 get inaccessible, and xpra attach cannot connect, despite it still continues running in background.
Any ideas of what is causing this?
xorg display kde vnc xpra
asked 1 hour ago
aizquieraizquier
1763
Working on any of the conventional desktop environments (KDE, mate, cinnamon, etc, wich usually run on the display :0 ), I am able to successfully launch a vnc xserver on display :1, and connect to it using a vncclient. As the vncserver works in the background, it continues to work even if I log out the (ie. KDE) session on display :0 .
After such a log out, :1 is still running, and I can connect to it again. However this time, trying to launch any graphical program inside the vncsession is not possible, and every application complains saying that they cannot connect to the :1 display:
$ xterm
No protocol specified
xterm: Xt error: Can't open display: :1
$ terminator
No protocol specified
/usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:57: GtkWarning: could not open display
warnings.warn(str(e), _gtk.Warning)
You need to run terminator in an X environment. Make sure $DISPLAY is properly set
Albeit they say that the $DISPLAY envvar is not set, it is correctly set indeed:
echo $DISPLAY
:1
I especulate that the logout procedure on :0 messed something (perhaps the X11 sockets for :1) in the vncserver, preventing newer applications to connect to :1, however, but I have not been able to figure it out.
This happens regardless the vncserver implementation (vncserver, vnc4server, tightvncserver.. etc).
Similarly, other remote display solutions as xpra get messed after logout, for instance display :100 get inaccessible, and xpra attach cannot connect, despite it still continues running in background.
Any ideas of what is causing this?
xorg display kde vnc xpra
xorg display kde vnc xpra
asked 1 hour ago
aizquieraizquier
1763
asked 1 hour ago
aizquieraizquier
1763
asked 1 hour ago
aizquieraizquier
1763
asked 1 hour ago
aizquieraizquier
1763
asked 1 hour ago
aizquieraizquier
1763
1763
In each environment, run(echo "=== set ===";set;echo "===env ==="; env | sort;echo "=== alias ===";alias), redirecting the output to diferent files. Inspect these files withless, compare them withdiff. I haveat.environment batch.environment cron.environment interactive.environment interactive.ssh.environment non-gui.environment ssh.environment term.environmentfiles that help.
– waltinator
1 hour ago
add a comment |
In each environment, run(echo "=== set ===";set;echo "===env ==="; env | sort;echo "=== alias ===";alias), redirecting the output to diferent files. Inspect these files withless, compare them withdiff. I haveat.environment batch.environment cron.environment interactive.environment interactive.ssh.environment non-gui.environment ssh.environment term.environmentfiles that help.
– waltinator
1 hour ago
In each environment, run
(echo "=== set ===";set;echo "===env ==="; env | sort;echo "=== alias ===";alias), redirecting the output to diferent files. Inspect these files with less, compare them with diff. I have at.environment batch.environment cron.environment interactive.environment interactive.ssh.environment non-gui.environment ssh.environment term.environment files that help.– waltinator
1 hour ago
In each environment, run
(echo "=== set ===";set;echo "===env ==="; env | sort;echo "=== alias ===";alias), redirecting the output to diferent files. Inspect these files with less, compare them with diff. I have at.environment batch.environment cron.environment interactive.environment interactive.ssh.environment non-gui.environment ssh.environment term.environment files that help.– waltinator
1 hour ago
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1127689%2fx11-logout-on-display-0-messes-the-behaviour-of-other-x11-displays-running-at-t%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1127689%2fx11-logout-on-display-0-messes-the-behaviour-of-other-x11-displays-running-at-t%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
In each environment, run
(echo "=== set ===";set;echo "===env ==="; env | sort;echo "=== alias ===";alias), redirecting the output to diferent files. Inspect these files withless, compare them withdiff. I haveat.environment batch.environment cron.environment interactive.environment interactive.ssh.environment non-gui.environment ssh.environment term.environmentfiles that help.– waltinator
1 hour ago