Got "Couldn't add screen" while working with chroot #231

ISNing · 2023-02-19T15:47:37Z

I've been working on using this with a chroot container, I've checked issue#45, but found no one has mentioned how do they fix, just like they haven't done nothing but the problem disappeared...😓

I'm using artifacts from here: https://github.com/termux/termux-x11/actions/runs/4212225635

I'm using chroot container with debian Sid.
I've already done these:

Change XDG_RUNTIME_DIR to "/data/data/com.termux/files/home/.wayland (Both in termux-x11 app and termux)
(In termux)Mount the .wayland folder to /tmp/wayland in chroot container

WAYLAND_SOURCE_DIR="/data/data/com.termux/files/home/.wayland"
WAYLAND_MOUNT_POINT="/tmp/wayland"

su -c "mount -o bind ${WAYLAND_SOURCE_DIR} ${ROOTFS_DIR}${WAYLAND_MOUNT_POINT}"

(In chroot container)Make soft link for the socket file to /var/run/user/$_UID/wayland-0 (Because the socket file has been renamed to termux-x11 in the commit

_UID=$(id -u)
export XDG_RUNTIME_DIR="/var/run/user/$_UID"

if [[ ${_UID} = 0 ]];then
    mkdir -pv ${XDG_RUNTIME_DIR}
else
    sudo chmod -Rv 1777 /tmp/wayland
    sudo mkdir -pv ${XDG_RUNTIME_DIR}
    sudo chmod -Rv 1777 ${XDG_RUNTIME_DIR}
fi

ln -svf /tmp/wayland/termux-x11 ${XDG_RUNTIME_DIR}/wayland-0

(In chroot container) Install xwayland
sudo apt install xwayland
Set display number: export DISPLAY=:1
Open Termux:X11 app.
6.5. (in termux)Process termux-x11(Got same result whether done this. In my view, this is not necessary)
(In chroot container)Start xwayland: Xwayland -noreset ${DISPLAY} and got failure result
(If success)(In chroot container)Start xfce4: dbus-launch --exit-with-session startxfce4

I've also tried overriding mesa loader driver to avoid two warning, but got same result only with different warning.
MESA_LOADER_DRIVER_OVERRIDE=zink Xwayland -noreset ${DISPLAY}
Warning:

_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
libEGL warning: egl: failed to create dri2 screen

Refered to:
2moe/tmoe#113 (comment)
#45

Log is here:

_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
libEGL warning: MESA-LOADER: failed to open msm_drm: /usr/lib/dri/msm_drm_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/aarch64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri)

libEGL warning: MESA-LOADER: failed to open msm_drm: /usr/lib/dri/msm_drm_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/aarch64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri)

could not connect to wayland server
(EE)
Fatal server error:
(EE) Couldn't add screen
(EE)

The text was updated successfully, but these errors were encountered:

twaik · 2023-02-19T16:25:55Z

Read #44 .

Because the socket file has been renamed to termux-x11

It was renamed for a reason. Some programs try to connect wayland-0 and crash fake compositor. Use WAYLAND_DISPLAY variable with Xwayland.

twaik · 2023-02-21T13:29:21Z

@ISNing Did you read it? Did it help?

ask9027 · 2023-02-21T13:37:40Z

@ISNing did you root your devices?
and using ubuntu or debian as distro?

i just found a way to use termux-x11 with custom chroot(only rooted devices)

ISNing · 2023-02-21T15:32:43Z

@ISNing Did you read it? Did it help?

Yes, but it doesn't help, I tried commands in comment, it makes no difference... If I misunderstood you, please tell me.

P.S. Sorry for my late responding because I'm on high school and going to graduate months later

ISNing · 2023-02-21T15:33:43Z

@ISNing did you root your devices?
and using ubuntu or debian as distro?

i just found a way to use termux-x11 with custom chroot(only rooted devices)

Surely yes, I'm using chroot and debian. It obviously that I've rooted my device

twaik · 2023-02-21T15:36:39Z

