In our case we're not using either of the gnome snaps but just the
distro packages. We trust @seb128 more than those crazy snap people ;-)
I imagine that the fix for Inkscape is to switch to core22, which will
grab the newer GTK3. The next release for Inkscape is roughly aligned
with when 22.04 is
Snaps which use the gnome-38 snapcraft extension wouldn't be affected,
but snaps that use gnome-3-34 may.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1922464
Title:
GNO
I'm not able to spend more time on that one at the moment but still
having it in a my backlog of things to check. Could someone give a
testcase showing the issue?
The original issue has to do with gsettings key changes but confined
snaps aren't using host schemas but a copy of their own or the one
Sorry for the delay, I finally got back to that request but it's not as
simple as backporting the one patch, the codebase changed between .20
and .25 and other changes are needed. Would anyone interest to work on a
proper backport and testing, I personally doesn't really have the free
slots for doi
@seb128: would you take care of uploading that patch, or should somebody
else do it?
I'm not a core-dev, so I would still need a sponsor for the actual
upload (though I have them already), so if you have the tuits it might
just be quicker/easier if you could do it ^^
--
You received this bug not
snaps build is a valid reason indeed, thank you Ted!
** Changed in: gtk+3.0 (Ubuntu Focal)
Status: Incomplete => Triaged
** Changed in: gtk+3.0 (Ubuntu Focal)
Importance: Wishlist => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, w
The problem is that snaps that are built on focal don't work on GNOME
40. So in my case I'm concerned about Inkscape, but most Electron apps
will fall into the same boat.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0
What would be the point, it's to handle changes from GNOME 40 which only
landed in impish? If someone want to skip several GNOME cycles ahead
they probably would have an easy job updating to a new serie than trying
to get the updates in focal
** Changed in: gtk+3.0 (Ubuntu Focal)
Importance: Un
@seb128: but is the patch that you uploaded with 3.24.25-1ubuntu4 (i.e.
this
http://launchpadlibrarian.net/532459482/gtk+3.0_3.24.25-1ubuntu3_3.24.25-1ubuntu4.diff.gz
) really that inappropriate for a SRU on top of the current version in
focal-updates?
--
You received this bug notification becaus
** Also affects: gtk+3.0 (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: gtk+3.0 (Ubuntu Hirsute)
Importance: Undecided
Status: New
** No longer affects: gtk+3.0 (Ubuntu Hirsute)
** Changed in: gtk+3.0 (Ubuntu Focal)
Status: New => Confirmed
--
You
This bug was fixed in the package gtk+3.0 - 3.24.25-1ubuntu4
---
gtk+3.0 (3.24.25-1ubuntu4) hirsute; urgency=medium
* debian/patches/git_wayland_fonts.patch:
- cherry pick a fix for GTK applications hitting errors under wayland
on GNOME40, it isn't in Ubuntu yet but it sho
** Changed in: gtk+3.0 (Ubuntu)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1922464
Title:
GNOME 40: GTK3 apps crash with: Se
Much appreciated, thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1922464
Title:
GNOME 40: GTK3 apps crash with: Settings schema 'org.gnome.settings-
daemon.plugi
it's clearly a bug in the ppa if they ship updates that trigger a bug in
GTK without either shipping that fix or having worked with the distro to
get the issue fixed in the main package.
We are post beta and the archive is frozen for release at this point,
adding changes always carry a risk so we
As you're no doubt aware, using a PPA is at the moment the only way to
use GNOME 40 without compiling it from scratch or switching to another
distro. However the PPA does not ship GTK3, only GTK4 - hence this is a
bug in an Ubuntu package.
Since this bug occurs in Ubuntu's packaged version of GTK3
Thank you for your bug report, Ubuntu doesn't have GNOME 40 though so it
seems rather a bug in the ppa your are using, shouldn't you make the
request there to fix the issue they are creating?
** Changed in: gtk+3.0 (Ubuntu)
Status: New => Incomplete
** Changed in: gtk+3.0 (Ubuntu)
Impor
I just rebuilt the current packaged version of GTK 3 with the patch from
the MR and can confirm it fixes the crash.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1922464
Ti
17 matches
Mail list logo