Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Bug#995811: enlightenment: Firefox does not respond to mouse cursor/keys until you double press F11

118 views
Skip to first unread message

Dmitri Sinitin

unread,
Oct 6, 2021, 7:10:03 AM10/6/21
to
Package: enlightenment
Version: 0.24.2-8
Severity: normal
X-Debbugs-Cc: thedrunky...@gmail.com

Hello!
Hope you are doing well!

Unlike other wayland compositors (weston etc) in enlightenment you have to enter fullscreen mode at least in Firefox so it begun to react at the mouse pointer events.
After that the menus are still immune to clicks. Hotkeys works flawless.

ffstart command:
MOZ_ENABLE_WAYLAND=1 firefox


-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.14.0-2-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages enlightenment depends on:
ii dbus-user-session [default-dbus-session-bus] 1.12.20-2
ii enlightenment-data 0.24.2-8
ii libasound2 1.2.5.1-1
ii libbluetooth3 5.61-1
ii libc6 2.32-4
ii libecore-con1 1.25.1-1
ii libecore-drm2-1 1.25.1-1
ii libecore-evas1 1.25.1-1
ii libecore-file1 1.25.1-1
ii libecore-input1 1.25.1-1
ii libecore-ipc1 1.25.1-1
ii libecore-wl2-1 1.25.1-1
ii libecore-x1 1.25.1-1
ii libecore1 1.25.1-1
ii libedje-bin 1.25.1-1
ii libedje1 1.25.1-1
ii libeet1 1.25.1-1
ii libeeze1 1.25.1-1
ii libefreet-bin 1.25.1-1
ii libefreet1a 1.25.1-1
ii libeina1a 1.25.1-1
ii libeio1 1.25.1-1
ii libelementary1 1.25.1-1
ii libelput1 1.25.1-1
ii libemile1 1.25.1-1
ii libemotion1 1.25.1-1
ii libevas1 1.25.1-1
ii libevas1-engines-drm 1.25.1-1
ii libevas1-engines-wayland 1.25.1-1
ii libevas1-engines-x 1.25.1-1
ii libpam0g 1.4.0-10
ii libpulse0 15.0+dfsg1-2
ii libuuid1 2.37.2-3
ii libwayland-client0 1.19.0-2+b1
ii libwayland-server0 1.19.0-2+b1
ii libxkbcommon0 1.0.3-2

Versions of packages enlightenment recommends:
ii acpid 1:2.0.32-1
ii bc 1.07.1-3+b1
ii bluez 5.61-1
ii libddcutil3 0.9.9-2
ii libevas-loaders 1.25.1-1
ii packagekit 1.2.2-2
ii terminology [x-terminal-emulator] 1.9.0-2
ii udisks2 2.9.4-1

Versions of packages enlightenment suggests:
pn gdb <none>
pn x-display-manager <none>

-- no debconf information

Ross Vandegrift

unread,
Oct 6, 2021, 3:00:02 PM10/6/21
to
Hi Dmitri,

On Wed, Oct 06, 2021 at 01:02:06PM +0200, Dmitri Sinitin wrote:
> Unlike other wayland compositors (weston etc) in enlightenment you have to enter fullscreen mode at least in Firefox so it begun to react at the mouse pointer events.
> After that the menus are still immune to clicks. Hotkeys works flawless.
>
> ffstart command:
> MOZ_ENABLE_WAYLAND=1 firefox

I tried this with firefox-esr from bullseye, and I only got the
client-side decorations. The main content is all black, and nothing
brings the mouse to life. :(

Upstream usually suggests that if you want to use wayland, you should
build from git. So even though it's enabled in the packages, I'm not
surprised to hear that it isn't usable.

Sorry,
Ross

Трезвый Дворник

unread,
Oct 6, 2021, 6:30:02 PM10/6/21
to
Hi Ross,
Thanks for your reply!

I do believe the esr version has no wayland support at this moment. I've checked at my workstation with AMD radeon graphics, the initial report was made from a notebook with Intel graphics.
Here is the same problem, but I get  FF react after any window size change, not only by the full screen trick.

Also i've checked the library versions

curl -s "https://www.enlightenment.org/download" | grep "EFL<\|Enlightenment<" | awk -F'[<>]' '{print $5, $11}'
EFL 1.25.1
Python-EFL 1.25.0
Enlightenment 0.24.2

aptitude search ~i~mpkg-e-devel ~ifirefox$ -F '%p %v'
enlightenment            0.24.2-8      
enlightenment-data       0.24.2-8      
firefox                  93.0-1        
libecore-audio1          1.25.1-1      
libecore-bin             1.25.1-1      
libecore-con1            1.25.1-1      
libecore-drm2-1          1.25.1-1      
libecore-evas1           1.25.1-1      
libecore-fb1             1.25.1-1      
libecore-file1           1.25.1-1      
libecore-imf1            1.25.1-1      
libecore-input1          1.25.1-1      
libecore-ipc1            1.25.1-1      
libecore-wl2-1           1.25.1-1      
libecore-x1              1.25.1-1      
libecore1                1.25.1-1      
libector1                1.25.1-1      
libedje-bin              1.25.1-1      
libedje1                 1.25.1-1      
libeet1                  1.25.1-1      
libeeze1                 1.25.1-1      
libefreet-bin            1.25.1-1      
libefreet1a              1.25.1-1      
libeina1a                1.25.1-1      
libeio1                  1.25.1-1      
libelementary-bin        1.25.1-1      
libelementary-data       1.25.1-1      
libelementary1           1.25.1-1      
libelput1                1.25.1-1      
libembryo-bin            1.25.1-1      
libembryo1               1.25.1-1      
libemile1                1.25.1-1      
libemotion1              1.25.1-1      
libethumb-client-bin     1.25.1-1      
libethumb-client1        1.25.1-1      
libethumb1               1.25.1-1      
libevas-loaders          1.25.1-1      
libevas1                 1.25.1-1      
libevas1-engines-drm     1.25.1-1      
libevas1-engines-fb      1.25.1-1      
libevas1-engines-wayland 1.25.1-1      
libevas1-engines-x       1.25.1-1 


Upstream usually suggests that if you want to use wayland, you should
build from git.  So even though it's enabled in the packages, I'm not
surprised to hear that it isn't usable.


Will try to build from git on weekend

Best regards
 
0 new messages