I am not sure if I can help here, because I have no rooted devices. I am working on something that will make process easier but I am not sure how much time it will take.

ask9027 · 2023-02-21T16:39:07Z

@ISNing did you root your devices?
and using ubuntu or debian as distro?
i just found a way to use termux-x11 with custom chroot(only rooted devices)

Surely yes, I'm using chroot and debian. It obviously that I've rooted my device

if you want to use termux-x11 with chroot ,
you need to add user same uid of termux user,
and bind termux tmp to chroot debian tmp and use chmod 777 (tmp dir if not working)
Note: it will break apt update(maybe) but after unbind termux tmp apt update will work

ask9027 · 2023-02-21T16:39:20Z

sorry for bad english

ISNing · 2023-02-24T15:44:52Z

@ISNing did you root your devices?
and using ubuntu or debian as distro?
i just found a way to use termux-x11 with custom chroot(only rooted devices)

Surely yes, I'm using chroot and debian. It obviously that I've rooted my device

if you want to use termux-x11 with chroot ,
you need to add user same uid of termux user,
and bind termux tmp to chroot debian tmp and use chmod 777 (tmp dir if not working)
Note: it will break apt update(maybe) but after unbind termux tmp apt update will work

But if this can work, I think chmod 777 should also work...
Can there be any other reason?

ISNing · 2023-02-24T15:53:33Z

Yes, it still got failed to add screen...
termux:x:10248:isning

ISNing · 2023-02-24T15:55:00Z

I am not sure if I can help here, because I have no rooted devices. I am working on something that will make process easier but I am not sure how much time it will take.

Hope it could help some🤣

ask9027 · 2023-02-24T15:56:05Z

@ISNing did you root your devices?
and using ubuntu or debian as distro?
i just found a way to use termux-x11 with custom chroot(only rooted devices)

Surely yes, I'm using chroot and debian. It obviously that I've rooted my device

if you want to use termux-x11 with chroot ,
you need to add user same uid of termux user,
and bind termux tmp to chroot debian tmp and use chmod 777 (tmp dir if not working)
Note: it will break apt update(maybe) but after unbind termux tmp apt update will work

But if this can work, I think chmod 777 should also work... Can there be any other reason?

don't know, i tried it a month ago (on rooted devices android v 12) and tried many methods but nothing works but when i tried to add user with same termux uid(with linux deploy app) it works,
you may try to add uid like this

hope this will help.(tested at linux deploy app)

ISNing · 2023-02-24T16:08:50Z

~ $ id
uid=10248(u0_a248) gid=10248(u0_a248) groups=10248(u0_a248),3003(inet),9997(everybody),20248(u0_a248_cache),50248(all_a248)

