You are not logged in.

#1 2021-10-03 05:57:23

daigennki
Member
Registered: 2020-10-23
Posts: 17

[SOLVED] Firefox needs .Xauthority whitelisted for WebGL to work, why?

Hi. I've been trying to figure out why WebGL sites weren't working in Firefox on Arch Linux even though a friend said it works just fine (I think using a different Linux distribution). I narrowed the problem down to .Xauthority in my user home folder ("/home/username/.Xauthority") having to be whitelisted in "security.sandbox.content.read_path_whitelist" in the about:config page, and now WebGL sites work as expected. It's nice that I solved the problem, but I can't help but wonder why I had to do it on my machine in particular. Could this be a result of improper configuration on my machine?

Last edited by daigennki (2021-10-04 14:32:00)

Offline

#2 2021-10-03 07:38:02

seth
Member
Registered: 2012-09-03
Posts: 25,141

Re: [SOLVED] Firefox needs .Xauthority whitelisted for WebGL to work, why?

Kinda related (I guess): https://wiki.archlinux.org/title/Firefo … able_WebGL
Does it yell informative errors w/o the sandbox whitelist?

Online

#3 2021-10-03 07:46:01

daigennki
Member
Registered: 2020-10-23
Posts: 17

Re: [SOLVED] Firefox needs .Xauthority whitelisted for WebGL to work, why?

Not sure, but I just found something even weirder. I deleted .Xauthority, removed the whitelist for it (back to default settings), then rebooted, and now everything works as it should. There is no longer a ".Xauthority" file after rebooting, and instead there is an empty (0 bytes) ".Xauthority-n" file in the same place.

Offline

#4 2021-10-03 07:56:46

seth
Member
Registered: 2012-09-03
Posts: 25,141

Re: [SOLVED] Firefox needs .Xauthority whitelisted for WebGL to work, why?

.Xauthority-n is a transitional file used by xauth to update .Xauthority (ie. it writes there and then copies to the actual file)
Is this a wayland session?
If not, I could imagine that you're running into an issue because the GPU is not ready when X11 starts, https://wiki.archlinux.org/title/Kernel … _KMS_start

Online

#5 2021-10-03 08:01:18

daigennki
Member
Registered: 2020-10-23
Posts: 17

Re: [SOLVED] Firefox needs .Xauthority whitelisted for WebGL to work, why?

No, this is an X11 session using XFCE, and I already have early KMS configured for amdgpu.
Also, while it still works after a reboot and there is no .Xauthority (though there still is an empty .Xauthority-n), if I specifically log out and log in without rebooting, the .Xauthority file is back again and I'm having WebGL issues in Firefox again until I delete .Xauthority and then reboot.

Last edited by daigennki (2021-10-03 08:03:33)

Offline

#6 2021-10-03 08:15:01

seth
Member
Registered: 2012-09-03
Posts: 25,141

Re: [SOLVED] Firefox needs .Xauthority whitelisted for WebGL to work, why?

xauth -v list

Edit: you may obfuscate the hashes (but mark equal ones)

seth wrote:

Does it yell informative errors w/o the sandbox whitelist?

Last edited by seth (2021-10-03 08:15:51)

Online

#7 2021-10-03 08:43:42

daigennki
Member
Registered: 2020-10-23
Posts: 17

Re: [SOLVED] Firefox needs .Xauthority whitelisted for WebGL to work, why?

Okay, here's "xauth -v list" with .Xauthority in the home folder (Firefox WebGL doesn't work):

Using authority file /home/ggreywolfe/.Xauthority
GUNGNIR-160126L:0  MIT-MAGIC-COOKIE-1  <hash 1>
GUNGNIR-160126L:0  MIT-MAGIC-COOKIE-1  <hash 1>
GUNGNIR-160126L:0  MIT-MAGIC-COOKIE-1  <hash 1>
GUNGNIR-160126L:0  MIT-MAGIC-COOKIE-1  <hash 1>
GUNGNIR-160126L/unix:0  MIT-MAGIC-COOKIE-1  <hash 1>

and without .Xauthority in the home folder (Firefox WebGL does work):

Using authority file /tmp/.XauthTf2TOe
GUNGNIR-160126L:0  MIT-MAGIC-COOKIE-1  <hash 2>
GUNGNIR-160126L:0  MIT-MAGIC-COOKIE-1  <hash 2>
GUNGNIR-160126L:0  MIT-MAGIC-COOKIE-1  <hash 2>
GUNGNIR-160126L:0  MIT-MAGIC-COOKIE-1  <hash 2>
GUNGNIR-160126L/unix:0  MIT-MAGIC-COOKIE-1  <hash 2>

As for errors, while I didn't see anything in "journalctl -b -r" at the moment that Firefox was started, either with or without .Xauthority in the home folder, I saw this when logging in after logging out without a reboot, after deleting .Xauthority:

