This bug was fixed in the package gdm3 - 3.33.90-1ubuntu1
---------------
gdm3 (3.33.90-1ubuntu1) eoan; urgency=medium
* Merge with Debian. Remaining changes:
+ README.Debian: update for correct paths in Ubuntu
+ control.in:
- Don't recommend desktop-base
- Depend on bash for config_error_dialog.patch
- Update Vcs field
+ rules:
- Don't override default user/group
- --enable-gdm-xsession to install upstream Xsession script
- override dh_installinit with --no-start to avoid session being killed
+ rules, README.Debian, gdm3.8.pod:
Use upstream custom.conf instead of daemon.conf
+ gdm3.{postinst,postrm}: rename user and group back to gdm
+ gdm3.postinst, gdm3.prerm: don't kill gdm on upgrade
+ gdm3.*.pam: Make pam_env read ~/.pam_environment
+ gdm3.install:
- Stop installing default.desktop. It adds unnecessary clutter
("System Default") to the session chooser.
- Don't install debian/Xsession
+ Add run_xsession.d.patch
+ Add xresources_is_a_dir.patch
- Fix loading from /etc/X11/Xresources/*
+ Add nvidia_prime.patch:
- Add hook to run prime-offload (as root) and prime-switch if
nvidia-prime is installed
+ Add revert_override_LANG_with_accountservices.patch:
- On Ubuntu accountservices only stores the language and not the
full locale as needed by LANG.
+ Add dont_set_language_env.patch:
- Don't run the set_up_session_language() function, since it
overrides variable values set by ~/.pam_environment
+ Add config_error_dialog.patch:
- Show warning dialog in case of error in ~/.profile etc. and
don't let a syntax error make the login fail
+ Add debian/patches/revert_nvidia_wayland_blacklist.patch:
- Don't blacklist nvidia for wayland
+ Add gdm3.service-wait-for-drm-device-before-trying-to-start-i.patch:
- Wait for the first valid gdm device on pre-start
+ Add debian/default.pa
- Disable Bluetooth audio devices in PulseAudio from gdm3.
+ debian/gdm3.install
- Added details of the default.pa file
+ debian/gdm3.postinst
- Added installation of default.pa and creation of dir if it doesn't
exist.
+ debian/greeter.dconf-defaults: Don't set Debian settings in the
greeter's dconf DB
* Should fix Wayland to Xorg fallback on slow machines (LP: #1798790)
-- Iain Lane <[email protected]> Thu, 15 Aug 2019 18:06:24 +0100
** Changed in: gdm3 (Ubuntu Eoan)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1798790
Title:
Ubuntu login screen sometimes doesn't appear on a single GPU Nvidia
system (and setting WaylandEnable=false fixes it)
Status in gdm:
Fix Released
Status in gdm3 package in Ubuntu:
Fix Released
Status in gnome-session package in Ubuntu:
In Progress
Status in gnome-shell package in Ubuntu:
In Progress
Status in mutter package in Ubuntu:
Invalid
Status in gdm3 source package in Eoan:
Fix Released
Status in gnome-session source package in Eoan:
In Progress
Status in gnome-shell source package in Eoan:
In Progress
Status in mutter source package in Eoan:
Invalid
Bug description:
https://gitlab.gnome.org/GNOME/gdm/issues/483
formerly https://gitlab.gnome.org/GNOME/gdm/issues/435
---
The boot process hangs with the last message being "started bpfilter".
There is unusual Network activity during that time. The light of the
WiFi adapter is blinking a lot.
I am not sure the problem is with the gdm3 package. As a matter of
fact, I would remove it and let someone more experienced to set it.
I'm afraid I might break something, though.
The specific steps or actions you took that caused you to encounter the
problem: 1. Boot Ubuntu 18.10 with the Nvidia proprietary drivers
installed.
The behavior you expected: I expected Ubuntu 18.10 to boot normally.
The behavior you actually encountered: The computer gets stuck in a
command-like environment with the last message being "started
bpfilter". You can't type any commands.
I have found that uninstalling the Nvidia proprietary drivers by going
into recovery mode fixes the issue.
Booting with the earlier kernel doesn't fix the issue. Installing the
earlier v.340 driver also doesn't fix the issue.
This (https://askubuntu.com/questions/1032639/ubuntu-18-04-stuck-in-
boot-after-starting-gnome-display-manager-on-intel-graphic) seems
relevant. This is where I found the "solution".
To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1798790/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
