Thanks for your attention, but as I need the machines for some kind of production work, I cannot revert them to the buggy state currently, as I had to fix and modify a lot: mainline kernel, xservers from lucid, and a self-compiled savage xserver from the lucid sources as I had to do a bugfix in the driver source code, but this is not related to this problem.
Can I still use your collection command to gather something useful, even if I keep the system in working state? This would not be any problem. -- maverick: S3 savage (but also with vesa driver): X crash/restart after first switch to console and back, garbaged and unusable screen after second console switch https://bugs.launchpad.net/bugs/660301 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
