[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]
** Changed in: xorg (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1354841
Tit
** Tags added: saucy
** Tags removed: bios-outdated-a16
** Tags added: latest-bios-a16
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1354841
Title:
Screen corruption (characters are drawn as black
Looks related to
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1034110 except that I
have an Intel card
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1354841
Title:
Screen corruption (character
Hello,
The bug is still there after upgrading the BIOS.
I should add that I only have the problem with Firefox and Thunderbird, but not
the KDE apps.
I suspect the problem is related to GTK: some programs like grsync and gimp
seem OK, but I've seen they don't display much text like firefox or thu
Dear Christopher,
Thank you for checking the BIOS version, I haven't thought about that. I
have already done several BIOS upgrades on this machine, so it shouldn't
be a problem. I will update the bug report accordingly once it is done
Thank you
Matthieu
PS: I have at this very moment the "white"
M, as per
http://www.dell.com/support/home/us/en/19/product-support/product/latitude-e5510/drivers
an update to your BIOS is available (A16). If you update to this following
https://help.ubuntu.com/community/BIOSUpdate does it change anything? If it
doesn't, could you please both specify what
apport information
** Tags added: apport-collected
** Description changed:
Sometimes, the characters are rendered as black squares (cf attachment). I
couldn't find any event in the systems logs that could explain that.
I can "stop" the bug by changing the anti-aliasing options in the system
Yes it still happens from time to time on 14.04
Actually, I think it didn't happen at all in Sept-Oct, but it happened a couple
of times in Nov. It coincides with the reboot I did at the beginning of Nov to
upgrade the system, but I can't tell if it's related to the bug due to its
highly intermi
M, this bug was reported a while ago and there hasn't been any activity
in it recently. We were wondering if this is still an issue? If so,
could you please run the following command in the development release
from a Terminal as it will automatically gather and attach updated debug
information to t