~ $ debian
isning@localhost:~$ id
uid=1000(isning) gid=10248(termux) group=**10248(termux)**,1000(aid_system),1001(aid_radio),1002(aid_bluetooth),1003(aid_graphics),1004(aid_input),1005(aid_audio),1006(aid_camera),1007(aid_log),1008(aid_compass),1009(aid_mount),1010(aid_wifi),1011(aid_adb),1012(aid_install),1013(aid_media),1014(aid_dhcp),1015(aid_sdcard_rw),1016(aid_vpn),1017(aid_keystore),1018(aid_usb),1019(aid_drm),1020(aid_mdnsr),1021(aid_gps),1023(aid_media_rw),1024(aid_mtp),1026(aid_drmrpc),1027(aid_nfc),1028(aid_sdcard_r),1029(aid_clat),1030(aid_loop_radio),1031(aid_media_drm),1032(aid_package_info),1033(aid_sdcard_pics),1034(aid_sdcard_av),1035(aid_sdcard_all),1036(aid_logd),1037(aid_shared_relro),1038(aid_dbus),1039(aid_tlsdate),1040(aid_media_ex),1041(aid_audioserver),1042(aid_metrics_coll),1043(aid_metricsd),1044(aid_webserv),1045(aid_debuggerd),1046(aid_media_codec),1047(aid_cameraserver),1048(aid_firewall),1049(aid_trunks),1050(aid_nvram),1051(aid_dns),1052(aid_dns_tether),1053(aid_webview_zygote),1054(aid_vehicle_network),1055(aid_media_audio),1056(aid_media_video),1057(aid_media_image),1058(aid_tombstoned),1059(aid_media_obb),1060(aid_ese),1061(aid_ota_update),1062(aid_automotive_evs),1063(aid_lowpan),1064(aid_hsm),1065(aid_reserved_disk),1066(aid_statsd),1067(aid_incidentd),1068(aid_secure_element),1069(aid_lmkd),1070(aid_llkd),1071(aid_iorapd),1072(aid_gpu_service),1073(aid_network_stack),2000(aid_shell),2001(aid_cache),2002(aid_diag),2900(aid_oem_reserved_start),2999(aid_oem_reserved_end),3001(aid_net_bt_admin),3002(aid_net_bt),3003(aid_inet),3004(aid_net_raw),3005(aid_net_admin),3006(aid_net_bw_stats),3007(aid_net_bw_acct),3009(aid_readproc),3010(aid_wakelock),3011(aid_uhid),9997(aid_everybody),9998(aid_misc),9999(aid_nobody),10000(aid_app_start),19999(aid_app_end),20000(aid_cache_gid_start),**20248(termux_cache)**,29999(aid_cache_gid_end),30000(aid_ext_gid_start),39999(aid_ext_gid_end),40000(aid_ext_cache_gid_start),49999(aid_ext_cache_gid_end),50000(aid_shared_gid_start),**50248(termux_all)**,59999(aid_shared_gid_end),99000(aid_isolated_start),99999(aid_isolated_end),100000(aid_user_offset)

Still doesn't work.....

ask9027 · 2023-02-24T16:29:48Z

i think you should also add uid and gid same as termux.
here is id from rooted mobile

ISNing · 2023-02-24T17:37:25Z

i think you should also add uid and gid same as termux.
here is id from rooted mobile

Sorry, but not working

isning@localhost:~$ id
uid=1000(isning) gid=60000(isning) groups=60000(isning),1000(aid_system),1001(aid_radio),1002(aid_bluetooth),1003(aid_graphics),1004(aid_input),1005(aid_audio),1006(aid_camera),1007(aid_log),1008(aid_compass),1009(aid_mount),1010(aid_wifi),1011(aid_adb),1012(aid_install),1013(aid_media),1014(aid_dhcp),1015(aid_sdcard_rw),1016(aid_vpn),1017(aid_keystore),1018(aid_usb),1019(aid_drm),1020(aid_mdnsr),1021(aid_gps),1023(aid_media_rw),1024(aid_mtp),1026(aid_drmrpc),1027(aid_nfc),1028(aid_sdcard_r),1029(aid_clat),1030(aid_loop_radio),1031(aid_media_drm),1032(aid_package_info),1033(aid_sdcard_pics),1034(aid_sdcard_av),1035(aid_sdcard_all),1036(aid_logd),1037(aid_shared_relro),1038(aid_dbus),1039(aid_tlsdate),1040(aid_media_ex),1041(aid_audioserver),1042(aid_metrics_coll),1043(aid_metricsd),1044(aid_webserv),1045(aid_debuggerd),1046(aid_media_codec),1047(aid_cameraserver),1048(aid_firewall),1049(aid_trunks),1050(aid_nvram),1051(aid_dns),1052(aid_dns_tether),1053(aid_webview_zygote),1054(aid_vehicle_network),1055(aid_media_audio),1056(aid_media_video),1057(aid_media_image),1058(aid_tombstoned),1059(aid_media_obb),1060(aid_ese),1061(aid_ota_update),1062(aid_automotive_evs),1063(aid_lowpan),1064(aid_hsm),1065(aid_reserved_disk),1066(aid_statsd),1067(aid_incidentd),1068(aid_secure_element),1069(aid_lmkd),1070(aid_llkd),1071(aid_iorapd),1072(aid_gpu_service),1073(aid_network_stack),2000(aid_shell),2001(aid_cache),2002(aid_diag),2900(aid_oem_reserved_start),2999(aid_oem_reserved_end),3001(aid_net_bt_admin),3002(aid_net_bt),3003(aid_inet),3004(aid_net_raw),3005(aid_net_admin),3006(aid_net_bw_stats),3007(aid_net_bw_acct),3009(aid_readproc),3010(aid_wakelock),3011(aid_uhid),9997(aid_everybody),9998(aid_misc),9999(aid_nobody),10000(aid_app_start),10248(termux),19999(aid_app_end),20000(aid_cache_gid_start),20248(termux_cache),29999(aid_cache_gid_end),30000(aid_ext_gid_start),39999(aid_ext_gid_end),40000(aid_ext_cache_gid_start),49999(aid_ext_cache_gid_end),50000(aid_shared_gid_start),50248(termux_all),59999(aid_shared_gid_end),99000(aid_isolated_start),99999(aid_isolated_end),100000(aid_user_offset)
isning@localhost:~$ Xwayland
libEGL warning: MESA-LOADER: failed to open msm_drm: /usr/lib/dri/msm_drm_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/aarch64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri)

