Further diagnostics show that although my environment variable XDG_SESSION_TYPE reports x11, loginctl show-session reports Type=wayland, indicating my session is actually running on Wayland. The clipboard tool wl-copy works, further proving that Wayland is active. This suggests the real problem is environment inconsistency or misreporting of session type, not failure to offer or start Wayland sessions.
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2115722 Title: Wayland sessions missing in GDM on Ubuntu 24.04.2 despite supported Intel hardware Status in gnome-shell package in Ubuntu: New Bug description: On my Dell Latitude laptop with Intel Iris Xe (Raptor Lake-P) graphics, running Ubuntu 24.04.2 LTS with GNOME 46, GDM does not offer Wayland sessions at login, even though: /etc/gdm3/custom.conf has #WaylandEnable=false (i.e., Wayland is enabled) Wayland session files exist: /usr/share/wayland-sessions/gnome- wayland.desktop and /usr/share/wayland-sessions/ubuntu-wayland.desktop Kernel modesetting is active with Intel’s i915 driver No NVIDIA or hybrid GPU present Kernel command line has no nomodeset or other blocking flags My hardware supports Wayland fully Attempting to select GNOME or Ubuntu sessions at GDM only starts X11 sessions; no explicit “on Wayland” option appears Steps to reproduce: Install Ubuntu 24.04.2 LTS on Intel-only laptop with i915 driver (e.g., Dell Latitude with Iris Xe graphics) Boot into GDM login screen Click user → open gear menu Observe that “Ubuntu on Wayland” or “GNOME on Wayland” are missing Logging in starts X11 session every time Expected result: GDM offers “Ubuntu on Wayland” and/or “GNOME” options that start a Wayland session. Actual result: No Wayland session options appear. GNOME only starts in X11. Environment details: Distro: Ubuntu 24.04.2 LTS Kernel: Linux 6.8.0-62-generic GNOME: GNOME Shell 46.0, GDM 46.2 Graphics: Intel Iris Xe (Raptor Lake-P), driver i915 Kernel command line: ini Copy Edit BOOT_IMAGE=/boot/vmlinuz-6.8.0-62-generic root=UUID=0ef1034c-27b6-4c84-afa1-00f402038d91 ro quiet splash vt.handoff=7 DRM status: DRM devices report connected outputs Security modules: AppArmor active; SELinux not installed Wayland session files exist: swift Copy Edit /usr/share/wayland-sessions/gnome.desktop /usr/share/wayland-sessions/gnome-wayland.desktop /usr/share/wayland-sessions/ubuntu.desktop /usr/share/wayland-sessions/ubuntu-wayland.desktop What I’ve tried: ✅ Verified kernel command line → no nomodeset or GPU blacklist ✅ Verified /etc/gdm3/custom.conf → Wayland enabled ✅ Verified kernel DRM → modesetting active ✅ Verified GDM logs → no fallback or Wayland errors appear ✅ Verified GNOME/GDM versions are recent ✅ Verified no NVIDIA GPU present Impact: Cannot run GNOME on Wayland despite compatible hardware, affecting security and performance benefits. Attachments: Can provide journalctl -b -u gdm output and other logs upon request. I previously used Wayland successfully on this system (evidenced by a clipboard function relying on wl-copy), but after recent updates or GUI crashes, Wayland options disappeared from GDM and I cannot start a Wayland session anymore. clip function: clip() { local cmd_output cmd_output="$("$@" 2>&1)" || return 1 { echo "$*" echo "--------------------" echo "$cmd_output" } | tee >(wl-copy >/dev/null) } weedom at weedom-Latitude-5340 in ~ $ dmesg | grep -iE 'drm|i915|gpu|error' dmesg: read kernel buffer failed: Operation not permitted weedom at weedom-Latitude-5340 in ~ $ sudo dmesg | grep -iE 'drm|i915|gpu|error' [ 0.223584] ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.TXHC.RHUB.SS01._DSM], AE_ALREADY_EXISTS (20230628/dswload2-326) [ 0.223601] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220) [ 0.223612] ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.TXHC.RHUB.SS02._DSM], AE_ALREADY_EXISTS (20230628/dswload2-326) [ 0.223615] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220) [ 1.144831] ACPI: bus type drm_connector registered [ 1.156702] [drm] Initialized simpledrm 1.0.0 20200625 for simple-framebuffer.0 on minor 0 [ 1.157743] simple-framebuffer simple-framebuffer.0: [drm] fb0: simpledrmdrmfb frame buffer device [ 1.205970] RAS: Correctable Errors collector initialized. [ 5.593389] systemd[1]: Starting [email protected] - Load Kernel Module drm... [ 5.600866] systemd[1]: [email protected]: Deactivated successfully. [ 5.601117] systemd[1]: Finished [email protected] - Load Kernel Module drm. [ 5.912957] EDAC igen6 MC1: HANDLING IBECC MEMORY ERROR [ 5.912963] EDAC igen6 MC0: HANDLING IBECC MEMORY ERROR [ 6.379164] i915 0000:00:02.0: [drm] VT-d active for gfx access [ 6.386204] RAPL PMU: hw unit of domain pp1-gpu 2^-14 Joules [ 6.394584] i915 0000:00:02.0: vgaarb: deactivate vga console [ 6.394645] i915 0000:00:02.0: [drm] Using Transparent Hugepages [ 6.395141] i915 0000:00:02.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=io+mem:owns=io+mem [ 6.398506] i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/adlp_dmc.bin (v2.20) [ 6.416629] i915 0000:00:02.0: [drm] GT0: GuC firmware i915/adlp_guc_70.bin version 70.36.0 [ 6.416637] i915 0000:00:02.0: [drm] GT0: HuC firmware i915/tgl_huc.bin version 7.9.3 [ 6.433961] i915 0000:00:02.0: [drm] GT0: HuC: authenticated for all workloads [ 6.434425] i915 0000:00:02.0: [drm] GT0: GUC: submission enabled [ 6.434429] i915 0000:00:02.0: [drm] GT0: GUC: SLPC enabled [ 6.434834] i915 0000:00:02.0: [drm] GT0: GUC: RC enabled [ 6.435839] i915 0000:00:02.0: [drm] Protected Xe Path (PXP) protected content support initialized [ 7.558525] mei_pxp 0000:00:16.0-fbf6fcf1-96cf-4e2e-a6a6-1bab8cbe36b1: bound 0000:00:02.0 (ops i915_pxp_tee_component_ops [i915]) [ 7.559678] mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_ops [i915]) [ 7.727903] [drm] Initialized i915 1.6.0 20230929 for 0000:00:02.0 on minor 1 [ 7.790972] i915 display info: display version: 13 [ 7.790976] i915 display info: cursor_needs_physical: no [ 7.790977] i915 display info: has_cdclk_crawl: yes [ 7.790979] i915 display info: has_cdclk_squash: no [ 7.790980] i915 display info: has_ddi: yes [ 7.790981] i915 display info: has_dp_mst: yes [ 7.790982] i915 display info: has_dsb: yes [ 7.790983] i915 display info: has_fpga_dbg: yes [ 7.790984] i915 display info: has_gmch: no [ 7.790985] i915 display info: has_hotplug: yes [ 7.790986] i915 display info: has_hti: no [ 7.790987] i915 display info: has_ipc: yes [ 7.790988] i915 display info: has_overlay: no [ 7.790989] i915 display info: has_psr: yes [ 7.790990] i915 display info: has_psr_hw_tracking: no [ 7.790992] i915 display info: overlay_needs_physical: no [ 7.790993] i915 display info: supports_tv: no [ 7.790994] i915 display info: has_hdcp: yes [ 7.790995] i915 display info: has_dmc: yes [ 7.790996] i915 display info: has_dsc: yes [ 7.790997] i915 display info: rawclk rate: 19200 kHz [ 7.842278] fbcon: i915drmfb (fb0) is primary device [ 7.842285] i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device [ 7.842311] snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) [59151.880516] i915 0000:00:02.0: Using 39-bit DMA addresses weedom at weedom-Latitude-5340 in ~ and weedom at weedom-Latitude-5340 in ~ $ grep " upgrade " /var/log/apt/history.log weedom at weedom-Latitude-5340 in ~ $ # dmidecode 3.5 Getting SMBIOS data from sysfs. SMBIOS 3.6 present. # SMBIOS implementations newer than version 3.5.0 are not # fully supported by this version of dmidecode. Handle 0x0000, DMI type 0, 26 bytes BIOS Information Vendor: Dell Inc. Version: 1.21.0 Release Date: 02/26/2025 ROM Size: 32 MB Characteristics: PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported EDD is supported Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported Smart battery is supported BIOS boot specification is supported Function key-initiated network boot is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 1.21 Firmware Revision: 1.22 Handle 0x0D00, DMI type 13, 22 bytes BIOS Language Information Language Description Format: Abbreviated Installable Languages: 1 enUS Currently Installed Language: enUS weedom at weedom-Latitude-5340 in ~ $ Dell Inc. Latitude 5340 │ ├─13th Gen Intel Core™ i7-1365U: │ Device ID: 4bde70ba4e39b28f9eab1628f9dd6e6244c03027 │ Current version: 0x00004128 │ Vendor: Intel │ GUIDs: c3f97ae6-7da2-54cc-ad26-3225f9517203 ← CPUID\PRO_0&FAM_06&MOD_BA │ cd7d026a-65a8-597d-a73f-b856af9dc9e2 ← CPUID\PRO_0&FAM_06&MOD_BA&STP_3 │ Device Flags: • Internal device │ ├─Integrated Webcam FHD: │ Device ID: 65a54fb6ce182f0e75edf0e43047d547a0d61f0e │ Current version: 24.41 │ Vendor: CN089MTT8LG0035VD697A00 (USB:0x0C45) │ Serial Number: SN0001 │ GUID: 84db5bd4-2fe2-5637-b738-1b44c3cb69ea ← USB\VID_0C45&PID_674C │ Device Flags: • Updatable │ ├─Internal SPI Controller: │ Device ID: a41715edae830e26b4c4a9246ffa62cddf8f7338 │ Summary: Memory Technology Device │ Vendor: DMI:Dell Inc. │ GUIDs: 5f93d7e7-e282-59b9-b663-0146e382f8f6 ← MTD\NAME_0000:00:1f.5 │ b858f197-3e26-5077-a45c-69bb2ddd6a9e ← MTD\VENDOR_Dell-Inc.&NAME_0000:00:1f.5 │ e9f5385c-63b4-5388-a4d5-256832337963 ← MTD\VENDOR_Dell-Inc.&PRODUCT_Latitude-5340&NAME_0000:00:1f.5 │ Device Flags: • Internal device │ • Updatable │ • Needs a reboot after installation │ • Cryptographic hash verification is available │ ├─KBG50ZNS512G NVMe KIOXIA 512GB: │ Device ID: c430a03ca2a65dfe2412ff950c79c51f6aec1317 │ Summary: NVM Express solid state drive │ Current version: 11200109 │ Vendor: KIOXIA Corporation (NVME:0x1E0F) │ Serial Number: 23RC73TCEWDX │ GUIDs: 22755fde-6467-597f-a58d-5bc06fd62b36 ← STORAGE-DELL-111195 │ aac4a8cc-a312-11eb-bcbc-0242ac130002 │ Device Flags: • Updatable │ • System requires external power source │ • Supported on remote server │ • Needs a reboot after installation │ • Signed Payload │ ├─Raptor Lake-P [Iris Xe Graphics]: │ Device ID: 5792b48846ce271fab11c4a545f7a3df0d36e00a │ Current version: 04 │ Vendor: Intel Corporation (PCI:0x8086) │ GUIDs: 7114c807-404e-558e-89a4-120d80d7cbdb ← PCI\VEN_8086&DEV_A7A1 │ 78bc9fba-c752-5012-bb04-aa50a0c30e58 ← PCI\VEN_8086&DEV_A7A1&SUBSYS_10280C03 │ Device Flags: • Internal device │ • Cryptographic hash verification is available │ ├─System Firmware: │ │ Device ID: 623b053a48da9408f3abd3cd8e5278b5d8442d74 │ │ Summary: UEFI System Resource Table device (updated via NVRAM) │ │ Current version: 1.21.0 │ │ Minimum Version: 1.21.0 │ │ Vendor: Dell (DMI:Dell Inc.) │ │ Update State: Success │ │ GUID: f83d49a0-36d0-4cbd-a573-dcda2685800b │ │ Device Flags: • Internal device │ │ • Updatable │ │ • System requires external power source │ │ • Supported on remote server │ │ • Needs a reboot after installation │ │ • Cryptographic hash verification is available │ │ • Device is usable for the duration of the update │ │ Device Requests: • Message │ │ │ ├─AMT [unprovisioned]: │ │ Device ID: 8d5470e73fd9a31eaa460b2b6aea95483fe3f14c │ │ Summary: Hardware and firmware technology for remote out-of-band management │ │ Current version: 16.1.35.2557 │ │ Bootloader Version:16.1.35.2557 │ │ Vendor: Intel Corporation (MEI:0x8086) │ │ GUIDs: 12f80028-b4b7-4b2d-aca8-46e0ff65814c │ │ fccad2fe-62ae-5879-b7a9-4ead7bce50f4 ← MEI\VEN_8086&DEV_51E0 │ │ f88579c3-2e33-5465-ad58-82851a7c966d ← MEI\VEN_8086&DEV_51E0&SUBSYS_10280C03 │ │ Device Flags: • Internal device │ │ │ ├─BootGuard Configuration: │ │ Device ID: b0d4430dfa6bde9f0c22680df36dbc8c15c80753 │ │ Current version: 01 │ │ Vendor: Intel Corporation (MEI:0x8086) │ │ GUIDs: dd17041c-09ea-4b17-a271-5b989867ec65 │ │ fccad2fe-62ae-5879-b7a9-4ead7bce50f4 ← MEI\VEN_8086&DEV_51E0 │ │ f88579c3-2e33-5465-ad58-82851a7c966d ← MEI\VEN_8086&DEV_51E0&SUBSYS_10280C03 │ │ Device Flags: • Internal device │ │ │ └─UEFI dbx: │ Device ID: 362301da643102b9f38477387e2193e57abaa590 │ Summary: UEFI revocation database 6b4328eb │ Vendor: UEFI:Microsoft │ Install Duration: 1 second │ GUIDs: 4a6cd2cb-8741-5257-9d1f-89a275dacca7 ← UEFI\CRT_E28D59CA489BD2AD580F2EA5D62D6A29BB9C02AE5A818434A37DA7FC11DFF9E9&ARCH_X64 │ f8ba2887-9411-5c36-9cee-88995bb39731 ← UEFI\CRT_A1117F516A32CEFCBA3F2D1ACE10A87972FD6BBE8FE0D0B996E09E65D802A503&ARCH_X64 │ Device Flags: • Internal device │ • Updatable │ • Needs a reboot after installation │ • Device is usable for the duration of the update │ • Only version upgrades are allowed │ • Signed Payload │ ├─TPM: │ Device ID: c6a80ac3a22083423992a3cb15018989f37834d6 │ Current version: 1.258.0.0 │ Vendor: ST Microelectronics (TPM:STM) │ GUIDs: 84df3581-f896-54d2-bd1a-372602f04c32 ← TPM\VEN_STM&DEV_0001 │ bfaed10a-bbc1-525b-a329-35da2f63e918 ← TPM\VEN_STM&MOD_ │ 70b7b833-7e1a-550a-a291-b94a12d0f319 ← TPM\VEN_STM&DEV_0001&VER_2.0 │ 06f005e9-cb62-5d1a-82d9-13c534c53c48 ← TPM\VEN_STM&MOD_&VER_2.0 │ 69ad4ade-f050-5659-ab3e-8dcf987bf7d8 ← 0c03-2.0 │ Device Flags: • Internal device │ • Updatable │ • System requires external power source │ • Needs a reboot after installation │ • Device can recover flash failures │ • Full disk encryption secrets may be invalidated when updating │ • Signed Payload │ ├─UEFI Device Firmware: │ Device ID: 694ed746ce6dd1a450f0849944a2ac8d5e6c2c61 │ Summary: UEFI System Resource Table device (updated via NVRAM) │ Current version: 16675 │ Minimum Version: 16675 │ Vendor: DMI:Dell Inc. │ Update State: Success │ GUID: e72475a2-b8f0-4217-bbea-3304b187ae54 │ Device Flags: • Internal device │ • Updatable │ • System requires external power source │ • Needs a reboot after installation │ • Device is usable for the duration of the update │ Device Requests: • Message │ ├─UEFI Device Firmware: │ Device ID: d357520c99a2564819b8b609d0f44cb6561b85d1 │ Summary: UEFI System Resource Table device (updated via NVRAM) │ Current version: 287310089 │ Minimum Version: 287310089 │ Vendor: DMI:Dell Inc. │ Update State: Success │ GUID: aac4a8cc-a312-11eb-bcbc-0242ac130002 │ Device Flags: • Internal device │ • Updatable │ • System requires external power source │ • Needs a reboot after installation │ • Device is usable for the duration of the update │ Device Requests: • Message │ ──────────────────────────────────────────────── Devices that have been updated successfully: • System Firmware (1.19.2 → 1.21.0) • System Firmware (1.16.0 → 1.17.0) Uploading firmware reports helps hardware vendors to quickly identify failing and successful updates on real devices. Review and upload report now? (Requires internet connection) [Y|n]: n Do you want to disable this feature for future updates? [y|N]: N Declined upload weedom at weedom-Latitude-5340 in ~ $ ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell 46.0-0ubuntu6~24.04.9 ProcVersionSignature: Ubuntu 6.8.0-62.65-generic 6.8.12 Uname: Linux 6.8.0-62-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.7 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jul 1 10:58:05 2025 DisplayManager: gdm3 InstallationDate: Installed on 2023-09-19 (651 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) RelatedPackageVersions: mutter-common 46.2-1ubuntu0.24.04.8 SourcePackage: gnome-shell UpgradeStatus: Upgraded to noble on 2025-01-21 (161 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2115722/+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
