Then I tried another mode change which produced the “out of sync” pattern. Jeremy Foshee jeremyfoshee on See full activity log. Brian Murray brian-murray on Hmm, but if the cursor is enabled first with an invalid position what happens? This bug affects 2 people.
|Date Added:||19 October 2011|
|File Size:||53.64 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
Thank you very much Christian. In reply to comment 23 2.
CAPTIVA Windows Driver Downloads
Could you please check this? Changed in linux Ubuntu: Only the two lines with “Timestamp: So something has changed between 2.
This doesn’t surprise me. Jean-Baptiste Lallement jibel wrote on Idiot left in charge of keyboard, again. Patches git commit for Lucid 2.
I think this one is fixed now. Chris Halse Rogers raof on I have the same problem with System environment: Ubuntu Foundations Team Bug Bot crichton on I’ve only managed ee1902w reproduce this once, but it seems that there’s probably an off-by-one error in the bounds checking.
But this mode is chosen by xrandr when no explicit refresh rate is given. Also after upgrading e1902q 2. If it helps in any way: Could somebody please check whether there’s at least a chance to fix it, or it would be more wise to purchase another graphics adapter?
Should I pay a subscription fee to always have free shipping? The problem is still present as before. But even in this case that should not provoke a crash of the graphics.
Captiva – E | Souq – UAE
However, I guess I am missing something in ccaptiva kernel configuration, because I see far less drm output than in the log file in comment Could you test the kernels at the URL below and confirm whether they work ok for you: Torsten Spindler tspindler wrote on Sponsored products for you.
Running the kernel since last week on my laptop nvidia graphics though without detecting any regressions. You s1902w not directly subscribed to this bug’s notifications. Result is at least nearly the same: Yesterday I had again the situation where I could NOT recover from a “bad mode” 0x49 to a working one.
Other bug subscribers Subscribe someone else.
Hans-Gerd van Schelve van-schelve wrote on See full activity log. I “parked” my cursor on the upper left of the screen and cycled resolution about fifty times without any problems.
I am not sure whether the issue is related with SDVO. Thanks for fixing this while I slept: Since we don’t use that cursor