As per
https://bugs.launchpad.net/ubuntu/+source/xrdp/+bug/339032/comments/8 .
** Changed in: xrdp (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/339032
Title:
I ran into this same problem. I checked over my sesman.ini file, and
found that the problem disappeared after a changed the ip-binding back
to 127.0.0.1. Apparently, it's a misconception on the part of some
(including myself) that the ip-binding needs to match that of the
static-eth0 address.
An
It seems to be working correctly for Maverick i386 and amd64 now.
--
xrdp dies when starting at boot time
https://bugs.launchpad.net/bugs/339032
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
Please fix!
Thanx.
--
xrdp dies when starting at boot time
https://bugs.launchpad.net/bugs/339032
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/
That is useful information! I'll give it a try and post the results
here. Thanks!
--
xrdp dies when starting at boot time
https://bugs.launchpad.net/bugs/339032
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing li
I had the same problem. xrdp wouldn't stay running from the startup
scripts, but if I logged in I could run it manually with no problems.
After a few days of trying everything I could think of I stumbled upon a
solution. Putting a delay at the end of /etc/init.d/xrdp seems to do
the trick. I add
I have the same problem on my office computer, but not on my home
computer even if both of them have updated jaunty. The only difference
in installing was while testing xrdp on my office computer I installed
it with vnc4server as dependency. When I found that tightvnc is better
supported, I uninsta
Ignore the above - gconf settings for one person shouldn't be able to do
this. But oddly enough the problem seems to have disappeared for me,
not sure why - maybe an update fixed it?
--
xrdp dies when starting at boot time
https://bugs.launchpad.net/bugs/339032
You received this bug notification
After encountering the keyboard issue
(https://bugs.launchpad.net/ubuntu/+source/xrdp/+bug/320393) I think
these might be related since fixing that issue with the workaround given
for the referenced bug seems to fix this one.
--
xrdp dies when starting at boot time
https://bugs.launchpad.net/bugs
Same problem here, but even if the init.d script is modified to clear the pid
files, the server doesn't start properly on its own. After clearing
sesman.log, after a reboot, the contents of sesman.log are
[20090530-00:59:49] [INFO ] starting signal handling thread...
[20090530-00:59:49] [INFO ]
10 matches
Mail list logo
