** Tags removed: bot-comment
** Tags added: wayland-session
** Changed in: xwayland (Ubuntu)
Status: Incomplete => New
** Description changed:
# System Details Report
---
## Report details
- **Date generated:** 2024-09-11 04:00:17
## Hardware I
*** This bug is a duplicate of bug 1965563 ***
https://bugs.launchpad.net/bugs/1965563
I am running into this issue with nvidia-driver-560-open on wayland in
latest Oracular as of today. Specifically I get this error:
https://discussion.fedoraproject.org/t/gdk-message-error-71-protocol-
error-
** Tags removed: oracular
** Tags added: noble
** Tags removed: noble
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xwayland in Ubuntu.
https://bugs.launchpad.net/bugs/2077663
Title:
Some games crashed on Wayland for Ubuntu 24.10
To manage
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
an
If Xwayland isn't leaving core files (which would show up as crash files
in /var/crash) then it might be inheriting Xorg's built-in crash
handler, logging the stack trace to *somewhere* and that never makes it
to the system journal.
--
You received this bug notification because you are a member o
Dropped the 'regression-update' tag because this bug really has existed
forever. The only regression-update is bug 2080498.
** Tags removed: regression-update
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to egl-wayland in Ubuntu.
https://bugs.la
This gnome-shell suicide is the only explanation I can see:
Sep 18 15:01:22 shanu-Inspiron-15-3511 gnome-shell[16721]: Connection to
xwayland lost
Sep 18 15:01:22 shanu-Inspiron-15-3511 gnome-shell[16721]: Xwayland terminated,
exiting since it was mandatory
Sep 18 15:01:22 shanu-Inspiron-15-3511
You have been subscribed to a public bug:
20:22:40 kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.ECDV._Q66 due to
previous error (AE_AML_MUTEX_NOT_ACQUIRED) (20230628/psparse-529)
20:03:28 systemd: Failed to start
app-gnome-ubuntu\x2dreport\x2don\x2dupgrade-2586.scope - Application launched
> Alessandro informs me that this was caused by some combination of kernel
> 6.8.0 and a
> nvidia-driver-550 update, so tagging regression-update, and I'll review the
> proposed fix next.
The regression-update is probably better tracked in bug 2080498.
--
You received this bug notification bec
Unsubscribing ~ubuntu-sponsors as there is nothing left to sponsor.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to egl-wayland in Ubuntu.
https://bugs.launchpad.net/bugs/1965563
Title:
GNOME apps crash with "Protocol error" in NVIDIA Wayland
Hello Gunnar, or anyone else affected,
Accepted egl-wayland into jammy-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/egl-
wayland/1:1.1.9-1.1ubuntu0.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
New debdiff addressing all comments
** Patch added: "egl-wayland_1.1.9-1.1ubuntu0.1.debdiff"
https://bugs.launchpad.net/gtk/+bug/1965563/+attachment/5818943/+files/egl-wayland_1.1.9-1.1ubuntu0.1.debdiff
--
You received this bug notification because you are a member of Ubuntu-X,
which is subs
** Description changed:
[ Impact ]
- * GTK applications fail to start on a hybrid graphics machine with an
+ * GTK applications fail to start on a hybrid graphics machine with an
NVIDIA discrete GPU.
- * The NVIDIA egl-wayland extension 1.1.9 only supports rendering to the
+ * The NV
> > A possible regression would be that the driver starts reporting as
incompatible on NVIDIA single-GPU systems too. One would notice by all
wayland-native applications suddenly being very slow. Note that such
systems would not default to Wayland in Jammy.
> Please add to the Test Plan to verify
Both patches come from upstream,
egl-wayland-retrieve-DRM-device-name-before-acquiring-.patch originally had to
be manually rebased to apply cleanly. but with both patches in this order they
both apply cleanly, so i just took both from upstream.
I realize i forgot to re-apply the debian headers
SRU review:
1) debian/patches/egl-wayland-retrieve-DRM-device-name-before-
acquiring-.patch is being modified for no good reason (at least, it
isn't documented) and the dep3 headers are being dropped. Please explain
or fix.
2) Not essential, but the expected package version string would be
1:1.1.
In theory this is fix released now that Oracular has Nvidia-560. I can't
totally confirm it though, because once again Chrome has regressed to
not having any hardware acceleration enabled. But let's keep that
separate...
** Also affects: nvidia-graphics-drivers-560 (Ubuntu)
Importance: Undecid
Alessandro informs me that this was caused by some combination of kernel
6.8.0 and a nvidia-driver-550 update, so tagging regression-update, and
I'll review the proposed fix next.
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu-X,
which i
18 matches
Mail list logo