10月 03 17:29:20 GUNGNIR-160126L at-spi2-registr[3882]: AT-SPI: Cannot open default display
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[3882]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Successfully activated service 'org.a11y.atspi.Registry'
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[3882]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:20 GUNGNIR-160126L at-spi2-registr[3882]: Could not open X display
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Activating service name='org.a11y.atspi.Registry' requested by ':1.188' (uid=1000 pid=3689 comm="/usr/lib/xfce4/panel/wrapper-2.0 /usr/lib/xfce4/pa")
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[3870]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:20 GUNGNIR-160126L at-spi2-registr[3870]: AT-SPI: Cannot open default display
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[3870]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Successfully activated service 'org.a11y.atspi.Registry'
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[3870]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:20 GUNGNIR-160126L at-spi2-registr[3870]: Could not open X display
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Activating service name='org.a11y.atspi.Registry' requested by ':1.164' (uid=1000 pid=3617 comm="xfdesktop --display :0.0 --sm-client-id 2a11d2ab7-")
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[3850]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:20 GUNGNIR-160126L at-spi2-registr[3850]: AT-SPI: Cannot open default display
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[3850]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Successfully activated service 'org.a11y.atspi.Registry'
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[3850]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:20 GUNGNIR-160126L at-spi2-registr[3850]: Could not open X display
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Activating service name='org.a11y.atspi.Registry' requested by ':1.188' (uid=1000 pid=3689 comm="/usr/lib/xfce4/panel/wrapper-2.0 /usr/lib/xfce4/pa")
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[3840]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:20 GUNGNIR-160126L at-spi2-registr[3840]: AT-SPI: Cannot open default display
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[3840]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Successfully activated service 'org.a11y.atspi.Registry'
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[3840]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:20 GUNGNIR-160126L at-spi2-registr[3840]: Could not open X display
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Activating service name='org.a11y.atspi.Registry' requested by ':1.168' (uid=1000 pid=3630 comm="xfce4-terminal --geometry=160x32 --display :0.0 --")
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[3821]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:20 GUNGNIR-160126L at-spi2-registr[3821]: AT-SPI: Cannot open default display
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[3821]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Successfully activated service 'org.a11y.atspi.Registry'
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[3821]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:20 GUNGNIR-160126L at-spi2-registr[3821]: Could not open X display
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Activating service name='org.a11y.atspi.Registry' requested by ':1.78' (uid=1000 pid=3344 comm="xfce4-session ")
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[3807]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:20 GUNGNIR-160126L NetworkManager[361]: <info>  [1633249760.1054] agent-manager: agent[0f62d66524780148,:1.55/org.freedesktop.nm-applet/1000]: agent registered
10月 03 17:29:20 GUNGNIR-160126L at-spi2-registr[3807]: AT-SPI: Cannot open default display
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[3807]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Successfully activated service 'org.a11y.atspi.Registry'
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[3807]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:20 GUNGNIR-160126L at-spi2-registr[3807]: Could not open X display
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Activating service name='org.a11y.atspi.Registry' requested by ':1.171' (uid=1000 pid=3636 comm="/usr/lib/xfce4/panel/wrapper-2.0 /usr/lib/xfce4/pa")
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[3801]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:20 GUNGNIR-160126L at-spi2-registr[3801]: AT-SPI: Cannot open default display
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[3801]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Successfully activated service 'org.a11y.atspi.Registry'
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[3801]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:20 GUNGNIR-160126L at-spi2-registr[3801]: Could not open X display
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Activating service name='org.a11y.atspi.Registry' requested by ':1.187' (uid=1000 pid=3669 comm="/usr/lib/xfce4/notifyd/xfce4-notifyd ")
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[3786]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:20 GUNGNIR-160126L at-spi2-registr[3786]: AT-SPI: Cannot open default display
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[3786]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Successfully activated service 'org.a11y.atspi.Registry'
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[3786]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:20 GUNGNIR-160126L at-spi2-registr[3786]: Could not open X display
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Activating service name='org.a11y.atspi.Registry' requested by ':1.169' (uid=1000 pid=3631 comm="xfce4-power-manager --restart --sm-client-id 2fdcf")
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[3774]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:20 GUNGNIR-160126L at-spi2-registr[3774]: AT-SPI: Cannot open default display
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[3774]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Successfully activated service 'org.a11y.atspi.Registry'
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[3774]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:20 GUNGNIR-160126L at-spi2-registr[3774]: Could not open X display
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Activating service name='org.a11y.atspi.Registry' requested by ':1.160' (uid=1000 pid=3606 comm="Thunar --sm-client-id 218a8ba42-cb5b-4dcf-a6c5-289")
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[3760]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:20 GUNGNIR-160126L at-spi2-registr[3760]: AT-SPI: Cannot open default display
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[3760]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Successfully activated service 'org.a11y.atspi.Registry'
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[3760]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:20 GUNGNIR-160126L at-spi2-registr[3760]: Could not open X display
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Activating service name='org.a11y.atspi.Registry' requested by ':1.177' (uid=1000 pid=3646 comm="/usr/lib/polkit-gnome/polkit-gnome-authentication-")
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[3745]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:20 GUNGNIR-160126L at-spi2-registr[3745]: AT-SPI: Cannot open default display
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[3745]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Successfully activated service 'org.a11y.atspi.Registry'
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[3745]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:20 GUNGNIR-160126L at-spi2-registr[3745]: Could not open X display
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Activating service name='org.a11y.atspi.Registry' requested by ':1.78' (uid=1000 pid=3344 comm="xfce4-session ")
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[3732]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:20 GUNGNIR-160126L at-spi2-registr[3732]: AT-SPI: Cannot open default display
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[3732]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Successfully activated service 'org.a11y.atspi.Registry'
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[3732]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:20 GUNGNIR-160126L at-spi2-registr[3732]: Could not open X display
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Activating service name='org.a11y.atspi.Registry' requested by ':1.156' (uid=1000 pid=3600 comm="xfce4-panel --display :0.0 --sm-client-id 2abc6ed3")
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[3726]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:20 GUNGNIR-160126L at-spi2-registr[3726]: AT-SPI: Cannot open default display
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[3726]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Successfully activated service 'org.a11y.atspi.Registry'
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[3726]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:20 GUNGNIR-160126L at-spi2-registr[3726]: Could not open X display
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Activating service name='org.a11y.atspi.Registry' requested by ':1.169' (uid=1000 pid=3631 comm="xfce4-power-manager --restart --sm-client-id 2fdcf")
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[3717]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:20 GUNGNIR-160126L at-spi2-registr[3717]: AT-SPI: Cannot open default display
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[3717]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Successfully activated service 'org.a11y.atspi.Registry'
10月 03 17:29:20 GUNGNIR-160126L at-spi-bus-launcher[3717]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:20 GUNGNIR-160126L at-spi2-registr[3717]: Could not open X display
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Activating service name='org.a11y.atspi.Registry' requested by ':1.87' (uid=1000 pid=3394 comm="xfsettingsd --display :0.0 --sm-client-id 28595332")
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3704]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:19 GUNGNIR-160126L at-spi2-registr[3704]: AT-SPI: Cannot open default display
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3704]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Successfully activated service 'org.a11y.atspi.Registry'
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3704]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:19 GUNGNIR-160126L at-spi2-registr[3704]: Could not open X display
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Activating service name='org.a11y.atspi.Registry' requested by ':1.87' (uid=1000 pid=3394 comm="xfsettingsd --display :0.0 --sm-client-id 28595332")
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3698]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:19 GUNGNIR-160126L at-spi2-registr[3698]: AT-SPI: Cannot open default display
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3698]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Successfully activated service 'org.a11y.atspi.Registry'
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3698]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:19 GUNGNIR-160126L polkitd[488]: Registered Authentication Agent for unix-session:3 (system bus name :1.54 [/usr/lib/polkit-gnome/polkit-gnome-authentication-agent-1], object path /org/gnome/PolicyKit1/AuthenticationAgent, locale ja_JP.UTF-8)
10月 03 17:29:19 GUNGNIR-160126L at-spi2-registr[3698]: Could not open X display
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Activating service name='org.a11y.atspi.Registry' requested by ':1.164' (uid=1000 pid=3617 comm="xfdesktop --display :0.0 --sm-client-id 2a11d2ab7-")
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3693]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:19 GUNGNIR-160126L at-spi2-registr[3693]: AT-SPI: Cannot open default display
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3693]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Successfully activated service 'org.a11y.atspi.Registry'
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3693]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:19 GUNGNIR-160126L at-spi2-registr[3693]: Could not open X display
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Activating service name='org.a11y.atspi.Registry' requested by ':1.82' (uid=1000 pid=3384 comm="xfwm4 --display :0.0 --sm-client-id 2499a69b9-b31c")
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3691]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:19 GUNGNIR-160126L at-spi2-registr[3691]: AT-SPI: Cannot open default display
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3691]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Successfully activated service 'org.a11y.atspi.Registry'
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3691]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:19 GUNGNIR-160126L at-spi2-registr[3691]: Could not open X display
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Activating service name='org.a11y.atspi.Registry' requested by ':1.160' (uid=1000 pid=3606 comm="Thunar --sm-client-id 218a8ba42-cb5b-4dcf-a6c5-289")
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3681]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:19 GUNGNIR-160126L at-spi2-registr[3681]: AT-SPI: Cannot open default display
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3681]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Successfully activated service 'org.a11y.atspi.Registry'
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3681]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:19 GUNGNIR-160126L at-spi2-registr[3681]: Could not open X display
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Activating service name='org.a11y.atspi.Registry' requested by ':1.169' (uid=1000 pid=3631 comm="xfce4-power-manager --restart --sm-client-id 2fdcf")
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3668]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:19 GUNGNIR-160126L at-spi2-registr[3668]: AT-SPI: Cannot open default display
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3668]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
10月 03 17:29:19 GUNGNIR-160126L pulseaudio[626]: Failed to load module "module-x11-publish" (argument: "display=:0.0 xauthority="): initialization failed.
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Successfully activated service 'org.a11y.atspi.Registry'
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3668]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:19 GUNGNIR-160126L pulseaudio[626]: XOpenDisplay() failed
10月 03 17:29:19 GUNGNIR-160126L pulseaudio[626]: No protocol specified
10月 03 17:29:19 GUNGNIR-160126L at-spi2-registr[3668]: Could not open X display
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Activating service name='org.a11y.atspi.Registry' requested by ':1.82' (uid=1000 pid=3384 comm="xfwm4 --display :0.0 --sm-client-id 2499a69b9-b31c")
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3660]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:19 GUNGNIR-160126L at-spi2-registr[3660]: AT-SPI: Cannot open default display
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3660]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Successfully activated service 'org.a11y.atspi.Registry'
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3660]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:19 GUNGNIR-160126L at-spi2-registr[3660]: Could not open X display
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Activating service name='org.a11y.atspi.Registry' requested by ':1.169' (uid=1000 pid=3631 comm="xfce4-power-manager --restart --sm-client-id 2fdcf")
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3629]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:19 GUNGNIR-160126L at-spi2-registr[3629]: AT-SPI: Cannot open default display
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3629]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Successfully activated service 'org.a11y.atspi.Registry'
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3629]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:19 GUNGNIR-160126L at-spi2-registr[3629]: Could not open X display
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Activating service name='org.a11y.atspi.Registry' requested by ':1.164' (uid=1000 pid=3617 comm="xfdesktop --display :0.0 --sm-client-id 2a11d2ab7-")
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3627]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:19 GUNGNIR-160126L at-spi2-registr[3627]: AT-SPI: Cannot open default display
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3627]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Successfully activated service 'org.a11y.atspi.Registry'
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3627]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:19 GUNGNIR-160126L at-spi2-registr[3627]: Could not open X display
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Activating service name='org.a11y.atspi.Registry' requested by ':1.164' (uid=1000 pid=3617 comm="xfdesktop --display :0.0 --sm-client-id 2a11d2ab7-")
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3625]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:19 GUNGNIR-160126L at-spi2-registr[3625]: AT-SPI: Cannot open default display
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3625]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Successfully activated service 'org.a11y.atspi.Registry'
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3625]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:19 GUNGNIR-160126L at-spi2-registr[3625]: Could not open X display
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Activating service name='org.a11y.atspi.Registry' requested by ':1.164' (uid=1000 pid=3617 comm="xfdesktop --display :0.0 --sm-client-id 2a11d2ab7-")
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3621]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:19 GUNGNIR-160126L at-spi2-registr[3621]: AT-SPI: Cannot open default display
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3621]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Successfully activated service 'org.a11y.atspi.Registry'
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3621]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:19 GUNGNIR-160126L at-spi2-registr[3621]: Could not open X display
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Activating service name='org.a11y.atspi.Registry' requested by ':1.160' (uid=1000 pid=3606 comm="Thunar --sm-client-id 218a8ba42-cb5b-4dcf-a6c5-289")
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3619]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:19 GUNGNIR-160126L at-spi2-registr[3619]: AT-SPI: Cannot open default display
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3619]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Successfully activated service 'org.a11y.atspi.Registry'
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3619]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:19 GUNGNIR-160126L at-spi2-registr[3619]: Could not open X display
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Activating service name='org.a11y.atspi.Registry' requested by ':1.160' (uid=1000 pid=3606 comm="Thunar --sm-client-id 218a8ba42-cb5b-4dcf-a6c5-289")
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3616]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:19 GUNGNIR-160126L at-spi2-registr[3616]: AT-SPI: Cannot open default display
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3616]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Successfully activated service 'org.a11y.atspi.Registry'
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3616]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:19 GUNGNIR-160126L at-spi2-registr[3616]: Could not open X display
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Activating service name='org.a11y.atspi.Registry' requested by ':1.160' (uid=1000 pid=3606 comm="Thunar --sm-client-id 218a8ba42-cb5b-4dcf-a6c5-289")
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3610]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:19 GUNGNIR-160126L at-spi2-registr[3610]: AT-SPI: Cannot open default display
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3610]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Successfully activated service 'org.a11y.atspi.Registry'
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3610]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:19 GUNGNIR-160126L at-spi2-registr[3610]: Could not open X display
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Activating service name='org.a11y.atspi.Registry' requested by ':1.156' (uid=1000 pid=3600 comm="xfce4-panel --display :0.0 --sm-client-id 2abc6ed3")
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3608]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:19 GUNGNIR-160126L at-spi2-registr[3608]: AT-SPI: Cannot open default display
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3608]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Successfully activated service 'org.a11y.atspi.Registry'
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3608]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:19 GUNGNIR-160126L at-spi2-registr[3608]: Could not open X display
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Activating service name='org.a11y.atspi.Registry' requested by ':1.156' (uid=1000 pid=3600 comm="xfce4-panel --display :0.0 --sm-client-id 2abc6ed3")
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3605]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:19 GUNGNIR-160126L at-spi2-registr[3605]: AT-SPI: Cannot open default display
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3605]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Successfully activated service 'org.a11y.atspi.Registry'
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3605]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:19 GUNGNIR-160126L at-spi2-registr[3605]: Could not open X display
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Activating service name='org.a11y.atspi.Registry' requested by ':1.156' (uid=1000 pid=3600 comm="xfce4-panel --display :0.0 --sm-client-id 2abc6ed3")
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3473]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:19 GUNGNIR-160126L at-spi2-registr[3473]: AT-SPI: Cannot open default display
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3473]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Successfully activated service 'org.a11y.atspi.Registry'
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3473]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:19 GUNGNIR-160126L at-spi2-registr[3473]: Could not open X display
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Activating service name='org.a11y.atspi.Registry' requested by ':1.78' (uid=1000 pid=3344 comm="xfce4-session ")
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3467]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:19 GUNGNIR-160126L at-spi2-registr[3467]: AT-SPI: Cannot open default display
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3467]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Successfully activated service 'org.a11y.atspi.Registry'
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3467]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:19 GUNGNIR-160126L at-spi2-registr[3467]: Could not open X display
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Activating service name='org.a11y.atspi.Registry' requested by ':1.87' (uid=1000 pid=3394 comm="xfsettingsd --display :0.0 --sm-client-id 28595332")
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3461]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:19 GUNGNIR-160126L at-spi2-registr[3461]: AT-SPI: Cannot open default display
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3461]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Successfully activated service 'org.a11y.atspi.Registry'
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3461]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:19 GUNGNIR-160126L at-spi2-registr[3461]: Could not open X display
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Activating service name='org.a11y.atspi.Registry' requested by ':1.78' (uid=1000 pid=3344 comm="xfce4-session ")
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3458]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:19 GUNGNIR-160126L at-spi2-registr[3458]: AT-SPI: Cannot open default display
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3458]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Successfully activated service 'org.a11y.atspi.Registry'
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3458]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:19 GUNGNIR-160126L at-spi2-registr[3458]: Could not open X display
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Activating service name='org.a11y.atspi.Registry' requested by ':1.87' (uid=1000 pid=3394 comm="xfsettingsd --display :0.0 --sm-client-id 28595332")
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3454]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:19 GUNGNIR-160126L at-spi2-registr[3454]: AT-SPI: Cannot open default display
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3454]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Successfully activated service 'org.a11y.atspi.Registry'
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3454]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:19 GUNGNIR-160126L at-spi2-registr[3454]: Could not open X display
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Activating service name='org.a11y.atspi.Registry' requested by ':1.82' (uid=1000 pid=3384 comm="xfwm4 --display :0.0 --sm-client-id 2499a69b9-b31c")
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3446]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:19 GUNGNIR-160126L at-spi2-registr[3446]: AT-SPI: Cannot open default display
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3446]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Successfully activated service 'org.a11y.atspi.Registry'
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3446]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:19 GUNGNIR-160126L at-spi2-registr[3446]: Could not open X display
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Activating service name='org.a11y.atspi.Registry' requested by ':1.78' (uid=1000 pid=3344 comm="xfce4-session ")
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3440]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:19 GUNGNIR-160126L at-spi2-registr[3440]: AT-SPI: Cannot open default display
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3440]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Successfully activated service 'org.a11y.atspi.Registry'
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3440]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:19 GUNGNIR-160126L at-spi2-registr[3440]: Could not open X display
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Activating service name='org.a11y.atspi.Registry' requested by ':1.82' (uid=1000 pid=3384 comm="xfwm4 --display :0.0 --sm-client-id 2499a69b9-b31c")
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3437]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:19 GUNGNIR-160126L at-spi2-registr[3437]: AT-SPI: Cannot open default display
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3437]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Successfully activated service 'org.a11y.atspi.Registry'
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3437]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:19 GUNGNIR-160126L at-spi2-registr[3437]: Could not open X display
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Activating service name='org.a11y.atspi.Registry' requested by ':1.87' (uid=1000 pid=3394 comm="xfsettingsd --display :0.0 --sm-client-id 28595332")
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3411]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:19 GUNGNIR-160126L at-spi2-registr[3411]: AT-SPI: Cannot open default display
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3411]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Successfully activated service 'org.a11y.atspi.Registry'
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3411]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:19 GUNGNIR-160126L at-spi2-registr[3411]: Could not open X display
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Activating service name='org.a11y.atspi.Registry' requested by ':1.78' (uid=1000 pid=3344 comm="xfce4-session ")
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3403]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:19 GUNGNIR-160126L at-spi2-registr[3403]: AT-SPI: Cannot open default display
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3403]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Successfully activated service 'org.a11y.atspi.Registry'
10月 03 17:29:19 GUNGNIR-160126L at-spi-bus-launcher[3403]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:19 GUNGNIR-160126L at-spi2-registr[3403]: Could not open X display
10月 03 17:29:18 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Activating service name='org.a11y.atspi.Registry' requested by ':1.82' (uid=1000 pid=3384 comm="xfwm4 --display :0.0 --sm-client-id 2499a69b9-b31c")
10月 03 17:29:18 GUNGNIR-160126L at-spi-bus-launcher[3396]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:18 GUNGNIR-160126L at-spi2-registr[3396]: AT-SPI: Cannot open default display
10月 03 17:29:18 GUNGNIR-160126L at-spi-bus-launcher[3396]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
10月 03 17:29:18 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Successfully activated service 'org.a11y.atspi.Registry'
10月 03 17:29:18 GUNGNIR-160126L at-spi-bus-launcher[3396]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:18 GUNGNIR-160126L at-spi2-registr[3396]: Could not open X display
10月 03 17:29:18 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Activating service name='org.a11y.atspi.Registry' requested by ':1.82' (uid=1000 pid=3384 comm="xfwm4 --display :0.0 --sm-client-id 2499a69b9-b31c")
10月 03 17:29:18 GUNGNIR-160126L at-spi-bus-launcher[3393]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:18 GUNGNIR-160126L at-spi2-registr[3393]: AT-SPI: Cannot open default display
10月 03 17:29:18 GUNGNIR-160126L at-spi-bus-launcher[3393]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
10月 03 17:29:18 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Successfully activated service 'org.a11y.atspi.Registry'
10月 03 17:29:18 GUNGNIR-160126L at-spi-bus-launcher[3393]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:18 GUNGNIR-160126L at-spi2-registr[3393]: Could not open X display
10月 03 17:29:18 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Activating service name='org.a11y.atspi.Registry' requested by ':1.82' (uid=1000 pid=3384 comm="xfwm4 --display :0.0 --sm-client-id 2499a69b9-b31c")
10月 03 17:29:18 GUNGNIR-160126L at-spi-bus-launcher[3386]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:18 GUNGNIR-160126L at-spi2-registr[3386]: AT-SPI: Cannot open default display
10月 03 17:29:18 GUNGNIR-160126L at-spi-bus-launcher[3386]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
10月 03 17:29:18 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Successfully activated service 'org.a11y.atspi.Registry'
10月 03 17:29:18 GUNGNIR-160126L at-spi-bus-launcher[3386]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:18 GUNGNIR-160126L at-spi2-registr[3386]: Could not open X display
10月 03 17:29:18 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Activating service name='org.a11y.atspi.Registry' requested by ':1.78' (uid=1000 pid=3344 comm="xfce4-session ")
10月 03 17:29:18 GUNGNIR-160126L at-spi-bus-launcher[3383]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:18 GUNGNIR-160126L at-spi2-registr[3383]: AT-SPI: Cannot open default display
10月 03 17:29:18 GUNGNIR-160126L at-spi-bus-launcher[3383]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
10月 03 17:29:18 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Successfully activated service 'org.a11y.atspi.Registry'
10月 03 17:29:18 GUNGNIR-160126L at-spi-bus-launcher[3383]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:18 GUNGNIR-160126L at-spi2-registr[3383]: Could not open X display
10月 03 17:29:18 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Activating service name='org.a11y.atspi.Registry' requested by ':1.78' (uid=1000 pid=3344 comm="xfce4-session ")
10月 03 17:29:18 GUNGNIR-160126L at-spi-bus-launcher[3370]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:18 GUNGNIR-160126L gpg-agent[3380]: listening on: std=6 extra=5 browser=4 ssh=3
10月 03 17:29:18 GUNGNIR-160126L gpg-agent[3380]: using fd 6 for std socket (/run/user/1000/gnupg/S.gpg-agent)
10月 03 17:29:18 GUNGNIR-160126L gpg-agent[3380]: using fd 5 for extra socket (/run/user/1000/gnupg/S.gpg-agent.extra)
10月 03 17:29:18 GUNGNIR-160126L gpg-agent[3380]: using fd 4 for browser socket (/run/user/1000/gnupg/S.gpg-agent.browser)
10月 03 17:29:18 GUNGNIR-160126L gpg-agent[3380]: using fd 3 for ssh socket (/run/user/1000/gnupg/S.gpg-agent.ssh)
10月 03 17:29:18 GUNGNIR-160126L gpg-agent[3380]: gpg-agent (GnuPG) 2.2.29 starting in supervised mode.
10月 03 17:29:18 GUNGNIR-160126L systemd[529]: Started GnuPG cryptographic agent and passphrase cache.
10月 03 17:29:18 GUNGNIR-160126L gpg-agent[3377]: listening on: std=6 extra=5 browser=4 ssh=3
10月 03 17:29:18 GUNGNIR-160126L gpg-agent[3377]: using fd 6 for std socket (/run/user/1000/gnupg/S.gpg-agent)
10月 03 17:29:18 GUNGNIR-160126L gpg-agent[3377]: using fd 5 for extra socket (/run/user/1000/gnupg/S.gpg-agent.extra)
10月 03 17:29:18 GUNGNIR-160126L gpg-agent[3377]: using fd 4 for browser socket (/run/user/1000/gnupg/S.gpg-agent.browser)
10月 03 17:29:18 GUNGNIR-160126L gpg-agent[3377]: using fd 3 for ssh socket (/run/user/1000/gnupg/S.gpg-agent.ssh)
10月 03 17:29:18 GUNGNIR-160126L gpg-agent[3377]: gpg-agent (GnuPG) 2.2.29 starting in supervised mode.
10月 03 17:29:18 GUNGNIR-160126L systemd[529]: Started GnuPG cryptographic agent and passphrase cache.
10月 03 17:29:18 GUNGNIR-160126L at-spi2-registr[3370]: AT-SPI: Cannot open default display
10月 03 17:29:18 GUNGNIR-160126L at-spi-bus-launcher[3370]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
10月 03 17:29:18 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Successfully activated service 'org.a11y.atspi.Registry'
10月 03 17:29:18 GUNGNIR-160126L at-spi-bus-launcher[3370]: Invalid MIT-MAGIC-COOKIE-1 key
10月 03 17:29:18 GUNGNIR-160126L at-spi2-registr[3370]: Could not open X display
10月 03 17:29:18 GUNGNIR-160126L at-spi-bus-launcher[588]: dbus-daemon[588]: Activating service name='org.a11y.atspi.Registry' requested by ':1.78' (uid=1000 pid=3344 comm="xfce4-session ")

