[Bug 1874818] [NEW] Please pull Mutter/Wayland fixes for desktop freeze
Public bug reported: I have upstreamed a GNOME/Wayland desktop freeze fix in: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1209 (master) https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1215 (3.36 branch) https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1216 (3.34 branch) I diagnosed the freeze on Mutter 3.34 Ubuntu 19.10 flavour first, with DisplayLink hardware. Any DRM driver that may temporarily fail drmModePageFlip() calls might trigger this. I triggered the freeze particularly by trying to make a DisplayLink output the only active output via GNOME display settings. Other triggers are possible. This fix may help with https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1853357 but I don't know for sure. ** Affects: mutter (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874818 Title: Please pull Mutter/Wayland fixes for desktop freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1874818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853357] Re: display (whole computer?) hangs when I attempt to use DisplayLink with Wayland
On Eoan, I was able to trigger a freeze when trying to set the DisplayLink output as the only output. I have proposed a fix for that in https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1209 , maybe it could help here as well? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853357 Title: display (whole computer?) hangs when I attempt to use DisplayLink with Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1853357/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867757] Re: Please pull Mutter cursor fixes for DisplayLink devices
Ok, thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867757 Title: Please pull Mutter cursor fixes for DisplayLink devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1867757/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867757] Re: Please pull Mutter cursor fixes for DisplayLink devices
Where is the SCM repository for Mutter in Focal? I want to verify that the fix is complete in there. Can I read about that new policy somewhere? Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867757 Title: Please pull Mutter cursor fixes for DisplayLink devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1867757/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867757] Re: Please pull Mutter cursor fixes for DisplayLink devices
What does "Fix Committed" actually mean? Committed in upstream? git://git.launchpad.net/~ubuntu-desktop/ubuntu/+source/mutter does not contain anything post 3.35.91-1ubuntu1 https://git.launchpad.net/ubuntu/+source/mutter has 3.36.0-2ubuntu1 and does not contain https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1097 Linked from https://packages.ubuntu.com/source/focal/mutter , https://salsa.debian.org/gnome-team/mutter/-/commits/ubuntu/master/ has 3.36.0-2ubuntu1 too and does not contain https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1097 Which packaging repository should I be looking at for Mutter in Focal? Did it change recently? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867757 Title: Please pull Mutter cursor fixes for DisplayLink devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1867757/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867757] [NEW] Please pull Mutter cursor fixes for DisplayLink devices
Public bug reported: For GNOME/Wayland to use hardware cursors on DisplayLink devices (proprietary userspace driver for USB 3 devices), the following Mutter fixes should be included: Mutter 3.34 branch (tentatively 3.34.5): - https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1116 Initialize cursor support on GPU hotplug (backport to 3.34) Mutter 3.36 (currently master) branch (tentatively 3.36.1): - https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1079 Handle lack of explicit cursor planes better - https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1097 Initialize cursor support on GPU hotplug Without "Initialize cursor support on GPU hotplug" performance on hotplugged DisplayLink devices that create a new DRM device node suffers, because Mutter uses a software cursor which implies that DisplayLink needs to update the whole screen on every cursor motion. Without "Handle lack of explicit cursor planes better" there will not be a cursor at all on DisplayLink devices in Mutter 3.36. I would assume that the 3.34 branch is relevant to Ubuntu 19.10 and the 3.36 branch is relevant to Ubuntu 20.04. ** Affects: mutter (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867757 Title: Please pull Mutter cursor fixes for DisplayLink devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1867757/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853357] Re: display (whole computer?) hangs when I attempt to use DisplayLink with Wayland
I tested with a Dell D3100 dock and two monitors connected to the dock via HDMI in addition to laptop built-in screen. I did this on Ubuntu 19.10 with the libmutter fix from eoan-proposed (libmutter-5-0 package version 3.34.3-1ubuntu1~19.10.1). I tried unplugging and hotplugging each HDMI cable individually and together. I tried hotplugging and unplugging the dock itself (USB). I tried booting with the dock connected, and booting with the dock disconnected then hotplugged. With all three monitors on, I left one glxgears running on one DisplayLink output and the laptop screen each, and a terminal printing the fps on the other DL output for 10 minutes. Then I changed the refresh rate of one DL output to 50 Hz and the other DL output to 75 Hz, confirmed from the monitors themselves to actually run with those refresh rates, and left things running for a couple of minutes more. (Everything defaulted to 60 Hz before.) I was unable to reproduce any kind of freeze. However, I did notice that with three monitors, gnome-control-center Display settings is crash-happy if any monitor was disabled. But that is off-topic here, because even that did not cause anything to freeze. I did also observe the "outdated content" issue I referred to in my earlier comment here. That should be fixed in EVDI kernel module once DisplayLink releases an update. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853357 Title: display (whole computer?) hangs when I attempt to use DisplayLink with Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1853357/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862753] Re: Backport GPU hotplug RandR fix
Let's keep them separate. Bug 1853357 is a Wayland-related bug with many other issues mixed in. This here is a Xorg patch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862753 Title: Backport GPU hotplug RandR fix To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1862753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862753] [NEW] Backport GPU hotplug RandR fix
Public bug reported: In order for the first DisplayLink device hotplug after reboot to be correctly acted on in GNOME, the following fix should be backported to all Xorg-server downstream branches that already apply the patch "xf86: autobind GPUs to the screen" (upstream 078277e4d92f05a90c4715d61b89b9d9d38d68ea): https://gitlab.freedesktop.org/xorg/xserver/merge_requests/326 The related upstream bug report fixed by this is https://gitlab.freedesktop.org/xorg/xserver/issues/909 I originally diagnosed the issue on Ubuntu 19.04 with Xorg based on the 1.20.4 upstream release. Upstream will not backport this patch into the stable 1.20 branch, because that branch does not carry "xf86: autobind GPUs to the screen". ** Affects: xorg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862753 Title: Backport GPU hotplug RandR fix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1862753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853357] Re: display (whole computer?) hangs when I attempt to use DisplayLink with Wayland
Unfortunately I have no idea why something is or is not shipped in Focal. Sorry, I did not understand from the above that you cannot build the driver package's EVDI module or library on 20.04. Can you point me to the displaylink.com discussions if those happen to be public? I'm curious. I can still give it a try on Ubuntu 19.10 to see if I can trigger any kind of freeze with two monitors plugged in via DisplayLink. According to https://packages.ubuntu.com/source/focal/mutter Focal today has libmutter based on 3.34.3 upstream release which already contains backported patches from https://gitlab.gnome.org/GNOME/mutter/merge_requests/953 , so this would be something else. I assume that will be upgraded to 3.36 in 20.04 still. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853357 Title: display (whole computer?) hangs when I attempt to use DisplayLink with Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1853357/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853357] Re: display (whole computer?) hangs when I attempt to use DisplayLink with Wayland
Re: DisplayLink monitors not detected under Xorg, I wonder if that would have to do with https://gitlab.freedesktop.org/xorg/xserver/issues/909 ? But that's off-topic in this report too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853357 Title: display (whole computer?) hangs when I attempt to use DisplayLink with Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1853357/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853357] Re: display (whole computer?) hangs when I attempt to use DisplayLink with Wayland
Then the main issue: freezes. Do I understand correctly, that so far the freezes have only happened when you have had two monitors attached to the DisplayLink dock? Never with just one monitor? Which DisplayLink dock do you have? You said changing the display configuration is a sure way to freeze? What do you do exactly, something in GNOME display settings or plugging cables or? I doubt the HDMI vs. DVI or monitor brand/model would have an effect here, so I think you can leave testing those details for later. For now, I would like us to concentrate on Ubuntu 19.10, and the full DisplayLink driver package 5.2.14 which includes the EVDI kernel module and libevdi0. Verify what version of libmutter-5-0 package you have installed exactly. If it's older than the one mentioned here to contain the fix I thought would help, try to get that updated. Let me know what version you have, I can have a go at reproducing the freeze. When your machine freezes, can you access it from a remote, e.g. via ssh? If you can, you could first take a look at the process list: are gnome- shell and DisplayLinkManager running? Do they consume CPU? The next step would be installing a bunch of dbgsym packages and attaching GDB to gnome-shell when it's frozen to see where it is at. Do you know how to do that? ** Bug watch added: gitlab.freedesktop.org/xorg/xserver/issues #909 https://gitlab.freedesktop.org/xorg/xserver/issues/909 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853357 Title: display (whole computer?) hangs when I attempt to use DisplayLink with Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1853357/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853357] Re: display (whole computer?) hangs when I attempt to use DisplayLink with Wayland
What comes to the EVDI dkms version, the official DisplayLink driver 5.2.14 package contains EVDI 1.6.2. The release notes just write it out as v1.5.0-r1-76 (a1e1135), but that sha1 refers to 1.6.2 and the code between the official package and the 1.6.2 tag for the kernel module is identical. So I think the ones shipped in Ubuntu/Debian are older than the DisplayLink's own. I see that the Ubuntu evdi 1.6.0+dfsg-1ubuntu2 (the version I see in Ubuntu 19.10) contains some patches on top of 1.6.0, but none of those are GNOME Wayland related fixes found in 1.6.2. OTOH, it seems 1.6.2 already contains all the patches that Ubuntu adds. This probably makes no difference to your issues, but I'd prefer to stick to the DisplayLink official version to avoid confusion on what is actually being tested. 1.6.3 and 1.6.4 exist too, they have one patch each to libevdi0. I cannot off-hand say if those might be relevant or not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853357 Title: display (whole computer?) hangs when I attempt to use DisplayLink with Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1853357/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853357] Re: display (whole computer?) hangs when I attempt to use DisplayLink with Wayland
Xorg cursor artifacts all over everywhere: "When I use the evdi module and library shipped with Ubuntu in 20.04, then DisplayLink works in Xorg, but it's very glitchy, with cursor artifacts showing up constantly all over the place on all screens, both DisplayLink and non- DisplayLink." I've seen it, it is a know issue and has a workaround: setting "PageFlip" "false" in xorg.conf. This link is not exactly about cursor issues but explains how to set the PageFlip workaround: https://support.displaylink.com/knowledgebase/articles/1181623-displaylink-ubuntu-driver-after-recent-x-upgrades Anyway, that is off-topic too for this issue, so if you want to discuss that, I again suggest a new report. I don't think I can help with that though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853357 Title: display (whole computer?) hangs when I attempt to use DisplayLink with Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1853357/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853357] Re: display (whole computer?) hangs when I attempt to use DisplayLink with Wayland
Hi Jonathan, you seem to be having several different issues here, so I'll try to address them individually. First the slow updates, you wrote: "screen updates to the DisplayLink monitor are Extremely Slow. Like I am typing in a terminal window and it sometimes takes a second or two between when I type something and when the results of the typing show up in the terminal. If I move the same terminal window onto the built-in laptop display the lag goes away." Slow updates could be one of two things: either the copying of content to DisplayLink itself is slow, or DisplayLink is showing outdated content. To understand which one it is, you could try running 'glxgears' (or any program that animates continuously and reports fps) on the DisplayLink output and then see if the same slowness with a terminal still happens. If the issue is outdated content, then 'glxgears' by forcing repeated output updates should have the side-effect of making the slowness go away. Also glxgears should report the expected monitor refresh rate as fps (for a 60 Hz monitor I'd expect 58 - 60 fps). Your overall system CPU consumption could be somewhat high, but I would not expect any CPU core to be maxed out. If the issue is bad performance in copying the content, then running glxgears should not make the slowness disappear. Instead, glxgears should report very low fps, and your system CPU usage may or may not be high. It would be interesting to know if you have any CPU cores maxed out busy. In any case, I think we should talk about the slowness in a new bug report. Please, point me to it, if you file one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853357 Title: display (whole computer?) hangs when I attempt to use DisplayLink with Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1853357/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853357] Re: display (whole computer?) hangs when I attempt to use DisplayLink with Wayland
This will hopefully be fixed by https://gitlab.gnome.org/GNOME/mutter/merge_requests/953 . Yes, using the vendor driver package is required, because it contains DisplayLinkManager program (proprietary and closed source) for driving the DisplayLink USB 3 devices. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853357 Title: display (whole computer?) hangs when I attempt to use DisplayLink with Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1853357/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850622] [NEW] GDM does not offer Plasma Wayland session
Public bug reported: On Ubuntu 19.04, I installed Plasma with 'apt install kde-standard plasma-workspace-wayland', and when asked I told to keep gdm3 as the login manager. Expected result: - GDM offers Plasma Wayland as a session Actual result: - GDM offers only Plasma session, which is a Xorg session According to the hint from https://www.reddit.com/r/gnome/comments/dim3fo/gdm_does_not_see_the_plasma_wayland_session/f5nyjgi/ I edited /usr/share/wayland-sessions/plasmawayland.desktop: - deleted all Name and Comment lines - added line: Name=Plasma Wayland After logging out and back in GDM, GDM now offers Plasma Wayland session and launches it ok. ** Affects: plasma-workspace (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850622 Title: GDM does not offer Plasma Wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1850622/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826176] Re: Applications do not receive focus in Wayland sessions
Ubuntu 19.04 with all updates installed, using Ubuntu on Wayland desktop session. I believe I reproduced the issue: - click sidebar to launch Firefox (Firefox gets keyboard focus without further actions; ok) - click sidebar to launch Files (keyboard focus remains on Firefox which is below Files; fail) Using Terminal instead of Files fails the same way. Firefox is an X11 application, the rest are Wayland applications, so to me it seems the issue is specifically about not moving focus from an old X11 window to a new Wayland window. I cannot get it to fail otherwise, and the failure seems to be reliable for me. After upgrading to: libmutter-4-0: 3.32.1-2ubuntu1~19.04.1 I can no longer reproduce the issue I described above. I would propose to change the tag from verification-needed-disco to verification-done-disco. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826176 Title: Applications do not receive focus in Wayland sessions To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1826176/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826182] Re: [DisplayLink][fixed upstream] GNOME libmutter crash on hotplugging a dock with a monitor
I installed: - libmutter-4-0: 3.32.1-2ubuntu1~19.04.1 - gir1.2-mutter-4: 3.32.1-2ubuntu1~19.04.1 The issue is fixed. ** Tags removed: verification-needed-disco ** Tags added: verification-done-disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826182 Title: [DisplayLink][fixed upstream] GNOME libmutter crash on hotplugging a dock with a monitor To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1826182/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826182] [NEW] [DisplayLink][fixed upstream] GNOME libmutter crash on hotplugging a dock with a monitor
Public bug reported: Ubuntu 19.04 DisplayLink properietary driver installed. Log in to GNOME desktop in Wayland mode. Hotplug a DisplayLink USB dock with one monitor connected. What happens: The desktop session shuts down and throws me back into the login screen, where Wayland sessions are no longer available. What I would expect: the new monitor is taken into use and the desktop session continues normally. Installed: libmutter-4-0 3.32.0+git20190410-1ubuntu1 This issue is already fixed upstream: https://gitlab.gnome.org/GNOME/mutter/merge_requests/521 The fix has been released as part of mutter 3.32.1. I would hope the mutter package would be updated to the new upstream point release. ** Affects: mutter (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826182 Title: [DisplayLink][fixed upstream] GNOME libmutter crash on hotplugging a dock with a monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1826182/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
