This bug was fixed in the package gdm3 - 46.2-1ubuntu1~24.04.1
---------------
gdm3 (46.2-1ubuntu1~24.04.1) noble; urgency=medium
[ Marco Trevisan (Treviño) ]
* No-change backport of stable release 46.2 (LP: #2090876)
[ Jeremy Bícha ]
* Branch for noble
[ Alessandro Astone ]
* Default nvidia hybrid laptops to Xorg (LP: #2080498):
- Drop Revert-data-Disable-GDM-on-hybrid-graphics-laptops-with-v.patch
The hunks that are still relevant have been split into their own patches.
- Add Prefer-Xorg-for-all-Nvidia-versions.patch
This diff comes directly from the dropped patch.
- Add Drop-Nvidia-power-management-suspend-checks.patch
This diff comes directly from the dropped patch, and is still necessary
to keep Wayland as an option on nvidia >= 470 (both desktops and laptops).
- Add Drop-special-handling-of-nvidia-hybrid-laptops.patch
Align nvidia hybrid laptops with nvidia desktops: that means
disabling Wayland on nvidia < 470 and keeping it opt-in on nvidia >= 470.
Upstream also did this with GNOME 47, with the difference that there the
desktop defaults are different.
[ Nathan Pratta Teodosio ]
* Rewrite xresources_is_a_dir.patch.
To fix failure to load files in /etc/X11/Xresources (in case the latter is
a directory instead of a regular file). (LP: #1955850)
gdm3 (46.2-1ubuntu1) oracular; urgency=medium
* Merge with Debian, containing new upstream release. 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
- -dgdm-xsession=true 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
+ debian/tests/control:
- Use gdm user name
- Use needs-root instead of needs-sudo (to remove when ubuntu autopkgtest
will be updated to include such feature)
+ debian/tests/sssd-gdm-smartcard-pam-auth-tester-env.sh:
- Added to use needs-root autopkgtest instead of needs-sudo
+ gdm3.*.pam: make pam_env read ~/.pam_environment, as we use in g-c-c
settings
+ gdm3.install:
- 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 prefer_ubuntu_session_fallback.patch:
- Prefer ubuntu session as fallback instead of GNOME
+ add XSession-Use-x-terminal-emulator-as-fallback-instead-of-x.patch:
- Use x-terminal-emulator as fallback instead of xterm
+ add Revert-data-Disable-GDM-on-hybrid-graphics-laptops-with-v.patch:
- Ensure Nvidia 5xx drivers always get Wayland as the default unless
there's a stronger reason why it won't work (like modeset has been
disabled on the kernel command line)
+ 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
* Reverted debian patch to udev rules for nvidia S0ix suspend support
gdm3 (46.2-1) unstable; urgency=medium
[ Jeremy Bícha ]
* New upstream release
* Drop 2 patches applied in new release
[ Sebastian Andrzej Siewior ]
* Adapt autopkgtest for openssl3.2 (Closes: #1061458)
gdm3 (46.0-2ubuntu2) oracular; urgency=medium
* Remove the Ubuntu-specific rules that made Xorg the default for Nvidia.
Updated Revert-data-Disable-GDM-on-hybrid-graphics-laptops-with-v.patch
to ensure Nvidia 5xx drivers always get Wayland as the default unless
there's a stronger reason why it won't work (like modeset has been
disabled on the kernel command line).
Also refresh the patch description with a more recent justification.
(LP: #2080498)
-- Marco Trevisan (Treviño) <[email protected]> Mon, 02 Dec 2024
23:47:57 +0100
** Changed in: gdm3 (Ubuntu Noble)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/2080498
Title:
Default session type changed from Xorg to Wayland in some installs of
22.04 on Nvidia hybrids since kernel 6.8
Status in OEM Priority Project:
New
Status in gdm3 package in Ubuntu:
Fix Released
Status in gdm3 source package in Jammy:
New
Status in gdm3 source package in Noble:
Fix Released
Bug description:
[ Impact ]
On some nvidia hybrid systems, like the HP ZBook Fury G11 platform
preloaded with Ubuntu 22.04, the windowing system in "Settings ->
About" used to be Xorg but after doing kernel upgrade from 6.5-oem to
6.8-hwe, the windowing system become Wayland.
There is a race condition in udev rules that makes the default desktop
session either Xorg or Wayland depending on the ordering of hardware
discovery and modules loading. This would affect both jammy and noble,
but being a race condition it is unpredictable which hardware defaults
to which desktop session, and the same hardware may behave differently
in jammy vs in noble.
The intended default desktop session was meant to be Wayland, however
the vast majority of nvidia hybrid laptops defaulted to Xorg at
launch, including and particularly all Ubuntu Certified laptops. For
this reason we're considering this a bug and are taking measures to
ensure that all nvidia hybrid laptops keep defaulting to Xorg.
There is also at least onw known issues affecting nvidia hybrid laptops on
Wayland which might swing the preference towards Xorg:
* bug 2064205
The fix removes the udev logic that was trying to make nvidia hybrid
laptops specifically prefer Wayland, making that hardware use the same
udev rules as nvidia desktops which already default to Xorg.
[ Glossary ]
"nvidia" laptop/system/machine/etc...: A computer with at least one
nvidia GPU, running the proprietary driver version 470 or higher.
"affected" laptop/system/machine/etc...: An nvidia hybrid laptop that,
before installing the fix, on the log-in screen presents the options
to log-in to "Ubuntu" and "Ubuntu on Xorg".
"existing user": A unix user that has already logged-in to a desktop
session at least once, regardless of whether they ever changed the
log-in session or not.
"new user": A unix user that has never logged-in to a desktop session,
regardless of whether it was created before or after the update, or
whether it ever logged in to a TTY or not.
[ Test-plans overview ]
The expected behaviour after the update is that:
* for nvidia hybrid laptops affected by the bug: both existing and new users
will log-in to Xorg by default;
* for nvidia hybrid laptops unaffected by the bug: the default session for
new users is Xorg, but existing users will keep their previous preference;
* for nvidia desktops: the default session for new users is Xorg, but
existing users will keep their previous preference;
* for all non-nvidia systems: the default session for new users is Wayland,
but existing users will keep their previous preference;
Test Plan A and B verify that on a nvidia hybrid laptop both existing
users and new users log-in to Xorg by default after the update
Test plans C and D verify that on unaffected nvidia systems the user
preference about which session to log-in to is preserved the update.
Test plans E and F verify that on non-nvidia systems the user
preference about which session to log-in to is preserved after the
update.
Test plans *not* marked as "Regression" should only be verified on an
affected laptop.
[ Test Plan A ]
1. Get an affected nvidia hybrid laptop with Ubuntu 22.04 or 24.04
2. Before installing the update being tested, reboot to the log-in screen
3. Select your username
4. Click on the cogwheel icon at the bottom-right of the screen
5. Select "Ubuntu"
6. Log-in
7. Now install the gdm3 update being tested
8. Reboot
9. At the log-in screen, select your username
10. Verify that there is a cogwheel icon at the bottom-right of the screen
11. Click on the cogwheel icon to open up the menu
12. Verify that the selected option is "Ubuntu"
13. Verify that the alternative option is "Ubuntu on Wayland"
14. Close the menu without changing the selection ("Ubuntu")
15. Log-in
16. Verify via "Settings -> About" that "Windowing System" is X11
[ Test Plan B ]
1. Get an affected nvidia hybrid laptop with Ubuntu 22.04 or 24.04
2. Install the gdm3 update being tested
3. Create a new a new User on the system
4. Reboot
5. At the log-in screen, select the new User
6. Verify that there is a cogwheel icon at the bottom-right of the screen
7. Click on the cogwheel icon to open up the menu
8. Verify that the selected option is "Ubuntu"
9. Verify that the alternative option is "Ubuntu on Wayland"
10. Close the menu without changing the selection
11. Log-in
12. Verify via "Settings -> About" that "Windowing System" is X11
[ Test Plan C - Regression ]
1. Set up a desktop machine with a single nvidia GPU
2. Before installing the update being tested, reboot to the log-in screen
3. Select your username
4. Click on the cogwheel icon at the bottom-right of the screen
5. Select "Ubuntu on Wayland"
6. Log-in
7. Now install the gdm3 update being tested
8. Reboot
9. Select your username
10. Verify that there is a cogwheel icon at the bottom-right of the screen
11. Click on the cogwheel icon to open up the menu
12. Verify that the selected option is "Ubuntu on Wayland"
13. Close the menu without changing the selection
14. Log-in
15. Verify via "Settings -> About" that "Windowing System" is Wayland
[ Test Plan D - Regression ]
1. Set up a desktop machine with a single nvidia GPU
2. Before installing the update being tested, reboot to the log-in screen
3. Select your username
4. Click on the cogwheel icon at the bottom-right of the screen
5. Verify that the available options include "Ubuntu" and "Ubuntu on Wayland"
6. Select "Ubuntu"
7. Log-in
8. Now install the gdm3 update being tested
9. Reboot
10. Select your username
11. Verify that there is a cogwheel icon at the bottom-right of the screen
12. Click on the cogwheel icon to open up the menu
13. Verify that the selected option is "Ubuntu"
14. Verify that the alternative option is "Ubuntu on Wayland"
15. Close the menu without changing the selection
16. Log-in
17. Verify via "Settings -> About" that "Windowing System" is X11
[ Test plan E - Regression ]
1. Set up an Ubuntu system *without* any nvidia GPUs
2. Before installing the update being tested, reboot to the log-in screen
3. Select your username
4. Click on the cogwheel icon at the bottom-right of the screen
5. Verify that the available options include "Ubuntu" and "Ubuntu on Xorg"
6. Select "Ubuntu"
7. Log-in
8. Now install the gdm3 update being tested
9. Reboot
10. Select your username
11. Verify that there is a cogwheel icon at the bottom-right of the screen
12. Click on the cogwheel icon to open up the menu
13. Verify that the selected option is "Ubuntu"
14. Verify that the alternative option is "Ubuntu on Xorg"
15. Close the menu without changing the selection
16. Log-in
17. Verify via "Settings -> About" that "Windowing System" is Wayland
[ Test plan F - Regression ]
1. Set up an Ubuntu system *without* any nvidia GPUs
2. Before installing the update being tested, reboot to the log-in screen
3. Select your username
4. Click on the cogwheel icon at the bottom-right of the screen
5. Verify that the available options include "Ubuntu" and "Ubuntu on Xorg"
6. Select "Ubuntu on Xorg"
7. Log-in
8. Now install the gdm3 update being tested
9. Reboot
10. Select your username
10. Verify that there is a cogwheel icon at the bottom-right of the screen
11. Click on the cogwheel icon to open up the menu
12. Verify that the selected option is "Ubuntu on Xorg"
13. Verify that the alternative option is "Ubuntu"
14. Close the menu without changing the selection
15. Log-in
16. Verify via "Settings -> About" that "Windowing System" is X11
[ Where problems could occur ]
The patch only touches the gdm udev rules, only removing some broken udev
rules that matched specific hardware configurations.
At worst, Wayland on nvidia laptops could end up completely hidden away
rather than opt-in. This is controlled by checking the version of the nvidia
driver: versions 470 or higher should offer opt-in Wayland, while versions
lower than 470 should not offer Wayland at all.
There should be no regression potential for nvidia desktops or non-
nvidia hardware, because such hardware would not have matched the udev
rules that are being removed here.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2080498/+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
