termux / termux-x11

Termux X11 add-on application.
https://termux.dev
GNU General Public License v3.0
2.09k stars 311 forks source link

Debian Gnome not work in termux-x11 #340

Closed binhvo7794 closed 1 year ago

binhvo7794 commented 1 year ago

I try start gnome on termux-x11 but not working, here is output!

Details ``` (gnome-shell:11627): libupower-glib-WARNING **: 17:44:45.025: Couldn't connect to proxy: Could not connect: Connection refused (gnome-shell:11627): libupower-glib-WARNING **: 17:44:45.027: Couldn't connect to proxy: Could not connect: Connection refused (gnome-shell:11627): GLib-GObject-WARNING **: 17:44:45.028: invalid (NULL) pointer instance (gnome-shell:11627): GLib-GObject-CRITICAL **: 17:44:45.029: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed Xlib: extension "DPMS" missing on display ":0". Xlib: extension "DPMS" missing on display ":0". (gnome-shell:11627): Gjs-WARNING **: 17:44:47.966: JS ERROR: Gio.IOErrorEnum: Could not connect: Connection refused get system@resource:///org/gnome/gjs/modules/overrides/Gio.js:354:20 _init@resource:///org/gnome/shell/ui/status/power.js:49:9 wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22 _Base.prototype._construct@resource:///org/gnome/gjs/modules/_legacy.js:18:5 Class.prototype._construct/newClass@resource:///org/gnome/gjs/modules/_legacy.js:114:32 _init@resource:///org/gnome/shell/ui/panel.js:712:23 wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22 _Base.prototype._construct@resource:///org/gnome/gjs/modules/_legacy.js:18:5 Class.prototype._construct/newClass@resource:///org/gnome/gjs/modules/_legacy.js:114:32 _ensureIndicator@resource:///org/gnome/shell/ui/panel.js:1126:25 wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22 _updateBox@resource:///org/gnome/shell/ui/panel.js:1137:29 wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22 _updatePanel@resource:///org/gnome/shell/ui/panel.js:1047:9 wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22 _init@resource:///org/gnome/shell/ui/panel.js:824:9 wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22 _Base.prototype._construct@resource:///org/gnome/gjs/modules/_legacy.js:18:5 Class.prototype._construct/newClass@resource:///org/gnome/gjs/modules/_legacy.js:114:32 _initializeUI@resource:///org/gnome/shell/ui/main.js:184:13 start@resource:///org/gnome/shell/ui/main.js:133:5 @
:1:31 ** Message: 17:44:47.967: Execution of main.js threw exception: Script
threw an exception (gnome-shell:11627): Gjs-CRITICAL **: 17:44:48.001: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. (gnome-shell:11627): Gjs-CRITICAL **: 17:44:48.001: The offending signal was destroy on StBoxLayout 0x300173ea30. == Stack trace for context 0x3000475320 == (gnome-shell:11627): Gjs-CRITICAL **: 17:44:48.002: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. (gnome-shell:11627): Gjs-CRITICAL **: 17:44:48.002: The offending signal was destroy on StBoxLayout 0x30017308b0. == Stack trace for context 0x3000475320 == (gnome-shell:11627): Gjs-CRITICAL **: 17:44:48.003: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. (gnome-shell:11627): Gjs-CRITICAL **: 17:44:48.003: The offending signal was destroy on StBoxLayout 0x3001736170. == Stack trace for context 0x3000475320 == ```

But it works on vncserver! I already shared termux tmp! Screenshot_20230606-174606_RVNC Viewer Screenshot_20230606-174641_RVNC Viewer

twaik commented 1 year ago

Did you try termux-x11 -extension MIT-SHM :0?

binhvo7794 commented 1 year ago

Did you try termux-x11 -extension MIT-SHM :0?

Still same errors

twaik commented 1 year ago

Does xfce4-session work?

binhvo7794 commented 1 year ago

Does xfce4-session work?

Yes, xfce4 works

twaik commented 1 year ago

I am not sure what exactly is wrong here, logs are not so informative. Can not fix it.

binhvo7794 commented 1 year ago

