Description of problem: Running Live Media Fedora Workstation 21 Alpha TC5 lead to "Oh no! Something went wrong." on Sony Vaio powered by Intel 945GM. The same laptop has no problem running on the latest update of Fedora 20 using Gnome Shell 3.10. Version-Release number of selected component (if applicable): Gnome Shell 3.13.90 How reproducible: Always Steps to Reproduce: 1. Boot the Live Workstation 2. 3. Actual results: Crashed with "Oh no! Something went wrong." Expected results: The system should boot to the desktop. Additional info: Test done with Live Media version of Fedora 21 Workstation on Sony Vaio VGN-N250E https://docs.sony.com/release/specs/VGNN250EW_mksp.pdf
Can we please get the 'journalctl -b' output run as root, at least? That should identify the crashing component.
Created attachment 934327 [details] journalctl -b from the eeePC901 The output with crash using journalctl -b from the eeePC901
"Process 1198 (gnome-shell) of user 42 dumped core." Well, that's nice and clear...assuming Luya's hitting the same thing, it looks like it may well be graphics related, so we may also need to see the output after booting with 'drm.debug=15'. Does abrt not pick up the gnome-shell crash? Maybe if you check the 'system' (not user) crashes?
Created attachment 934374 [details] drm.debug=15 on the eeePC901 Attached is the journalctl -b from the eeePC 901 with drm.debug=15. I'll look for abrt captures in /var to see what I can see
That one seems to hit a different error, I see no crash but I see: Sep 04 12:36:49 localhost gnome-session[702]: (gnome-shell:920): Cogl-ERROR **: Failed to create texture 2d due to size/format constraints are you over 2048 pixels on any axis?
> are you over 2048 pixels on any axis? haha! There eeePC 901 is a mere 1024*600
Created attachment 934537 [details] journalctl -b from Sony Viao VGN-N250E Taken from Fedora 20 update. I was unable to copy the version F21TC5 Alpha version.
Created attachment 934539 [details] journalctl -b from Sony Viao VGN-N250E
(In reply to Adam Williamson (Red Hat) from comment #5) > That one seems to hit a different error, I see no crash but I see: > > Sep 04 12:36:49 localhost gnome-session[702]: (gnome-shell:920): Cogl-ERROR > **: Failed to create texture 2d due to size/format constraints > > are you over 2048 pixels on any axis? Mine is 1280x800
Created attachment 934566 [details] drm.debug=15 on Sony Viao VGN-N250E
luya: that log seems incomplete - it only has a couple of lines which aren't DRM lines. What happened on that boot? Did you cut any of the log out?
Created attachment 934607 [details] newer drm.debug=15 on Sony Viao VGN-N250E I put the wrong file. I rebooted F21TC5 and include the detailed drm.debug
Running F21 Alpha TC6. The issue is still occuring.
Created attachment 939479 [details] journalctl -b report from Sony Viao VGN-N250E Latest report using Fedora 21 Desing Suite Alpha. Notable observation: Sep 19 19:13:55 localhost gnome-session[1223]: libGL error: Version 4 or later of flush extension not found Sep 19 19:13:55 localhost gnome-session[1223]: libGL error: failed to load driver: i915 Sep 19 19:14:23 localhost gnome-session[1223]: (gnome-shell:1468): Cogl-ERROR **: Failed to create texture 2d due to size/format constraints
Rebooting using basic driver option from the live media leads to the full Gnome Shell. Based on the test, it seems the bug is possibilty driver related (i915). Peter, can you confirm the issue?
(In reply to Luya Tshimbalanga from comment #15) > Rebooting using basic driver option from the live media leads to the full > Gnome Shell. Based on the test, it seems the bug is possibilty driver > related (i915). Peter, can you confirm the issue? So with my latest "yum update" (previous was the 16th) it now works for me. Looking through the list of updates it seems it was either kernel, clutter or mutter update that likely fixed the issue for me.
(In reply to Peter Robinson from comment #16) > > So with my latest "yum update" (previous was the 16th) it now works for me. > Looking through the list of updates it seems it was either kernel, clutter > or mutter update that likely fixed the issue for me. In that case, it was likely a kernel issue as I was able to run Gnome Shell in nomodeset. I can also confirm the update fixed the issue. I am closing this bug under kernel component. Thank you for the help.