| Summary: | [NV43] GeForce 6600 GT doesn't log into Gnome Shell, falls back to old gnome desktop | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | info <info> | ||||||||||||||
| Component: | xorg-x11-drv-nouveau | Assignee: | Ben Skeggs <bskeggs> | ||||||||||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||
| Severity: | medium | Docs Contact: | |||||||||||||||
| Priority: | unspecified | ||||||||||||||||
| Version: | 15 | CC: | airlied, ajax, bskeggs, me | ||||||||||||||
| Target Milestone: | --- | Keywords: | Triaged | ||||||||||||||
| Target Release: | --- | ||||||||||||||||
| Hardware: | Unspecified | ||||||||||||||||
| OS: | Unspecified | ||||||||||||||||
| Whiteboard: | |||||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||
| Last Closed: | 2011-04-23 02:43:41 UTC | Type: | --- | ||||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||||
| Documentation: | --- | CRM: | |||||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||
| Attachments: |
|
||||||||||||||||
|
Description
info@kobaltwit.be
2011-02-22 21:17:47 UTC
Can you please attach your /var/log/Xorg.0.log and /var/log/messages from the testday livecd, thanks! Created attachment 480397 [details]
Xorg.0.log
Xorg.0.log from live CD session.
Created attachment 480398 [details]
/var/log/messages
/var/log/messages file from live CD session
If you execute "gnome-shell --replace" from a terminal, does it start? I tried that before I created this report. I know for sure it doesn't start, but I'm a little vague on what happened instead. I believe it just rendered the system useless. IIRC after the attempt I was left with the blue-striped background, but no menu bar or anything else to click on. I believe it mentioned compositing couldn't be enabled. If you want more details I could burn the live CD again (I replaced it with a network installation image) and try again. That would be useful if you could do that, yes :) If it exists, a newer live spin could be better to try to see if the problem's been resolved already? To run the test again, I have used the 32bit live cd from last week's Gnome3 test day [1]. Things are different from the previous test: 1. When booting up, the system logs in automatically, but doesn't load fully. It gets stuck at an empty, blue-striped background. The gnome's top panel doesn't appear (gnome 3) neither does it log into the fallback mode. 2. Switching to console and run (as root): "init 3" followed by "init 5" brings me at the gdm login screen. When I select the liveuser here, it does log in successfully into gnome shell. I will attach messages and Xorg.0.log as they were right after both steps. [1] http://fedoraproject.org/wiki/Test_Day:2011-03-10_GNOME3_Beta Created attachment 486189 [details]
/var/log/messages after boot and autologin
This is /var/log/messages after step 1. Until this point, I have not interacted with the graphical system at all, I booted the PC from the live CD and waited until it hung on the blue-striped background.
Created attachment 486191 [details]
Xorg.0.log after boot and (failed) automatic login
Same here. Xorg.0.log after boot and automatic login, which hangs on the blue-striped background.
Created attachment 486192 [details]
/var/log/messages after init3; init 5
This messages file is from after I ran init3 followed by init 5 and after which I could login successfully from gdm.
Created attachment 486193 [details]
/var/log/Xorg.0.log after init3; init 5
This Xorg.0.log file is from after I ran init3 followed by init 5 and after which I could login successfully from gdm.
Tested again today with F15-beta live CD. This time I am logged in automatically in the Gnome 3 shell. So I think this bug has been fixed now. Thanks ! Thanks for letting us know! |