libEGL warning: MESA-LOADER: failed to open msm_drm: /usr/lib/dri/msm_drm_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/aarch64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri)

could not connect to wayland server
(EE)
Fatal server error:
(EE) Couldn't add screen
(EE)
isning@localhost:~$ sudo su termux
$ id
uid=10248(termux) gid=10248(termux) groups=10248(termux)
$ Xwayland
libEGL warning: MESA-LOADER: failed to open msm_drm: /usr/lib/dri/msm_drm_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/aarch64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri)

libEGL warning: MESA-LOADER: failed to open msm_drm: /usr/lib/dri/msm_drm_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/aarch64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri)

could not connect to wayland server
(EE)
Fatal server error:
(EE) Couldn't add screen
(EE)

ask9027 · 2023-02-27T17:13:57Z

When opening termux-x11 directly, does it create any file in $PREFIX/tmp?

twaik · 2023-02-27T17:15:09Z

It creates a socket there.

ask9027 · 2023-02-27T17:16:52Z

oh , here is not any socket created when i open termux-x11 directly.

twaik · 2023-02-27T17:18:11Z

It must be created, it is required for establishing connection to xwayland...

ask9027 · 2023-02-27T17:19:44Z

ya, but it created when i exec termux-x11 & in termux app not by opening directly

twaik · 2023-02-27T17:21:28Z

It can not open anything in termux app's filesystem If you are talking about Termux:X11 which is android app...

twaik · 2023-03-03T15:15:01Z

@ISNing Can you please try last available build?

ISNing · 2023-03-04T13:02:31Z

Sorry, but maybe I need to continue test it 90days later(as well as after the colledge entrance exam)... My devices has been taken away several years ago

ISNing · 2023-03-04T13:05:38Z

@ask9027 in my way, it will create termux-x11 file in `/tmp/wayland`(As i was described in the issue)

wdlq · 2023-03-05T03:30:27Z

I tried last available build in 2023-3-2. But It still didn`t work.

wdlq · 2023-03-05T03:41:01Z

@ISNing 会不会是TMOE的问题？我按照ask9027所说的把termux和chroot debian 的用户名、用户id、组id都统一了，但还是报那个错。ask9027用的是Linux deploy，我用的termux+TMOE

twaik · 2023-03-06T15:33:24Z

But It still didn`t work.

Do export TERMUX_X11_DEBUG=1 before invoking termux-x11 and post logs.

twaik · 2023-03-06T22:48:27Z

@ISNing 会不会是TMOE的问题？我按照ask9027所说的把termux和chroot debian 的用户名、用户id、组id都统一了，但还是报那个错。ask9027用的是Linux deploy，我用的termux+TMOE

I do not speak Chinese...

twaik · 2023-06-04T16:00:37Z

