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 to integer parameter out of range
for operation
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
934660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934660
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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-4.19.0-5-amd64 works great.
This happend in my desktop and also my notebook.
Both uses nvidia driver (and not nouveau).
nvidia-driver/unstable,now 418.74-1 amd64 [installed]
Please, let me know if I should report this to the kernel
package instead.
* What was the outcome of this action?
When I boot with kernel linux-image-5.2.0-2-amd64, I get the screen:
"Oh no! Something has gone wrong.
A problem has occurred and the system can't recover.
Please log out and try again."
And clicking in the logout button leads to a tty console (that
doesn't really work, I had to hit Alt+F3 to get a console).
When I look at journalctl I see these:
Aug 12 22:34:45 livingroom /usr/lib/gdm3/gdm-x-session[911]: X Error of failed
request: BadValue (integer parameter out of range for operation)
Aug 12 22:34:45 livingroom /usr/lib/gdm3/gdm-x-session[911]: Major opcode of
failed request: 151 (GLX)
Aug 12 22:34:45 livingroom /usr/lib/gdm3/gdm-x-session[911]: Minor opcode of
failed request: 3 (X_GLXCreateContext)
Aug 12 22:34:45 livingroom /usr/lib/gdm3/gdm-x-session[911]: Value in failed
request: 0x0
Aug 12 22:34:45 livingroom /usr/lib/gdm3/gdm-x-session[911]: Serial number of
failed request: 19
Aug 12 22:34:45 livingroom /usr/lib/gdm3/gdm-x-session[911]: Current serial
number in output stream: 20
Aug 12 22:34:45 livingroom /usr/lib/gdm3/gdm-x-session[911]:
gnome-session-check-accelerated: GL Helper exited with code 256
Aug 12 22:34:45 livingroom gnome-session-c[1248]: eglGetDisplay() failed
Aug 12 22:34:45 livingroom /usr/lib/gdm3/gdm-x-session[911]:
gnome-session-check-accelerated: GLES Helper exited with code 256
Aug 12 22:34:45 livingroom /usr/lib/gdm3/gdm-x-session[911]:
gnome-session-binary[1228]: WARNING: software acceleration check failed: Child
process exited with code 1
Aug 12 22:34:45 livingroom /usr/lib/gdm3/gdm-x-session[911]:
gnome-session-binary[1228]: GLib-DEBUG(+): posix_spawn avoided (fd close
requested)
Aug 12 22:34:45 livingroom gnome-session-binary[1228]: WARNING: software
acceleration check failed: Child process exited with code 1
Aug 12 22:34:45 livingroom gnome-session-binary[1228]: GLib-DEBUG(+):
posix_spawn avoided (fd close requested)
The full log is available at http://ix.io/1Rts
* What outcome did you expect instead?
I expected the gdm login GUI screen and not the "Oh no" screen after booting.
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages gdm3 depends on:
ii accountsservice 0.6.45-2
ii adduser 3.118
ii dconf-cli 0.30.1-2
ii dconf-gsettings-backend 0.30.1-2
ii debconf [debconf-2.0] 1.5.73
ii gir1.2-gdm-1.0 3.30.2-3
ii gnome-session [x-session-manager] 3.30.1-2
ii gnome-session-bin 3.30.1-2
ii gnome-settings-daemon 3.30.2-3
ii gnome-shell 3.30.2-10
ii gnome-terminal [x-terminal-emulator] 3.30.2-2
ii gsettings-desktop-schemas 3.28.1-1
ii libaccountsservice0 0.6.45-2
ii libaudit1 1:2.8.5-2
ii libc6 2.28-10
ii libcanberra-gtk3-0 0.30-7
ii libcanberra0 0.30-7
ii libgdk-pixbuf2.0-0 2.38.1+dfsg-1
ii libgdm1 3.30.2-3
ii libglib2.0-0 2.60.6-1
ii libglib2.0-bin 2.60.6-1
ii libgtk-3-0 3.24.10-1
ii libkeyutils1 1.6-6
ii libpam-modules 1.3.1-5
ii libpam-runtime 1.3.1-5
ii libpam-systemd 241-7
ii libpam0g 1.3.1-5
ii librsvg2-common 2.44.14-1
ii libselinux1 2.9-2+b2
ii libsystemd0 241-7
ii libwrap0 7.6.q-28
ii libx11-6 2:1.6.7-1
ii libxau6 1:1.0.8-1+b2
ii libxcb1 1.13.1-2
ii libxdmcp6 1:1.1.2-3
ii lsb-base 10.2019051400
ii mutter [x-window-manager] 3.30.2-8
ii policykit-1 0.105-26
ii procps 2:3.3.15-2
ii ucf 3.0038+nmu1
ii x11-common 1:7.7+19
ii x11-xserver-utils 7.7+8
Versions of packages gdm3 recommends:
ii at-spi2-core 2.32.1-1
ii desktop-base 10.0.3
ii x11-xkb-utils 7.7+4
ii xserver-xephyr 2:1.20.4-1
ii xserver-xorg 1:7.7+19
ii zenity 3.30.0-2
Versions of packages gdm3 suggests:
ii gnome-orca 3.32.0-1
pn libpam-fprintd <none>
ii libpam-gnome-keyring 3.28.2-5
-- Configuration Files:
/etc/gdm3/daemon.conf changed:
[daemon]
[security]
[xdmcp]
[chooser]
[debug]
Enable=true
-- debconf information:
gdm3/daemon_name: /usr/sbin/gdm3
* shared/default-x-display-manager: gdm3
--- End Message ---
--- Begin Message ---
On Mon, 12 Aug 2019 at 23:32:39 -0300, Pedro Terra Delboni wrote:
> modprobe: FATAL: Module nvidia-current-modeset not found in directory
> /lib/modules/5.2.0-2-amd64
This probably indicates that the non-free NVIDIA driver module couldn't be
compiled successfully for the newer kernel. Unfortunately, this will
sometimes happen if you are relying on out-of-tree modules for your
graphics driver.
> 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?
The NVIDIA driver is probably better. Normally I'd reassign this bug, but
I don't think the maintainers of the NVIDIA driver will be able to do
anything particularly useful with the gdm-centric information you've
provided so far - hopefully when you re-run reportbug specifying the
NVIDIA driver, it will gather more information about the status of the
driver.
smcv
--- End Message ---
