Also seeing this intermittently on Debian 10 / latest kernel 4.19 there,
so it appears to be something kernel related that was backported as the
original report here mentions 5.15.
The workaround I've come up with (not fully validated yet, but manually
starting when it fails on boot seems to work)
/org/mate/desktop/sound/input-feedback-sounds actually fixed it for me
(not /org/gnome).
--
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/1970047
Title:
GTK file open dialog
input-feedback-sounds was already set to 'false' for me - explicitly
setting it unfortunately did not seem to make a difference.
--
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/bug
I tried running google-chrome against "stock" gtk-3 built similar to
follows:
sudo apt build-dep libgtk-3-0
apt source libgtk-3-0
cd gtk+3.0-3.24.33
quilt pop -a
rm debian/patches/series
rm debian/*.symbols
DEB_BUILD_OPTIONS=nocheck dpkg-buildpackage -uc -us -d -j16
Also tried building with 'CC=g
Also seeing this on various versions of the official google-chrome .deb
(99, 100, 101) on 22.04/amd64 (MATE Desktop, Xorg + nvidia proprietary
470.103.01, marco window manager + compton compositor).
Browser is unresponsive to any input events after downloading a file or
printing to file (i.e. afte
5 matches
Mail list logo
