Comment 31 for bug 298483

Hi Dominique,

As you see on the upstream bug, they believe this issue is fixed in the latest releases of several X components. These versions are all present in Jaunty.

Personally, I would like to see better proof from upstream that the issue is indeed resolved, but it would not surprise me to know that the issue is resolved with the newer components.

I can understand your hesitance at running an unreleased version of Ubuntu, but unfortunately without knowing from upstream specifically what caused and fixed the crash, we have little other way to prove whether the bug is gone or not.

I myself have been running jaunty on both my laptop and desktop since alpha-1, however I'm a developer and can deal with various problems if I run into them. So far in Jaunty I've run into a number of regressions, but they were mostly on the annoyance scale; most I reported as bugs and got fixes within a matter of weeks, although there is still a flash-breakage-on-amd64 I'm waiting to see fixed, and some other misc. issues. On my desktop (using -ati), I have an issue where the mouse cursor is sometimes slightly corrupted, but it goes away when I move it. I would classify all of these merely as minor annoyances. I've not run into anything that prevented me from using the system: network has been solid throughout jaunty, X has been okay (many complain about performance regressions on -intel though, but it's been acceptable for my modest needs on my laptop), I've had no kernel issues (although my laptop's speaker re-activated and produces an annoying beep when I boot), and all the Gnome software has been okay with a few hiccups (the worst was that opening url's from Gnome programs to firefox broke, but that's been fixed now). By now I think Jaunty has gotten pretty stable and the worst issues seem ironed out. Also I think the number of major changes from here until release will be pretty limited, and developers will be focusing more on just bug fixing here on out.

Aside from the problems, there is one improvement which may have bearing on this issue. With Jaunty I've improved the automatic apport-based X crash handler, such that it is more often able to capture and post to Launchpad when a crash occurs. So, if you do run Jaunty and happen to reproduce the error, it now may be able to automatically capture the full backtrace for you, no need to run gdb manually. (At least, I hope -- it's been working out okay for many).