8. Chromium is using GTK 3. And the unsandboxed one is too, so the
difference in behavior does not lay on the different GTK versions. Might
be the signal not being caught in the sandbox... I'm building it with a
patch with debugging statements to verify that.
--->
# For snapped Chromium
% for p in $(ps ax | awk '/chrom/{print $1}'); do lsof -p $p | grep gtk; done
chrome 193331 nteodosio mem REG 7,28 10754
/snap/chromium/2934/gnome-platform/usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2406.32
(stat: No such file or directory)
chrome 193331 nteodosio mem REG 7,28 10043
/snap/chromium/2934/gnome-platform/usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-cedilla.so
(stat: No such file or directory)
chrome 193331 nteodosio mem REG 7,28 16313
/snap/chromium/2934/gnome-platform/usr/share/locale/de/LC_MESSAGES/gtk30-properties.mo
(stat: No such file or directory)
chrome 193331 nteodosio mem REG 7,28 16314
/snap/chromium/2934/gnome-platform/usr/share/locale/de/LC_MESSAGES/gtk30.mo
(stat: No such file or directory)
# For unsandboxed Chromium
% for p in $(ps ax | awk '/chrom/{print $1}'); do lsof -p $p | grep gtk; done
chrome 196401 nteodosio mem REG 252,1 8128032 17310742
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2411.32
chrome 196401 nteodosio mem REG 252,1 14752 17958459
/usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-cedilla.so
<---
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077272
Title:
Gnome's large text accessibility setting not reflect in Chromium in
Wayland
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2077272/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
