Comment # 5
on bug 75128
from publicface@bak.rr.com
I've been able to fix ksnapshot (I didn't know how to force a reinstall - now I do). So since as I mentioned I already restarted kdm (and by inference, the X server) this problem can't be further explored at this time, what other tools/procedures should I be prepared with next time it happens? screenshot /var/log/Xorg.0.log dmesg xwininfo Anything else? For the record, the reason I reported it here is due to a discussion with someone else. And I quote: "I moved away from ATi/AMD altogether to nvidia because of the constant screen corruption issues on both the open source and proprietary drivers". Since changing cards isn't an option at this time, reporting the problem is a bit easier. It doesn't happen often, but it does happen every now and then. Me personally I'm not interested in blaming anyone or anything. I don't care where the bugs are, other than in terms of getting them fixed. Since restarting kdm is almost as extreme as rebooting, I would like to see a way to reset the screen without having the net effect of being logged out. I don't know if that's something that could be accomplished in the driver, or where exactly it could be done.
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
