gnome-session makes Xorg crash in xf86SetScrnInfoModes

This one is the one made by friendly-recovery

This is the one which worked for me for a long time. Sometime back it seems the "DRI" module is no more or something like that.

Sorry meant this one

Sorry meant this one

this is /var/log/Xorg.0.log

X.Org X Server 1.4.99.905 being used.

My graphic chipset

shirish@Mugglewille:~$ lspci | grep Graphics
00:02.0 VGA compatible controller: Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 03)

Hi all,
 Seems to have been issues with xorg.

I did the following from http://wiki.ubuntu.com/DebuggingProgramCrash

modifying x.org.conf

Section "ServerFlags"
        Option "NoTrapSignals" "true"
EndSection

attaching the new Xorg.0.log maybe that will give more pointers

NoTrapSignals will cause the server to not trap its own death and therefore not include the backtrace in its log. You will then need to find an apport log or a core file on which you can run gdb.

ah ok, removed it then, from the wiki I got some other understanding. Sorry.

can somebody tell me the best way to use gdb and xorg so that I can give something more substantial. Thanx. The wiki is very generic in this regard.

I don't understand from the description how the problem manifests itself. "Broke my GNOME"? Are you thrown back to the gdm greeter just after logging in? Does a failsafe gnome or terminal session work? Any errors is gdm.log? Are you using compiz?

Hi Tromod,
  First of all thanx for replying back on this. Yes, I get thrown back to the gdm greeter just after logging in. Attaching the output from /var/log/gdm/0.log as well. As far as compiz is concerned, no not using it.

Here is why:
(EE) Failed to load module "dri2" (module does not exist, 0)

This has been fixed upstream I think. Try to disable the "dri2" module in xorg.conf.

You can disable that module by adding this line to the Module section of your xorg.conf:
Disable "dri2"

I hope it helps.

I was a little too fast saying that was the reason. This error message should not be fatal. Indeed I get it myself running an Intrepid live CD, and X works fine nonetheless. The next thing in my log is the loading of the ati driver module.

Does a failsafe gnome or terminal session work?

Hi guys,
 Alberto I had used fix the xserver from friendly-recovery so that my xorg.conf is something like what I'm attaching. I don't see any 'module' section where I need to write Disable "dri2" .

I also looked up whatever I could find on "dri2 module" and although I don't understand much of stuff, found the following links

http://www.phoronix.com/scan.php?page=news_item&px=NjMxNw

http://wiki.x.org/wiki/DRI2

http://lists.freedesktop.org/archives/xorg/2008-February/032646.html

Tormod,
 While terminal-session works gnome-failsafe doesn't work. Even in terminal-session the terminal is without windowing i.e. without a bar having minimize, maximize and cancel on top .

The log shows some backtrace. If something more has to be done, would gladly do so. This is of the session where I tried to use gnome-failsafe.

You have to create a "Module" section yourself. The failsafe terminal session is just like that, a terminal and no window manager. At least that means X can start up, and that something in the gnome session makes it crash. Can you please run glxinfo in the failsafe terminal?

Intel cards are hit by http://bugs.freedesktop.org/show_bug.cgi?id=15477 but normally only when using compiz, so I don't know if it's related.

One of your xorg.conf's posted use the i810 driver, which I think is obsolete. You should use "intel" or better not specify anything. It should work fine without xorg.conf at all.

Tromod,
 couple of things, one of the xorg.confs which used the i810 was one which I tried when the other one wasn't working.

Is this the way the module section should be written?

Section "Module"
 Disable "dri2"
EndSection

Do please look where I have used caps or not and correct me if something is incorrect.

Also can this section appear anywhere in the xorg.conf or is there a defined place where it should be coming in?

Another thing did a glxinfo > glxinfo.txt which I'm attaching to the bug-report.

Please lemme know if something more is needed.

The time I was trying to glxinfo > glxinfo.txt I got this message as well as in the fail-safe terminal, dunno if its important or not.

Failed to initialize TTM buffer manager. Falling back to classic.

Your Module section looks fine. You can verify in your log that the module is not tried to be loaded like before.

Your glxinfo shows GLX_EXT_texture_from_pixmap which they talk about in the bug I mentioned. So I guess it is somewhat related and it will be fixed in Intrepid soon, with mesa 7.1~rc3-1 or newer (commit 4fab47b13c214dc79e0ae5d8001521029ce34231). I'll therefore set the bug to "fix committed", and please report back once you have tried the newer mesa.

