search

DisplayLink / evdi

Extensible Virtual Display Interface
MIT License
689 stars 179 forks source link

GDM and GNOME crash and return to login screen in Arch #470

Open RobertoBiundo opened 1 month ago

RobertoBiundo commented 1 month ago

Issue The current EVDI is causing GDM+GNOME to revert back to xorg instead of the default wayland when a displaylink device is connected.

Steps to reproduce.

  1. Start the laptop
  2. Wait until GDM is presented - At this point GDM shows the GNOME and GNOME + XOrg options
  3. Login using normal GNOME (This is the Wayland one)
  4. Check currently running Windowing system - Wayland is shown in the about app
  5. Connect a displaylink device
  6. The screen flashes and im returned to the login screen - At this point only the GNOME options is available (this is the X11 one)
  7. Login and open about app
  8. About app shows X11 as Windowing System confirming the issue

Checking the dmesg several EVDI warnings are shown, I'm not sure if they are relevant. Here is a file with the log dmesg.txt

Please let me know what other information could be useful.

Here is what i tried so far:

  1. Boot the system with the displaylink device connected - This ends up with a black screen and after stopping and restarting the GDM service GDM pops up with only X11 support
  2. Rolling back the kernel and headers to 6.8 (I known things worked there) - This makes no difference at all in the outcome of any of the scenarios explained so far
  3. Starting the laptop without the displayLink into wayland. Switching to a different virtual terminal ctrl+alt+F5. Connecting the displaylink device and then returning to the terminal where wayland was running ctrl+alt+F1. Wayland remains running but not video output on the displaylink displays. After a logout GDM reverts to X11.
  4. Uninstalling EVDI + DisplayLink and reinstalling them with clean builds (using yay). Nothing. Same outcome on all cases.
  5. Trying with a different displayLink device. Nothing. Same outcome on all cases.
csehpeti81s commented 1 month ago

This problem affects more than one computer, I have the same issue after updating a computer yesterday. I have exactly the same wayland version (1.23.0-1) but different kernel (6.6.32-1-lts). Linux version is also the same, Arch Linux.

I have not found the solution yet.

displaylink-emajewsk commented 1 month ago

Could you please report this to GNOME as well?

displaylink-emajewsk commented 1 month ago

@RobertoBiundo GNOME uses Gitlab: https://gitlab.gnome.org/GNOME/gnome-shell

RobertoBiundo commented 1 month ago

To keep track the issue in GNOME repo is https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7697

Scan-87 commented 1 month ago

Can also confirm this issue. Behavior is exactly as described

schmunk42 commented 1 month ago

JFTR

I was able to work around the issue by downgrading mesa from 1:24.1.0-1 to 1:24.0.8-1.

cedricroijakkers commented 4 weeks ago

I have the same issue here, and I can confirm that downgrading mesa works.

At first I was put off with the following error message that appears:

Jun 11 09:52:26 48HVWD3 org.gnome.Shell.desktop[2070]: MESA-LOADER: failed to open evdi: /usr/lib/dri/evdi_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/dri, suffix _dri)

But after the downgrade, it still appears, but in a different location:

Jun 11 09:52:44 48HVWD3 gnome-shell[3107]: MESA-LOADER: failed to open evdi: /usr/lib/dri/evdi_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/dri, suffix _dri)

So I'm not sure that is the problem here, but could still be related?

Update: It's not, this error is to be expected. The issue can be tracked in the GNOME issue tracker.

cedricroijakkers commented 4 weeks ago

To keep track the issue in GNOME repo is https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7697

It now seems this might be a mesa issue, opened an issue for them too: https://gitlab.freedesktop.org/mesa/mesa/-/issues/11321

delthas commented 3 weeks ago

Hi,

I had the exact same issue here. Thanks to your comments I just installed mesa-git and now everything works (the mentioned MR https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/29546 was merged).

cedricroijakkers commented 3 weeks ago

Issue should be fixed in mesa 24.1.2 to be released on 2024-06-19. This issue can be closed as it is now definitely a mesa issue.