After 24.04 upgrade, many graphical app failures under Wayland; no issues with Xorg

Bug #2061257 reported by Martin D. Weinberg
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Ubuntu
Fix Released
Undecided
Unassigned

Bug Description

Many applications seem to fail under a Wayland session that work correctly with an Xorg session. E.g.
- The nextcloud client app fails to contact the server and functions in the app will not launch with Wayland while they work perfectly in Xorg
- The Vivaldi browser exits with: MESA-INTEL: warning: Haswell Vulkan support is incomplete
libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed. It works correctly under Xorg.
- The Slack app works correct in Xorg not in Wayland.
- The Firefox snap works fine in both.

I assume that these are related? Esp. that latter suggests to me that there is some library problem?

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 13 19:58:00 2024
DistUpgraded: 2024-04-13 16:25:15,367 DEBUG migrateToDeb822Sources()
DistroCodename: noble
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
InstallationDate: Installed on 2021-11-11 (885 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: LENOVO 20ARA0S100
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-22-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to noble on 2024-04-13 (0 days ago)
dmi.bios.date: 03/19/2014
dmi.bios.release: 2.24
dmi.bios.vendor: LENOVO
dmi.bios.version: GJET74WW (2.24 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20ARA0S100
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.ec.firmware.release: 1.9
dmi.modalias: dmi:bvnLENOVO:bvrGJET74WW(2.24):bd03/19/2014:br2.24:efr1.9:svnLENOVO:pn20ARA0S100:pvrThinkPadT440s:rvnLENOVO:rn20ARA0S100:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AR_BU_Think_FM_ThinkPadT440s:
dmi.product.family: ThinkPad T440s
dmi.product.name: 20ARA0S100
dmi.product.sku: LENOVO_MT_20AR_BU_Think_FM_ThinkPad T440s
dmi.product.version: ThinkPad T440s
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.120-2
version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.3-1ubuntu4
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

Revision history for this message
Martin D. Weinberg (martin-weinberg-5) wrote :
Revision history for this message
Martin D. Weinberg (martin-weinberg-5) wrote :

I should also mention: this was an upgrade from 23.10 to 24.04 and all of the apps worked correctly in 23.10.

summary: - Many app failures under Wayland; no issues with Xorg
+ With 24.04: Many graphical app failures under Wayland; no issues with
+ Xorg
summary: - With 24.04: Many graphical app failures under Wayland; no issues with
- Xorg
+ After 24.04 upgrade, many graphical app failures under Wayland; no
+ issues with Xorg
Revision history for this message
Martin D. Weinberg (martin-weinberg-5) wrote :

I tried the same upgrade and test on an old Sandy Bridge laptop. Everything works as expected there. So a Haswell issue perhaps?

affects: xorg (Ubuntu) → wayland
affects: wayland → wayland (Ubuntu)
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in wayland (Ubuntu):
status: New → Confirmed
Revision history for this message
MichaelB (mrbou) wrote :

Same here.. I upgraded from 22.04 (upgrade failed but i managed to install missing packages with dpkg --configure -a, apt install -f, apt upgrade.. but it's not our issue in this thread)

When we click on nautilus icon, nothing happen (on wayland)

michael@michael-ubuntu:~$ nautilus
** Message: 22:29:35.550: Connecting to org.freedesktop.Tracker3.Miner.Files
libEGL warning: egl: failed to create dri2 screen
MESA-INTEL: warning: Haswell Vulkan support is incomplete
Erreur de segmentation

If i close the session and start with xorg it's fine, nautilus opened.

michael@michael-ubuntu:~$ nautilus
** Message: 22:29:35.550: Connecting to org.freedesktop.Tracker3.Miner.Files

This happen with some other applications as gnome-control-center by example.

Revision history for this message
Martin D. Weinberg (martin-weinberg-5) wrote :

Thanks. Sounds similar. My nautilus and gnome-control center do work strangely enough. But the more clues the better.

Revision history for this message
Martin D. Weinberg (martin-weinberg-5) wrote :

I also tried removing the Mesa Vulkan driver and set `export LIBVA_DRIVER_NAME=i965`. That gets rid of the warning message but I still get a hang with Vivaldi and nextcloud-desktop still does not work.

Revision history for this message
Daniel van Vugt (vanvugt) wrote (last edit ):

Thanks for the bug report. I suppose it's possible all these issues are related, but we shouldn't assume they are so quickly...

The Vulkan error message is being tracked in bug 2038313. As for Nextcloud, Vivaldi and Slack, they are all Chromium-based (or Electron which uses Chromium). So it's possible that Chromium's Wayland backend is a common point of failure. Although the error message itself is definitely coming from Mesa.

Since the only relevant Ubuntu package I can see is already tracked in bug 2038313 I will mark this as a duplicate of that, but you should also log bugs against each of the affected apps in their respective trackers.

affects: wayland (Ubuntu) → ubuntu
Revision history for this message
Martin D. Weinberg (martin-weinberg-5) wrote :

I'd tentatively suggest that this is not a duplicate in the following sense:

- bug 2038313 occurs on both Wayland and Xorg sessions
- the case(s) that I reported here occur only on Wayland; everything works as expected in Xorg

That seems like some sort of clue?

I did file a report on `nextcloud-desktop` as you suggested. My goal here is to help and I hope I've done that.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

That only means the Xorg code path isn't trying to use Vulkan. Or that it happens to work on Xorg. And the frequency of the error will be app-specific dependending on what features are used.

Revision history for this message
Jason Ernst (compscidr) wrote :

Not sure if related, but having similar graphical failures for nautilus, gnome-control-center, etc. Using nvidia-driver-535.

Had a similar upgrade case to https://bugs.launchpad.net/ubuntu/+bug/2061257/comments/6 where it failed initially and I recovered it.

Similar output of
`libEGL warning: egl: failed to create dri2 screen
Segmentation fault (core dumped)`

Revision history for this message
Martin D. Weinberg (martin-weinberg-5) wrote :

All of the Wayland issues for Haswell disappeared for me in fixes to the Intel drivers in the last week. The bug #2038313 in upscayl still remains.

Changed in ubuntu:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.