Can't start x server

[TeoColuccio]

I followed the instructions, but the app xsdl can't connect to userland. There are missing pieces, first of all, the "start" command can not be executed.

[carbonatedcaffeine]

It might just be you... I made a new one and works fine...

[TeoColuccio]

But when I type 'start lxde', it says 'command not found'. Then the port is not specified

[corbinlc]

Can you provide a link to the instructions you followed? We don't actually provide instructions for using XSDL. We plan on making that an integrated flow soon.

[MatthewTighe]

@corbinlc Our README contains instructions for XSDL thanks to @EnderNightLord-ChromeBook.

This issue was posted pre-1.0.3, so I don't think that's the root cause.

[carbonatedcaffeine]

this was just a typing error you put:

$ start lxde
but you should put
$ startlxde

I made a pull request to fix this in my instructions of installing a desktop... #454

[corbinlc]

Oh, I forgot that was added to the README. Thanks for pointing that out and thanks to @EnderNightLord-ChromeBook for fixing.

[carbonatedcaffeine]

your welcome 😄

[TeoColuccio]

Ok now startlxde works, the same doesn't work because there are errors and can not export the desktop:

teo @ localhost: $ export DISPLAY =: 0 PULSE SERVER = top: 127.0.0.1: 0
teo @ localhost: ~ $ startlxde
** Message: 23: 49: 24.334: main.vala: 102: Session is LXDE ** Message: 23: 49: 24.338: main.vala: 103: DE is LXDE (1xsession: 8227): Gtk-ING 23: 49: 24.375: can not open display:: 0

[carbonatedcaffeine]

right good luck with the rest 🎆

[ghost]

I got the same error when trying with Ubuntu on android Pie
but the weird thing is that when trying to list the displays I only have a :51
https://framapic.org/tS0oCLZRCrSG/JYYJvzJ67eZx.png
and when I try with :51, I get xlde launching but within my userland app, not inside the XSDL window.
is this the correct functioning ?
https://framapic.org/F7wjULcxFotc/pAscNJNI21Qv.png

[TeoColuccio]

Yes, on Android pie me too

[ghost]

@TeoColuccio man, how did you manage to copy/paste ? xD
sorry all for the IMG upload

[TeoColuccio]

@voxitme you must take screenshot, then there are many app for text reader ;)

[carbonatedcaffeine]

I haven't tested on android 9 yet... This may be a bug...

[ghost]

@TeoColuccio lol, that's what I tried at first, with https://gitlab.com/character-recognition/character-recognition which is on F-Droid , but so many characters were wrong, and I finally gave up !

[carbonatedcaffeine]

Go back to my answer it was a type error which I fixed...

[TeoColuccio]

I haven't tested on android 9 yet... This may be a bug...

Ok, I'll wait for news

[jwoehr]

I can't startlxde either.

• XSDL is installed
• export DISPLAY=:0 PULSE_SERVER=tcp:127.0.0.1:4712 (the port that XSDL says to use)

SOLVED: by using the DHCP-assigned WIFI address instead of loopback address as above.
E.g., export DISPLAY=123.456.789.1:0 PULSE_SERVER=tcp:123.456.789.1:4712 (the port that XSDL says to use)

[carbonatedcaffeine]

there you go...

[FTWJAY]

I too cannot use xsdl. I'm on a pixel 3 running Android 9. When I start xsdl it comes up with screen density choices. I have tried all screens but xsdl just keeps restarting then reaches a point with the message that it won't work. Too bad.
Any ideas? I'm just trying to get a desktop going. No matter what DISPLAY=:x I try I'm greeted with the message that it cannot open DISPLAY:x

[carbonatedcaffeine]

well if that wont work then it's time to go VNC. This time try using VNC and it should come up with the desktop. It's not as good as XSDL but it works. Just make a vnc with the filesystem your using and you should be good.

[Pevinsghost]

Is there a way to properly shut everything down doing it that way? I can startlxde from the vnc session, and the lxde interface logout command will return the terminal to a prompt, but the lxde session is clearly still running and will even still launch applications.

[Marcus0086]

