Comment 38 for bug 1860483
Revision history for this message
| Paul Collinsworth (collinsworth) wrote Revoked ... Re: Oop! Re: [Bug 1860483] Re: [nouveau, GeForce 7300 LE] screen background overlaid with scan type artifact in red | #38 |
Spoke (wrote) too soon. The artifact is there, in the screen of the new
install.
After the intitial install and restart, it wasn't there, while the
system was running the intitial image from sda1. I then powered down and
booted into sdb1, and, of course, the artifact was still present (well,
why wouldn't it be? I hadn't changed anything.). I did some stuff there,
since that's where my registered e-mail and 'net accounts are. Then I
restarted again, booting up in sda1.
And the artifact was there.
BTW, the linux generics for sda1 are the version of 5.3 that was being
loaded with the system installs yesterday. The sdb1 linux image set is
still 5.5...
The artifact as displayed when sda1 is up seems to be slightly different
from that of sdb1, but that may just be perceptual, due to the way the
two desktops are populated.
On 1/25/20 1:46 PM, Paul Collinsworth wrote:
> Disregard the 1/25 12:37 AM message.
>
> I reinstalled v18.04.3 and there's no problem with the system on that
> drive (sda1). There's a clear sharp "Bionic Beaver" line drawing.
>
> I had managed to complete the install last night on the drive I'd been
> using, sdb2, and that still has the display problem.
>
> A mixup happened at the mid-install restart; the bios was still queued
> up for boot on sdb2.
>
>
>
>
> On 1/25/20 12:37 AM, Paul Collinsworth wrote:
>> Another result. When I tried the v18.04.3 system preview from the USB
>> FD, the background was "normal". I just finished installing the
>> system, and the background now has the transparent red raster
>> overlay. I could get to "Settings" though without locking up the
>> system, so there was at least a marginal improvement there; haven't
>> tried to reproduce any other the other "no response"/lockup failures.
>>
>>
>> On 1/24/20 12:50 AM, Daniel van Vugt wrote:
>>> Although downloading the driver from the above link might cause even
>>> greater problems than we have here. Maybe hold that thought, since the
>>> only issue right now is corrupt wallpaper that might be the lesser evil.
>>>
>>> It's still possible this bug could be fixed with a kernel/mesa/mutter
>>> update.
>>>
>>> ** Changed in: linux (Ubuntu)
>>> Importance: Undecided => Medium
>>>
>>> ** Changed in: mesa (Ubuntu)
>>> Importance: Undecided => Medium
>>>
>>
>