The above is only shown in "journalctl -b -r" during the first login after a logout without a reboot after deleting .Xauthority. "Could not open X display" and "Invalid MIT-MAGIC-COOKIE-1 key" might especially be of interest here.

Last edited by daigennki (2021-10-03 09:13:47)

Offline

#8 2021-10-03 14:02:59

seth
Member
Registered: 2012-09-03
Posts: 25,141

Re: [SOLVED] Firefox needs .Xauthority whitelisted for WebGL to work, why?

How do you login and what are the outputs of

hostnamectl
loginctl session-status

(I currently suspect that you're not setting a hostname, that gets changed by possibly NM at runtime and you're loosing the connection to the server)

Online

#9 2021-10-03 14:27:35

daigennki
Member
Registered: 2020-10-23
Posts: 17

Re: [SOLVED] Firefox needs .Xauthority whitelisted for WebGL to work, why?

I use XDM, which starts XFCE using .xsession, as instructed in the wiki page.
Here's the output of "hostnamectl":

 Static hostname: GUNGNIR-160126L
       Icon name: computer-desktop
         Chassis: desktop
      Machine ID: <redacted>
         Boot ID: <redacted>
Operating System: Arch Linux
          Kernel: Linux 5.14.8-arch1-1
    Architecture: x86-64
 Hardware Vendor: System manufacturer
  Hardware Model: System Product Name

