Description of problem: epiphany, chrome, etc.. and shortly "out of memory" Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
There's not enough information to do anything with this report. Please provide: 1) The output of dmesg from a fresh boot and after seeing the issue. 2) A description of the actual problem you're seeing 3) If you think this is a permissions issue, the output of 'ls -ld /dev/shm' and 'ls -l /dev/shm'
gee, it's so easy to reproduce and most likely much better way to get all "needinfo" just by spinning up an install, in a VM maybe. I have to: $ chmod 1777 /dev/shm (which seems to be permission of all earlier versions, including early 4.7.x) in order to have epiphany to work, Chrome does not even start, crashes. journalctl Failed to create shared memory file /WK2SharedMemory.217656070: Permission denied Failed to create shared memory file /WK2SharedMemory.396350049: Permission denied Failed to create shared memory file /WK2SharedMemory.514132707: Permission denied Failed to create shared memory file /WK2SharedMemory.4087326799: Permission denied Failed to create shared memory file /WK2SharedMemory.3730609766: Permission denied DMA-API: debugging out of memory - disabling ... usb 1-1.3.3: SerialNumber: 0030900d8b99 Unable to fix SELinux security context of /dev/shm/lldpad.state: Permission denied Relabelled /dev and /run in 21.017ms. ... 5337:5337:0613/095720:ERROR:shared_memory_posix.cc(290)] Creating shared memory in /dev/shm/.com.google.Chrome.Hga13x failed: Permission denied ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=2 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=5337 comm="chrome" exe="/opt/google/chrome/chrome" sig=6 [5337:5337:0613/095720:ERROR:shared_memory_posix.cc(293)] Unable to access(W_OK|X_OK) /dev/shm: Permission denied [5337:5337:0613/095720:FATAL:shared_memory_posix.cc(295)] This is frequently caused by incorrect permissions on /dev/shm. Try 'sudo chmod 1777 /dev/shm' to fix. detected unhandled Python exception in '/usr/sbin/setroubleshootd' Failed to create shared memory file /WK2SharedMemory.2815042205: Permission denied (WebKitWebProcess:5696): Gtk-WARNING **: Theme parsing error: gtk.css:2554:8: not a number (WebKitWebProcess:5696): Gtk-WARNING **: Theme parsing error: gtk.css:2554:17: Using Pango syntax for the font: style property is deprecated; please use CSS syntax /var/spool/abrt is 1159601565 bytes (more than 1000MiB), deleting 'ccpp-2016-06-13-09:44:33-8497' Failed to create shared memory file /WK2SharedMemory.633331017: Permission denied Process 5337 (chrome) of user 1000 killed by SIGABRT - dumping core
(In reply to lejeczek from comment #2) > gee, it's so easy to reproduce and most likely much better way to get all > "needinfo" just by spinning up an install, in a VM maybe. [jwboyer@nuc-i7 ~]$ uname -a Linux nuc-i7 4.7.0-0.rc4.git1.1.fc25.x86_64 #1 SMP Tue Jun 21 15:11:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux [jwboyer@nuc-i7 ~]$ ls -ld /dev/shm drwxrwxrwt. 2 root root 80 Jun 24 09:20 /dev/shm [jwboyer@nuc-i7 ~]$ That's with the latest updated rawhide as of 20min ago. Maybe instead of snarky replies, you could provide the information we need to help you. > I have to: > $ chmod 1777 /dev/shm > (which seems to be permission of all earlier versions, including early 4.7.x) > in order to have epiphany to work, Chrome does not even start, crashes. Ok, what version of 4.7 did this start with and what is the newest kernel that works? Were there other packages that were updated at the same time as the kernel?
I dnf updated this morning, and with 4.7.0-0.rc4.git1.1.fc25.x86_64 I still needed to chmod. sorry I cannot tell with which version it changed, nor whether there were other updates, most likely, being on a rawhide and update every other day I can say updates come in bulk, so most likely yes. Maybe it's hardware=>soft, I attach dmesg.
Created attachment 1171973 [details] dmesg
This is like a duplicate of bug 1347436. We'll mark it as such for now. *** This bug has been marked as a duplicate of bug 1347436 ***