#700235 xserver-xorg-video-nouveau: uninitialized video memory or garbled images on login screen (lightdm) #700235
- Package:
- xserver-xorg-video-nouveau
- Source:
- xserver-xorg-video-nouveau
- Description:
- X.Org X server -- Nouveau display driver
- Submitter:
- Andrei POPESCU
- Date:
- 2019-12-05 17:39:04 UTC
- Severity:
- normal
Hello, I'm seeing #631391[1], but with lightdm and nouveau, even the workaround works (disabling compositing). Since I don't have any problems with the proprietary nvidia driver I thought it might be the driver. [1] if you don't want to look it up a short summary is: on login strange effects are seen when cold-booting or garbled pieces from previous session if you reboot. The workaround is to disable compositing. Kind regards, Andrei
Quite possible, although the submitter of #631391 has Radeon cards.
Can you please test version 1:1.0.6-1 from experimental?
Cheers,
Sven
Sorry, forgot to mention I already did. No change. Kind regards, Andrei
Okay, could you please temporarily disable the 3D driver, e.g. with # echo "LIBGL_ALWAYS_SOFTWARE=1" >> /etc/environment (not sure if lightdm makes any use of it, just to rule that out) and try a 3.7 kernel from experimental? If the problem still persists, file an upstream bug on freedesktop bugzilla, see http://nouveau.freedesktop.org/wiki/Bugs for instructions. Cheers, Sven
Version: 1:1.0.11-1 xserver-xorg-video-nouveau 1:1.0.10-1+b2 and rebooted, but couldn't reproduce the bug either. However I had an external monitor connected to my laptop, and I'm not sure that the bug appears with it under some conditions. So, I disconnected the monitor, rebooted, and tried again, and the bug was reproducible with 1:1.0.10-1+b2. Then I upgraded to 1:1.0.11-1 again (only this package), and the bug was no longer reproducible: just after login, instead of the usual garbage (more precisely, parts of passed X sessions), the lightdm background image remained displayed until it was replaced by my desktop. So, I confirm that the upgrade of xserver-xorg-video-nouveau from 1:1.0.10-1+b2 to 1:1.0.11-1 alone solves the problem. As I has been the only one commenting this bug (and the merged one) since Feb 2013, I'm closing it.
I can still reproduce this, most reliable on cold-boot or reboot. This doesn't seem to have any effect. I'm now on 3.16-2 from unstable. It's still on my TODO list, but... Kind regards, Andrei
I had submitted one upstream (see forwarded) and didn't close it since I didn't have the confirmation of any fix. Note that I still couldn't reproduce the bug (on two machines), even after a reboot, but I haven't tried more than a few times (before 1:1.0.11-1, it was always reproducible, IIRC).
I had a look at the changes in 1.0.11, but could not really find an
explanation for this change. Maybe it's because the GLXVBlank option
is now enabled by default.
Cheers,
Sven