@ask9027 Can you please check if it happens on the latest build?

ask9027 · 2023-06-04T16:15:01Z

@ask9027 Can you please check if it happens on the latest build?

starting these from root

#!/system/bin/sh
termux=/data/data/com.termux/files/usr
debian=/data/local/tmp/debian
export XKB_CONFIG_ROOT=${debian}/usr/share/X11/xkb
export TMPDIR=${termux}/tmp
export CLASSPATH=${termux}/libexec/termux-x11/loader.apk
/system/bin/app_process / com.termux.x11.Loader -ac :0

after this getting pointer error

Pointer tag for 0x76d251a4c8 was truncated, see 'https://source.android.com/devices/tech/debug/tagged-pointers'.
(EE)
Fatal server error:
(EE) Caught signal 6 (Aborted). Server aborting
(EE)

but without root it is working fine only if till desktop start otherwise getting same error if `termux-x11 app` manually closed

ask9027 · 2023-06-05T01:56:01Z

but without root it is working fine only if till desktop start otherwise getting same error if termux-x11 app manually closed

TERMUX_X11_DEBUG=1 not working

twaik · 2023-06-05T12:32:49Z

Pointer tag for 0x76d251a4c8 was truncated, see 'https://source.android.com/devices/tech/debug/tagged-pointers'.
(EE)
Fatal server error:
(EE) Caught signal 6 (Aborted). Server aborting
(EE)

It looks like that is caused by the way I am initializing GLX (without mesa code).

twaik · 2023-06-05T12:34:43Z

Latest build should fix this.

ask9027 · 2023-06-05T13:47:52Z

Latest build should fix this.

the issue is fixed in termux-app,

In root, x server start with desktop but termux-x11 showing Not Connected and nothing is showing
even TERMUX_X11_DEBUG=1 not working

twaik · 2023-06-06T08:57:48Z

TERMUX_X11_DEBUG=1 not working

It should not change something in code, it only shows logcat of main apk if it is available. Unfortunately I can not reproduce this.

3bdelrhman-rabie · 2023-06-07T08:30:57Z

Latest build should fix this.

the issue is fixed in termux-app,

In root, x server start with desktop but termux-x11 showing Not Connected and nothing is showing even TERMUX_X11_DEBUG=1 not working

I tried but got black screen

twaik · 2023-06-07T19:17:19Z

In root, x server start with desktop but termux-x11 showing Not Connected and nothing is showing
even TERMUX_X11_DEBUG=1 not working

What TMPDIR is set in su shell? I tried virtual device and it has /data/local/tmp which is pretty useless. What do you have?

su -c "echo \$TMPDIR"

twaik · 2023-06-07T19:52:32Z

Ok, I see something.

~ $ ls -la /data/data/com.termux/files/usr/tmp/.X11-unix/X0
srwxrwxrwx 1 root root 0 Jun  7 22:10 /data/data/com.termux/files/usr/tmp/.X11-unix/X0

Socket is world-writable but for some reason X clients can not connect it.

connect(3, {sa_family=AF_UNIX, sun_path="/data/data/com.termux/files/usr/tmp/.X11-unix/X0"}, 110) = -1 ECONNREFUSED (Connection refused)

twaik · 2023-06-07T20:25:35Z

Yeah, here lies a problem. For some reason clients can not connect this unix socket if server runs as root, even if a client runs as root.

Signed-off-by: Twaik Yont <twaikyont@gmail.com>

twaik · 2023-06-07T21:30:35Z

It looks like I've found the root of a problem. Try again. @ask9027

ask9027 · 2023-06-08T01:19:59Z

It looks like I've found the root of a problem. Try again. @ask9027

in tried but not working with root.

well, it is not necessary to use root to exec termux-x11.
Alternative we can mount or bind termux-app /data/data/com.termux/files/usr/tmp dir to chroot or proot-distro /tmp
Termux-app tmp dir should have 7777 permission. chmod 7777 $PREFIX/tmp
It will work properly.
So there is no point to use root shell to exec termux-x11.
It is my point of view.

