Comment 74 for bug 342923

Using the experimental PPA packages with UXA acceleration brought me some observations after some hours of use, besides the occasional screen "flashes" I had already reported (I use a "blank scren" screensaver that fires up after 5 minutes):

1/ Once the screensaver blanks the screen, it will sometimes be impossible to resume work. The screen is blank (black) and will remain so. The machine is not hanged as it is still possible to shift to texte console. But X is dead: Even killing X or restarting KDM won't result in anything else than a blank screen until the machine is rebooted.

2/ Suspend to RAM : About half of the times, the KDE session is dead at resume. The machine resumes on KDM login screen.

3/ Logging out the KDE session: Sometimes results in a blank (black) screen where the system doesn't react anymore. Nothing can be done locally except using the kernel's "Magic SysRq" keys. Machine will still be remotely usable using SSH - well, for rebooting it...

So it looks that indeed the cure made things worse :-(

I've installed some new MesaGL updates from PPA this morning, but if it doesn't bring an improvement I'll try reverting back to old Intrepid drivers (wonder if I won't simply restore my system from my last Intrepid backups and trash all that Jaunty Junk :-(

For everything was perfectly stable and working in Intrepid...