Showing login XRDP screen once, when trying login user its disappearing again its showing RDP setup screen
Using Ubuntu 14.04 LTS and installed XRDP and XFCE4 after this, when I am executing sudo service xrdp restart it shows a message:
It looks like xrdp is allready running,
if not delete the xrdp.pid file and try again
Getting XRDP Sesman-Xvnc login screen, trying login it automatically again reverts to the RDP setup screen.
Kinldy help me on this issue.
xrdp
edited Jan 31 at 15:49
maria
136113
asked Jan 31 at 13:36
mahesh surwarmahesh surwar
12
add a comment |
Using Ubuntu 14.04 LTS and installed XRDP and XFCE4 after this, when I am executing sudo service xrdp restart it shows a message:
It looks like xrdp is allready running,
if not delete the xrdp.pid file and try again
Getting XRDP Sesman-Xvnc login screen, trying login it automatically again reverts to the RDP setup screen.
Kinldy help me on this issue.
xrdp
edited Jan 31 at 15:49
maria
136113
asked Jan 31 at 13:36
mahesh surwarmahesh surwar
12
add a comment |
Using Ubuntu 14.04 LTS and installed XRDP and XFCE4 after this, when I am executing sudo service xrdp restart it shows a message:
It looks like xrdp is allready running,
if not delete the xrdp.pid file and try again
Getting XRDP Sesman-Xvnc login screen, trying login it automatically again reverts to the RDP setup screen.
Kinldy help me on this issue.
xrdp
edited Jan 31 at 15:49
maria
136113
asked Jan 31 at 13:36
mahesh surwarmahesh surwar
12
Using Ubuntu 14.04 LTS and installed XRDP and XFCE4 after this, when I am executing sudo service xrdp restart it shows a message:
It looks like xrdp is allready running,
if not delete the xrdp.pid file and try again
Getting XRDP Sesman-Xvnc login screen, trying login it automatically again reverts to the RDP setup screen.
Kinldy help me on this issue.
xrdp
xrdp
edited Jan 31 at 15:49
maria
136113
asked Jan 31 at 13:36
mahesh surwarmahesh surwar
12
edited Jan 31 at 15:49
maria
136113
asked Jan 31 at 13:36
mahesh surwarmahesh surwar
12
edited Jan 31 at 15:49
maria
136113
edited Jan 31 at 15:49
maria
136113
edited Jan 31 at 15:49
maria
136113
136113
asked Jan 31 at 13:36
mahesh surwarmahesh surwar
12
asked Jan 31 at 13:36
mahesh surwarmahesh surwar
12
asked Jan 31 at 13:36
mahesh surwarmahesh surwar
12
12
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
If pgrep xrdp shows no xrdp actually running, locate xrdp.pid will find the file (or read the documentation) that you should delete.
progname.pid files are traditionally used as lock files. That is, a program that wants to prevent 2 copies running at the same time will write it's PID into a progname.pid file, and plan to remove it when exiting. If a normal exit is precluded (User types ^C, system crashes, etc) the .pid file can be left hanging around.
Once you locate xrdp.pid, it's content should be the PID of the program that created it. ps -fp followed by the PID will show you the current status. E.g. ps -fp $(cat xrdp.pid). If ps shows nothing, the process that created the file no longer exists, and xrdp.pid can be deleted without worry.
answered Jan 31 at 14:25
waltinatorwaltinator
22.4k74169
add a comment |
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%2f1114410%2fshowing-login-xrdp-screen-once-when-trying-login-user-its-disappearing-again-it%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
If pgrep xrdp shows no xrdp actually running, locate xrdp.pid will find the file (or read the documentation) that you should delete.
progname.pid files are traditionally used as lock files. That is, a program that wants to prevent 2 copies running at the same time will write it's PID into a progname.pid file, and plan to remove it when exiting. If a normal exit is precluded (User types ^C, system crashes, etc) the .pid file can be left hanging around.
Once you locate xrdp.pid, it's content should be the PID of the program that created it. ps -fp followed by the PID will show you the current status. E.g. ps -fp $(cat xrdp.pid). If ps shows nothing, the process that created the file no longer exists, and xrdp.pid can be deleted without worry.
answered Jan 31 at 14:25
waltinatorwaltinator
22.4k74169
add a comment |
If pgrep xrdp shows no xrdp actually running, locate xrdp.pid will find the file (or read the documentation) that you should delete.
progname.pid files are traditionally used as lock files. That is, a program that wants to prevent 2 copies running at the same time will write it's PID into a progname.pid file, and plan to remove it when exiting. If a normal exit is precluded (User types ^C, system crashes, etc) the .pid file can be left hanging around.
Once you locate xrdp.pid, it's content should be the PID of the program that created it. ps -fp followed by the PID will show you the current status. E.g. ps -fp $(cat xrdp.pid). If ps shows nothing, the process that created the file no longer exists, and xrdp.pid can be deleted without worry.
answered Jan 31 at 14:25
waltinatorwaltinator
22.4k74169
add a comment |
If pgrep xrdp shows no xrdp actually running, locate xrdp.pid will find the file (or read the documentation) that you should delete.
progname.pid files are traditionally used as lock files. That is, a program that wants to prevent 2 copies running at the same time will write it's PID into a progname.pid file, and plan to remove it when exiting. If a normal exit is precluded (User types ^C, system crashes, etc) the .pid file can be left hanging around.
Once you locate xrdp.pid, it's content should be the PID of the program that created it. ps -fp followed by the PID will show you the current status. E.g. ps -fp $(cat xrdp.pid). If ps shows nothing, the process that created the file no longer exists, and xrdp.pid can be deleted without worry.
answered Jan 31 at 14:25
waltinatorwaltinator
22.4k74169
If pgrep xrdp shows no xrdp actually running, locate xrdp.pid will find the file (or read the documentation) that you should delete.
progname.pid files are traditionally used as lock files. That is, a program that wants to prevent 2 copies running at the same time will write it's PID into a progname.pid file, and plan to remove it when exiting. If a normal exit is precluded (User types ^C, system crashes, etc) the .pid file can be left hanging around.
Once you locate xrdp.pid, it's content should be the PID of the program that created it. ps -fp followed by the PID will show you the current status. E.g. ps -fp $(cat xrdp.pid). If ps shows nothing, the process that created the file no longer exists, and xrdp.pid can be deleted without worry.
answered Jan 31 at 14:25
waltinatorwaltinator
22.4k74169
answered Jan 31 at 14:25
waltinatorwaltinator
22.4k74169
answered Jan 31 at 14:25
waltinatorwaltinator
22.4k74169
answered Jan 31 at 14:25
waltinatorwaltinator
22.4k74169
22.4k74169
add a comment |
add a comment |
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%2f1114410%2fshowing-login-xrdp-screen-once-when-trying-login-user-its-disappearing-again-it%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
