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
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
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
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/
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/mut
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
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 in
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 h
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
078277e4d92f05a90c4715d61b
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 sti
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.
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 freez
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
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 i
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
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 notifica
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
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;
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 subscrib
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 l
20 matches
Mail list logo
