> P.S. This system also had a hardware-specific section for the console's
> monitor in /etc/X11/xorg.conf.d/ that initially prevented xrdp from
> starting at all. I worked around the issue by migrating that to
> /etc/X11/xorg.conf. Is that expected behavior or should I file a bug
> about it?
I
Interesting. Well, the system has a long and complicated history so this is
unsurprising, I guess. Thanks for that insight. If it happens to any of my
or systems, I'll know where to look.
Ben
P.S. This system also had a hardware-specific section for the console's
monitor in
I do indeed (or did)! Purging it fixes the issue. Thanks for all of your
help. I believe you can close this now, though it may be helpful to point
users at potential issues with xserver-xorg-legacy in the README.Debian
unless you work out a fix for that.
I'm happy to report the MS Android client
Hi,
> Oh, I just needed "exec 2> .local/share/xorg/xorg.err.log" in the already
> present /usr/bin/Xorg wrapper. OK. So now I get:
>
> synrg@lear:~$ cat .local/share/xorg/xorg.err.log
> /usr/lib/xorg/Xorg.wrap: Only console users are allowed to run the X server
This looks like you have
Oh, I just needed "exec 2> .local/share/xorg/xorg.err.log" in the already
present /usr/bin/Xorg wrapper. OK. So now I get:
synrg@lear:~$ cat .local/share/xorg/xorg.err.log
/usr/lib/xorg/Xorg.wrap: Only console users are allowed to run the X server
I think you're on the right track with my
On Sun, Jan 1, 2017 at 1:05 PM, Dominik George wrote:
> > I had originally similar thoughts, but after many unsuccessful attempts
> > to get the actual Xorg failure logged somewhere, I eventually gave up
> > (e.g. param lines in sesman.ini to pass -logfile and its argument).
> I had originally similar thoughts, but after many unsuccessful attempts
> to get the actual Xorg failure logged somewhere, I eventually gave up
> (e.g. param lines in sesman.ini to pass -logfile and its argument). If
> you could help me find a solution to that, I could try to get it to
> give me
On January 1, 2017 12:48:05 PM Dominik George wrote:
Hi,
Other ideas?
Hmm… not right now.
I am positive that the only change that could be responsible for this
can be the use of xauth that was introduced in this version, so maybe
play around with that for a while.
I
Hi,
> Other ideas?
Hmm… not right now.
I am positive that the only change that could be responsible for this
can be the use of xauth that was introduced in this version, so maybe
play around with that for a while.
-nik
--
PGP-Fingerprint: 3C9D 54A4 7575 C026 FB17 FD26 B79A 3C16 A0C4 F296
Yes, xauth is installed:
$ apt-cache policy xauth
xauth:
Installed: 1:1.0.9-1
Candidate: 1:1.0.9-1
Version table:
*** 1:1.0.9-1 990
990 http://lear.edennet:/debian stretch/main i386 Packages
500 http://lear.edennet:/debian sid/main i386 Packages
100
Hi,
> What next?
Do you have xauth installed?
If not, please install it and test again.
-nik
--
PGP-Fingerprint: 3C9D 54A4 7575 C026 FB17 FD26 B79A 3C16 A0C4 F296
Dominik George · Hundeshagenstr. 26 · 53225 Bonn
Mobile: +49-1520-1981389 · https://www.dominik-george.de/
Teckids e.V. ·
On Sun, Jan 1, 2017 at 6:25 AM, Dominik George wrote:
> Control: tags -1 + moreinfo
>
> Hi Ben,
>
> > Dec 25 15:49:14 lear xrdp-sesman[15632]: (15632)(-148605184)[INFO ] Xorg
> :10 -auth .Xauthority -config xrdp/xorg.conf -noreset -nolisten tcp
>
> Can you please try running
Control: tags -1 + moreinfo
Hi Ben,
> Dec 25 15:49:14 lear xrdp-sesman[15632]: (15632)(-148605184)[INFO ] Xorg :10
> -auth .Xauthority -config xrdp/xorg.conf -noreset -nolisten tcp
Can you please try running this exact command manually as the same user?
Cheers,
Nik
--
PGP-Fingerprint: 3C9D
Package: xrdp
Version: 0.9.1-1
Severity: normal
--- Please enter the report below this line. ---
After upgrading to 0.9.1-1, Xorg is no longer started when xrdp-sesman
runs. Downgrading back to xrdp_0.9.1~20161126+git589b29f-1 resolves the
issue.
Here's what is in journalctl -u xrdp-sesman
14 matches
Mail list logo