twaik · 2023-06-08T06:09:41Z

It is expected to work. Can you contact me in discord or telegram?

ask9027 · 2023-06-08T06:10:39Z

It is expected to work. Can you contact me in discord or telegram?

ya sure at discord

lateautumn233 · 2023-06-11T00:59:51Z

It is expected to work. Can you contact me in discord or telegram?

It doesn't work
root shell

Details

3bdelrhman-rabie · 2023-06-13T19:18:54Z

twaik · 2023-06-13T19:20:15Z

Cursor appearing means it is connected to the server. Try to open some application.

3bdelrhman-rabie · 2023-06-13T19:23:53Z

Cursor appearing means it is connected to the server. Try to open some application.

This is it while using vnc !

twaik · 2023-06-13T19:24:46Z

You are likely doing something wrong...

twaik · 2023-06-13T19:31:36Z

Why do you use termux's tmp while you are trying to connect chroot'ed environment?

3bdelrhman-rabie · 2023-06-13T20:41:59Z

Edited it to this :
termux=/data/data/com.termux/files/usr debian=/data/local/nhsystem/kali-arm64
export XKB_CONFIG_ROOT=${debian}/usr/share/X11/xkb
export TMPDIR=${debian}/tmp
export CLASSPATH=${termux}/libexec/termux-x11/loader.apk
/system/bin/app_process / com.termux.x11.Loader -ac :0

But still the same issue

twaik · 2023-06-13T20:43:50Z

I can try to connect your device and check what exactly happens, contact me in telegram or discord.

ask9027 · 2023-06-13T23:40:11Z

are you trying in rooted devices?
looks like, you are in termux user not in root.
simply install termux-x11-nightly and run termux-x11 -ac :0

3bdelrhman-rabie · 2023-06-14T08:14:05Z

Yes rooted
And installed all required packages .
The first method still working for me
I guess that I'm doing something wrong.

ask9027 · 2023-06-14T08:18:44Z

Yes rooted And installed all required packages . The first method still working for me I guess that I'm doing something wrong.

did you execute commonds from root shell?
like su before executing commonds.

3bdelrhman-rabie · 2023-06-15T16:15:35Z

Yes rooted And installed all required packages . The first method still working for me I guess that I'm doing something wrong.

did you execute commonds from root shell?
like su before executing commonds.

