emacs window a solid black block after a distribution upgrade

[Little Girl]

Hey there,

Ian Bruntlett wrote:

>Interesting. I tried pressing F11 and it didn't make a difference.
>I also tried running firefox in safe mode - no difference.
>I looked for an acceleration related parameter for Firefox but could
>not find anything.

The F11 suggestion was for emacs. I'm not sure if it would benefit
Firefox in any way.

To configure hardware acceleration in Firefox:

1. Open Firefox.
2. Click on the hamburger menu.
3. Click on "Settings".
4. Scroll down to the "Performance" section.
5. Make sure there is no check in the "Use hardware acceleration when
available" box.

>Here is what happens when I run Firefox....
>
>$ firefox
>Gtk-Message: 18:55:40.187: Not loading module "atk-bridge": The
>functionality is provided by GTK natively. Please try to not load it.
>[GFX1-]: ManageChildProcess(glxtest): poll failed: Success
>
>[GFX1-]: glxtest: ManageChildProcess failed
>[GFX1-]: No GPUs detected via PCI
>
>[ERROR viaduct::backend::ffi] Missing HTTP status
>[ERROR viaduct::backend::ffi] Missing HTTP status

This is beyond my scope of knowledge, but I know we have some Firefox
developers in here.

The atk-bridge should be inside of the Firefox snap. I did a quick
search for libatk-bridge on my Kubuntu 22.04 system and found it in
lots of places, including inside of the Firefox Snap:

$ locate libatk-bridge
/snap/gnome-3-38-2004/140/usr/lib/x86_64-linux-gnu/libatk-bridge-2.0.so
/snap/gnome-3-38-2004/140/usr/lib/x86_64-linux-gnu/libatk-bridge-2.0.so.0
/snap/gnome-3-38-2004/140/usr/lib/x86_64-linux-gnu/libatk-bridge-2.0.so.0.0.0
/snap/gnome-3-38-2004/140/usr/lib/x86_64-linux-gnu/gtk-2.0/modules/libatk-bridge.so
/snap/gnome-3-38-2004/143/usr/lib/x86_64-linux-gnu/libatk-bridge-2.0.so
/snap/gnome-3-38-2004/143/usr/lib/x86_64-linux-gnu/libatk-bridge-2.0.so.0
/snap/gnome-3-38-2004/143/usr/lib/x86_64-linux-gnu/libatk-bridge-2.0.so.0.0.0
/snap/gnome-3-38-2004/143/usr/lib/x86_64-linux-gnu/gtk-2.0/modules/libatk-bridge.so
/usr/lib/x86_64-linux-gnu/libatk-bridge-2.0.so.0
/usr/lib/x86_64-linux-gnu/libatk-bridge-2.0.so.0.0.0
/usr/share/doc/libatk-bridge2.0-0
/usr/share/doc/libatk-bridge2.0-0/changelog.Debian.gz
/usr/share/doc/libatk-bridge2.0-0/copyright
/usr/share/lintian/overrides/libatk-bridge2.0-0
/var/lib/dpkg/info/libatk-bridge2.0-0:amd64.list
/var/lib/dpkg/info/libatk-bridge2.0-0:amd64.md5sums
/var/lib/dpkg/info/libatk-bridge2.0-0:amd64.shlibs
/var/lib/dpkg/info/libatk-bridge2.0-0:amd64.symbols
/var/lib/dpkg/info/libatk-bridge2.0-0:amd64.triggers

This may or may not be of use here, but several comments in this
bug report are referencing Wayland. Are you using Wayland and does the
issue go away when you use Xorg?

https://bugzilla.mozilla.org/show_bug.cgi?id=1765042

>emacs -nw works OK in a console window.

Oh, good. I'm glad to hear it. Did you do something to fix it or did
it sort itself out?

-- 
Little Girl

There is no spoon.