and "loginctl session-status":

1 - ggreywolfe (1000)
	   Since: Sun 2021-10-03 17:32:35 JST; 5h 49min ago
	  Leader: 486 (xdm)
	    Seat: seat0; vc2
	 Display: :0
	 Service: xdm; type x11; class user
	   State: active
	    Unit: session-1.scope
		  ├─  486 "-:0                                                             "
		  ├─  535 /bin/sh -ls -c /home/ggreywolfe/.xsession
		  ├─  542 xfce4-session
		  ├─  601 /usr/bin/ssh-agent -s
		  ├─  610 xfwm4 --display :0.0 --sm-client-id 2499a69b9-b31c-4b59-8dfb-315de7868a5c
		  ├─  620 xfsettingsd --display :0.0 --sm-client-id 2ca4422ea-7c2c-4829-b358-b62f315bf07b
		  ├─  805 xfce4-panel --display :0.0 --sm-client-id 2abc6ed3b-352c-4b39-978a-c6cb7c8f511c
		  ├─  815 Thunar --sm-client-id 218a8ba42-cb5b-4dcf-a6c5-2899ee6c3443 --daemon
		  ├─  820 xfdesktop --display :0.0 --sm-client-id 2a11d2ab7-0ffb-42c7-98ff-71427798d8f1
		  ├─  824 xfce4-power-manager --restart --sm-client-id 2fdcffd40-26a7-4aa8-b3fa-5bb8224b962c
		  ├─  830 /usr/lib/xfce4/panel/wrapper-2.0 /usr/lib/xfce4/panel/plugins/libsystray.so 6 10485767 systray ステータストレイプラグイン ステータス通知アイテム(アプリケーションインジケーター)とレガシーシステムトレイアイテムを提供します
		  ├─  831 /usr/lib/xfce4/panel/wrapper-2.0 /usr/lib/xfce4/panel/plugins/libpulseaudio-plugin.so 8 10485768 pulseaudio "PulseAudio プラグイン" "PulseAudio サウンドシステムの音量を調整します"
		  ├─  833 bash /home/ggreywolfe/.local/share/Steam/steam.sh
		  ├─  834 "/opt/discord/Discord --start-minimized"
		  ├─  837 /usr/lib/polkit-gnome/polkit-gnome-authentication-agent-1
		  ├─  841 xscreensaver -no-splash
		  ├─  854 xscreensaver-systemd
		  ├─  863 nm-applet
		  ├─  875 /usr/lib/xfce4/notifyd/xfce4-notifyd
		  ├─  881 /usr/lib/xfce4/panel/wrapper-2.0 /usr/lib/xfce4/panel/plugins/libnotification-plugin.so 10 10485769 notification-plugin デスクトップ通知プラグイン Xfceパネルのための通知プラグイン
		  ├─  957 "/opt/discord/Discord --type=zygote --no-zygote-sandbox"
		  ├─  964 "/opt/discord/Discord --type=zygote"
		  ├─ 1008 "/opt/discord/Discord --type=zygote"
		  ├─ 1087 "/opt/discord/Discord --type=gpu-process --field-trial-handle=12791045075849075106,17303719905615602359,131072 --disable-features=CookiesWithoutSameSiteMustBeSecure,SameSiteByDefaultCookies,SpareRendererForSitePerProcess,WinRetrieveSuggestionsOnlyOnDemand --enable-crash-reporter=52a81dca-f304-427c-ad4c-2f427df8f96f,no_channel --global-crash-keys=52a81dca-f304-427c-ad4c-2f427df8f96f,no_channel,_companyName=Discord Inc.,_productName=Discord,_version=0.0.16 --gpu-preferences=UAAAAAAAAAAgAAAQAAAAAAAAAAAAAAAAAABgAAAAAAAwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAgAAAAAAAAACAAAAAAAAAA= --shared-files"
		  ├─ 1096 "/opt/discord/Discord --type=utility --utility-sub-type=network.mojom.NetworkService --field-trial-handle=12791045075849075106,17303719905615602359,131072 --disable-features=CookiesWithoutSameSiteMustBeSecure,SameSiteByDefaultCookies,SpareRendererForSitePerProcess,WinRetrieveSuggestionsOnlyOnDemand --lang=ja --service-sandbox-type=none --enable-crash-reporter=52a81dca-f304-427c-ad4c-2f427df8f96f,no_channel --global-crash-keys=52a81dca-f304-427c-ad4c-2f427df8f96f,no_channel,_companyName=Discord Inc.,_productName=Discord,_version=0.0.16 --shared-files=v8_context_snapshot_data:100"
		  ├─ 1189 /home/ggreywolfe/.local/share/Steam/ubuntu12_32/steam
		  ├─ 1208 fcitx
		  ├─ 1213 /usr/bin/dbus-daemon --syslog --fork --print-pid 4 --print-address 6 --config-file /usr/share/fcitx/dbus/daemon.conf
		  ├─ 1217 /usr/bin/fcitx-dbus-watcher unix:abstract=/tmp/dbus-xuxJOJtGLx,guid=4513f007072c7074d1516d6761596aa6 1213
		  ├─ 1220 /usr/lib/mozc/mozc_server
		  ├─ 1286 "/opt/discord/Discord --type=utility --utility-sub-type=audio.mojom.AudioService --field-trial-handle=12791045075849075106,17303719905615602359,131072 --disable-features=CookiesWithoutSameSiteMustBeSecure,SameSiteByDefaultCookies,SpareRendererForSitePerProcess,WinRetrieveSuggestionsOnlyOnDemand --lang=ja --service-sandbox-type=none --enable-crash-reporter=52a81dca-f304-427c-ad4c-2f427df8f96f,no_channel --global-crash-keys=52a81dca-f304-427c-ad4c-2f427df8f96f,no_channel,_companyName=Discord Inc.,_productName=Discord,_version=0.0.16 --shared-files=v8_context_snapshot_data:100"
		  ├─ 2817 /home/ggreywolfe/.local/share/Steam/ubuntu12_32/steam
		  ├─ 2818 ./steamwebhelper -lang=ja_JP -cachedir=/home/ggreywolfe/.local/share/Steam/config/htmlcache -steampid=1189 -buildid=1631912732 -steamid=0 -cachedir=/home/ggreywolfe/.local/share/Steam/config/htmlcache -steamuniverse=Public -realm=Global -clientui=/home/ggreywolfe/.local/share/Steam/clientui --enable-blink-features=ResizeObserver,Worklet,AudioWorklet --enable-media-stream --enable-smooth-scrolling --password-store=basic --log-file=/home/ggreywolfe/.local/share/Steam/logs/cef_log.txt --disable-quick-menu
		  ├─ 2877 "/home/ggreywolfe/.local/share/Steam/ubuntu12_64/steamwebhelper --type=zygote --no-sandbox --log-file=/home/ggreywolfe/.local/share/Steam/logs/cef_log.txt --product-version=Valve Steam Client --lang=en_US.UTF-8"
		  ├─ 2887 ./steamwebhelper --type=gpu-process --field-trial-handle=16697939023582109814,15779274798968400921,131072 --disable-features=MimeHandlerViewInCrossProcessFrame --no-sandbox --log-file=/home/ggreywolfe/.local/share/Steam/logs/cef_log.txt "--product-version=Valve Steam Client" --lang=en_US.UTF-8 --gpu-preferences=KAAAAAAAAAAgAAAgAAAAAAAAYAAAAAAAEAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAA --log-file=/home/ggreywolfe/.local/share/Steam/logs/cef_log.txt --service-request-channel-token=13927304781312119581
		  ├─ 2913 "/home/ggreywolfe/.local/share/Steam/ubuntu12_64/steamwebhelper --type=utility --field-trial-handle=16697939023582109814,15779274798968400921,131072 --disable-features=MimeHandlerViewInCrossProcessFrame --lang=ja --service-sandbox-type=network --no-sandbox --log-file=/home/ggreywolfe/.local/share/Steam/logs/cef_log.txt --product-version=Valve Steam Client --lang=en_US.UTF-8 --log-file=/home/ggreywolfe/.local/share/Steam/logs/cef_log.txt --service-request-channel-token=515573569965054466 --shared-files=v8_context_snapshot_data:100,v8_natives_data:101"
		  ├─ 3001 "/home/ggreywolfe/.local/share/Steam/ubuntu12_64/steamwebhelper --type=renderer --no-sandbox --log-file=/home/ggreywolfe/.local/share/Steam/logs/cef_log.txt --field-trial-handle=16697939023582109814,15779274798968400921,131072 --disable-features=MimeHandlerViewInCrossProcessFrame --enable-blink-features=ResizeObserver,Worklet,AudioWorklet --lang=ja --log-file=/home/ggreywolfe/.local/share/Steam/logs/cef_log.txt --product-version=Valve Steam Client --num-raster-threads=4 --enable-main-frame-before-activation --service-request-channel-token=15004320509952261343 --renderer-client-id=5 --shared-files=v8_context_snapshot_data:100,v8_natives_data:101"
		  ├─ 3097 "/home/ggreywolfe/.local/share/Steam/ubuntu12_64/steamwebhelper --type=renderer --no-sandbox --log-file=/home/ggreywolfe/.local/share/Steam/logs/cef_log.txt --field-trial-handle=16697939023582109814,15779274798968400921,131072 --disable-features=MimeHandlerViewInCrossProcessFrame --enable-blink-features=ResizeObserver,Worklet,AudioWorklet --lang=ja --log-file=/home/ggreywolfe/.local/share/Steam/logs/cef_log.txt --product-version=Valve Steam Client --num-raster-threads=4 --enable-main-frame-before-activation --service-request-channel-token=8606296099194471995 --renderer-client-id=7 --shared-files=v8_context_snapshot_data:100,v8_natives_data:101"
		  ├─ 3108 "/home/ggreywolfe/.local/share/Steam/ubuntu12_64/steamwebhelper --type=renderer --no-sandbox --log-file=/home/ggreywolfe/.local/share/Steam/logs/cef_log.txt --field-trial-handle=16697939023582109814,15779274798968400921,131072 --disable-features=MimeHandlerViewInCrossProcessFrame --enable-blink-features=ResizeObserver,Worklet,AudioWorklet --lang=ja --log-file=/home/ggreywolfe/.local/share/Steam/logs/cef_log.txt --product-version=Valve Steam Client --num-raster-threads=4 --enable-main-frame-before-activation --service-request-channel-token=4889976528813647209 --renderer-client-id=9 --shared-files=v8_context_snapshot_data:100,v8_natives_data:101"
		  ├─ 4013 "/opt/1Password/1password --silent"
		  ├─ 4016 "/opt/1Password/1password --type=zygote --no-zygote-sandbox"
		  ├─ 4017 "/opt/1Password/1password --type=zygote"
		  ├─ 4019 "/opt/1Password/1password --type=zygote"
		  ├─ 4051 "/opt/1Password/1password --type=gpu-process --field-trial-handle=16124013403893572902,1216049521518017459,131072 --disable-features=CookiesWithoutSameSiteMustBeSecure,SameSiteByDefaultCookies,SpareRendererForSitePerProcess --gpu-preferences=UAAAAAAAAAAgAAAQAAAAAAAAAAAAAAAAAABgAAAAAAAwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAgAAAAAAAAACAAAAAAAAAA= --shared-files"
		  ├─ 4073 "/opt/1Password/1password --type=utility --utility-sub-type=network.mojom.NetworkService --field-trial-handle=16124013403893572902,1216049521518017459,131072 --disable-features=CookiesWithoutSameSiteMustBeSecure,SameSiteByDefaultCookies,SpareRendererForSitePerProcess --lang=ja --service-sandbox-type=none --standard-schemes=resource,file-icon --enable-sandbox --secure-schemes --bypasscsp-schemes=resource,file-icon --cors-schemes --fetch-schemes=resource,file-icon --service-worker-schemes --streaming-schemes --shared-files=v8_context_snapshot_data:100"
		  ├─ 4116 /opt/1Password/1Password-KeyringHelper
		  ├─ 6293 /usr/lib/firefox/firefox "https://bbs.archlinux.org/viewtopic.php?id=270117"
		  ├─ 6502 /usr/lib/firefox/firefox -contentproc -childID 2 -isForBrowser -prefsLen 96 -prefMapSize 244216 -jsInit 285716 -parentBuildID 20210923165649 -appdir /usr/lib/firefox/browser 6293 true tab
		  ├─ 6552 /usr/lib/firefox/firefox -contentproc -childID 3 -isForBrowser -prefsLen 5619 -prefMapSize 244216 -jsInit 285716 -parentBuildID 20210923165649 -appdir /usr/lib/firefox/browser 6293 true tab
		  ├─ 6592 /opt/1Password/1Password-BrowserSupport /home/ggreywolfe/.mozilla/native-messaging-hosts/com.1password.1password.json {d634138d-c276-4fc8-924b-40a0ea21d284}
		  ├─ 6634 /opt/1Password/1Password-KeyringHelper
		  ├─ 6734 "/opt/discord/Discord --type=renderer --autoplay-policy=no-user-gesture-required --field-trial-handle=12791045075849075106,17303719905615602359,131072 --disable-features=CookiesWithoutSameSiteMustBeSecure,SameSiteByDefaultCookies,SpareRendererForSitePerProcess,WinRetrieveSuggestionsOnlyOnDemand --lang=ja --enable-crash-reporter=52a81dca-f304-427c-ad4c-2f427df8f96f,no_channel --global-crash-keys=52a81dca-f304-427c-ad4c-2f427df8f96f,no_channel,_companyName=Discord Inc.,_productName=Discord,_version=0.0.16 --app-path=/opt/discord/resources/app.asar --no-sandbox --no-zygote --num-raster-threads=4 --enable-main-frame-before-activation --renderer-client-id=12 --no-v8-untrusted-code-mitigations --shared-files=v8_context_snapshot_data:100 --enable-node-leakage-in-renderers"
		  ├─ 8290 /usr/lib/firefox/firefox -contentproc -childID 11 -isForBrowser -prefsLen 5732 -prefMapSize 244216 -jsInit 285716 -parentBuildID 20210923165649 -appdir /usr/lib/firefox/browser 6293 true tab
		  ├─ 8527 /usr/lib/firefox/firefox -contentproc -parentBuildID 20210923165649 -prefsLen 6182 -prefMapSize 244216 -appdir /usr/lib/firefox/browser 6293 true rdd
		  ├─13086 /usr/lib/firefox/firefox -contentproc -childID 33 -isForBrowser -prefsLen 6481 -prefMapSize 244216 -jsInit 285716 -parentBuildID 20210923165649 -appdir /usr/lib/firefox/browser 6293 true tab
		  ├─13219 /usr/lib/firefox/firefox -contentproc -childID 37 -isForBrowser -prefsLen 6481 -prefMapSize 244216 -jsInit 285716 -parentBuildID 20210923165649 -appdir /usr/lib/firefox/browser 6293 true tab
		  ├─14887 /usr/lib/firefox/firefox -contentproc -childID 45 -isForBrowser -prefsLen 6481 -prefMapSize 244216 -jsInit 285716 -parentBuildID 20210923165649 -appdir /usr/lib/firefox/browser 6293 true tab
		  ├─14922 /usr/lib/firefox/firefox -contentproc -childID 46 -isForBrowser -prefsLen 6481 -prefMapSize 244216 -jsInit 285716 -parentBuildID 20210923165649 -appdir /usr/lib/firefox/browser 6293 true tab
		  ├─15079 "/usr/share/vscodium-bin/codium --no-sandbox --unity-launch /home/ggreywolfe/hostnamectl_output.txt"
		  ├─15081 "/usr/share/vscodium-bin/codium --type=zygote --no-zygote-sandbox --no-sandbox"
		  ├─15082 "/usr/share/vscodium-bin/codium --type=zygote --no-sandbox"
		  ├─15110 "/usr/share/vscodium-bin/codium --type=gpu-process --field-trial-handle=10412945569329277911,15656210836487549122,131072 --disable-features=CookiesWithoutSameSiteMustBeSecure,SameSiteByDefaultCookies,SpareRendererForSitePerProcess --disable-color-correct-rendering --no-sandbox --gpu-preferences=UAAAAAAAAAAgAAAQAAAAAAAAAAAAAAAAAABgAAAAAAAwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAgAAAAAAAAACAAAAAAAAAA= --shared-files"
		  ├─15127 "/usr/share/vscodium-bin/codium --type=utility --utility-sub-type=network.mojom.NetworkService --field-trial-handle=10412945569329277911,15656210836487549122,131072 --disable-features=CookiesWithoutSameSiteMustBeSecure,SameSiteByDefaultCookies,SpareRendererForSitePerProcess --lang=ja --service-sandbox-type=none --no-sandbox --standard-schemes=vscode-webview,vscode-file --secure-schemes=vscode-webview,vscode-file --bypasscsp-schemes --cors-schemes=vscode-webview,vscode-file --fetch-schemes=vscode-webview,vscode-file --service-worker-schemes=vscode-webview --streaming-schemes --shared-files=v8_context_snapshot_data:100"
		  ├─15158 "/usr/share/vscodium-bin/codium --type=renderer --disable-color-correct-rendering --no-sandbox --field-trial-handle=10412945569329277911,15656210836487549122,131072 --disable-features=CookiesWithoutSameSiteMustBeSecure,SameSiteByDefaultCookies,SpareRendererForSitePerProcess --lang=ja --standard-schemes=vscode-webview,vscode-file --secure-schemes=vscode-webview,vscode-file --bypasscsp-schemes --cors-schemes=vscode-webview,vscode-file --fetch-schemes=vscode-webview,vscode-file --service-worker-schemes=vscode-webview --streaming-schemes --app-path=/usr/share/vscodium-bin/resources/app --no-sandbox --no-zygote --num-raster-threads=4 --enable-main-frame-before-activation --renderer-client-id=5 --no-v8-untrusted-code-mitigations --shared-files=v8_context_snapshot_data:100 --vscode-window-config=vscode:09312ade-9625-4ca8-88ad-b881fe8705c1"
		  ├─15181 /usr/share/vscodium-bin/codium --inspect-port=0 /usr/share/vscodium-bin/resources/app/out/bootstrap-fork --type=extensionHost --skipWorkspaceStorageLock
		  ├─15189 "/usr/share/vscodium-bin/codium --type=renderer --disable-color-correct-rendering --no-sandbox --field-trial-handle=10412945569329277911,15656210836487549122,131072 --disable-features=CookiesWithoutSameSiteMustBeSecure,SameSiteByDefaultCookies,SpareRendererForSitePerProcess --lang=ja --standard-schemes=vscode-webview,vscode-file --secure-schemes=vscode-webview,vscode-file --bypasscsp-schemes --cors-schemes=vscode-webview,vscode-file --fetch-schemes=vscode-webview,vscode-file --service-worker-schemes=vscode-webview --streaming-schemes --app-path=/usr/share/vscodium-bin/resources/app --no-sandbox --no-zygote --disable-blink-features=Auxclick --num-raster-threads=4 --enable-main-frame-before-activation --renderer-client-id=7 --no-v8-untrusted-code-mitigations --shared-files=v8_context_snapshot_data:100 --vscode-window-config=vscode:e836ad7a-206f-46b2-8d9b-110b2f1ab442"
		  ├─15215 /usr/share/vscodium-bin/codium /usr/share/vscodium-bin/resources/app/out/bootstrap-fork --type=ptyHost
		  ├─15533 /usr/lib/firefox/firefox -contentproc -childID 48 -isForBrowser -prefsLen 8981 -prefMapSize 244216 -jsInit 285716 -parentBuildID 20210923165649 -appdir /usr/lib/firefox/browser 6293 true tab
		  ├─15623 /usr/lib/firefox/firefox -contentproc -childID 49 -isForBrowser -prefsLen 8981 -prefMapSize 244216 -jsInit 285716 -parentBuildID 20210923165649 -appdir /usr/lib/firefox/browser 6293 true tab
		  ├─15792 /usr/bin/xfce4-terminal
		  ├─15837 bash
		  └─15851 loginctl session-status