--------- beginning of main
06-15 18:14:24.685 25282 25282 V LorieBroadcastReceiver: Extracting X connection socket.
06-15 18:14:26.621 25282 25289 E com.termux.x11: failed to connect to jdwp control socket: Connection refused
06-15 18:14:27.937 25282 25282 E Xlorie-client: XCB connection is successfull
06-15 18:14:27.946 25282 25282 D SurfaceChangedListener: Surface was changed: 0x0
06-15 18:14:27.956 25282 25282 V LorieBroadcastReceiver: Got new ACTION_START intent
06-15 18:14:27.956 25282 25282 V LorieBroadcastReceiver: Extracting logcat fd.
--------- beginning of main
06-15 18:14:24.685 25282 25282 V LorieBroadcastReceiver: Extracting X connection socket.
06-15 18:14:26.621 25282 25289 E com.termux.x11: failed to connect to jdwp control socket: Connection refused
06-15 18:14:27.937 25282 25282 E Xlorie-client: XCB connection is successfull
06-15 18:14:27.946 25282 25282 D SurfaceChangedListener: Surface was changed: 0x0
06-15 18:14:27.956 25282 25282 V LorieBroadcastReceiver: Got new ACTION_START intent
06-15 18:14:27.956 25282 25282 V LorieBroadcastReceiver: Extracting logcat fd.
06-15 18:14:27.961 25282 25282 D LorieNative: Starting logcat with output to given fd
06-15 18:14:28.647 25282 25289 E com.termux.x11: failed to connect to jdwp control socket: Connection refused
06-15 18:14:30.652 25282 25289 E com.termux.x11: failed to connect to jdwp control socket: Connection refused
06-15 18:14:31.205 25282 25304 V stderr  : logcat: failed to clear the 'main' log.
06-15 18:14:31.205 25282 25304 V stderr  :
06-15 18:14:31.223 25282 25282 V LorieBroadcastReceiver: Extracting X connection socket.
06-15 18:14:31.251 25282 25282 E Xlorie-client: XCB connection is successfull
06-15 18:14:31.253 25282 25282 D SurfaceChangedListener: Surface was changed: 1080x2263
06-15 18:14:32.664 25282 25289 E com.termux.x11: failed to connect to jdwp control socket: Connection refused
06-15 18:14:34.702 25282 25289 E com.termux.x11: failed to connect to jdwp control socket: Connection refused
06-15 18:14:36.743 25282 25289 E com.termux.x11: failed to connect to jdwp control socket: Connection refused
06-15 18:14:38.746 25282 25289 E com.termux.x11: failed to connect to jdwp control socket: Connection refused
06-15 18:14:40.779 25282 25289 E com.termux.x11: failed to connect to jdwp control socket: Connection refused
06-15 18:14:42.050 25282 25282 D SurfaceChangedListener: Surface was changed: 1080x2263
06-15 18:14:42.083 25282 25282 D SamsungDexUtils: Could not call com.samsung.android.view.SemWindowManager.requestMetaKeyEvent
06-15 18:14:42.083 25282 25282 D SamsungDexUtils: java.lang.ClassNotFoundException: com.samsung.android.view.SemWindowManager
06-15 18:14:42.788 25282 25289 E com.termux.x11: failed to connect to jdwp control socket: Connection refused
06-15 18:14:44.790 25282 25289 E com.termux.x11: failed to connect to jdwp control socket: Connection refused
06-15 18:14:46.791 25282 25289 E com.termux.x11: failed to connect to jdwp control socket: Connection refused
06-15 18:14:48.792 25282 25289 E com.termux.x11: failed to connect to jdwp control socket: Connection refused
06-15 18:14:49.884 25282 25282 D SamsungDexUtils: Could not call com.samsung.android.view.SemWindowManager.requestMetaKeyEvent
06-15 18:14:49.884 25282 25282 D SamsungDexUtils: java.lang.ClassNotFoundException: com.samsung.android.view.SemWindowManager
06-15 18:14:50.792 25282 25289 E com.termux.x11: failed to connect to jdwp control socket: Connection refused
06-15 18:14:52.793 25282 25289 E com.termux.x11: failed to connect to jdwp control socket: Connection refused
06-15 18:14:54.820 25282 25289 E com.termux.x11: failed to connect to jdwp control socket: Connection refused

twaik · 2023-06-25T13:34:26Z

Closing this due to the lack of activity...

ISNing changed the title ~~"Couldn't add screen" working with chroot~~ Got "Couldn't add screen" while working with chroot Feb 19, 2023

twaik added the bug Something isn't working label Feb 21, 2023

twaik added a commit that referenced this issue Jun 7, 2023

Fixing #231 (needs triage)

c846256

Signed-off-by: Twaik Yont <twaikyont@gmail.com>

twaik closed this as completed Jun 25, 2023

Got "Couldn't add screen" while working with chroot #231

Got "Couldn't add screen" while working with chroot #231

Comments

ISNing commented Feb 19, 2023 • edited Loading

twaik commented Feb 19, 2023

twaik commented Feb 21, 2023

ask9027 commented Feb 21, 2023 • edited Loading

ISNing commented Feb 21, 2023

ISNing commented Feb 21, 2023 • edited Loading

twaik commented Feb 21, 2023

ask9027 commented Feb 21, 2023

ask9027 commented Feb 21, 2023

ISNing commented Feb 24, 2023

ISNing commented Feb 24, 2023

ISNing commented Feb 24, 2023

ask9027 commented Feb 24, 2023 • edited Loading

ISNing commented Feb 24, 2023

ask9027 commented Feb 24, 2023 • edited Loading

