Hi,

Torbrowser crashes when trying to save something.
For instance using 'Save page as...' immediately crashes torbrowser.
Same when downloading a file to be saved.

[ log ]
$ ~/.local/share/torbrowser/tbb/x86_64/tor-browser/Browser/start-tor-browser --log /tmp/log.txt

Log report from doing 'Save page as...' => crash {
**
Gtk:ERROR:../../../gtk/gtkiconhelper.c:495:ensure_surface_for_gicon: assertion failed (error == NULL): Failed to load /usr/share/icons/Tango/16x16/status/image-missing.png: No image loaders are configured. You might need to install a package like glycin-loaders.
Used config: Config {
    image_loader: {},
    image_editor: {},
} (gdk-pixbuf-error-quark, 0)
Bail out! Gtk:ERROR:../../../gtk/gtkiconhelper.c:495:ensure_surface_for_gicon: assertion failed (error == NULL): Failed to load /usr/share/icons/Tango/16x16/status/image-missing.png: No image loaders are configured. You might need to install a package like glycin-loaders. Used config: Config {     image_loader: {},     image_editor: {}, } (gdk-pixbuf-error-quark, 0)
Redirecting call to abort() to mozalloc_abort

Exiting due to channel error.
Exiting due to channel error.
Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: CompositorBridgeChild receives IPC close with reason=AbnormalShutdown (t=16.3152) [GFX1-]: CompositorBridgeChild receives IPC close with reason=AbnormalShutdown
Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: CompositorBridgeChild receives IPC close with reason=AbnormalShutdown (t=17.393) [GFX1-]: CompositorBridgeChild receives IPC close with reason=AbnormalShutdown
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
}


[ Workaround ]
"Serialnumber"'s workaround worked for me:
mv ~/.local/share/torbrowser/ ~
ln -s ~/torbrowser/ ~/.local/share
From https://forum.manjaro.org/t/tor-browser-file-picker-crashes/184216


[ FYI ]
Did not help:
- rm -rf ~/.local/share/torbrowser
- reinstalling torbrowser
- reinstalling glycin-loaders
ii  glycin-loaders 2.0.8-1      amd64
ii  torbrowser-launcher 0.3.9-1      amd64

Kind regards,
Franck Richter

It's look like problem with AppArmor rules. Just add this two lines to file
/etc/apparmor.d/torbrowser.Browser.firefox (at line 6 or below):

# allow read glycin-loader for image loading I guess
/usr/share/glycin-loaders/** r,
# allow run bwrap. May be there are more suitable options than ux, I
don't know
/usr/bin/bwrap ux,

The suggested apparmor changes from Message 10 on bug #1130690 are
insecure and incomplete (and too wide).

However, as Firefox (and Tor Browser) both use glycin under the hood
*and* use `bwrap` for sandboxing, there is a set of policies in
`abstractions/glycin` on AppArmor that include proper glycin:bwrap
settings AND all other related glycin requirements.

A patched version of the package is in the process of being uploaded,
0.3.9-2, which includes modifications to the torbrowser.Browser.firefox
AppArmor policies that includes the glycin abstractions, and should
solve this issue.