10月 03 17:32:35 GUNGNIR-160126L systemd[1]: Started Session 1 of User ggreywolfe.
10月 03 17:52:00 GUNGNIR-160126L sudo[4340]: pam_systemd_home(sudo:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
10月 03 17:52:00 GUNGNIR-160126L sudo[4340]: ggreywolfe : TTY=pts/0 ; PWD=/home/ggreywolfe ; USER=root ; COMMAND=/usr/bin/pacman -R at-spi2-core
10月 03 17:52:00 GUNGNIR-160126L sudo[4340]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
10月 03 17:52:00 GUNGNIR-160126L sudo[4340]: pam_unix(sudo:session): session closed for user root
10月 03 17:52:05 GUNGNIR-160126L sudo[4342]: pam_systemd_home(sudo:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
10月 03 17:52:05 GUNGNIR-160126L sudo[4342]: ggreywolfe : TTY=pts/0 ; PWD=/home/ggreywolfe ; USER=root ; COMMAND=/usr/bin/pacman -R at-spi2-core at-spi2-atk
10月 03 17:52:05 GUNGNIR-160126L sudo[4342]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
10月 03 17:52:05 GUNGNIR-160126L sudo[4342]: pam_unix(sudo:session): session closed for user root
10月 03 21:47:43 GUNGNIR-160126L xscreensaver-auth[12886]: pam_warn(xscreensaver:account): function=[pam_sm_acct_mgmt] flags=0 service=[xscreensaver] terminal=[:0.0] user=[ggreywolfe] ruser=[<unknown>] rhost=[<unknown>]

(hopefully there isn't any sensitive information in there...)

Offline

#10 2021-10-03 14:40:42

seth
Member
Registered: 2012-09-03
Posts: 25,141

Re: [SOLVED] Firefox needs .Xauthority whitelisted for WebGL to work, why?

Can you replicate this w/ xinit/startx?
https://wiki.archlinux.org/title/Xinit#xinitrc

Online

#11 2021-10-03 15:05:41

daigennki
Member
Registered: 2020-10-23
Posts: 17

Re: [SOLVED] Firefox needs .Xauthority whitelisted for WebGL to work, why?

If you mean replace the part with the example programs in .xinitrc with "startxfce4", instead of putting it in .xsession, no, because it immediately sends me back to XDM. However, if I open a tty immediately after that with Ctrl+Alt+F3, then list the files in the home folder, it looks like .Xauthority has been created when I got sent back to XDM.

Offline

#12 2021-10-03 15:11:31

seth
Member
Registered: 2012-09-03
Posts: 25,141

Re: [SOLVED] Firefox needs .Xauthority whitelisted for WebGL to work, why?

No, I mean using startx or xinit to launch the session - no xdm.
Something™ is off about the authority file, we need to identify the cause and it seems/might be xdm handing off the authority to your user.

Online

#13 2021-10-03 15:24:59

daigennki
Member
Registered: 2020-10-23
Posts: 17

Re: [SOLVED] Firefox needs .Xauthority whitelisted for WebGL to work, why?

Ah, okay. I ran "startx" from the tty with "startxfce4" in .xinitrc, and now although .Xauthority is being created upon login, I can still use WebGL in Firefox with default sandbox security settings. It also works even after logging out of XFCE, then running "startx" again from the same tty.

Last edited by daigennki (2021-10-03 15:27:08)

Offline

#14 2021-10-03 18:39:22

seth
Member
Registered: 2012-09-03
Posts: 25,141

Re: [SOLVED] Firefox needs .Xauthority whitelisted for WebGL to work, why?

One final element would be to rule out a race condition, ie. autostart X11 via startx (similar to xdm being autostarted) or alternatively don't enable xdm, but login to the console, start the xdm service and login then.

https://wiki.archlinux.org/title/Getty# … al_console
https://wiki.archlinux.org/title/Xinit# … X_at_login

If autostarting startx doesn't cause and/or delaying XDM still does cause the issue, it's all about XDM handing off the xauthority.

Edit, found this ancient bug:
https://bugs.debian.org/cgi-bin/bugrepo … bug=595748
Cehck whether /tmp/.Xauth* exists in any case and whether $XAUTHORITY is exported and whether exporting it to firefox gets you ahead.

Last edited by seth (2021-10-03 18:41:47)

Online

#15 2021-10-04 01:18:07

daigennki
Member
Registered: 2020-10-23
Posts: 17

Re: [SOLVED] Firefox needs .Xauthority whitelisted for WebGL to work, why?

Okay, I did as instructed and made it so that startx is run on login for tty1, without XDM. It's always creating .Xauthority, and WebGL does work correctly in Firefox. /tmp/.Xauth* never exists when it's run without XDM, and XAUTHORITY is exported to all applications.
However, when XFCE is started from XDM as before, /tmp/.Xauth* exists for the first login, and doesn't after the second (without a reboot) when .Xauthority does exist. In either case, as long as XFCE is started from XDM, XAUTHORITY is not exported to any application. Exporting XAUTHORITY to Firefox in the case where WebGL would not work (using XDM and .Xauthority does exist), does allow WebGL to work. Interesting...

Offline

#16 2021-10-04 07:03:35

seth
Member
Registered: 2012-09-03
Posts: 25,141

Re: [SOLVED] Firefox needs .Xauthority whitelisted for WebGL to work, why?

https://man.archlinux.org/man/extra/xorg-xdm/xdm.8.en

DisplayManager.DISPLAY.userAuthDir
When xdm is unable to write to the usual user authorization file ($HOME/.Xauthority), it creates a unique file name in this directory and points the environment variable XAUTHORITY at the created file. It uses /tmp by default.

Anything about your $HOME that might inhibit xdm from writing there?

Online

#17 2021-10-04 07:18:43

daigennki
Member
Registered: 2020-10-23
Posts: 17

Re: [SOLVED] Firefox needs .Xauthority whitelisted for WebGL to work, why?

Not sure. Is there some sort of permission I should be checking?

Offline

#18 2021-10-04 07:28:48

seth
Member
Registered: 2012-09-03
Posts: 25,141

Re: [SOLVED] Firefox needs .Xauthority whitelisted for WebGL to work, why?

Does xdm run as root?
Is $HOME (eg. encrypted and) only mounted on login?

XDM ultimately seems to be able to edit ~/.Xauthority so it's likely a transitional issue.
What if you simply delay "sleep 5; startxfce4" in .xsession?

Online

#19 2021-10-04 07:43:47

daigennki
Member
Registered: 2020-10-23
Posts: 17

Re: [SOLVED] Firefox needs .Xauthority whitelisted for WebGL to work, why?

XDM is run from xdm-archlinux.service. $HOME is on the same partition as root, so it's already mounted from the start. Adding "sleep 5" to the beginning of .xsession did not help.

Also, I noticed this when running "systemctl status xdm-archlinux.service". Does this have anything to do with the issue?

10月 04 16:40:27 GUNGNIR-160126L xdm[9444]: pam_systemd_home(xdm:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
10月 04 16:40:27 GUNGNIR-160126L xdm[9444]: pam_unix(xdm:session): session opened for user ggreywolfe(uid=1000) by (uid=0)
10月 04 16:40:27 GUNGNIR-160126L xdm[9444]: pam_env(xdm:session): deprecated reading of user environment enabled

EDIT: Enabling systemd-homed.service didn't change anything except for pam_systemd_home saying "Not a user managed by systemd-homed: No home for user ggreywolfe known" instead, so guess not.

Last edited by daigennki (2021-10-04 07:55:43)

Offline

#20 2021-10-04 08:25:08

seth
Member
Registered: 2012-09-03
Posts: 25,141

Re: [SOLVED] Firefox needs .Xauthority whitelisted for WebGL to work, why?

Does this have anything to do with the issue? … guess not

Exporting XAUTHORITY to Firefox in the case where WebGL would not work (using XDM and .Xauthority does exist), does allow WebGL to work. Interesting...

test -e $HOME/.Xauthority && export XAUTHORITY=$HOME/.Xauthority
startxfce4

?

Online

#21 2021-10-04 10:35:16

daigennki
Member
Registered: 2020-10-23
Posts: 17

Re: [SOLVED] Firefox needs .Xauthority whitelisted for WebGL to work, why?

Okay, yes, putting that in .Xsession works, XAUTHORITY is exported to all applications and WebGL works in Firefox. What's up with that?

Offline

#22 2021-10-04 14:13:21

seth
Member
Registered: 2012-09-03
Posts: 25,141

Re: [SOLVED] Firefox needs .Xauthority whitelisted for WebGL to work, why?

idk why FF conditionally needs to whitelist the xauthority file for the content to read (what sounds wrong) but the original issue is that XDM doesn't properly hand off the X11 authority to the active user.

You can
a) keep the workaround
b) file a bug, https://gitlab.freedesktop.org/xorg/app/xdm (no idea whether this will ever be addressed)
c) stop using xdm and use xinit instead (esp. if this is virtually a single-user system, you can just autologin to a locked session)

Online

#23 2021-10-04 14:31:02

daigennki
Member
Registered: 2020-10-23
Posts: 17

Re: [SOLVED] Firefox needs .Xauthority whitelisted for WebGL to work, why?

Hmm, yeah, seems like xdm isn't being maintained much anymore, so maybe I should just use something like like lightdm. Sorry that you went through all the effort to help me, only for me to simply stop using xdm, but thanks anyways. I'll mark this as solved since the solution is to not use xdm, I guess.

And yes, the XAUTHORITY and Firefox WebGL issues do not occur with lightdm instead of xdm.

Offline

Board footer

Powered by FluxBB