JS ERROR: Exception in callback for signal: login-format-changed: Error: Wrong type number; string expected
Affected version
- gnome-shell-40.9-1.fc34.x86_64
- Fedora 34 x86_64
- running in XOrg (in /etc/gdm/custom.conf: WaylandEnable=False; DefaultSession=gnome-xorg.desktop)
- NVIDIA's drivers: nvidia-driver-510.73.05-1.fc34.x86_64
- I am using Samba Winbind with a Windows Active Directory Domain. My account is an A/D account. I also have winbindd caching on. This has been working this year (and on Fedora 34), but I don't know exactly when it stopped working because I usually use this computer remotely.
Bug summary
gnome-shell crashes on boot-up. I am presented with a black, blank screen. To recover, I must get to a TTY via Ctrl+Alt+F2. I login in. I then "sudo init 3", I then run "sudo init 5". At this point, I am presented with what I expect: a gnome-shell login screen.
Steps to reproduce
- boot up
What happened
after bootup, gnome-shell flashes very fast and then a black, blank screen (monitor is on/active). gnome-shell crashes with no recourse in X/graphics mode. I have get a TTY, then do the init 3 and init 5 to get gnome-shell back.
What did you expect to happen
I expect to be able to login.
Relevant logs, screenshots, screencasts etc.
Jun 03 14:42:14 8ball.decisiv.net gnome-shell[1485]: JS ERROR: Exception in callback for signal: login-format-changed: Error: Wrong type number; string expected
setMessage@resource:///org/gnome/shell/gdm/authPrompt.js:474:13
_showRealmLoginHint@resource:///org/gnome/shell/gdm/loginDialog.js:921:26
_emit@resource:///org/gnome/gjs/modules/core/_signals.js:114:47
_updateLoginFormat@resource:///org/gnome/shell/gdm/realmd.js:85:18
_reloadRealm@resource:///org/gnome/shell/gdm/realmd.js:57:14
_onRealmLoaded@resource:///org/gnome/shell/gdm/realmd.js:64:14
_makeProxyWrapper/</<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:245:34
Edited by Allen Hewes