Bug 524701 - Unable to log in (X repeatedly crashes when logging in)
Unable to log in (X repeatedly crashes when logging in)
Status: CLOSED DUPLICATE of bug 518748
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel (Show other bugs)
11
All Linux
low Severity urgent
: ---
: ---
Assigned To: Kristian Høgsberg
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2009-09-21 15:33 EDT by markm
Modified: 2009-09-23 09:45 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-09-23 09:45:51 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Screen output when I try to start X manually (as root) (207.30 KB, image/jpeg)
2009-09-21 15:33 EDT, markm
no flags Details
Xorg.0.log (37.35 KB, text/plain)
2009-09-21 15:57 EDT, markm
no flags Details
Xorg.0.log.old (38.67 KB, text/plain)
2009-09-21 15:58 EDT, markm
no flags Details

  None (edit)
Description markm 2009-09-21 15:33:19 EDT
Created attachment 361983 [details]
Screen output when I try to start X manually (as root)

Description of problem:

When I am trying to log in to my desktop, X crashes while loading Gnome and loads login screen again.

Version-Release number of selected component (if applicable):

rpm -qa | grep xorg-x11-drv-intel
xorg-x11-drv-intel-2.7.0-7.fc11.i586

How reproducible:

95%

Steps to Reproduce:
1. Start computer
2. Wait until login screen
3. Login in
  
Actual results:

After 1-2 seconds X crashes and returns to the login screen (gdm)

Expected results:

Being able to log-in.

Additional info:

I was using happily suspend/resume functionality, but unfortunately it got broken - in 10-20% cases after resume I could only see fedora logo and that's all (I've filled bug regarding this issue and my friend, who's using a laptop with intel graphics card confirmed this issue on his machine too).

I've tried earlier kernel, same result, I've also tried to use “nomodeset” - same result. Changing AccelMethod to “EXA” - same result, changing to “XAA” - no screen, though computer works, when I press “power-off” button, it switches off.
Comment 1 markm 2009-09-21 15:57:40 EDT
Created attachment 361984 [details]
Xorg.0.log
Comment 2 markm 2009-09-21 15:58:12 EDT
Created attachment 361985 [details]
Xorg.0.log.old
Comment 3 markm 2009-09-21 15:59:56 EDT
I've just tried Fedora 12 Spin 1 Live - worked fine, logged in without any problems, though panels/windows where flashing after I've enabled compiz...
Comment 4 markm 2009-09-21 20:11:57 EDT
Testing Fedora 12 Spin 3 XFCE Live - worked fine till log in screen, then got a message “Unable to load a failsafe session” with explanation:

Unable to determine failsafe session name. Possible causes: xfconfd isn't running (D-Bus setup problem); environment variable $XDG_CONFIG_DIRS is set incorrectly (must include "/etc"), or xfce4-session is installed incorrectly.

and when I press “quit”, I get the login screen again :)
Comment 5 Matěj Cepl 2009-09-22 11:06:10 EDT
Nice catch, thanks!

Backtrace:
0: /usr/bin/Xorg(xorg_backtrace+0x3b) [0x812d37b]
1: /usr/bin/Xorg(xf86SigHandler+0x9e) [0x80c096e]
2: [0x1cb400]
3: /usr/lib/dri/i915_dri.so(intelDestroyContext+0x104) [0x366388]
4: /usr/lib/dri/i915_dri.so [0x348476]
5: /usr/lib/xorg/modules/extensions//libglx.so [0x6b2009]
6: /usr/lib/xorg/modules/extensions//libglx.so(__glXFreeContext+0x91) [0x6a6151]
7: /usr/lib/xorg/modules/extensions//libglx.so [0x6a6577]
8: /usr/bin/Xorg(CallCallbacks+0x56) [0x808ae86]
9: /usr/bin/Xorg(CloseDownClient+0x67) [0x8080e97]
10: /usr/bin/Xorg(Dispatch+0x1d8) [0x8086538]
11: /usr/bin/Xorg(main+0x395) [0x806bb55]
12: /lib/libc.so.6(__libc_start_main+0xe6) [0x1e2a66]
13: /usr/bin/Xorg [0x806b001]

Fatal server error:
Caught signal 11.  Server aborting
Comment 6 Adam Jackson 2009-09-23 09:45:51 EDT

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

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