Description of problem: After a period of use the display on a KDE session gets all messed up. Windows don't redraw properly, lines appear across the display, etc. I doubt this is a radeontool issue, but I don't know what other package to assign it to. Version-Release number of selected component (if applicable): Whatever packages are in the following isos. They both had the same problem, although the F12 rawhide iso went longer before the bad redraws started occurring. Fedora-11-i686-Live-KDE.iso kde-i386-20091012.16.iso How reproducible: Both times I tried for each live distribution. Steps to Reproduce: 1. Download either of the above isos. Mount them on a USB flash drive using liveusb-creator. 2. Boot the usb image. Run it doing normal things. File browsing with Dolphin, web browsing with Konqueror, etc. Actual results: The display for the session gets messed up. Black lines appear. Windows gray out. Things flicker. Expected results: The session should run without display errors. The same USB flash drives run fine without any display issues on an HP laptop with an Intel display driver. The F11 live flash drive runs fine on an HP laptop with an nvidia display driver. Additional info: Here is a link to the machine that it failed on. LT3108H http://www.bestbuy.ca/catalog/proddetail.asp?sku_id=0926INGFS10126124&catid=28597&logon=&langid=EN Here is a link to a similar machine that has more information. LT3103U http://www.gateway.com/systems/product/529668268.php This all happened in the store, so I didn't gather more information than that. I will get more information if you need it. Thanks for listening.
description sounds like display driver, reassigning => xorg-x11-drv-ati
Please attach dmesg and output of lspci -vvnnxx with fedora 12.
I didn't buy the machine (yet), so I can't attach the dmesg output. If I happen to go to the store again I'll try to get it.
This doesn't make any sense. We cannot debug issue with computer where we cannot get all required information. If you actually buy the copmuter and will have the problem (or you befriend store personal so much that you can collect all these information :)), feel free to file a new bug with information requested in comment 2 and /var/log/Xorg.0.log attached to it as uncompressed separate attachments. Meanwhile closing this bug as INSUFFICIENT_DATA
Its a bug. What doesn't make sense ? I know that I can't provide information to help debug it, but the fact that it got registered may help other people who run into the same problem. Secondly, I am not sure that one can even get the log file once it messes up because you can't see anything on most of the windows. Best Buy sells these things. Take a USB drive loaded with F12 Live and try it yourself.
(In reply to comment #5) > I know that I can't provide information to help debug it, but the fact that it > got registered may help other people who run into the same problem. If somebody finds it, she is very welcome to reopen it with additional information (as said in my comment). > Secondly, I am not sure that one can even get the log file once it messes up > because you can't see anything on most of the windows. There is sometimes possibility of having other computer and log into the broken one with ssh, you can restart in text mode (just add "text" to the kernel command line) and collect logs post mortem. > Best Buy sells these things. Take a USB drive loaded with F12 Live and try it > yourself. Unfortunately, the closest Best Buy to Prague, Czech republic, where I live is couple of thousand miles away. Sorry, I couldn't resist to reply to this one. If you want to help development of Fedora, you can much easily do the same thing yourself, collect the information from crash (or whatever is going on), and provide the logs. But you don't have to ... when there is a bug like this, there is high chance that somebody else in the better position to test this will get hit by it as well. That's how FLOSS development works ... when you cannot help, somebody else will. Anyway, thank you very much for taking pain in filing this bug report, and I am sorry we couldn't fix this for you.