On 23/04/17 11:47, Julien Cristau wrote: > On Sat, Apr 22, 2017 at 13:00:08 +0200, Daniel Pocock wrote: > >> Package: libdrm2 >> Version: 2.4.74-1 >> Severity: important >> >> This problem was observed on a virtual machine running stretch inside a >> KVM environment. The machine had been a fresh install of stretch in >> January 2017, updated with apt in the last 24 hours. >> >> Last time I used my VM, I had stretched the virt-manager window to be >> quite large. spice-vdagent is running in the VM and the screen size >> adapted and it was working fine. My physical display is a 4k monitor. >> >> Next time I booted the VM, the gdm login didn't appear, just a dark gray >> background, it appeared to be sized at one of the default resolutions >> like 800x600. >> >> I connected to the VM with ssh and found this in journalctl: >> >> test-vm1 kernel: [drm:qxl_crtc_mode_set [qxl]] *ERROR* Mode doesn't fit >> in vram size (vgamem) >> test-vm1 kernel: [drm:drm_crtc_helper_set_config [drm_kms_helper]] >> *ERROR* failed to set mode on [CRTC:27:crtc-0] >> > This isn't a bug in libdrm2. It's a driver issue, either on the kernel > or userspace side.
Why close the bug then, shouldn't it be reopened and assigned to the kernel package? The reboot of the VM had been made after running "apt-get upgrade", leaving the impression the upgrade had broken the login screen. Looking at journalctl I felt that it wasn't caused by the upgrade, but for many users this would just leave a bad impression. Regards, Daniel
