[Desktop-packages] [Bug 1970884]
IIUC there are now several runners using Ubuntu 22.04, notably for bug 1813588, so I guess this can be closed and most dependent bugs can depend on that bug instead? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1970884 Title: Firefox snap does not use wayland backend by default Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: In Progress Bug description: Previous versions of Firefox worked with the wayland backend, with the latest version ( 99.0.1 ) wayland is not available and it has to use xwayland. This breaks the screen sharing and also the fonts are not as sharp as using the wayland backend. Nightly version 101.0a1 without snap works fine. ``` Gtk-Message: 09:20:51.884: Failed to load module "canberra-gtk-module" Gtk-Message: 09:20:51.885: Failed to load module "canberra-gtk-module" [GFX1-]: glxtest: Could not connect to wayland socket ``` Tested on Ubuntu 21.10 and 22.04 with the latest updates. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-06-21 (315 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Snap: firefox 99.0.1-1 (latest/stable/ubuntu-22.04) Snap.Changes: no changes found Tags: jammy wayland-session Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-28 (4 days ago) UserGroups: docker sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1970884/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987976]
Oh wow, I think I just managed to reproduce this on my Iris laptop - in a fresh session with Xwayland on demand. That and comment 45 points to a race condition in the FF code regarding switching between composited and non-composited X11. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1987976 Title: firefox black window Status in Mozilla Firefox: Confirmed Status in Mutter: New Status in firefox package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: nicolas@nicolas-fixe:~$ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 nicolas@nicolas-fixe:~$ apt-cache policy firefox firefox: Installé : 1:1snap1-0ubuntu2 Candidat : 1:1snap1-0ubuntu2 Table de version : *** 1:1snap1-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status When I boot Ubuntu and start Firefox, the Firefox's window is totally black. See attachment. I am at your disposal to answer any question you have. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 12:42:29 2022 InstallationDate: Installed on 2022-08-25 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Snap.Changes: aucun changement trouvé SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987976]
Since this was reported for a device running the Crocus Mesa driver in situations where implicit drm modifiers are most likely used (Xwayland, X11 compositor), there's certain chance that it will be fixed by https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/21209 Michelet/Alan, any chance you could test that commit? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1987976 Title: firefox black window Status in Mozilla Firefox: Confirmed Status in Mutter: New Status in firefox package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: nicolas@nicolas-fixe:~$ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 nicolas@nicolas-fixe:~$ apt-cache policy firefox firefox: Installé : 1:1snap1-0ubuntu2 Candidat : 1:1snap1-0ubuntu2 Table de version : *** 1:1snap1-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status When I boot Ubuntu and start Firefox, the Firefox's window is totally black. See attachment. I am at your disposal to answer any question you have. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 12:42:29 2022 InstallationDate: Installed on 2022-08-25 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Snap.Changes: aucun changement trouvé SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987976]
Hm, this pretty much sounds like Gnome-Shell bug around Xwayland-on- demand to me - so maybe a better place for that would be https://gitlab.gnome.org/GNOME/mutter/-/issues (or a Ubuntu bug, in case they ship some custom patches). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1987976 Title: firefox black window Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Confirmed Bug description: nicolas@nicolas-fixe:~$ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 nicolas@nicolas-fixe:~$ apt-cache policy firefox firefox: Installé : 1:1snap1-0ubuntu2 Candidat : 1:1snap1-0ubuntu2 Table de version : *** 1:1snap1-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status When I boot Ubuntu and start Firefox, the Firefox's window is totally black. See attachment. I am at your disposal to answer any question you have. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 12:42:29 2022 InstallationDate: Installed on 2022-08-25 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Snap.Changes: aucun changement trouvé SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987976]
So the fact that even software rendering (`gfx.webrender.software:true`) is broken strongly suggest that something with the affected setup is deeply broken - disabling hardware acceleration is usually our last resort for such issues. Alan, have you tested a few other Xwayland apps and do they all work correctly? And is this on a clean system without weird modifications? :P -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1987976 Title: firefox black window Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Confirmed Bug description: nicolas@nicolas-fixe:~$ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 nicolas@nicolas-fixe:~$ apt-cache policy firefox firefox: Installé : 1:1snap1-0ubuntu2 Candidat : 1:1snap1-0ubuntu2 Table de version : *** 1:1snap1-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status When I boot Ubuntu and start Firefox, the Firefox's window is totally black. See attachment. I am at your disposal to answer any question you have. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 12:42:29 2022 InstallationDate: Installed on 2022-08-25 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Snap.Changes: aucun changement trouvé SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987976]
Oh, that's really interesting...so does launching with `MOZ_GTK_TITLEBAR_DECORATION=system` also solve the issue? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1987976 Title: firefox black window Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Confirmed Bug description: nicolas@nicolas-fixe:~$ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 nicolas@nicolas-fixe:~$ apt-cache policy firefox firefox: Installé : 1:1snap1-0ubuntu2 Candidat : 1:1snap1-0ubuntu2 Table de version : *** 1:1snap1-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status When I boot Ubuntu and start Firefox, the Firefox's window is totally black. See attachment. I am at your disposal to answer any question you have. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 12:42:29 2022 InstallationDate: Installed on 2022-08-25 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Snap.Changes: aucun changement trouvé SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987976]
(In reply to Alan Jenkins from comment #35) > Weird! Indeed :( But thanks for testing! > I can run glxgears, xeyes, and xvidtune ok :-). (Didn't bother trying those immediately after login). I think these are all apps with server side decorations (SSD). Could you try `GDK_BACKEND=x11 cheese` or `GDK_BACKEND=x11 gedit`? So we have GTK apps with client side decorations (CSD)? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1987976 Title: firefox black window Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Confirmed Bug description: nicolas@nicolas-fixe:~$ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 nicolas@nicolas-fixe:~$ apt-cache policy firefox firefox: Installé : 1:1snap1-0ubuntu2 Candidat : 1:1snap1-0ubuntu2 Table de version : *** 1:1snap1-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status When I boot Ubuntu and start Firefox, the Firefox's window is totally black. See attachment. I am at your disposal to answer any question you have. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 12:42:29 2022 InstallationDate: Installed on 2022-08-25 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Snap.Changes: aucun changement trouvé SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987976]
Also, I suppose `gfx.webrender.software:true` works around the issue? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1987976 Title: firefox black window Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Confirmed Bug description: nicolas@nicolas-fixe:~$ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 nicolas@nicolas-fixe:~$ apt-cache policy firefox firefox: Installé : 1:1snap1-0ubuntu2 Candidat : 1:1snap1-0ubuntu2 Table de version : *** 1:1snap1-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status When I boot Ubuntu and start Firefox, the Firefox's window is totally black. See attachment. I am at your disposal to answer any question you have. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 12:42:29 2022 InstallationDate: Installed on 2022-08-25 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Snap.Changes: aucun changement trouvé SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987976]
Another interesting point would be if setting `gfx.x11-egl.force- disabled` (in `about:config`) to `true` helps with the issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1987976 Title: firefox black window Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Confirmed Bug description: nicolas@nicolas-fixe:~$ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 nicolas@nicolas-fixe:~$ apt-cache policy firefox firefox: Installé : 1:1snap1-0ubuntu2 Candidat : 1:1snap1-0ubuntu2 Table de version : *** 1:1snap1-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status When I boot Ubuntu and start Firefox, the Firefox's window is totally black. See attachment. I am at your disposal to answer any question you have. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 12:42:29 2022 InstallationDate: Installed on 2022-08-25 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Snap.Changes: aucun changement trouvé SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930485]
Closing as unresponsive (and likely fixed).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1930485
Title:
Can't Start Firefox 88 on Weston/Wayland, Ubuntu 18.0.4.
Status in Mozilla Firefox:
Unknown
Status in firefox package in Ubuntu:
New
Bug description:
I am running Weston/Wayland on Ubuntu 18.0.4.
I am able to successfully start the display server:
```
export XDG_RUNTIME_DIR=/run/weston
weston --tty 1 &
```
Next, I try to run firefox on it:
```
export XDG_RUNTIME_DIR=/run/weston
export GDK_BACKEND=wayland
export MOZ_ENABLE_WAYLAND=1
export DISPLAY=wayland-0
export LD_LIBRARY_PATH=/usr/lib:/usr/lib/aarch64-linux-gnu/
export WAYLAND_DEBUG=1
export WAYLAND_DISPLAY=wayland-0
firefox \
--g-fatal-warnings \
--kiosk \
--private-window \
https://bing.com
```
This outputs:
```
[1446891.592] -> wl_display@1.get_registry(new id wl_registry@2)
[1446891.702] -> wl_disp...@1.sync(new id wl_callback@3)
[1446893.656] wl_display@1.delete_id(3)
[1446893.737] wl_registry@2.global(1, "wl_compositor", 4)
[1446893.781] -> wl_regis...@2.bind(1, "wl_compositor", 3, new id
[unknown]@4)
[1446893.852] wl_registry@2.global(2, "wl_subcompositor", 1)
[1446893.889] -> wl_regis...@2.bind(2, "wl_subcompositor", 1, new id
[unknown]@5)
[1446893.938] wl_registry@2.global(3, "wp_viewporter", 1)
[1446893.973] wl_registry@2.global(4, "wp_presentation", 1)
[1446894.007] wl_registry@2.global(5, "zwp_relative_pointer_manager_v1", 1)
[1446894.041] wl_registry@2.global(6, "zwp_pointer_constraints_v1", 1)
[1446894.075] wl_registry@2.global(7, "wl_data_device_manager", 3)
[1446894.109] -> wl_regis...@2.bind(7, "wl_data_device_manager", 3, new id
[unknown]@6)
[1446894.156] wl_registry@2.global(8, "wl_shm", 1)
[1446894.190] -> wl_regis...@2.bind(8, "wl_shm", 1, new id [unknown]@7)
[1446894.429] -> wl_shm@7.create_pool(new id wl_shm_pool@8, fd 9, 2304)
[1446894.974] -> wl_shm_pool@8.resize(5568)
[1446895.214] -> wl_shm_pool@8.resize(12096)
[1446895.273] wl_registry@2.global(9, "wayland_buffer_backend", 4)
[1446895.315] wl_registry@2.global(10, "wl_seat", 5)
[1446895.353] -> wl_regis...@2.bind(10, "wl_seat", 5, new id [unknown]@9)
[1446925.977] -> wl_compositor@4.create_surface(new id wl_surface@10)
[1446926.203] -> wl_data_device_manager@6.get_data_device(new id
wl_data_device@11, wl_seat@9)
[1446926.370] -> wl_compositor@4.create_surface(new id wl_surface@12)
[1446926.636] -> wl_disp...@1.sync(new id wl_callback@13)
[1446926.765] wl_registry@2.global(11, "zwp_linux_dmabuf_v1", 3)
[1446926.845] wl_registry@2.global(12, "gbm_buffer_backend", 1)
[1446926.906] wl_registry@2.global(13, "wl_output", 3)
[1446926.965] -> wl_regis...@2.bind(13, "wl_output", 2, new id [unknown]@14)
[1446927.172] -> wl_disp...@1.sync(new id wl_callback@15)
[1446927.246] wl_registry@2.global(14, "zwp_input_panel_v1", 1)
[1446927.319] wl_registry@2.global(15, "zwp_input_method_v1", 1)
[1446927.378] wl_registry@2.global(16, "zwp_text_input_manager_v1", 1)
[1446927.436] wl_registry@2.global(17, "zxdg_shell_v6", 1)
[1446927.494] wl_registry@2.global(18, "xdg_shell", 1)
[1446927.585] wl_registry@2.global(19, "wl_shell", 1)
[1446927.643] wl_registry@2.global(20, "weston_desktop_shell", 1)
[1446927.716] wl_registry@2.global(21, "weston_screenshooter", 1)
[1446927.777] wl_callb...@3.done(1)
[1446929.537] wl_display@1.delete_id(13)
[1446929.624] wl_display@1.delete_id(15)
[1446929.656] wl_shm@7.format(0)
[1446929.684] wl_shm@7.format(1)
[1446929.709] wl_shm@7.format(909199186)
[1446929.733] wl_shm@7.format(842093913)
[1446929.758] wl_shm@7.format(842094158)
[1446929.783] wl_shm@7.format(1448695129)
[1446929.807] wl_seat@9.capabilities(2)
[1446929.834] -> wl_seat@9.get_keyboard(new id wl_keyboard@3)
[1446929.903] wl_s...@9.name("default")
[1446929.931] wl_callb...@13.done(1)
[1446929.958] wl_output@14.geometry(0, 0, 0, 0, 0, "QCM", "unknown", 0)
[1446930.094] wl_output@14.scale(1)
[1446930.123] wl_out...@14.mode(3, 1920, 1080, 6)
[1446930.193] wl_out...@14.done()
[1446930.245] wl_callb...@15.done(1)
[1446930.278] -> wl_regis...@2.bind(17, "zxdg_shell_v6", 1, new id
[unknown]@15)
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: eglBindAPI
returned an error (t=0.548409) [GFX1-]: glxtest: eglBindAPI returned an error
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: eglBindAPI
returned an error (t=0.548409) |[1][GFX1-]: glxtest: EGL test failed
(t=0.548476) [GFX1-]: glxtest: EGL test failed
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: eglBindAPI
returned an error (t=0.548409) |[1][GFX1-]: glxtest: EGL test failed
(t=0.548476) |[2][GFX1-]: No GPUs detected via PCI (t=0.548504) [GFX1-]: No
GPUs detected via
[Desktop-packages] [Bug 1930485]
This should have been fixed a while ago and it works for me -
jhwilliams, can you still reproduce this issue?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1930485
Title:
Can't Start Firefox 88 on Weston/Wayland, Ubuntu 18.0.4.
Status in Mozilla Firefox:
New
Status in firefox package in Ubuntu:
New
Bug description:
I am running Weston/Wayland on Ubuntu 18.0.4.
I am able to successfully start the display server:
```
export XDG_RUNTIME_DIR=/run/weston
weston --tty 1 &
```
Next, I try to run firefox on it:
```
export XDG_RUNTIME_DIR=/run/weston
export GDK_BACKEND=wayland
export MOZ_ENABLE_WAYLAND=1
export DISPLAY=wayland-0
export LD_LIBRARY_PATH=/usr/lib:/usr/lib/aarch64-linux-gnu/
export WAYLAND_DEBUG=1
export WAYLAND_DISPLAY=wayland-0
firefox \
--g-fatal-warnings \
--kiosk \
--private-window \
https://bing.com
```
This outputs:
```
[1446891.592] -> wl_display@1.get_registry(new id wl_registry@2)
[1446891.702] -> wl_disp...@1.sync(new id wl_callback@3)
[1446893.656] wl_display@1.delete_id(3)
[1446893.737] wl_registry@2.global(1, "wl_compositor", 4)
[1446893.781] -> wl_regis...@2.bind(1, "wl_compositor", 3, new id
[unknown]@4)
[1446893.852] wl_registry@2.global(2, "wl_subcompositor", 1)
[1446893.889] -> wl_regis...@2.bind(2, "wl_subcompositor", 1, new id
[unknown]@5)
[1446893.938] wl_registry@2.global(3, "wp_viewporter", 1)
[1446893.973] wl_registry@2.global(4, "wp_presentation", 1)
[1446894.007] wl_registry@2.global(5, "zwp_relative_pointer_manager_v1", 1)
[1446894.041] wl_registry@2.global(6, "zwp_pointer_constraints_v1", 1)
[1446894.075] wl_registry@2.global(7, "wl_data_device_manager", 3)
[1446894.109] -> wl_regis...@2.bind(7, "wl_data_device_manager", 3, new id
[unknown]@6)
[1446894.156] wl_registry@2.global(8, "wl_shm", 1)
[1446894.190] -> wl_regis...@2.bind(8, "wl_shm", 1, new id [unknown]@7)
[1446894.429] -> wl_shm@7.create_pool(new id wl_shm_pool@8, fd 9, 2304)
[1446894.974] -> wl_shm_pool@8.resize(5568)
[1446895.214] -> wl_shm_pool@8.resize(12096)
[1446895.273] wl_registry@2.global(9, "wayland_buffer_backend", 4)
[1446895.315] wl_registry@2.global(10, "wl_seat", 5)
[1446895.353] -> wl_regis...@2.bind(10, "wl_seat", 5, new id [unknown]@9)
[1446925.977] -> wl_compositor@4.create_surface(new id wl_surface@10)
[1446926.203] -> wl_data_device_manager@6.get_data_device(new id
wl_data_device@11, wl_seat@9)
[1446926.370] -> wl_compositor@4.create_surface(new id wl_surface@12)
[1446926.636] -> wl_disp...@1.sync(new id wl_callback@13)
[1446926.765] wl_registry@2.global(11, "zwp_linux_dmabuf_v1", 3)
[1446926.845] wl_registry@2.global(12, "gbm_buffer_backend", 1)
[1446926.906] wl_registry@2.global(13, "wl_output", 3)
[1446926.965] -> wl_regis...@2.bind(13, "wl_output", 2, new id [unknown]@14)
[1446927.172] -> wl_disp...@1.sync(new id wl_callback@15)
[1446927.246] wl_registry@2.global(14, "zwp_input_panel_v1", 1)
[1446927.319] wl_registry@2.global(15, "zwp_input_method_v1", 1)
[1446927.378] wl_registry@2.global(16, "zwp_text_input_manager_v1", 1)
[1446927.436] wl_registry@2.global(17, "zxdg_shell_v6", 1)
[1446927.494] wl_registry@2.global(18, "xdg_shell", 1)
[1446927.585] wl_registry@2.global(19, "wl_shell", 1)
[1446927.643] wl_registry@2.global(20, "weston_desktop_shell", 1)
[1446927.716] wl_registry@2.global(21, "weston_screenshooter", 1)
[1446927.777] wl_callb...@3.done(1)
[1446929.537] wl_display@1.delete_id(13)
[1446929.624] wl_display@1.delete_id(15)
[1446929.656] wl_shm@7.format(0)
[1446929.684] wl_shm@7.format(1)
[1446929.709] wl_shm@7.format(909199186)
[1446929.733] wl_shm@7.format(842093913)
[1446929.758] wl_shm@7.format(842094158)
[1446929.783] wl_shm@7.format(1448695129)
[1446929.807] wl_seat@9.capabilities(2)
[1446929.834] -> wl_seat@9.get_keyboard(new id wl_keyboard@3)
[1446929.903] wl_s...@9.name("default")
[1446929.931] wl_callb...@13.done(1)
[1446929.958] wl_output@14.geometry(0, 0, 0, 0, 0, "QCM", "unknown", 0)
[1446930.094] wl_output@14.scale(1)
[1446930.123] wl_out...@14.mode(3, 1920, 1080, 6)
[1446930.193] wl_out...@14.done()
[1446930.245] wl_callb...@15.done(1)
[1446930.278] -> wl_regis...@2.bind(17, "zxdg_shell_v6", 1, new id
[unknown]@15)
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: eglBindAPI
returned an error (t=0.548409) [GFX1-]: glxtest: eglBindAPI returned an error
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: eglBindAPI
returned an error (t=0.548409) |[1][GFX1-]: glxtest: EGL test failed
(t=0.548476) [GFX1-]: glxtest: EGL test failed
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: eglBindAPI
returned an error (t=0.548409) |[1][GFX1-]: glxtest: EGL test failed
(t=0.548476) |[2][GFX1-]: No
[Desktop-packages] [Bug 1871644]
(In reply to Emilio Cobos Álvarez (:emilio) from comment #30) > So given there's no way to access the other border corners, and that this > works for our purposes, I think we should probably just roll with it, > thoughts? I'd agree - should work well for almost everyone. One question I had to think of is if we want to use rounded corners at the bottom at some point - more and more GTK4 apps do that, e.g. nautilus/files. But we can also leave that for the future. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1871644 Title: Top corners of Firefox windows have weird black protrusions from the rounded edges Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Image to illustrate the problem is attached. All firefox windows on Wayland (EDIT: and X11) have a weird black protrusion from the top- left and top-right corners where yaru has curved the window corners, but something from Firefox appears to not be being clipped by the theme. I need to double check whether this appears on X11, but for now consider it Wayland only until I report back, although oSoMoN has checked their system and they don't see the behaviour (on X11). EDIT: I have now checked X11 on my system and I see the same behaviour as described above, so this is affecting BOTH Wayland AND X11 for me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 BuildID: 20200403170909 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 14:48:56 2020 InstallationDate: Installed on 2020-03-03 (35 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1871644/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871644]
Thanks emilio, that's a good hint. The comment says > It may cause performance issues so let's put it under a preference and enable > it for desktop environment which do that by default. This is clearly outdated and from a pre Webrender time. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1871644 Title: Top corners of Firefox windows have weird black protrusions from the rounded edges Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Image to illustrate the problem is attached. All firefox windows on Wayland (EDIT: and X11) have a weird black protrusion from the top- left and top-right corners where yaru has curved the window corners, but something from Firefox appears to not be being clipped by the theme. I need to double check whether this appears on X11, but for now consider it Wayland only until I report back, although oSoMoN has checked their system and they don't see the behaviour (on X11). EDIT: I have now checked X11 on my system and I see the same behaviour as described above, so this is affecting BOTH Wayland AND X11 for me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 BuildID: 20200403170909 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 14:48:56 2020 InstallationDate: Installed on 2020-03-03 (35 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1871644/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871644]
This just became even more prominent in 95 with colorways. We need a way to support this with alpha visuals as XShape is neither available on Wayland nor on X11 with HW Webrender - i.e. it's only available in legacy fallback paths. As the default theme supports this (even though with a grey corner), I suppose this is not really a graphics but rather a theme issue. Emilio, do you happen to know how the default theme gets its corners and what would need to be done to make it work for other themes as well? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1871644 Title: Top corners of Firefox windows have weird black protrusions from the rounded edges Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Image to illustrate the problem is attached. All firefox windows on Wayland (EDIT: and X11) have a weird black protrusion from the top- left and top-right corners where yaru has curved the window corners, but something from Firefox appears to not be being clipped by the theme. I need to double check whether this appears on X11, but for now consider it Wayland only until I report back, although oSoMoN has checked their system and they don't see the behaviour (on X11). EDIT: I have now checked X11 on my system and I see the same behaviour as described above, so this is affecting BOTH Wayland AND X11 for me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 BuildID: 20200403170909 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 14:48:56 2020 InstallationDate: Installed on 2020-03-03 (35 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1871644/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915870] Re: gnome-shell/gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so]
Just got crash reports at Firefox about this - apparently visiting/closing any website with WebGL is enough to trigger this on affected drivers. https://crash- stats.mozilla.org/report/index/318626ed-3353-4bf4-8df2-75ccb0210403 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1915870 Title: gnome-shell/gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so] Status in Mesa: Unknown Status in mesa package in Ubuntu: Fix Released Status in mesa package in Fedora: Confirmed Bug description: Graphical user interface is not coming up upon start. Only SSH is possible. lsb_release -rd: Description: Ubuntu 20.10 Release: 20.10 dmesg: [ 11.985343] gnome-session-c[1013]: segfault at 0 ip sp 7fff7679ca48 error 14 in gnome-session-check-accelerated-gl-helper[56020e238000+2000] [ 11.985352] Code: Unable to access opcode bytes at RIP 0xffd6. [ 14.216117] gnome-shell[1094]: segfault at 0 ip sp 7ffeddff9f88 error 14 [ 14.216122] Code: Unable to access opcode bytes at RIP 0xffd6. [ 15.316292] gnome-shell[1109]: segfault at 0 ip sp 7ffc70716198 error 14 [ 15.316297] Code: Unable to access opcode bytes at RIP 0xffd6. apt-cache policy: gnome-session: Installed: (none) Candidate: 3.38.0-1ubuntu1 Version table: 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages gnome-session-bin: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status gnome-session-common: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages 100 /var/lib/dpkg/status /var/crash: see attachment To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1915870/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1917191]
Jan, this might be important for you as well (archlinux). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1917191 Title: firefox will not start after it crashed unexpectedly Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Confirmed Bug description: firefox crashed unexpectedly, and it will not start or restart. I am running the latest ubuntu-20.04.2 LTS, all updates applied. firefox 86.0+build3 --- ProblemType: Bug AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: johnfg 1725 F pulseaudio /dev/snd/controlC1: johnfg 1725 F pulseaudio BuildID: 20210222142601 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:348 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing DistroRelease: Ubuntu 20.04 ForcedLayersAccel: False InstallationDate: Installed on 2020-02-22 (371 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IpRoute: default via 192.168.1.1 dev wlp10s0 proto dhcp metric 600 10.8.0.0/24 via 10.8.0.17 dev tun0 10.8.0.17 dev tun0 proto kernel scope link src 10.8.0.18 169.254.0.0/16 dev wlp10s0 scope link metric 1000 192.168.1.0/24 dev wlp10s0 proto kernel scope link src 192.168.1.8 metric 600 NonfreeKernelModules: openafs Package: firefox 86.0+build3-0ubuntu0.20.04.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:348 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=80.0/20200818235255 (Out of date) Profile0 - LastVersion=86.0/20210222142601 RunningIncompatibleAddons: False Tags: focal Uname: Linux 5.4.0-66-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-24 (309 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/05/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V4.00L12 dmi.board.asset.tag: No Asset Tag dmi.board.name: CF52-4 dmi.board.vendor: Panasonic Corporation dmi.board.version: 1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Panasonic Corporation dmi.chassis.version: 001 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV4.00L12:bd07/05/2011:svnPanasonicCorporation:pnCF-52SLGDD1M:pvr004:rvnPanasonicCorporation:rnCF52-4:rvr1:cvnPanasonicCorporation:ct10:cvr001: dmi.product.family: CF52-4 dmi.product.name: CF-52SLGDD1M dmi.product.sku: CF-52SLGDD1M dmi.product.version: 004 dmi.sys.vendor: Panasonic Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1917191/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905330] [NEW] Backport Wayland frame callback fix for 3.28 for Firefox testing infrastructure
Public bug reported: The Firefox testing infrastructure is based on Ubuntu 18.04. In order to enable the Wayland backend by default, we need to also run test on that. There is one particular bug in Mutter 3.28 that I'd like to see fixed for that, thus requesting a backport of a patch. It's already in the upstream repo, but as 3.28 is not supported upstream any more, I request it here explicitly: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1570 @vanvugt @3v1n0 this would be super helpful for us, I hope I can convince you about that, even if Ubuntu 18.04 doesn't support Wayland officially. It can be tested by running Firefox with `MOZ_ENABLE_WAYLAND=1` and setting `widget.wayland_vsync.enabled:1` in the config (soon to be enabled by default). If, after launching Firefox again, everything works as expected - well, then it works. Bonus: the patch also affects a number of other Wayland applications, so some users might be happy to see it as well. ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: wayland ** Tags added: wayland ** Description changed: The Firefox testing infrastructure is based on Ubuntu 18.04. In order to - enable the Wayland backend by default, we need to enable it for the - Wayland backend first. + enable the Wayland backend by default, we need to also run test on that. There is one particular bug in Mutter 3.28 that I'd like to see fixed for that, thus requesting a backport of a patch. It's already in the upstream repo, but as 3.28 is not supported upstream any more, I request it here explicitly: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1570 @vanvugt @3v1n0 this would be super helpful for us, I hope I can convince you about that, even if Ubuntu 18.04 doesn't support Wayland officially. It can be tested by running Firefox with `MOZ_ENABLE_WAYLAND=1` and setting `widget.wayland_vsync.enabled:1` in the config (soon to be enabled by default). If, after launching Firefox again, everything works as expected - well, then it works. Bonus: the patch also affects a number of other Wayland applications, so some users might be happy to see it as well. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1905330 Title: Backport Wayland frame callback fix for 3.28 for Firefox testing infrastructure Status in mutter package in Ubuntu: New Bug description: The Firefox testing infrastructure is based on Ubuntu 18.04. In order to enable the Wayland backend by default, we need to also run test on that. There is one particular bug in Mutter 3.28 that I'd like to see fixed for that, thus requesting a backport of a patch. It's already in the upstream repo, but as 3.28 is not supported upstream any more, I request it here explicitly: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1570 @vanvugt @3v1n0 this would be super helpful for us, I hope I can convince you about that, even if Ubuntu 18.04 doesn't support Wayland officially. It can be tested by running Firefox with `MOZ_ENABLE_WAYLAND=1` and setting `widget.wayland_vsync.enabled:1` in the config (soon to be enabled by default). If, after launching Firefox again, everything works as expected - well, then it works. Bonus: the patch also affects a number of other Wayland applications, so some users might be happy to see it as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1905330/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893021]
Ouch, sorry and thanks for that! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1893021 Title: Flash plugin symbol lookup error with firefox 80.0+build2 on xenial (gtk_window_set_titlebar) Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Committed Bug description: When testing firefox 80.0+build2 on xenial (from https://launchpad.net /~ubuntu-mozilla-security/+archive/ubuntu/ppa/+packages), I'm observing that the flash plugin (installed by flashplugin-installer) doesn't work. This appears to affect only xenial, flash is working in the bionic and focal builds. This is what I'm seeing when launching firefox from a terminal: /usr/lib/firefox/plugin-container: symbol lookup error: /usr/lib/firefox/libxul.so: undefined symbol: gtk_window_set_titlebar This is most likely caused by this recent upstream change: https://phabricator.services.mozilla.com/D84623 To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1893021/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1889784]
It's likely that you see bug 1658035 - should be fixed by next nightly. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1889784 Title: Hardware-accelerated video decoding (VA-API) broken in Firefox 79 (Wayland) Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Triaged Bug description: After updating Firefox from 78 to 79, hardware-accelerated video decoding no longer works properly in Wayland: streaming video gets cut off with an error message from the service. == Steps to reproduce == 1. Follow the steps in [1] to enable VA-API. 2. Open a Youtube/Twitch video (for instance https://www.twitch.tv/rifftrax), press play == What I expect to happen == For the video be played without issues (as it did with Firefox 78). == What happens == After playing for a while (anything from just a few seconds to a couple of minutes), the video stops and is replaced by a service-specific error message, such as error #3000 (in case of Twitch). Even when playing, the video also flickers green. After reloading the tab, the video again plays for a few seconds before the error message reappears. == Other info == A fix is apparently already in the works upstream [2]. * [1] https://mastransky.wordpress.com/2020/06/03/firefox-on-fedora-finally-gets-va-api-on-wayland/ * [2] https://bugzilla.mozilla.org/show_bug.cgi?id=1645671 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 79.0+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BuildID: 20200720193547 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 31 17:07:50 2020 InstallationDate: Installed on 2016-10-13 (1387 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2020-05-11T14:52:22.308877 To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1889784/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1688592]
(In reply to eric.riese from comment #34) > > In my opinion the bounty was already earned when this issue was resolved but > I don't know who gets to be the arbiter. That would certainly be Martin Stránský :) Martin, do you want to claim the bounty? If you don't care about it / don't need it yourself, you could donate it or so. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1688592 Title: Missing VA-API hardware decoding support drains battery Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Confirmed Bug description: Current devices ship with graphics devices supporting hardware decoding of certain video formats. While doing that, energy can be saved, as the main processor can go to sleep, and the graphics devices do their jobs more efficiently saving energy. Today, the browser is used a lot to watch movies. Unfortunately, the Firefox browser does not support VA-API hardware decoding, which is the interface to be used for Intel graphics device, which are included in current Intel processors. The issue in the Mozilla bug tracker [1] is open for over two years. Currently, this missing feature is a major show stopper for people using Ubuntu GNU/Linux on their laptops, as compared to Microsoft Windows one battery charge(?) lasts noticeably less time. [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1210727 To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1688592/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1424201]
(In reply to eric.riese from comment #34) > > In my opinion the bounty was already earned when this issue was resolved but > I don't know who gets to be the arbiter. That would certainly be Martin Stránský :) Martin, do you want to claim the bounty? If you don't care about it / don't need it yourself, you could donate it or so. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1424201 Title: Web browsers lacking hardware-accelerated video decoding Status in Chromium Browser: Unknown Status in Mozilla Firefox: Confirmed Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in chromium-browser package in CentOS: Unknown Bug description: The chromium team has done a great job to totally disable hardware decoding on Linux. Even ignoring the GPU blacklist does not enable GPU decoding. How ever the patch is quite simple and it's already working using this PPA ( using libVA ) : https://launchpad.net/~saiarcot895/+archive/ubuntu/chromium-dev the corresponding patch is here : http://bazaar.launchpad.net/~saiarcot895/chromium-browser/chromium- browser.trusty.beta/view/head:/debian/patches/enable_vaapi_on_linux.diff that would be great if we could have this patch indefault Ubuntu chromium build, this situation is really sad right now, google use linux to make chromeOS so chromebook are really good at playing videos but GNU/Linux chromium is slow at doing it. To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1424201/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1688592]
That should be bug 1572697 for Wayland. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1688592 Title: Missing VA-API hardware decoding support drains battery Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Current devices ship with graphics devices supporting hardware decoding of certain video formats. While doing that, energy can be saved, as the main processor can go to sleep, and the graphics devices do their jobs more efficiently saving energy. Today, the browser is used a lot to watch movies. Unfortunately, the Firefox browser does not support VA-API hardware decoding, which is the interface to be used for Intel graphics device, which are included in current Intel processors. The issue in the Mozilla bug tracker [1] is open for over two years. Currently, this missing feature is a major show stopper for people using Ubuntu GNU/Linux on their laptops, as compared to Microsoft Windows one battery charge(?) lasts noticeably less time. [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1210727 To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1688592/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1424201]
That should be bug 1572697 for Wayland. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1424201 Title: Web browsers lacking hardware-accelerated video decoding Status in Chromium Browser: Unknown Status in Mozilla Firefox: Confirmed Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in chromium-browser package in CentOS: Unknown Bug description: The chromium team has done a great job to totally disable hardware decoding on Linux. Even ignoring the GPU blacklist does not enable GPU decoding. How ever the patch is quite simple and it's already working using this PPA ( using libVA ) : https://launchpad.net/~saiarcot895/+archive/ubuntu/chromium-dev the corresponding patch is here : http://bazaar.launchpad.net/~saiarcot895/chromium-browser/chromium- browser.trusty.beta/view/head:/debian/patches/enable_vaapi_on_linux.diff that would be great if we could have this patch indefault Ubuntu chromium build, this situation is really sad right now, google use linux to make chromeOS so chromebook are really good at playing videos but GNU/Linux chromium is slow at doing it. To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1424201/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1688592]
Although this bug is only about decoding support, I'd like to leave a note about the rendering: AFAIK rendering without any slow copies requires DMABUF support, so processes can share resources on the GPU. For the Wayland backend this about to land, see bug 1552590, quote: > Wayland dmabuf surface are located in GPU and can be attached as EGLImage or wl_buffer. It allows direct rendering to GPU and share the HW buffer across processes. Also see bug 1010527 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1688592 Title: Missing VA-API hardware decoding support drains battery Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Current devices ship with graphics devices supporting hardware decoding of certain video formats. While doing that, energy can be saved, as the main processor can go to sleep, and the graphics devices do their jobs more efficiently saving energy. Today, the browser is used a lot to watch movies. Unfortunately, the Firefox browser does not support VA-API hardware decoding, which is the interface to be used for Intel graphics device, which are included in current Intel processors. The issue in the Mozilla bug tracker [1] is open for over two years. Currently, this missing feature is a major show stopper for people using Ubuntu GNU/Linux on their laptops, as compared to Microsoft Windows one battery charge(?) lasts noticeably less time. [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1210727 To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1688592/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1424201]
Although this bug is only about decoding support, I'd like to leave a note about the rendering: AFAIK rendering without any slow copies requires DMABUF support, so processes can share resources on the GPU. For the Wayland backend this about to land, see bug 1552590, quote: > Wayland dmabuf surface are located in GPU and can be attached as EGLImage or wl_buffer. It allows direct rendering to GPU and share the HW buffer across processes. Also see bug 1010527 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1424201 Title: Web browsers lacking hardware-accelerated video decoding Status in Chromium Browser: Unknown Status in Mozilla Firefox: Confirmed Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in chromium-browser package in CentOS: Unknown Bug description: The chromium team has done a great job to totally disable hardware decoding on Linux. Even ignoring the GPU blacklist does not enable GPU decoding. How ever the patch is quite simple and it's already working using this PPA ( using libVA ) : https://launchpad.net/~saiarcot895/+archive/ubuntu/chromium-dev the corresponding patch is here : http://bazaar.launchpad.net/~saiarcot895/chromium-browser/chromium- browser.trusty.beta/view/head:/debian/patches/enable_vaapi_on_linux.diff that would be great if we could have this patch indefault Ubuntu chromium build, this situation is really sad right now, google use linux to make chromeOS so chromebook are really good at playing videos but GNU/Linux chromium is slow at doing it. To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1424201/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1688592]
The dependency of this bug could probably changed from ogl-linux-beta to bug 1491303, as webrender will replace all the old rendering architecture and is already enabled on linux + intel in nightly. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1688592 Title: Missing VA-API hardware decoding support drains battery Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Current devices ship with graphics devices supporting hardware decoding of certain video formats. While doing that, energy can be saved, as the main processor can go to sleep, and the graphics devices do their jobs more efficiently saving energy. Today, the browser is used a lot to watch movies. Unfortunately, the Firefox browser does not support VA-API hardware decoding, which is the interface to be used for Intel graphics device, which are included in current Intel processors. The issue in the Mozilla bug tracker [1] is open for over two years. Currently, this missing feature is a major show stopper for people using Ubuntu GNU/Linux on their laptops, as compared to Microsoft Windows one battery charge(?) lasts noticeably less time. [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1210727 To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1688592/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714989] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64()
The patch got accepted upstream for gnome-shell 3.30. And hopefully for some 3.28.3 version. For Fedora users who end up here because it's the top entry on a common search engine, the corresponding bug entry is here: https://bugzilla.redhat.com/show_bug.cgi?id=1489554 ** Bug watch added: Red Hat Bugzilla #1489554 https://bugzilla.redhat.com/show_bug.cgi?id=1489554 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1714989 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64() Status in GNOME Shell: Fix Released Status in gjs package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Fix Released Status in gjs source package in Bionic: Won't Fix Status in gnome-shell source package in Bionic: Fix Committed Bug description: Saw some reports with the same title but they're all for previous versions. error reports: https://errors.ubuntu.com/problem/1c95cc2653ab00054b5d1764e41d974328a5f49d https://errors.ubuntu.com/problem/811164cadd3e9e891f9e2d439bda59925f91a62c [ Impact ] gnome-shell crashes [ Test case ] 1. No clear test case for this issue. Some extensions (clipboard indicator) seems to trigger it, but there's no an an easy and reproducible test-case for this so far. So install "clipboard indicator" indicator and expect this to run properly. [ Regression Potential ] Nothing really should be regressing. Labels could not be updated correctly on disposed labels (not destroyed yet). ProblemType: CrashDistroRelease: Ubuntu 17.10 Package: gnome-shell 3.25.91-0ubuntu2 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 4 16:52:13 2017 DisplayManager: gdm3 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2017-04-21 (135 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fd97c8e7e5d : movzbl 0x16(%rax),%edx PC (0x7fd97c8e7e5d) ok source "0x16(%rax)" (0xeb1e) not located in a known VMA region (needed readable region)! destination "%edx" ok SegvReason: reading NULL VMA Signal: 11SourcePackage: gnome-shell StacktraceTop: g_type_check_instance_cast () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 st_label_set_text () from /usr/lib/gnome-shell/libst-1.0.so ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ?? () from /usr/lib/libgjs.so.0 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1714989/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
