Local Ubuntu desktop cannot login after opened Xrdp session
I have Ubuntu 18.04 and Xrdp 0.9.5.
I can login directly to local desktop after boot.
If I logout, I still can login via Xrdp.
Otherwise, if Xrdp session has opened, even if I closed it, I cannot login to desktop locally, I think Xrdp session is blocking it. I need to restart the machine so I can login locally.
How do I close the Xrdp session?
When I tried to login locally, the log says :
Jul 10 09:34:55 gdm-password]: pam_unix(gdm-password:session): session opened for user superadmin by (uid=0)
Jul 10 09:34:55 systemd-logind[879]: New session 3 of user superadmin.
Jul 10 09:34:57 gdm-password]: pam_unix(gdm-password:session): session closed for user superadmin
Jul 10 09:34:57 systemd-logind[879]: Removed session 3.
Jul 10 09:35:01 CRON[2485]: pam_unix(cron:session): session opened for user root by (uid=0)
Jul 10 09:35:01 CRON[2485]: pam_unix(cron:session): session closed for user root
Restarting the machine is the only way to fix this right now.
UPDATE
After some trial and error, and referenced to @Sylla suggestion, I found that not only Xrdp process to kill, but also XOrg
7313 ? 00:00:02 Xorg
7325 ? 00:00:00 xrdp-chansrv
After that, I can now login locally.
Now the next question is: Is there any chance I could make it automatically kill the processes after I close remote desktop?
login remote-desktop xrdp
add a comment |
I have Ubuntu 18.04 and Xrdp 0.9.5.
I can login directly to local desktop after boot.
If I logout, I still can login via Xrdp.
Otherwise, if Xrdp session has opened, even if I closed it, I cannot login to desktop locally, I think Xrdp session is blocking it. I need to restart the machine so I can login locally.
How do I close the Xrdp session?
When I tried to login locally, the log says :
Jul 10 09:34:55 gdm-password]: pam_unix(gdm-password:session): session opened for user superadmin by (uid=0)
Jul 10 09:34:55 systemd-logind[879]: New session 3 of user superadmin.
Jul 10 09:34:57 gdm-password]: pam_unix(gdm-password:session): session closed for user superadmin
Jul 10 09:34:57 systemd-logind[879]: Removed session 3.
Jul 10 09:35:01 CRON[2485]: pam_unix(cron:session): session opened for user root by (uid=0)
Jul 10 09:35:01 CRON[2485]: pam_unix(cron:session): session closed for user root
Restarting the machine is the only way to fix this right now.
UPDATE
After some trial and error, and referenced to @Sylla suggestion, I found that not only Xrdp process to kill, but also XOrg
7313 ? 00:00:02 Xorg
7325 ? 00:00:00 xrdp-chansrv
After that, I can now login locally.
Now the next question is: Is there any chance I could make it automatically kill the processes after I close remote desktop?
login remote-desktop xrdp
add a comment |
I have Ubuntu 18.04 and Xrdp 0.9.5.
I can login directly to local desktop after boot.
If I logout, I still can login via Xrdp.
Otherwise, if Xrdp session has opened, even if I closed it, I cannot login to desktop locally, I think Xrdp session is blocking it. I need to restart the machine so I can login locally.
How do I close the Xrdp session?
When I tried to login locally, the log says :
Jul 10 09:34:55 gdm-password]: pam_unix(gdm-password:session): session opened for user superadmin by (uid=0)
Jul 10 09:34:55 systemd-logind[879]: New session 3 of user superadmin.
Jul 10 09:34:57 gdm-password]: pam_unix(gdm-password:session): session closed for user superadmin
Jul 10 09:34:57 systemd-logind[879]: Removed session 3.
Jul 10 09:35:01 CRON[2485]: pam_unix(cron:session): session opened for user root by (uid=0)
Jul 10 09:35:01 CRON[2485]: pam_unix(cron:session): session closed for user root
Restarting the machine is the only way to fix this right now.
UPDATE
After some trial and error, and referenced to @Sylla suggestion, I found that not only Xrdp process to kill, but also XOrg
7313 ? 00:00:02 Xorg
7325 ? 00:00:00 xrdp-chansrv
After that, I can now login locally.
Now the next question is: Is there any chance I could make it automatically kill the processes after I close remote desktop?
login remote-desktop xrdp
I have Ubuntu 18.04 and Xrdp 0.9.5.
I can login directly to local desktop after boot.
If I logout, I still can login via Xrdp.
Otherwise, if Xrdp session has opened, even if I closed it, I cannot login to desktop locally, I think Xrdp session is blocking it. I need to restart the machine so I can login locally.
How do I close the Xrdp session?
When I tried to login locally, the log says :
Jul 10 09:34:55 gdm-password]: pam_unix(gdm-password:session): session opened for user superadmin by (uid=0)
Jul 10 09:34:55 systemd-logind[879]: New session 3 of user superadmin.
Jul 10 09:34:57 gdm-password]: pam_unix(gdm-password:session): session closed for user superadmin
Jul 10 09:34:57 systemd-logind[879]: Removed session 3.
Jul 10 09:35:01 CRON[2485]: pam_unix(cron:session): session opened for user root by (uid=0)
Jul 10 09:35:01 CRON[2485]: pam_unix(cron:session): session closed for user root
Restarting the machine is the only way to fix this right now.
UPDATE
After some trial and error, and referenced to @Sylla suggestion, I found that not only Xrdp process to kill, but also XOrg
7313 ? 00:00:02 Xorg
7325 ? 00:00:00 xrdp-chansrv
After that, I can now login locally.
Now the next question is: Is there any chance I could make it automatically kill the processes after I close remote desktop?
login remote-desktop xrdp
login remote-desktop xrdp
edited Feb 20 at 2:24
Kevin Bowen
14.7k155970
14.7k155970
asked Jul 11 '18 at 3:22
AsuleAsule
167
167
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
I did not know that Xrdp has two config file (xrdp.ini
& sesman.ini
).
So, I created an issue in Xrdp repository here
.
The developer told me that the configuration is in sesman.ini
. The variable named KillDisconnected
will do the job. but as I read it, it cannot have less than a value of 60s
.
add a comment |
1) First solution:
ps -u your_username | grep xrdp
will give you the process id.
You can then
kill -9 pid_number
pid refers to your xrdp process ID.
2) Second solution
If you want to close xrdp session, you can use this command
/etc/init.d/xrdp stop
And if you decide to use your xrdp:
/etc/init.d/xrdp start
To check which status you have:
/etc/init.d/xrdp status
i tried your suggestion: but$ sudo xrdp status Unknown Parameter xrdp -h for help
not recognizing status parameter$ ps -u superadmin | grep xrdp 1818 ? 00:00:00 xrdp-chansrv $ kill -9 1818 $ ps -u superadmin | grep xrdp 1818 ? 00:00:00 xrdp-chansrv <defunct>
i'm still logged in xrdp, even can reconnect xrdp normally. any suggestion?
– Asule
Jul 11 '18 at 9:51
Not 'sudo xrdp status' but "/etc/init.d/xrdp" status If the status is "active" (running), you have to run this command as root: "/etc/init.d/xrdp stop" without quotes!
– Sylla
Jul 11 '18 at 9:56
ok, actually i've tried service xrdp restart yesterday, and made me kicked out of xrdp , but still cannot login locally to desktop. just now i tried your suggestion to stop the service, now i cannot login both locally or xrdp. :(
– Asule
Jul 11 '18 at 10:16
Restart your computer and do ctrl+Alt+F1 for terminal command. And type this command: "/etc/init.d/xrdp start
– Sylla
Jul 11 '18 at 12:01
well, that is true i should restart the machine, the only one way i could login back locally, no need to start xrdp manually. But here i am looking for the better way. btw thanks for your responses.
– Asule
Jul 12 '18 at 1:16
add a comment |
I'm a bit late to the party on this one, but was experiencing the very same problem you were with almost the identical setup. I tried just about everything, including different desktops uninstalling and reinstalling gnome desktop, but nothing really worked. The only truly reliable way to login locally was to reboot the computer which wasn't the solution I was after. Quite by accident while using the remote xrdp client, rather than just closing the application from the toolbar as I usually do, I tried logging out of the remote session. Low and behold that did the trick!! I was able to reliably log in locally. So to summarize, logout out of the xrdp session rather than simply closing it. Hope this solution works for you as well.
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%2f1054063%2flocal-ubuntu-desktop-cannot-login-after-opened-xrdp-session%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
I did not know that Xrdp has two config file (xrdp.ini
& sesman.ini
).
So, I created an issue in Xrdp repository here
.
The developer told me that the configuration is in sesman.ini
. The variable named KillDisconnected
will do the job. but as I read it, it cannot have less than a value of 60s
.
add a comment |
I did not know that Xrdp has two config file (xrdp.ini
& sesman.ini
).
So, I created an issue in Xrdp repository here
.
The developer told me that the configuration is in sesman.ini
. The variable named KillDisconnected
will do the job. but as I read it, it cannot have less than a value of 60s
.
add a comment |
I did not know that Xrdp has two config file (xrdp.ini
& sesman.ini
).
So, I created an issue in Xrdp repository here
.
The developer told me that the configuration is in sesman.ini
. The variable named KillDisconnected
will do the job. but as I read it, it cannot have less than a value of 60s
.
I did not know that Xrdp has two config file (xrdp.ini
& sesman.ini
).
So, I created an issue in Xrdp repository here
.
The developer told me that the configuration is in sesman.ini
. The variable named KillDisconnected
will do the job. but as I read it, it cannot have less than a value of 60s
.
edited Feb 20 at 2:21
Kevin Bowen
14.7k155970
14.7k155970
answered Jul 13 '18 at 10:24
AsuleAsule
167
167
add a comment |
add a comment |
1) First solution:
ps -u your_username | grep xrdp
will give you the process id.
You can then
kill -9 pid_number
pid refers to your xrdp process ID.
2) Second solution
If you want to close xrdp session, you can use this command
/etc/init.d/xrdp stop
And if you decide to use your xrdp:
/etc/init.d/xrdp start
To check which status you have:
/etc/init.d/xrdp status
i tried your suggestion: but$ sudo xrdp status Unknown Parameter xrdp -h for help
not recognizing status parameter$ ps -u superadmin | grep xrdp 1818 ? 00:00:00 xrdp-chansrv $ kill -9 1818 $ ps -u superadmin | grep xrdp 1818 ? 00:00:00 xrdp-chansrv <defunct>
i'm still logged in xrdp, even can reconnect xrdp normally. any suggestion?
– Asule
Jul 11 '18 at 9:51
Not 'sudo xrdp status' but "/etc/init.d/xrdp" status If the status is "active" (running), you have to run this command as root: "/etc/init.d/xrdp stop" without quotes!
– Sylla
Jul 11 '18 at 9:56
ok, actually i've tried service xrdp restart yesterday, and made me kicked out of xrdp , but still cannot login locally to desktop. just now i tried your suggestion to stop the service, now i cannot login both locally or xrdp. :(
– Asule
Jul 11 '18 at 10:16
Restart your computer and do ctrl+Alt+F1 for terminal command. And type this command: "/etc/init.d/xrdp start
– Sylla
Jul 11 '18 at 12:01
well, that is true i should restart the machine, the only one way i could login back locally, no need to start xrdp manually. But here i am looking for the better way. btw thanks for your responses.
– Asule
Jul 12 '18 at 1:16
add a comment |
1) First solution:
ps -u your_username | grep xrdp
will give you the process id.
You can then
kill -9 pid_number
pid refers to your xrdp process ID.
2) Second solution
If you want to close xrdp session, you can use this command
/etc/init.d/xrdp stop
And if you decide to use your xrdp:
/etc/init.d/xrdp start
To check which status you have:
/etc/init.d/xrdp status
i tried your suggestion: but$ sudo xrdp status Unknown Parameter xrdp -h for help
not recognizing status parameter$ ps -u superadmin | grep xrdp 1818 ? 00:00:00 xrdp-chansrv $ kill -9 1818 $ ps -u superadmin | grep xrdp 1818 ? 00:00:00 xrdp-chansrv <defunct>
i'm still logged in xrdp, even can reconnect xrdp normally. any suggestion?
– Asule
Jul 11 '18 at 9:51
Not 'sudo xrdp status' but "/etc/init.d/xrdp" status If the status is "active" (running), you have to run this command as root: "/etc/init.d/xrdp stop" without quotes!
– Sylla
Jul 11 '18 at 9:56
ok, actually i've tried service xrdp restart yesterday, and made me kicked out of xrdp , but still cannot login locally to desktop. just now i tried your suggestion to stop the service, now i cannot login both locally or xrdp. :(
– Asule
Jul 11 '18 at 10:16
Restart your computer and do ctrl+Alt+F1 for terminal command. And type this command: "/etc/init.d/xrdp start
– Sylla
Jul 11 '18 at 12:01
well, that is true i should restart the machine, the only one way i could login back locally, no need to start xrdp manually. But here i am looking for the better way. btw thanks for your responses.
– Asule
Jul 12 '18 at 1:16
add a comment |
1) First solution:
ps -u your_username | grep xrdp
will give you the process id.
You can then
kill -9 pid_number
pid refers to your xrdp process ID.
2) Second solution
If you want to close xrdp session, you can use this command
/etc/init.d/xrdp stop
And if you decide to use your xrdp:
/etc/init.d/xrdp start
To check which status you have:
/etc/init.d/xrdp status
1) First solution:
ps -u your_username | grep xrdp
will give you the process id.
You can then
kill -9 pid_number
pid refers to your xrdp process ID.
2) Second solution
If you want to close xrdp session, you can use this command
/etc/init.d/xrdp stop
And if you decide to use your xrdp:
/etc/init.d/xrdp start
To check which status you have:
/etc/init.d/xrdp status
answered Jul 11 '18 at 8:49
SyllaSylla
11
11
i tried your suggestion: but$ sudo xrdp status Unknown Parameter xrdp -h for help
not recognizing status parameter$ ps -u superadmin | grep xrdp 1818 ? 00:00:00 xrdp-chansrv $ kill -9 1818 $ ps -u superadmin | grep xrdp 1818 ? 00:00:00 xrdp-chansrv <defunct>
i'm still logged in xrdp, even can reconnect xrdp normally. any suggestion?
– Asule
Jul 11 '18 at 9:51
Not 'sudo xrdp status' but "/etc/init.d/xrdp" status If the status is "active" (running), you have to run this command as root: "/etc/init.d/xrdp stop" without quotes!
– Sylla
Jul 11 '18 at 9:56
ok, actually i've tried service xrdp restart yesterday, and made me kicked out of xrdp , but still cannot login locally to desktop. just now i tried your suggestion to stop the service, now i cannot login both locally or xrdp. :(
– Asule
Jul 11 '18 at 10:16
Restart your computer and do ctrl+Alt+F1 for terminal command. And type this command: "/etc/init.d/xrdp start
– Sylla
Jul 11 '18 at 12:01
well, that is true i should restart the machine, the only one way i could login back locally, no need to start xrdp manually. But here i am looking for the better way. btw thanks for your responses.
– Asule
Jul 12 '18 at 1:16
add a comment |
i tried your suggestion: but$ sudo xrdp status Unknown Parameter xrdp -h for help
not recognizing status parameter$ ps -u superadmin | grep xrdp 1818 ? 00:00:00 xrdp-chansrv $ kill -9 1818 $ ps -u superadmin | grep xrdp 1818 ? 00:00:00 xrdp-chansrv <defunct>
i'm still logged in xrdp, even can reconnect xrdp normally. any suggestion?
– Asule
Jul 11 '18 at 9:51
Not 'sudo xrdp status' but "/etc/init.d/xrdp" status If the status is "active" (running), you have to run this command as root: "/etc/init.d/xrdp stop" without quotes!
– Sylla
Jul 11 '18 at 9:56
ok, actually i've tried service xrdp restart yesterday, and made me kicked out of xrdp , but still cannot login locally to desktop. just now i tried your suggestion to stop the service, now i cannot login both locally or xrdp. :(
– Asule
Jul 11 '18 at 10:16
Restart your computer and do ctrl+Alt+F1 for terminal command. And type this command: "/etc/init.d/xrdp start
– Sylla
Jul 11 '18 at 12:01
well, that is true i should restart the machine, the only one way i could login back locally, no need to start xrdp manually. But here i am looking for the better way. btw thanks for your responses.
– Asule
Jul 12 '18 at 1:16
i tried your suggestion: but
$ sudo xrdp status Unknown Parameter xrdp -h for help
not recognizing status parameter $ ps -u superadmin | grep xrdp 1818 ? 00:00:00 xrdp-chansrv $ kill -9 1818 $ ps -u superadmin | grep xrdp 1818 ? 00:00:00 xrdp-chansrv <defunct>
i'm still logged in xrdp, even can reconnect xrdp normally. any suggestion?– Asule
Jul 11 '18 at 9:51
i tried your suggestion: but
$ sudo xrdp status Unknown Parameter xrdp -h for help
not recognizing status parameter $ ps -u superadmin | grep xrdp 1818 ? 00:00:00 xrdp-chansrv $ kill -9 1818 $ ps -u superadmin | grep xrdp 1818 ? 00:00:00 xrdp-chansrv <defunct>
i'm still logged in xrdp, even can reconnect xrdp normally. any suggestion?– Asule
Jul 11 '18 at 9:51
Not 'sudo xrdp status' but "/etc/init.d/xrdp" status If the status is "active" (running), you have to run this command as root: "/etc/init.d/xrdp stop" without quotes!
– Sylla
Jul 11 '18 at 9:56
Not 'sudo xrdp status' but "/etc/init.d/xrdp" status If the status is "active" (running), you have to run this command as root: "/etc/init.d/xrdp stop" without quotes!
– Sylla
Jul 11 '18 at 9:56
ok, actually i've tried service xrdp restart yesterday, and made me kicked out of xrdp , but still cannot login locally to desktop. just now i tried your suggestion to stop the service, now i cannot login both locally or xrdp. :(
– Asule
Jul 11 '18 at 10:16
ok, actually i've tried service xrdp restart yesterday, and made me kicked out of xrdp , but still cannot login locally to desktop. just now i tried your suggestion to stop the service, now i cannot login both locally or xrdp. :(
– Asule
Jul 11 '18 at 10:16
Restart your computer and do ctrl+Alt+F1 for terminal command. And type this command: "/etc/init.d/xrdp start
– Sylla
Jul 11 '18 at 12:01
Restart your computer and do ctrl+Alt+F1 for terminal command. And type this command: "/etc/init.d/xrdp start
– Sylla
Jul 11 '18 at 12:01
well, that is true i should restart the machine, the only one way i could login back locally, no need to start xrdp manually. But here i am looking for the better way. btw thanks for your responses.
– Asule
Jul 12 '18 at 1:16
well, that is true i should restart the machine, the only one way i could login back locally, no need to start xrdp manually. But here i am looking for the better way. btw thanks for your responses.
– Asule
Jul 12 '18 at 1:16
add a comment |
I'm a bit late to the party on this one, but was experiencing the very same problem you were with almost the identical setup. I tried just about everything, including different desktops uninstalling and reinstalling gnome desktop, but nothing really worked. The only truly reliable way to login locally was to reboot the computer which wasn't the solution I was after. Quite by accident while using the remote xrdp client, rather than just closing the application from the toolbar as I usually do, I tried logging out of the remote session. Low and behold that did the trick!! I was able to reliably log in locally. So to summarize, logout out of the xrdp session rather than simply closing it. Hope this solution works for you as well.
add a comment |
I'm a bit late to the party on this one, but was experiencing the very same problem you were with almost the identical setup. I tried just about everything, including different desktops uninstalling and reinstalling gnome desktop, but nothing really worked. The only truly reliable way to login locally was to reboot the computer which wasn't the solution I was after. Quite by accident while using the remote xrdp client, rather than just closing the application from the toolbar as I usually do, I tried logging out of the remote session. Low and behold that did the trick!! I was able to reliably log in locally. So to summarize, logout out of the xrdp session rather than simply closing it. Hope this solution works for you as well.
add a comment |
I'm a bit late to the party on this one, but was experiencing the very same problem you were with almost the identical setup. I tried just about everything, including different desktops uninstalling and reinstalling gnome desktop, but nothing really worked. The only truly reliable way to login locally was to reboot the computer which wasn't the solution I was after. Quite by accident while using the remote xrdp client, rather than just closing the application from the toolbar as I usually do, I tried logging out of the remote session. Low and behold that did the trick!! I was able to reliably log in locally. So to summarize, logout out of the xrdp session rather than simply closing it. Hope this solution works for you as well.
I'm a bit late to the party on this one, but was experiencing the very same problem you were with almost the identical setup. I tried just about everything, including different desktops uninstalling and reinstalling gnome desktop, but nothing really worked. The only truly reliable way to login locally was to reboot the computer which wasn't the solution I was after. Quite by accident while using the remote xrdp client, rather than just closing the application from the toolbar as I usually do, I tried logging out of the remote session. Low and behold that did the trick!! I was able to reliably log in locally. So to summarize, logout out of the xrdp session rather than simply closing it. Hope this solution works for you as well.
answered Feb 20 at 1:37
silversprsilverspr
62
62
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%2f1054063%2flocal-ubuntu-desktop-cannot-login-after-opened-xrdp-session%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