https://github.com/termux/termux-x11/assets/66165345/5396d69d-7d0e-4d0a-a751-e5a12a35d3cf

twaik commented 1 year ago

Still not informative. Video will not help here.

ask9027 commented 1 year ago

screen-20230606-221822.mp4

how you install gnome in ubuntu in proot-distro(just want)?

Saikatsaha1996 commented 1 year ago

In my device debian perfectly working .. My bad luck jammy not working..

Try to login with

proot-distro login debian --bind /dev/null:/dev/dri/card0 --shared-tmp --bind /sdcard:/sdcard --bind /dev/null:/proc/sys/kernel/cap_last_cap

But

Just remove pid file..

Create a file like this..

nano /usr/bin/desktop

#!/bin/sh
export XDG_CURRENT_DESKTOP="GNOME"
export XDG_RUNTIME_DIR=/tmp
sudo service dbus start
gnome-shell --x11

chmod +x /usr/bin/desktop

creat a xstartup

mkdir .vnc nano .vnc/xstartup

#!/bin/sh
/usr/bin/desktop

Then exit from proot the start termux-x11 open termux-x11 u will see black screen with x cursor.. go to preference enable pip mode..

Then re-login proot & run

desktop

If you login as user use sudo desktop

I am sure in your device not working because you mey not mentioned session name or runtime dir

Screenshot_2023-06-07-15-05-11-01_00df01c412509efb9bd6450c382822af

binhvo7794 commented 1 year ago

In my device debian perfectly working .. My bad luck jammy not working..

Try to login with

proot-distro login debian --bind /dev/null:/dev/dri/card0 --shared-tmp --bind /sdcard:/sdcard --bind /dev/null:/proc/sys/kernel/cap_last_cap

But

Just remove pid file..

Create a file like this..

nano /usr/bin/desktop

#!/bin/sh
export XDG_CURRENT_DESKTOP="GNOME"
export XDG_RUNTIME_DIR=/tmp
sudo service dbus start
gnome-shell --x11

chmod +x /usr/bin/desktop

creat a xstartup

mkdir .vnc nano .vnc/xstartup

#!/bin/sh
/usr/bin/desktop

Then exit from proot the start termux-x11 open termux-x11 u will see black screen with x cursor.. go to preference enable pip mode..

Then re-login proot & run

desktop

If you login as user use sudo desktop

I am sure in your device not working because you mey not mentioned session name or runtime dir

Screenshot_2023-06-07-15-05-11-01_00df01c412509efb9bd6450c382822af

https://github.com/termux/termux-x11/assets/66165345/de4dabab-e231-4bdb-afdd-22a2587cc8c2

Thank you, now it worked but it so lagging and can't open any application

Saikatsaha1996 commented 1 year ago

Add one more line

nano /usr/bin/desktop

#!/bin/sh
export GALLIUM_DRIVER=llvmpipe
export XDG_CURRENT_DESKTOP="GNOME"
export XDG_RUNTIME_DIR=/tmp
sudo service dbus start
gnome-shell --x11
Saikatsaha1996 commented 1 year ago

@twaik remove bug level.. it is not bug..

binhvo7794 commented 1 year ago

Add one more line

nano /usr/bin/desktop

#!/bin/sh
export GALLIUM_DRIVER=llvmpipe
export XDG_CURRENT_DESKTOP="GNOME"
export XDG_RUNTIME_DIR=/tmp
sudo service dbus start
gnome-shell --x11

Not works sir

