On Wed, 10 Jun 2015, Stanislav Baiduzhyi wrote:
Log shows 1280x800 and 1280x1024, are those native resolutions for your monitor?
Yes they are.
Could you post the output from 'xrandr --query' as well?
Yes: Screen 0: minimum 8 x 8, current 1280 x 1824, maximum 32767 x 32767 LVDS1 connected 1280x800+0+1024 (normal left inverted right x axis y axis) 0mm x 0mm 1280x800 60.16*+ 1024x768 60.00 800x600 60.32 56.25 640x480 59.94 DVI1 disconnected (normal left inverted right x axis y axis) VGA1 connected primary 1280x1024+0+0 (normal left inverted right x axis y axis) 338mm x 270mm 1280x1024 60.02*+ 75.02 1280x960 60.00 1280x800 74.93 59.81 1152x864 75.00 1280x768 74.89 59.87 1024x768 75.08 70.07 60.00 1024x576 59.97 832x624 74.55 800x600 72.19 75.00 60.32 56.25 848x480 60.00 640x480 75.00 72.81 66.67 60.00 720x400 70.08 VIRTUAL1 disconnected (normal left inverted right x axis y axis) On Wed, 10 Jun 2015, Anton Aylward wrote:
You don't say if this is a laptop or a desktop or what type of desktop (SFF perhaps), the vendor. You don't say if the video is integrated but I'd presume so from the lspci line.
The reason I didn't mention too much hardware spec, is because I ruled out hardware issue in the first run. Chromium always display webpage content correclty although the UI (title bar) messes up -> straight lead me to suspect software. Yes, it is a laptop, "Toshiba Portégé Dynabook R600" is the model. Now to think about it, I can reboot to Windows to use a few hours, see if it affects Windows too. I doubt so, because I don't remember any problem on this openssue before upgrading to 13.1. The model is about the age to break down.
The 'it doesn't happen at boot' suggests something in the class of a thermal problem.
Right - but it also suggest that this is trigged by lock-screen, when monitor is shutdown to save power and restarted with a lock-screen. I'll force monitor to be on for a few days for observation.
A final test to see if this is a hardware problem .... within some bounds ... would be to ssh -X to it.
I forget to mention that ssh -X always perform okay (on the X of another host of couse), so it leads us away from fonts and gtk again. But, that only moves suspicion to the X-server, and that could be either a driver bug or hardware problem.