On 11/21/2013 01:38 PM, Dale wrote: > Alan McKinnon wrote: >> On 21/11/2013 17:10, Mateusz Kowalczyk wrote: >>> Greetings, >>> >>> I spent a chunk of yesterday updating world on my machines (2 file >>> servers and 1 netbook) and with some effort, the updates went through. I >>> had to go out today so I rebooted my netbook and I started noticing >>> weird graphical glitches in certain applications, as if parts of the >>> screen weren't updating, namely in urxvt and emacs. In urxvt, my shell >>> prompt seems to not render the cursor and often keeps the letters I >>> remove still on the prompt (only graphically, they aren't actually >>> there). This is extremely annoying. >>> >>> It's also terrible in emacs: cursor sometimes doesn't get rendered and I >>> get tons of artefacts from different buffers when I switch or from text >>> I was editing. You can find an example image of such glitches in emacs >>> at [1]. This is absolutely tragic for me as I spend majority of my time >>> in emacs. I'd like to note that I'm running emacs in a graphical frame >>> and not in a terminal. >> >> A quick note to say that you are not alone, I get this as well since >> about 6 weeks ago (a ~amd system). So it's not something you and just >> you managed to do, I got it as well. >> >> In my case it's as if the system's idea of what is on the screen is off >> by one row of pixels. I get a stray row of dots at the top of lines that >> correspond to the risers of glyphs on the previous line, and new >> underscores don't show up until I enter a newline. >> >> This is a mostly KDE system using konsole, so it's not the terminal >> emulator or editor that's the root cause. >> > > Some may recall I have posted about similar issues in the past. Heck, I > still do when I upgrade the drivers. I'm stuck using a older driver but > still run into the issue every once in a while. > > The biggest giveaway for me is that my clock is stuck. I have mine set > to show seconds and it either stops or the time sort of jumps several > seconds at a time. > > It's weird but as Alan said, it is not just you. You got plenty of > company on this one.
One other possibility is that xorg updated something that broke some video drivers. Maybe "qlop -l xorg" would give you a hint about when your video problem first appeared?