"DISPLAY=127.0.0.1:0 PULSE_SERVER=tcp:127.0.0.1:4712 startlxde &"
Use this if anything happens now so let me know.

[FTWJAY]

Having trouble getting it to keep working on a Samsung tab e. It will work but then crash after a while and then not start at all. Trying to figure it out. But got lxde to work finally. Where is the virtual file holding the Linux system so I can make sure it's clean when I do a reinstall of UserLand? Also is there any way to get UserLand to see an SD card?

On Sun, Jan 13, 2019, 12:50 PM Marcus0086 ***@***.***> wrote: "DISPLAY=127.0.0.1:0 PULSE_SERVER=tcp:127.0.0.1:4712 startlxde &" Use this if anything happens now so let me know. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#445 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AdGoSKs3PEFTjipg9ADq_UEotoLy6W1Iks5vC3_8gaJpZM4ZBK1N> .

-- May Hashem Bless you abundantly

[Pevinsghost]

Tried on my OnePlus 6, still not working :
https://i.imgur.com/EjLOk3P.jpg

pevinsghost@localhost:~$ DISPLAY=127.0.0.1:04712 startlxde &

[1] 17093

pevinsghost@localhost:”$ ** Message: main.uala:102: Session is LKDE

** Message: main.vala:103: DE is LXDE PULSE_SERVER=tcp:127.0.0.1:

(lxsession:17093): Gtk-Warning **: cannot open display: 127.0.0.1:0

[Marcus0086]

So everyone wants xsdl.
Hey let me tell u that by using vnc u can use gui better than xsdl. Xsdl is laggy.
First install realvnc from play store
Then open ur shell
Install tightvncserver by sudo apt install tightvncserver
(I'm assuming that u have lxde or mate installed)
Now use command "sudo vncserver :1 -geometry 1920x1080(urs phone resolution) "
Now it will ask for password and then enter no.
Then "sudo export DISPLAY=:1"
then "startlxde &"
It will start vncserver over 127.0.0.1:5901
Open realvnc add then enter 127.0.0.1:5901 and computer name
Then put ur password u entered just before.
Then ur all set ready to go.
In order to kill vncservice use "sudo vncserver -kill :1"

[carbonatedcaffeine]

no... as a long time user. xsdl is actually better for launching applications.

[dishanr]

I can't startlxde either.

* XSDL is installed

* `export DISPLAY=:0 PULSE_SERVER=tcp:127.0.0.1:4712` (the port that XSDL says to use)

SOLVED: by using the DHCP-assigned WIFI address instead of loopback address as above.
E.g., export DISPLAY=123.456.789.1:0 PULSE_SERVER=tcp:123.456.789.1:4712 (the port that XSDL says to use)

Using the DHCP address worked for me too. I connected to the phone via MobaXTerm on Windows. Seems like XServer XSDL app does not support Android Pie. It keeps crashing and restarting.

[JanuszChmiel]

Dear users,
The situation while using Xwindows system on Android is not easy. In fact, Xserver XSDL try to do its best to support 99 % of The Xserver protocol. But it is Java code with Native C code and I Am even afraid, that many positive changes are applied on Github of this project. But compiled up to date code is not packed on GOogle Play. There are several projects on Github but Xserver XSDL, even it is not ideal have some positives. It support even connected physical BLuetooh or USB keyboard. Support all Xserver protocol features so even Orca screen reader for visually impaired can work with many applications.
There is even some code Xserver for Android on Github, but code is not compiled and released as .apk file. I would even try VNC, but I can not cooperate with such environment because I do not know, if physical external keyboard would be supported inside running X session when using VNC. Because I did not tried VNC, I do not want to tell , that it is bad or good. The interesting question is about sound while running VNC session.
If user must install Termux, run Pulseaudio from it and play sounds, or if there is some prepared approach directly in Userland.

[JanuszChmiel]

We must ppatiently wait. I have got info from The developer of Xserver XSDL that code on GIthub would not work so this is The reason why this app is not on GOogle Play store yet, because it would contain non functioning code. So users of new Android 9 and newer will had to use VNC. I could try VNC too, but I do not know, if BLuetooth keyboard would be supported when running X session and what about sound support?