After installing the 20 November 2015 updates to my -Current installs, Google Chrome no longer runs.

It seems that something, perhaps eudev, has changed the permissions for /dev/shm to 1755. I'm not sure what the permissions were before, but I know Chrome worked.

When I look at the permission on Slackware 14.1, I see: 1777 for /dev/shm.

Does anyone have a better solution than to chmod /dev/shm on each reboot?

On mine, I had to create /dev/shm and then apply the 1777 attributes. Once I did that, chrome started just fine. The strange thing about it is that /dev/shm is in my fstab

i guess your using slackpkg. you need to edit your /etc/slackpkg/blacklist and put hash # in front of aaa_elflibs
you must do a slackpkg install new. you must do a slackpkg new-config.
or you can do it the slackware way.
as pat posted here. http://www.linuxquestions.org/questi...8/#post5455324

/dev/shm is for "shared memory". It's strange that you should have to create it, the kernel supposedly create and automount it if I remember well...

Ah, it seems the aaa_elflibs update of 25 November, 2015 fixed my issue. Yay! Or not . . . it is fixed now, but it worked *before* the elflibs update.
I almost wish I knew what changed, but I'll accept working without understanding the fix.

It seems that a rebuild of eudev is what I needed. (From the changelog for Slackware64):
a/eudev-3.1.5-x86_64-6.txz: Rebuilt.
rc.udev: create all static modes in /dev before starting udevd.
Thanks to Robby Workman.
Support loading additional devices from /etc/udev/devices.

I'm thankful for a Slackware64-current machine that runs Google Chrome without having to change permissions on /dev/shm!