Bug 679528 - Test Day:2011-02-22 Nouveau:restartx test fails
Summary: Test Day:2011-02-22 Nouveau:restartx test fails
Keywords:
Status: CLOSED DUPLICATE of bug 679924
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-nouveau
Version: rawhide
Hardware: i686
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Ben Skeggs
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-22 19:37 UTC by Andy Pengelly
Modified: 2011-02-28 22:14 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-02-28 22:14:20 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Xorg.0.log (41.62 KB, application/octet-stream)
2011-02-22 19:37 UTC, Andy Pengelly
no flags Details

Description Andy Pengelly 2011-02-22 19:37:21 UTC
Created attachment 480223 [details]
Xorg.0.log

Description of problem:
Can't startx a second time.

Boot to runlevel 3 using the LiveCD provided with the test day.  Login as liveuser.  Startx and run applications (firefox), all OK; although there is a message about crash in gnome-user-share while the desktop is loading.  Logout back to console prompt.  Xorg.0.log at this point attached.

startx again, and desktop background appears and a message in the top right appears and then disappears quickly saying crash in mutter but nothing else.  Can see black bands flash across the screen and then disappear.  ctrl-alt-del brings up dialogue to log out of system now.  Choose logout but nothing happens.  After a while the screen goes blank and the system does not response (caps lock/num lock lights don't work)

Version-Release number of selected component (if applicable):
F15 graphics test day 2011-02-22

How reproducible:
As above

Expected results:
To be able to startx a second time.

Additional info:
H/W profile at http://www.smolts.org/client/show/pub_6cbc9690-7702-4945-ae58-df8810bafb6f

Comment 1 Ben Skeggs 2011-02-28 06:19:46 UTC
Adam, look like this could primarily be the 32-bit mesa bug?

Comment 2 Adam Williamson 2011-02-28 06:45:45 UTC
yeah, it kinda looks like it - looks like he hit a fortuitous combination of the 'session-is-accelerated takes too long' bug and the '32-bit mesa' bug. andy, are you running a 32-bit live image? On the initial boot, do you see the GNOME Shell interface ('Activities' in the top-left corner, no bottom panel) or the fallback mode (two panels, mix of black and grey)? If the latter, do you get the same crash if you just open a terminal and run 'gnome-shell --replace' ?

Comment 3 Andy Pengelly 2011-02-28 22:02:25 UTC
I was using the 32-bit live image.
On the initial boot it goes to fallback mode.
I have just booted the live image again and logged in as liveuser.
Once the fallback desktop had appeared I opened a terminal and typed gnome-shell --replace.

The two panels disappeared and I was left with a terminal window and nothing else.  The cursor was doing a timer thing.  The terminal showed the following:

Gtk-Message: Failed to load module "pk-gtk-module"
Window manager warning: log level 16: AT-SPI: Accessability bus not found - Using session bus
(mutter:1885) Clutter-DEBUG: Signal type minimise not supported
(mutter:1885) Clutter-DEBUG: Signal type minimise not supported
(mutter:1885) Clutter-DEBUG: Signal type minimise not supported
JS LOG cannot create "Network" item .desktop file not found or corrupt
JS LOG Gnome shell started at Mon Feb 28 2011 21:40:32 GMT-0500 (EST)
shell failed with signal 11

I could highlight text in the terminal window, and access the menus in the terminal, but could not type anything into the terminal.  I chose to close the terminal window and was left with a completely empty desktop.  ctrl-alt-del did nothing.  caps lock/num lock lights were still toggling but I couldn't get any other response.  I hit the restart button.

Comment 4 Adam Williamson 2011-02-28 22:14:20 UTC
yup, looks like it is what we thought it was. You hit both of these bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=679326 (caused you to get fallback mode instead of Shell)
https://bugzilla.redhat.com/show_bug.cgi?id=679924 (caused Clutter to crash when you actually managed to start up Shell)

they're both known bugs, the first is currently being resolved, the second is already resolved for Alpha RC2. Thanks!

*** This bug has been marked as a duplicate of bug 679924 ***


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