Bug#934660:

Hi On 2019-08-12 23:32:39, Pedro Terra Delboni wrote: > Hi, > > I just saw in the logs: > > modprobe: FATAL: Module nvidia-current-modeset not found in directory > /lib/modules/5.2.0-2-amd64 > > Sorry for the noise, doesn't look a gdm bug after all, just a missing module. > Should I report this

Bug#934660: marked as done (gdm3: "System can't recover" due to integer parameter out of range for operation)

Your message dated Tue, 13 Aug 2019 08:16:34 +0100 with message-id <20190813071634.ga29...@espresso.pseudorandom.co.uk> and subject line Re: Bug#934660: Module nvidia-current-modeset not found has caused the Debian Bug report #934660, regarding gdm3: "System can't recover" due

Bug#934660:

Hi, I just saw in the logs: modprobe: FATAL: Module nvidia-current-modeset not found in directory /lib/modules/5.2.0-2-amd64 Sorry for the noise, doesn't look a gdm bug after all, just a missing module. Should I report this against the kernel package or the nvidia driver? Thanks Pedro

Bug#934660: gdm3: "System can't recover" due to integer parameter out of range for operation

Package: gdm3 Version: 3.30.2-3 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? Booting with kernel linux-image-5.2.0-2-amd64 * What exactly did you do (or not do) that was effective (or ineffective)? Booting with linux-image-