No cursor on DisplayLink screen after login to Wayland sesion in Ubuntu 20.04

Bug #1868702 reported by Łukasz Spintzyk
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mutter (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

Cursor is not visible on screen connected via DisplayLink usb3 docking stations.

It is working fine when the display is first time attached after login to Wayland Gnome session.
Then after logout it disappears.
On other hand cursor is working fine in XServer session.

Steps to reproduce:
0. Install DisplayLink driver from https://www.displaylink.com/downloads/ubuntu
1. Boot with DisplayLink device unplugged
2. Plug the device on login screen. -> screen should be added and cursor should work on it.
3. Login to Gnome on Wayland (Ubuntu on wayland option)

Expected:
Cursor should is working on screen attached via DisplayLink device
Got:
Cursor is invisible

Reproduces with Ubuntu 20.04
Gnome/Wayland mutter version: mutter/focal 3.35.91-1ubuntu1
Reproducible on wide range of laptops, e.g XPS 13 9343

The problem is most likely related to pre-existing /dev/driX devices, as when using the hotplug path everything is fine.

Tags: focal
Revision history for this message
Łukasz Spintzyk (lspintzyk) wrote :

Guys from DisplayLink together with Collabora are working on the fix.
It should be available in Gnome mutter upstream soon.
It would be very helpful to have it merged in Ubuntu 20.04 LTS

description: updated
tags: added: focal
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Can you tell us the upstream links we should be tracking for this?

Changed in mutter (Ubuntu):
status: New → Incomplete
Revision history for this message
Łukasz Spintzyk (lspintzyk) wrote :

Together with bug #1867757 and new mutter 3.36 it is no longer reproducible.
I consider this fixed.

Thank you!

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.