AFAICT upstream preferred to fix this in GTK, and we already ship the
GTK fix:
https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/4122
The fix is also in the gnome-3-38-2004 snap.
** Tags removed: rls-jj-incoming
** Tags added: fixed-in-gtk-3.24.31 fixed-in-gtk-4.5.1 fixed-upstream
--
You
** Also affects: gtk+3.0 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: gtk4 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gtk+3.0 (Ubuntu)
Status: New => Fix Released
** Changed in: gtk4 (Ubuntu)
Status: New => Fix Released
--
You
This bug is closed. To help us fully understand the remaining issue,
please open a new bug.
I recall that drag and drop was known to be broken in Firefox on Wayland
recently, which was one of the reasons it was reverted to use X11
instead (Xwayland).
** Tags added: dnd
--
You received this
I currently have the bug with Firefox 103.0b9 and mutter 42.2-0ubuntu1.
It went away for a while then it came back; I was not able to determine
the exact version which determined the (possible) regression. I am
available for tests and any additional information if it can help. Thank
you in advance
** Changed in: firefox
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1964541
Title:
Cannot use Drag and Drop in gnome-shell 42 (Wayland session)
** Changed in: mutter
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1964541
Title:
Cannot use Drag and Drop in gnome-shell 42 (Wayland session)
To
Sounds like Mozilla is doing the right thing, just the timing is
inconvenient for jammy.
It doesn't hurt live sessions because those are Xorg anyway. But after
you install, if Firefox is still using Xwayland for Wayland sessions
then you will see Firefox has:
* Slower frame rates
* More
I think the stable channel will stay on Xwayland for a while, as mozilla
wants to fully test what they ship as default and they're not doing it
in wayland right now.
So, maybe Olivier, could you maybe move `DISABLE_WAYLAND` thingy in the
firefox launcher so that if `MOZ_ENABLE_WAYLAND` is set
The bug is now fixed in mutter, so to get back full performance of
Firefox-on-Wayland you can do this:
sudo snap remove firefox
sudo snap install --beta firefox
Just a temporary workaround until the stable channel returns to native
Wayland.
--
You received this bug notification because you
You can try MOZ_ENABLE_WAYLAND=1 in /etc/environment
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1964541
Title:
Cannot use Drag and Drop in gnome-shell 42 (Wayland session)
To
is there a way for users to re-enable wayland / override the
DISABLE_WAYLAND=1 setting recently set in the snap?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1964541
Title:
> I hope we get back to Firefox with Wayland enabled soon because the
performance difference was noticeable last time I checked.
Plus, rendering of the entire Firefox window got blurry with fractional
scaling. (Just to add one more reason :-) )
--
You received this bug notification because you
This bug was fixed in the package mutter - 42.0-3ubuntu1
---
mutter (42.0-3ubuntu1) jammy; urgency=medium
[ Marco Trevisan (Treviño) ]
* debian/patches: Cherry-pick various upstream commits for 42.1:
+ onscreen/native: Fall back if COPY_MODE_SECONDARY_GPU fails to init
Yes, that's definitely the intention. Mozilla was concerned that they
didn't have automated testing in place to catch bugs and regressions in
a timely manner, hence the temporary revert. See
https://bugzilla.mozilla.org/show_bug.cgi?id=1725245 for more details.
** Bug watch added: Mozilla
I hope we get back to Firefox with Wayland enabled soon because the
performance difference was noticeable last time I checked.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1964541
Corrado is right, but that's a side effect of disabling native wayland
support in the firefox snap, thus having it use xwayland, rather than an
actual fix to the root cause of the problem. But as Daniel is pointing
out, a proper fix is coming.
Note that only the stable channel has been reverted
No I don't think so...
FAIL: 99.0-2 (1188)
FAIL: 100.0b5-1 (1236)
Doesn't matter though, because a proper fix is coming in mutter.
** Changed in: firefox (Ubuntu)
Status: Won't Fix => Invalid
** Changed in: firefox (Ubuntu)
Assignee: Daniel van Vugt (vanvugt) => (unassigned)
--
Problem solved with firefox 99.0.1-1 1232
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1964541
Title:
Cannot use Drag and Drop in gnome-shell 42 (Wayland session)
To manage
So... Per sé the issue only affect apps that are bundled / static linked
with old Gdk version, while there may be many around in snaps and
flatpaks, I think it's better to workaround the issue at mutter level
too, so we'll handle both there and in the platform snap.
--
You received this bug
Upstream issue is https://gitlab.gnome.org/GNOME/mutter/-/issues/2216
Proposed fix:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2368
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2216
https://gitlab.gnome.org/GNOME/mutter/-/issues/2216
** Also affects: mutter via
https://gitlab.gnome.org/GNOME/mutter/-/issues/2216
Importance: Unknown
Status: Unknown
--
You received this bug notification because
21 matches
Mail list logo