ISNing commented Feb 24, 2023 • edited Loading

ask9027 commented Feb 27, 2023

twaik commented Feb 27, 2023 • edited Loading

ask9027 commented Feb 27, 2023

twaik commented Feb 27, 2023 • edited Loading

ask9027 commented Feb 27, 2023

twaik commented Feb 27, 2023

twaik commented Mar 3, 2023

ISNing commented Mar 4, 2023 via email

ISNing commented Mar 4, 2023 via email

wdlq commented Mar 5, 2023

wdlq commented Mar 5, 2023

twaik commented Mar 6, 2023

twaik commented Mar 6, 2023

twaik commented Jun 4, 2023

ask9027 commented Jun 4, 2023 • edited Loading

but without root it is working fine only if till desktop start otherwise getting same error if termux-x11 app manually closed

ask9027 commented Jun 5, 2023 • edited by twaik Loading

but without root it is working fine only if till desktop start otherwise getting same error if termux-x11 app manually closed

twaik commented Jun 5, 2023

twaik commented Jun 5, 2023

ask9027 commented Jun 5, 2023 • edited Loading

twaik commented Jun 6, 2023

3bdelrhman-rabie commented Jun 7, 2023 • edited by twaik Loading

twaik commented Jun 7, 2023

twaik commented Jun 7, 2023

twaik commented Jun 7, 2023

twaik commented Jun 7, 2023 • edited Loading

ask9027 commented Jun 8, 2023 • edited Loading

twaik commented Jun 8, 2023 • edited Loading

ask9027 commented Jun 8, 2023 • edited by twaik Loading

lateautumn233 commented Jun 11, 2023 • edited Loading

3bdelrhman-rabie commented Jun 13, 2023 • edited by twaik Loading

twaik commented Jun 13, 2023

3bdelrhman-rabie commented Jun 13, 2023

twaik commented Jun 13, 2023

twaik commented Jun 13, 2023

3bdelrhman-rabie commented Jun 13, 2023

twaik commented Jun 13, 2023

ask9027 commented Jun 13, 2023

3bdelrhman-rabie commented Jun 14, 2023 • edited Loading

ask9027 commented Jun 14, 2023 • edited Loading

3bdelrhman-rabie commented Jun 15, 2023 • edited by twaik Loading

twaik commented Jun 25, 2023

ISNing commented Feb 19, 2023 •

edited

Loading

ask9027 commented Feb 21, 2023 •

edited

Loading

ISNing commented Feb 21, 2023 •

edited

Loading

ask9027 commented Feb 24, 2023 •

edited

Loading

ask9027 commented Feb 24, 2023 •

edited

Loading

ISNing commented Feb 24, 2023 •

edited

Loading

twaik commented Feb 27, 2023 •

edited

Loading

twaik commented Feb 27, 2023 •

edited

Loading

ask9027 commented Jun 4, 2023 •

edited

Loading

but without root it is working fine only if till desktop start otherwise getting same error if `termux-x11 app` manually closed

ask9027 commented Jun 5, 2023 •

edited by twaik

Loading

but without root it is working fine only if till desktop start otherwise getting same error if `termux-x11 app` manually closed

ask9027 commented Jun 5, 2023 •

edited

Loading

3bdelrhman-rabie commented Jun 7, 2023 •

edited by twaik

Loading

twaik commented Jun 7, 2023 •

edited

Loading

ask9027 commented Jun 8, 2023 •

edited

Loading

twaik commented Jun 8, 2023 •

edited

Loading

ask9027 commented Jun 8, 2023 •

edited by twaik

Loading

lateautumn233 commented Jun 11, 2023 •

edited

Loading

3bdelrhman-rabie commented Jun 13, 2023 •

edited by twaik

Loading

3bdelrhman-rabie commented Jun 14, 2023 •

edited

Loading

ask9027 commented Jun 14, 2023 •

edited

Loading

3bdelrhman-rabie commented Jun 15, 2023 •

edited by twaik

Loading