hi all,
 mesa 1.7 hit yesterday but still the same issue.

libgl1-mesa-dev version :- 7.1~rc3-1ubuntu1
xorg :- 1:7.4~0ubuntu1
xorg-xserver-video-intel :- 2:2.3.2-2ubuntu3

Adding the glxinfo I tried with the new version.

The GLX_EXT_texture_from_pixmap disappeared from "GLX extensions:" which is good. You say "same issue", do you still get "Failed to initialize TTM buffer manager"? Does it crash if you try to start compiz in the failsafe terminal session?

Can you please try to get a full backtrace from Xorg? See that wiki page and the DebuggingXorg link on it.

"Me too".
     I upgraded from 8.04.1 for PowerPC to 8.10... on a well, it's a Frankenstein. 1250mhz G4 Windtunnel motherboard, but stuck into a Compaq SP750 case. Yeah.. kind of a prank. (When I was on vacation, my coworkers backed up my data, pulled the SP750 board, replaced the G4 with an identical 8.04 PPC setup, complete with proper USB adapter so I had the same IBM Model M keyboard hooked up and everything; they took bets on how long it'd take me to notice... about 4 hours. It was pretty obvious after I rebooted and heard the mac startup sound & Mac boot loader; otherwise, not obvious at all.)

Excerpt from Xorg.0.log.old, which is attached. The failsafe terminal works; I put on xfce4, which was super-stripped but a friend showed me how to add some menus and launchers; it doesn't crash either.
====================================
X.Org X Server 1.4.99.905 (1.5.0 RC 5)
Release Date: 5 September 2007
X Protocol Version 11, Revision 0
Build Operating System: Linux Ubuntu (xorg-server 2:1.4.99.905-0ubuntu5)
Current Operating System: Linux user-desktop 2.6.24-19-powerpc #1 Fri Jul 11 21:37:37 UTC 2008 ppc
Build Date: 01 August 2008 12:03:37AM
............
Backtrace:
0: /usr/X11R6/bin/X(xf86SigHandler+0x94) [0x10088c44]
1: [0x100344]
2: [0x10211c98]
3: /usr/X11R6/bin/X(xf86SetScrnInfoModes+0x1e0) [0x100b80f0]
4: /usr/X11R6/bin/X [0x100c23e8]
5: /usr/X11R6/bin/X(RRGetInfo+0xf8) [0x1014caa8]
6: /usr/X11R6/bin/X(ProcRRGetScreenResources+0x13c) [0x10151c2c]
7: /usr/X11R6/bin/X [0x101494ac]
8: /usr/X11R6/bin/X(Dispatch+0x4b0) [0x10047bb0]
9: /usr/X11R6/bin/X(main+0x43c) [0x100289dc]
10: /lib/libc.so.6 [0xf975b24]
11: /lib/libc.so.6 [0xf975ce0]

Fatal server error:
Caught signal 11. Server aborting
=======================================
And, relevant line from lspci -v:

0000:00:10.0 VGA compatible controller: ATI Technologies Inc Radeon RV250 If [Radeon 9000] (rev 01)
        Subsystem: ATI Technologies Inc Radeon RV250 If [Radeon 9000]
        Flags: bus master, stepping, 66MHz, medium devsel, latency 255, IRQ 48
        Memory at 98000000 (32-bit, prefetchable) [size=128M]
        I/O ports at 0400 [size=256]
        Memory at 90000000 (32-bit, non-prefetchable) [size=64K]
        Expansion ROM at f1000000 [disabled] [size=128K]
        Capabilities: <access denied>
        Kernel driver in use: radeonfb

     I just updated today, but I don't know how far behind the PPC builds are compared to regular. libgl1-mesa-dri is at 7.1~rc3.1ubuntu2 though.

     Umm... never mind I guess? The local OpenBSD expert was netbooted the box into OpenBSD for a few days. When I rebooted into Ubuntu, without even running any updates since the last time it didn't work, it now works. Odd. I do have a different Trinitron hooked up..?

Hi all,
 Yesterday's updates fixed my stuff.

xorg :- 1:7.4~0ubuntu2
xserver-xorg-video-intel :- 2:2.4.0-1ubuntu1
mesa-utils :- 7.1~rc3-1ubuntu2
gnome-session :- 2.23.6-0ubuntu1

Can just say this combo works for me (WFM)