![Screenshot_20230607-185214_Termux](https://github.com/termux/termux-x11/assets/66165345/b5b8597b-8f82-4430-8bcd-44b7b8af8181)
twaik commented 1 year ago

it so lagging and can't open any application

It is likely not a problem of termux-x11. Besides the methods used to display an image on Android screen, Termux-X11 is a fairly standard X server. The problem is something else.

remove bug level.. it is not bug..

It was a bug until we knew that it can work with some special parameters...

Saikatsaha1996 commented 1 year ago

Add one more line nano /usr/bin/desktop

#!/bin/sh
export GALLIUM_DRIVER=llvmpipe
export XDG_CURRENT_DESKTOP="GNOME"
export XDG_RUNTIME_DIR=/tmp
sudo service dbus start
gnome-shell --x11

Not works sir

![Screenshot_20230607-185214_Termux](https://user-images.githubusercontent.com/66165345/244048641-b5b8597b-8f82-4430-8bcd-44b7b8af8181.png)

Okay remove export GALLIUM_DRIVER=llvmpipe

And add it to .bashrc

exit from proot.. re-login..

And check GALLIUM_DRIVER=llvmpipe glxinfo -B

If it show you llvm then okay if showing softpipe then it will lag..

Then check.. i hope it will work..

Don't expect better performance with 4 GB Ram ..

binhvo7794 commented 1 year ago

Add one more line

nano /usr/bin/desktop

#!/bin/sh
export GALLIUM_DRIVER=llvmpipe
export XDG_CURRENT_DESKTOP="GNOME"
export XDG_RUNTIME_DIR=/tmp
sudo service dbus start
gnome-shell --x11

Here is my log, pls see what wrong 🥹, but why u get it work perfectly, can u share what u do?

Details ``` sudo desk Removing stale PID file /var/run/dbus/pid.. Starting system message bus: dbusdbus[27835]: Unknown username "geoclue" in message bus configuration file . dbus[27844]: Unable to set up transient service directory: XDG_RUNTIME_DIR "/tmp" can be written by others (mode 041777) Xlib: extension "DPMS" missing on display ":0". Xlib: extension "DPMS" missing on display ":0". (gnome-shell:27842): GUdev-CRITICAL **: 12:05:03.535: g_udev_client_query_by_device_file: assertion 'device_file != NULL' failed (gnome-shell:27842): dbind-WARNING **: 12:05:03.560: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-3PFMwX8W8B: Connection refused (gnome-shell:27842): dbind-WARNING **: 12:05:03.631: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-3PFMwX8W8B: Connection refused GNOME Shell-Message: 12:05:04.322: Getting parental controls for user 0 (gnome-shell:27842): mutter-WARNING **: 12:05:04.756: Called enable_unredirect_for_display while unredirection is enabled. GNOME Shell-Message: 12:05:06.282: Failed to register AuthenticationAgent GNOME Shell-Message: 12:05:06.296: Telepathy is not available, chat integration will be disabled. GNOME Shell-Message: 12:05:06.703: Warning: Hiding app because parental controls not yet initialised: yelp.desktop GNOME Shell-Message: 12:05:06.754: Warning: Hiding app because parental controls not yet initialised: gnome-control-center.desktop GNOME Shell-Message: 12:05:06.756: Warning: Hiding app because parental controls not yet initialised: org.gnome.Terminal.desktop GNOME Shell-Message: 12:05:06.844: Failed to create file /tmp/gnome-shell-disable-extensions: Error opening file “/tmp/gnome-shell-disable-extensions”: File exists GNOME Shell-Message: 12:05:07.057: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.GeoClue2 was not provided by any .service files GNOME Shell-Message: 12:05:07.278: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation (gnome-shell:27842): mutter-WARNING **: 12:05:07.305: NOTE: Not using GLX TFP! (gnome-shell:27842): Clutter-WARNING **: 12:05:07.682: Bogus presentation time 0 travelled back in time, using current time. GNOME Shell-Message: 12:05:07.705: GNOME Shell started at Wed Jun 07 2023 12:05:06 GMT+0000 (UTC) GNOME Shell-Message: 12:05:07.735: Registering session with GDM GNOME Shell-Message: 12:05:08.128: Error registering session with GDM: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.DisplayManager was not provided by any .service files ```
lin-calvin commented 1 year ago

Add one more line nano /usr/bin/desktop

#!/bin/sh
export GALLIUM_DRIVER=llvmpipe
export XDG_CURRENT_DESKTOP="GNOME"
export XDG_RUNTIME_DIR=/tmp
sudo service dbus start
gnome-shell --x11

Here is my log, pls see what wrong 🥹, but why u get it work perfectly, can u share what u do? Details

I found a way to deal with it just delete the file /usr/share/dbus-1/system-services/org.freedesktop.login1.service and it will run