[Ubuntu-x-swat] [Bug 337243] Re: [g33] X.org crash on Intel 82G33/G31 (with stacktrace)

2009-08-11 Thread Bryce Harrington
We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this

[Ubuntu-x-swat] [Bug 337243] Re: [g33] X.org crash on Intel 82G33/G31 (with stacktrace)

2009-07-16 Thread Bryce Harrington
** Changed in: xserver-xorg-video-intel (Ubuntu) Status: Incomplete = New ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: New = Incomplete -- [g33] X.org crash on Intel 82G33/G31 (with stacktrace) https://bugs.launchpad.net/bugs/337243 You received this bug notification

[Ubuntu-x-swat] [Bug 337243] Re: [g33] X.org crash on Intel 82G33/G31 (with stacktrace)

2009-07-01 Thread Bryce Harrington
Hrm, bummer. Well this new issue is a separate bug, an X freeze. Basically, the GPU has locked up, which is why restarting X isn't sufficient to get it going again. gdb doesn't really give anything useful for X freeze bugs, but we have other tools for gathering data on that.

[Ubuntu-x-swat] [Bug 337243] Re: [g33] X.org crash on Intel 82G33/G31 (with stacktrace)

2009-06-30 Thread Tom Sillence
On karmic, X hung when I tried to open SystemPreferencesScreensaver. The backtrace looks very different (attached). Also, gdb now hangs when I try to continue after getting a backtrace - before I could continue but reattaching would show the stack hadn't changed. The last line of the logfile

[Ubuntu-x-swat] [Bug 337243] Re: [g33] X.org crash on Intel 82G33/G31 (with stacktrace)

2009-06-25 Thread Bryce Harrington
[This is an automatic notification.] A new major version of the -intel driver is now available in Karmic. This version includes a major reworking of the acceleration architecture, which resolves a huge number of issues. We do not know whether it resolves the issue you reported. Would you mind