Odd close button with snaps

[ Focal]

Hi,

I do experience quite often this with my snaps windows:

image

(Adwaita, same behaviour using Yaru)

It happens, as far I can guess, when I open a 2nd window of Firefox. And it does affect, after that, every snap window (e.g. snap store).

Is this bug known?

1 Like

this one ?

EDIT: and this one too … seems to be a wayland related issue

Do you get it every time you open another firefox? You are using it as a snap? Is there anything printed in the journal log when you get the issue?

@ogra
First one yes, exactly. I run a Wayland GNOME session.

@seb128
I restart my laptop to reproduce and check logs.

Ok I got directly Firefox snap with weird close button after a restart and FF snap launch.

Logs:

20:49:42 systemd: gnome-launched-firefox_firefox.desktop-3565.scope: Succeeded.
20:49:39 rtkit-daemon: Supervising 5 threads of 3 processes of 1 users.
20:49:39 MainThread: Failed to load module “canberra-gtk-module”
20:49:39 MainThread: Failed to load module “canberra-gtk-module”
20:49:39 MainThread: Failed to load module “canberra-gtk-module”
20:49:38 rtkit-daemon: Supervising 5 threads of 3 processes of 1 users.
20:49:38 MainThread: Failed to load module “canberra-gtk-module”
20:49:38 rtkit-daemon: Supervising 5 threads of 3 processes of 1 users.
20:49:37 MainThread: Failed to load module “canberra-gtk-module”
20:49:37 firefox-bin: Sandbox: /tmp/.X11-unix/X0 is inaccessible (No such file or directory); can’t isolate network namespace in content processes
20:49:37 kernel: audit: type=1326 audit(1605642577.358:100): auid=1000 uid=1000 gid=1000 ses=3 subj=snap.firefox.firefox pid=3565 comm=“firefox-bin” exe="/snap/firefox/457/firefox-bin" sig=0 arch=c000003e syscall=203 compat=0 ip=0x7f99c167bb9f code=0x50000
20:49:37 firefox-bin: SECCOMP auid=1000 uid=1000 gid=1000 ses=3 subj=snap.firefox.firefox pid=3565 comm=“firefox-bin” exe="/snap/firefox/457/firefox-bin" sig=0 arch=c000003e syscall=203 compat=0 ip=0x7f99c167bb9f code=0x50000
20:49:37 kernel: audit: type=1326 audit(1605642577.186:98): auid=1000 uid=1000 gid=1000 ses=3 subj=snap.firefox.firefox pid=3642 comm=“firefox-bin” exe="/snap/firefox/457/firefox-bin" sig=0 arch=c000003e syscall=203 compat=0 ip=0x7f99c167bb9f code=0x50000
20:49:37 firefox-bin: SECCOMP auid=1000 uid=1000 gid=1000 ses=3 subj=snap.firefox.firefox pid=3642 comm=“firefox-bin” exe="/snap/firefox/457/firefox-bin" sig=0 arch=c000003e syscall=203 compat=0 ip=0x7f99c167bb9f code=0x50000
20:49:37 kernel: audit: type=1326 audit(1605642577.158:94): auid=1000 uid=1000 gid=1000 ses=3 subj=snap.firefox.firefox pid=3642 comm=“firefox-bin” exe="/snap/firefox/457/firefox-bin" sig=0 arch=c000003e syscall=203 compat=0 ip=0x7f99c167bb9f code=0x50000
20:49:37 firefox-bin: SECCOMP auid=1000 uid=1000 gid=1000 ses=3 subj=snap.firefox.firefox pid=3642 comm=“firefox-bin” exe="/snap/firefox/457/firefox-bin" sig=0 arch=c000003e syscall=203 compat=0 ip=0x7f99c167bb9f code=0x50000
20:49:37 firefox-bin: SECCOMP auid=1000 uid=1000 gid=1000 ses=3 subj=snap.firefox.firefox pid=3642 comm=“firefox-bin” exe="/snap/firefox/457/firefox-bin" sig=0 arch=c000003e syscall=203 compat=0 ip=0x7f99c167bb9f code=0x50000
20:49:37 firefox-bin: SECCOMP auid=1000 uid=1000 gid=1000 ses=3 subj=snap.firefox.firefox pid=3642 comm=“firefox-bin” exe="/snap/firefox/457/firefox-bin" sig=0 arch=c000003e syscall=203 compat=0 ip=0x7f99c167bb9f code=0x50000
20:49:37 firefox-bin: SECCOMP auid=1000 uid=1000 gid=1000 ses=3 subj=snap.firefox.firefox pid=3642 comm=“firefox-bin” exe="/snap/firefox/457/firefox-bin" sig=0 arch=c000003e syscall=203 compat=0 ip=0x7f99c167bb9f code=0x50000
20:49:37 firefox-bin: SECCOMP auid=1000 uid=1000 gid=1000 ses=3 subj=snap.firefox.firefox pid=3642 comm=“firefox-bin” exe="/snap/firefox/457/firefox-bin" sig=0 arch=c000003e syscall=203 compat=0 ip=0x7f99c167bb9f code=0x50000
20:49:36 systemd: Started Application launched by gnome-shell.

It is known issue - see

https://askubuntu.com/q/1206868/66509

given that this is a snapd bug, discussing it here or on askubuntu will not get the attention of the snapd developers, better take it to the snap forum … (just bump one of the older threads perhaps) or file it at bugs.launchpad.net/snapd

Ok I bump Norbert’s bug.

2 Likes

perhaps add some note that it seems wayland specific too …

done :wink: …

1 Like