Comment 16 for bug 269509

Bryce Harrington [2009-01-07 6:32 -0000]:
> However, if you're seeing it report 'software rasterizer' on the
> first head too, that does seem to be a legitimate bug.

I do.

> First, can you reproduce this when booted into a single session? I.e.
> does it always show software rasterizer

yes.

>, or only when you have the guest session going?

No, I first produced glxinfo.primarysession.jaunty.txt, then started
the second session, and then produced the other dump.

> I tried reproducing it on my 965 box but couldn't, would you mind
> listing the exact steps to reproduce it?

for glxinfo:
- boot
- log into GNOME
- glxinfo > glxinfo.primarysession.txt
- start guest session
- glxinfo > /tmp/glxinfo.guest.txt
- switch to primary session with ctrl+alt+f7 (since quitting the guest
  session kills all files of guest)
- copy /tmp/glxinfo.guest.txt to ~
- switch back to guest and close the session

For checking white screen:
 - edit /usr/bin/compiz and disable the abort_* thing in

        # check if we run with software rasterizer and if so, bail out
        if check_software_rasterizer; then
                verbose "Software rasterizer detected, aborting"
                abort_with_fallback_wm
        fi

Then start the guest session.

> Second, could you attach your Xorg.0.log and Xorg.20.log taken from when
> both sessions are up; upstream usually wants that.

Done.

> Third, you mentioned that glxinfo reports 65 fps... did you mean
> glxgears?

Yes, sorry. glxgears.

> 65 seems like a pretty low framerate. Do you recall or could
> you test what you get when running the Intrepid LiveCD where the primary
> session is not showing up as software rasterizer?

Will do in a minute and report back.

--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)