Bug 683994 - Starting Gnome crashes system
Summary: Starting Gnome crashes system
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-ati
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Jérôme Glisse
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-10 21:21 UTC by Matthias Runge
Modified: 2011-03-19 23:03 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-03-19 08:13:31 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
glxinfo (23.51 KB, text/plain)
2011-03-10 21:21 UTC, Matthias Runge
no flags Details
Xorg.log (37.01 KB, text/plain)
2011-03-13 19:42 UTC, Matthias Runge
no flags Details
Smolt Profile (2.61 KB, text/plain)
2011-03-13 19:46 UTC, Matthias Runge
no flags Details
System start, login into gnome desktop, crash (/var/log/messages) (142.69 KB, text/plain)
2011-03-13 20:08 UTC, Matthias Runge
no flags Details

Description Matthias Runge 2011-03-10 21:21:48 UTC
Created attachment 483566 [details]
glxinfo

Description of problem:

log in to gnome 3 crashes system. System does not react in any form 

Version-Release number of selected component (if applicable):
mutter-2.91.91-1.fc15.i686


How reproducible:
every time


Steps to Reproduce:
1. log into gnome 3 session
2. 
3.
  
Actual results:
system hangs, no logs are written.


Expected results:
start gnome 3 session


Additional info:
system was able to run gnome-shell previews (from f13/f14) but no go for f15 gnome3 

lspci shows
01:00.0 VGA compatible controller: ATI Technologies Inc M22 [Mobility Radeon X300]

kernel-PAE-2.6.38-0.rc8.git0.1.fc15.i686
mesa-libGLU-7.10-0.27.fc15.i686
mesa-libGL-7.10-0.27.fc15.i686
mesa-dri-drivers-7.10-0.27.fc15.i686
xorg-x11-drv-ati-6.14.0-2.20110204gita27b5dbd9.fc15.i686

Comment 1 Matthias Runge 2011-03-11 15:26:23 UTC
since xorg-update today, it goes some further:
Log into gnome3 shows a desktop (menuline on top and bottom of the screen). System freezes right after desktop appears.
Maybe hardware related?

Comment 2 Peter Robinson 2011-03-13 01:59:27 UTC
Please add the following details to the ticket as per standard X debug procedures.

https://fedoraproject.org/wiki/Xorg/Debugging

Comment 3 Matthias Runge 2011-03-13 19:42:23 UTC
Created attachment 484040 [details]
Xorg.log

Comment 4 Matthias Runge 2011-03-13 19:46:37 UTC
Created attachment 484041 [details]
Smolt Profile

Comment 5 Matthias Runge 2011-03-13 20:08:59 UTC
Created attachment 484046 [details]
System start, login into gnome desktop, crash (/var/log/messages)

Comment 6 Matthias Runge 2011-03-13 20:14:10 UTC
Sadly, I was unable, to catch more detailed logs. System is does not react in any form, when desktop is shown.

Comment 7 Matthias Runge 2011-03-13 20:19:28 UTC
in messages, there is one crash mentioned:
Mar 13 20:50:59 sofja gnome-session[2287]: WARNING: Application 'gsettings-data-convert.desktop' failed to register before timeout

calling gsettings-data-convert results in another error:
(gsettings-data-convert:4655): GLib-GIO-WARNING **: g_settings_set_value: value for key 'color-shading-type' in schema 'org.gnome.desktop.background' is outside of valid range

GLib-GIO-ERROR **: Settings schema 'org.gnome.desktop.screensaver' does not contain a key named 'mode'
aborting...
Aborted (core dumped)

Comment 8 Matthias Runge 2011-03-13 20:56:44 UTC
using kernel-2.6.37.2 from koji works. seems to be a kernel issue

Comment 9 Dave Airlie 2011-03-19 08:13:31 UTC
kernel 2.6.38 and over should also work, it was a bug in the 38-rc series fixed in final.

Comment 10 Matthias Runge 2011-03-19 12:21:48 UTC
Sadly, it still crashes reproducible, so issue is not fixed. The system is fully updated.

Comment 11 Matthias Runge 2011-03-19 17:21:34 UTC
OK, this is getting a little awkward for me. I tried it again (today) and it's currently running flawlessly, not crashing, gnome shell runs ok.

I'll keep an eye on this.


Note You need to log in before you can comment on or make changes to this bug.