termux / termux-packages

A package build system for Termux.
https://termux.dev
Other
13.1k stars 3k forks source link

[Bug]: firefox not working under wayland #18360

Open TobiaszCudnik opened 11 months ago

TobiaszCudnik commented 11 months ago

Problem description

Because wayland seems to be deliberately disable in GTK3 (and 4), Firefox doesnt start, crashing on "no DISPLAY" instead.

Considering its 2023 and both wlroots and sway are available in this repo, theres no reason to disable wayland in one of the main UI libraries.

-Dwayland_backend=false in https://github.com/termux/termux-packages/blob/master/x11-packages/gtk3/build.sh

What steps will reproduce the bug?

  1. Start sway
  2. Start wayvnc
  3. Start xterm
  4. Start firefox

What is the expected behavior?

Firefox starts using the wayland renderer.

System information

termux-info:

Termux Variables:
TERMUX_API_VERSION=0.50.1
TERMUX_APK_RELEASE=F_DROID
TERMUX_APP_PACKAGE_MANAGER=apt
TERMUX_APP_PID=10924
TERMUX_IS_DEBUGGABLE_BUILD=0
TERMUX_MAIN_PACKAGE_FORMAT=debian
TERMUX_VERSION=0.118.0
Packages CPU architecture:
aarch64
Subscribed repositories:
# sources.list
deb https://is.mirror.flokinet.net/termux/termux-main stable main
# root-repo (sources.list.d/root.list)
deb https://is.mirror.flokinet.net/termux/termux-root root stable
# x11-repo (sources.list.d/x11.list)
deb https://is.mirror.flokinet.net/termux/termux-x11 x11 main
# tur-repo (sources.list.d/tur.list)
deb https://tur.kcubeterm.com tur-packages tur tur-on-device tur-continuous
Updatable packages:
All packages up to date
termux-tools version:
1.39.3
Android version:
12
Kernel build information:
Linux localhost 5.10.101-android12-9-00001-gf4c0e37dbcde-ab8596533 #1 SMP PREEMPT Mon May 16 05:21:23 UTC 2022 aarch64 Android
Device manufacturer:
nubia
Device model:
NX679J
LD Variables:
LD_LIBRARY_PATH=
LD_PRELOAD=/data/data/com.termux/files/usr/lib/libtermux-exec.so
Installed termux plugins:
com.termux.api versionCode:51
com.termux.boot versionCode:7
com.termux.widget versionCode:13
twaik commented 11 months ago

theres no reason to disable wayland in one of the main UI libraries.

Actually there is a reason. In the most cases Wayland compositors require real GL which is not available on Android devices.