Created attachment 514743 [details] Google chrome output when it was run in terminal emulator Description of problem: Google Chrome (both beta and stable) and Chromium (stable) crash on twitter.com Russian Fedora Remix 15 (that issue was in 14th also) xorg-x11-drv-nouveau-0.0.16-24.20110324git8378443.fc15.i686 for this moment $ uname -a Linux gex 2.6.38.8-35.fc15.i686 #1 SMP Wed Jul 6 14:46:26 UTC 2011 i686 i686 i386 GNU/Linux How reproducible: Just open twitter.com in chrome/chromium while nouveau is loaded Actual results: Twitter tab crashes after a second Expected results: Everything goes fine Additional info: Chromium can be run by root, twitter works well in this case. Google Chrome can't be run by root. Cleaning Default profile and cache doesn't make sense. This issue occurs on my Lenovo B450 laptop with GeForce G105M VGA and nouveau loaded (xorg-x11-drv-nouveau-0.0.16-24.20110324git8378443.fc15.i686 for this moment) Opening twitter tab and closing it (crashed tab) produces the following in /var/log/messages: [38761.558001] chromium-browse[8702]: segfault at 4 ip 076bc40b sp bfbd5c70 error 4 in nouveau_dri.so[7620000+405000] [38905.031973] [drm] nouveau 0000:01:00.0: PGRAPH - DATA_ERROR INVALID_ENUM [38905.031980] [drm] nouveau 0000:01:00.0: PGRAPH - DATA_ERROR [38905.031985] [drm] nouveau 0000:01:00.0: PGRAPH - ch 4 (0x0007044000) subc 5 class 0x8597 mthd 0x17b0 data 0x00000000 [38905.031994] [drm] nouveau 0000:01:00.0: PGRAPH - DATA_ERROR INVALID_VALUE [38905.031997] [drm] nouveau 0000:01:00.0: PGRAPH - DATA_ERROR [38905.032001] [drm] nouveau 0000:01:00.0: PGRAPH - ch 4 (0x0007044000) subc 6 class 0x502d mthd 0x1420 data 0x00000000 Terminal output of google chrome is in attachment.
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue. Please add drm.debug=0x04 to the kernel command line, restart computer, and attach * your X server config file (/etc/X11/xorg.conf, if available), * X server log file (/var/log/Xorg.*.log*; check with grep Backtrace /var/log/Xorg* which logs might be the most interesting ones, and send us at least Xorg.0.log), * output of (run as root briefly after the crash happens) ausearch -m AVC -ts recent |audit2allow * output of the dmesg command, and * system log (/var/log/messages) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above. We will review this issue again once you've had a chance to attach this information. Thanks in advance.
Created attachment 516674 [details] dmesg dmesg output
Created attachment 516675 [details] /var/log/messages
Created attachment 516676 [details] Xorg log after reboot
Created attachment 516677 [details] Xorg.0.log.old
Created attachment 516678 [details] Xorg.9.log
(In reply to comment #1) Hi. 1. I opened twitter in chromium stable 2. Added 'drm.debug=0x04' grub kernel line and restarted fedora 3. Opened twitter couple times in chromium uname -a Linux gex 2.6.40-4.fc15.i686 #1 SMP Fri Jul 29 18:54:39 UTC 2011 i686 i686 i386 GNU/Linux I have no xorg.conf file 'ausearch -m AVC -ts recent |audit2allow' shows nothing: $ sudo ausearch -m AVC -ts recent |audit2allow <no matches>
I forgot to mention that 'grep Backtrace /var/log/Xorg*' has no output.
I have my deep suspicion that this is actually a bug in chromium itself, but if not it should be somewhere around mesa. Reassigning.
Seems to be an SElinux issue - see http://blog.randell.ph/2011/06/11/fix-for-aw-snap-while-loading-twitter-in-fedora-15-with-selinux-enforcing-enabled/ for some more context and a quite simple workaround: restorecon -R .config/ in your home dir. Worked for me. According to Rahul this problem is part of https://fedoraproject.org/wiki/Features/SELinuxFileNameTransition Maybe some quick fix is possible as quite some people are suffering from this? Jan
> restorecon -R .config/ That command worked for me, thanks!
Glad it helped, gerfert :-) I have changed the subject line of this bugzilla entry to reflect that we have nailed it down to SElinux. Jan
Dup of bug 710276
*** This bug has been marked as a duplicate of bug 710276 ***