I upgraded my F11 system to F12 (whatever's in the yum repos right now), and, on startup, /dev/shm has 0755 permissions. This breaks all kinds of things. This looks like a bug at least in dracut, and maybe in /etc/fstab and/or initscripts. fstab has a line: tmpfs /dev/shm tmpfs defaults 0 0 And dracut has (in 99base/init): mount -t tmpfs /dev/shm /dev/shm >/dev/null 2>&1 In any case, this bug should be fixed before release.
Pushing to dracut for the moment.
I'm not seeing this here; it's 1777 for me.
Out of curiousity, are you using RAID?
I'm using LVM over dm-crypt.
dracut-003-1.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/dracut-003-1.fc12
dracut-003-1.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update dracut'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2009-12432
dracut-003-1.fc12 fixes this bug for me. Thanks!
dracut-004-4.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/dracut-004-4.fc12
dracut-004-4.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update dracut'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2010-1088
dracut-004-4.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.
I have recently installed Fedora 12 in a separate partition to dual boot it with Ubuntu. After installation of Chromium I was confronted with the following error: [1801:1809:1835452427:FATAL:base/shared_memory_posix.cc(193)] Creating shared memory in /dev/shm/org.chromium.heCy9T failed. This is frequently caused by incorrect permissions on /dev/shm. Try 'sudo chmod 777 /dev/shm' to fix. In a comment on my blog post (see: http://resa.linux-hardcore.com/?p=512) I was made aware of this bug report. This comment is based on the request as done in comment 10. After reboot these are the rights that are displayed for /dev/shm $ ls -lZd /dev/shm drwxr-xr-x root root unlabeled /dev/shm I have the latest version of dracut installed (see outcome of yum info dracut): Loaded plugins: presto, refresh-packagekit Installed Packages Name : dracut Arch : noarch Version : 004 Release : 4.fc12 Size : 136 k Repo : installed Summary : Initramfs generator using udev URL : http://apps.sourceforge.net/trac/dracut/wiki License : GPLv2+ Description: dracut is a new, event-driven initramfs infrastructure based around : udev Please advise how I could circumvent this issue or let me know if you need more info.
(In reply to comment #11) > I have recently installed Fedora 12 in a separate partition to dual boot it > with Ubuntu. After installation of Chromium I was confronted with the following > error: > > [1801:1809:1835452427:FATAL:base/shared_memory_posix.cc(193)] Creating shared > memory in /dev/shm/org.chromium.heCy9T failed. This is frequently caused by > incorrect permissions on /dev/shm. Try 'sudo chmod 777 /dev/shm' to fix. > > In a comment on my blog post (see: http://resa.linux-hardcore.com/?p=512) I was > made aware of this bug report. This comment is based on the request as done in > comment 10. > > After reboot these are the rights that are displayed for /dev/shm > $ ls -lZd /dev/shm > drwxr-xr-x root root unlabeled /dev/shm did you recreate your initramfs image? # dracut -f
(In reply to comment #12) > > did you recreate your initramfs image? > > # dracut -f I just did, but after rebooting the result remains unchanged: $ ls -lZd /dev/shm drwxr-xr-x root root unlabeled /dev/shm
strange... $ ls -lZd /dev/shm drwxrwxrwt root root ? /dev/shm
Created attachment 410169 [details] Verbose output of dracut -f Please find attached the verbose output of the dracut -f command. Maybe you find something in there that can explain the cause for the fact that I am still having the issue of wrong permission
I have been looking into this issue a bit more. Some additional info: Ubuntu is my main distro with GRUB2 as bootloader. Ubuntu is installed on /dev/sda1 (/ ext3) and /dev/sda2 (/home ext4). Fedora is installed on /dev/sda5 (/ ext4) and /dev/sda6 (/home ext4). /dev/sda3 is swap (for both Ubuntu and Fedora) In dmesg I find the following comments: EXT3-fs: sda5: couldn't mount because of unsupported optional features (240). EXT4-fs (sda5): mounted filesystem with ordered data mode VFS: Mounted root (ext4 filesystem) readonly on device 8:5. Although after startup /etc/mtab indicates the following: $ cat /etc/mtab /dev/sda5 / ext4 rw 0 0 proc /proc proc rw 0 0 sysfs /sys sysfs rw 0 0 devpts /dev/pts devpts rw,gid=5,mode=620 0 0 tmpfs /dev/shm tmpfs rw 0 0 /dev/sda6 /home ext4 rw 0 0 none /proc/sys/fs/binfmt_misc binfmt_misc rw 0 0 gvfs-fuse-daemon /home/rdrijsen/.gvfs fuse.gvfs-fuse-daemon rw,nosuid,nodev,user=rdrijsen 0 0 So it seems that /dev/sda5 (Fedora /) is properly mounted, but dmesg indicates it is mounted readonly. Could the fact that I still have wrong permissions for /dev/shm be caused by this?