Looks like in my case the problem is connected to "failed to connect to
lvmetad falling back to device scanning" problem. No idea where to
search for a solution so far.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Having the same problem after update 16.10 -> 17.04. Have to do "sudo
chmod -R a+w /dev/shm/" after each reboot.
cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust
closing as invalid due to lack of information.
** Changed in: mountall (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/566788
Title:
/dev/shm isn't
/dev/shm is a tmpfs, and tmpfs in the kernel has a default mode of
01777. I don't see how this could be happening without a) an /etc/fstab
entry overriding the /lib/init/fstab entry, or b) a rogue local script
running at start-up that's changing the mode.
I certainly don't see any bugs in
I do not have a line in /etc/fstab for /dev/shm and update-initramfs
does not fix the problem for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/566788
Title:
/dev/shm isn't writable, causing
My workaround is to create a /etc/init/my-on-mounted.conf file, with the
following content:
start on mounted
script
chmod 777 /dev/shm
end script
** Changed in: mountall (Ubuntu)
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Regenerating the initrd fixed it for me:
update-initramfs -k all -u
hth hand
--
/dev/shm isn't writable, causing problems with glibc 2.2+ apps such as chromium
https://bugs.launchpad.net/bugs/566788
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This line in /etc/fstab is the problem. Once I remove it, chromium
starts up and works just fine.
none /dev/shm tmpfs nosuid,nodev 0 0
--
/dev/shm isn't writable, causing problems with glibc 2.2+ apps such as chromium
https://bugs.launchpad.net/bugs/566788
You received this bug notification
I am getting this in maverick
and...@790fx:~$ chromium-browser
[16682:16691:7522193672:FATAL:base/shared_memory_posix.cc(193)] Creating shared
memory in /dev/shm/.org.chromium.pk526V failed. This is frequently caused by
incorrect permissions on /dev/shm. Try 'sudo chmod 777 /dev/shm' to fix.:
** Also affects: archlinux
Importance: Undecided
Status: New
--
/dev/shm isn't writable, causing problems with glibc 2.2+ apps such as chromium
https://bugs.launchpad.net/bugs/566788
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Is there anything we can help to fix this bug? What are the temporary
fix options?
--
/dev/shm isn't writable, causing problems with glibc 2.2+ apps such as chromium
https://bugs.launchpad.net/bugs/566788
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I'm looking at a whole at a few bugs that I -didn't- have in a late beta
and I DO have in the release versions. I thought I was going mad, but it
does seem this appears between beta and current.
I reinstalled fresh from the beta copy. This bug (/dev/shm permissions
problem) does NOT appear in a
Same problem, after upgrading to Lucid and when installing a new version
of chromium. Downgrading chromium didn't solve the problem.
$ chromium-browser
[5094:5094:10359541725:FATAL:base/shared_memory_posix.cc(193)] Creating shared
memory in /dev/shm/org.chromium.DyN5DD failed. This is
I ran into the same problem after upgrading to 10.04.
Here's /proc/self/mountinfo:
15 19 0:0 / /sys rw,nosuid,nodev,noexec,relatime - sysfs none rw
16 19 0:3 / /proc rw,nosuid,nodev,noexec,relatime - proc none rw
17 19 0:5 / /dev rw,relatime - devtmpfs none
Same problem here, appeared after a bunch of updates against the beta.
Didn't have the problem on first install.
It's been consistent for a little while now, didn't report it straight
away until I was sure it was EVERY time I rebooted. It's a real problem
so by all means mark this incomplete
Can you remove your fix and reboot, then run cat
/proc/self/mountinfo and attach that?
Thanks
** Changed in: mountall (Ubuntu)
Importance: Undecided = Medium
** Changed in: mountall (Ubuntu)
Status: New = Incomplete
--
/dev/shm isn't writable, causing problems with glibc 2.2+ apps
I reverted fstab to the preferred content and rebooted. /dev/shm has
the correct permissions still/again. Do you still want mountinfo?
I'll definitely keep an eye out for this again, and post the mountinfo
if /dev/shm ever again has the wrong permissions.
--
/dev/shm isn't writable, causing
Argh, that's a shame!
If it does happen, please do reopen the bug and post that information!
Thanks for the report
** Changed in: mountall (Ubuntu)
Status: Incomplete = Invalid
--
/dev/shm isn't writable, causing problems with glibc 2.2+ apps such as chromium
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/44828022/Dependencies.txt
--
/dev/shm isn't writable, causing problems with glibc 2.2+ apps such as chromium
https://bugs.launchpad.net/bugs/566788
You received this bug notification because you are a member of Ubuntu
Bugs,
19 matches
Mail list logo
