Public bug reported:
All games (with or without Steam) freeze after a random amount of time.
This bug is triggered, when another windows gets focus, but it happens
randomly too.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu
** Project changed: snappy => xorg-server (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1760252
Title:
starting slack crashes xwayland on 18.04
To manage notifications about this bug go
*** This bug is a duplicate of bug 1754693 ***
https://bugs.launchpad.net/bugs/1754693
I get the same error when starting the skype snap:
org.gnome.Shell.desktop[2477]: (EE)
org.gnome.Shell.desktop[2477]: (EE) Backtrace:
org.gnome.Shell.desktop[2477]: (EE) 0: /usr/bin/Xwayland
*** This bug is a duplicate of bug 1754693 ***
https://bugs.launchpad.net/bugs/1754693
** This bug has been marked a duplicate of bug 1754693
Xwayland crashed with SIGABRT in st_renderbuffer_delete()
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
mutter (wayland) is ignoring wl_shell_surface_move and
wl_shell_surface_resize request, which prevents the use of subsurfaces
window decorations (example:
http://github.com/christianrauch/wayland_window_decoration_example). The
same example works on weston.
The fault is in
Installing libnvidia-gl-390:i386 fixed the issue for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784117
Title:
Steam fails to start: glxChooseVisual failed
To manage notifications about
Is this fix being backported to bionic?
I am still getting crashes with the snap version of skype (8.34.0.78) on
xwayland-hwe-18.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1754693
Title:
I think this is upstream bug
https://gitlab.gnome.org/GNOME/mutter/issues/655.
The bug has been solved by:
https://gitlab.gnome.org/GNOME/mutter/merge_requests/924
https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/815
It is a quite critical bug since it renders the shell unusable.
Would
Public bug reported:
The compilation of `examples.tar.gz` in package `libcgal-demo` fails:
```
Scanning dependencies of target deform_mesh_for_botsch08_format_sre_arap
[ 89%] Building CXX object
The mutter MR https://gitlab.gnome.org/GNOME/mutter/merge_requests/801
should fix that issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768734
Title:
Restoring edge tiled windows on Wayland
Public bug reported:
On Mesa 20.0.4, the Intel Iris driver is affected by an issue with
selecting the appropriate dma buffer format on Wayland
(https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4869).
This issue will prevent using most OpenGL applications on Wayland. You
can check if you
This is still an issue on Ubuntu 20.10, while the GNOME Shell remote-
desktop / screencast support on Wayland has been enabled for Fedora and
other distributions for some time now.
What is Ubuntu holding back from enabling Wayland remote-desktop support
(and consecutively a Wayland-by-default
Thanks @tjaalton. I see from https://launchpad.net/ubuntu/+source/mesa
that version 20.0.8-0ubuntu1 made it into Groovy proposed.
Is there a chance this will also make it into focal-proposed so that it
can be tested on the current LTS? Or do we have to wait until this gets
merged into groovy?
--
I tested version '20.0.8-0ubuntu1~20.04.1' from 'focal-proposed' and it
fixes the issues I encountered with EGL and specifically
'es2gears_wayland'.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Is Mesa 20.0.7 going to be backported to Ubuntu Focal? It would be a
shame to be unable to use native OpenGL programs on Wayland for the next
5 years.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
To clarify, the original issue (not being able to move subsurface) is
still present on an up-to-date Ubuntu 16.04. The patch is for the
original debian source package at
http://archive.ubuntu.com/ubuntu/pool/universe/m/mutter/mutter_3.18.3.orig.tar.xz
and is also still valid.
@vanvugt What do you
Well the patch is for mutter 3.18.3, so it will still be needed on this
version.
However, this issue and patch are now more than 2 years old (without any
response during this time). It has been fixed in newer mutter versions
as used in Ubuntu 18.04 or 20.04.
--
You received this bug
Public bug reported:
"apt-key add" fails to import keys if there exists another key with a
malformed file name.
Such malformed key names used to be provided by the openSUSE Build
Service (https://github.com/openSUSE/software-o-o/issues/842).
After importing such malformed key, future key
It's in the latest Ubuntu LTS and will stay be there until 2025. If it
is legacy and deprecated, maybe it should have been removed?
In its current state, this apt-key issue has some security implications:
First, the Ubuntu update GUI is not very intuitive in handling this
issue. It presents the
I have to say that it is quite a shame that Canonical does not provide a
proper solution for this problem, as it has quite a big impact if you
cannot update packages with security fixes anymore.
Anyway, I managed to solve the problem. From an earlier repo
installation I had a file
I have to say that it is quite a shame that Canonical does not provide a
proper solution for this problem, as it has quite a big impact if you
cannot update packages with security fixes anymore.
Anyway, I managed to solve the problem. From an earlier repo
installation, I had a key file with the
I updated via focal-proposed to mutter and gnome-shell version 3.36.9
(3.36.9-0ubuntu0.20.04.1) but unfortunately my original issue reported
at https://gitlab.gnome.org/GNOME/mutter/-/issues/1700 still persists.
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1700
Public bug reported:
Interactively resizing a Wayland window while it resizes itself results
in the window jumping out of the screen. This happens on GNOME Shell and
pure mutter on the 3.36 branch but has been resolved on newer versions
(3.37.1 onwards).
See
A bit unrelated, but the reason that there is no "nautilus-dbgsym" for
the updated nautilus package (version 1:3.36.3-0ubuntu from "focal-
updates") is that the dbgsym index for the released version ("focal")
at:
http://ddebs.ubuntu.com/dists/focal/main/binary-amd64/Packages
shows the
Public bug reported:
I got a nonreproducible crash of Xwayland with the following backtrace:
```
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1 0x7f88c73c4859 in __GI_abort () at abort.c:79
#2 0x55dfca054e40 in OsAbort () at ../../../../os/utils.c:1351
#3
bug 1922034 is gnome-terminal specific. The upstream issue was
https://gitlab.gnome.org/GNOME/mutter/-/issues/1723.
But this bug is generic for any Wayland client. And it also has been
fixed in the 3.38 release.
Now, this very issue is tagged "fixed-in-3.36.8" which is not correct I think.
At
It would be helpful to also update the packages "mutter-dbgsym" and
"libmutter-6-0-dbgsym" to the corresponding point/patch versions.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1919143
Title:
I believe that this is the same issue that causes crashes for me in some
situations where a Wayland surface is committed without a window
geometry.
The upstream bug https://gitlab.gnome.org/GNOME/mutter/-/issues/1739
includes a backtrace of the crash on the "gnome-3-36" branch. So this
issue will
Public bug reported:
This is a request to update mutter to version 3.36.8 to fix various
issues that have been fixed upstream.
See https://gitlab.gnome.org/GNOME/mutter/-/issues/1700#note_1058654 for
the original mutter issue report that will be fixed by 3.36.8.
ProblemType: Bug
DistroRelease:
Public bug reported:
I encounter the (rare) situation where the update-manager's "reminder"
popped up with the "Restart Now" button below my mouse cursor just when
I clicked with the intention to select something in the window below the
newly opened reminder window. As a result, my PC rebooted
I am a bit confused about the version scheme here. My "About" page in
the settings says I am already on GNOME Version 3.36.8, but the mutter
version is 3.36.7 and the gnome-shell version is 3.36.4.
How is this "GNOME Version" determined? Shouldn't all the GNOME packages
be on the same version
I am experiencing this issue on two laptops with 20.04.2. But I just
verified that it indeed works as expected with a Live ISO inside a VM.
Is there a way to debug this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
When extracting ZIP archives from within nautilus (e.g. right-click ->
"Extract Here") the extracted file structure is missing subfolders.
Reproduce:
1. download a ZIP archive that includes files and folders in the root (e.g.
Public bug reported:
nautilus crashes when I try to create a symbolic link via drag and drop:
1. open an arbitrary folder in nautlus
2. hold 'Alt' and drag and drop a file
3. a context dialog will open with options to move, copy or link the file
4. chose any option
Choosing any option (even
I have the ddebs sources added:
deb http://ddebs.ubuntu.com focal main restricted universe multiverse
deb http://ddebs.ubuntu.com focal-updates main restricted universe multiverse
deb http://ddebs.ubuntu.com focal-proposed main restricted universe multiverse
But the dbgsym version does not match
After installing that dbgsym package, I still do not get a backtrace. It
just exits with "[Inferior 1 (process 116937) exited with code 01]" so
maybe it does not crash but the failed assertion makes it just quit?
Also, there is nothing in "/var/crash" which is another indicator that
the process
*** This bug is a duplicate of bug 1900098 ***
https://bugs.launchpad.net/bugs/1900098
I am getting the same error:
$ software-properties-gtk
ERROR:dbus.proxies:Introspect error on :1.8502:/:
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message
recipient disconnected
*** This bug is a duplicate of bug 1900098 ***
https://bugs.launchpad.net/bugs/1900098
The Qt (software-properties-qt) and KDE (software-properties-kde)
versions still work when launched as root via sudo.
** This bug has been marked a duplicate of bug 1900098
software-properties-gtk fails
*** This bug is a duplicate of bug 1900098 ***
https://bugs.launchpad.net/bugs/1900098
** This bug has been marked a duplicate of bug 1900098
software-properties-gtk fails to open with error
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I encountered the same error (see duplicate
https://bugs.launchpad.net/ubuntu/+source/software-
properties/+bug/1930974/comments/5) and was able to resolve the issue by
reinstalling packages "python3-six" and "python3-certifi" as suggested
in https://bugs.launchpad.net/ubuntu/+source/software-
40 matches
Mail list logo
