> This needs verifying in Oracular to see if it's still the case.
It is behaving as designed. Because NVIDIA has priority in EGL, it will
always be tried first. Without libnvidia-egl-wayland1 it fails so the
second driver is probed, MESA.
> If the maintainer of the nvidia-graphics-drivers-550 sou
>From the GLVND documentation:
> EGL can't rely on asking an X server for a vendor name like GLX can,
so instead, it enumerates and loads every available vendor library.
Loading every vendor is also needed to support extensions such as
EGL_EXT_device_enumeration.
> When the application calls eglG
** Changed in: gnome-shell (Ubuntu)
Status: New => Triaged
** Changed in: switcheroo-control (Ubuntu)
Status: New => Triaged
** Changed in: gnome-shell (Ubuntu)
Assignee: (unassigned) => Alessandro Astone (aleasto)
** Changed in: switcheroo-control (Ubuntu)
** Tags added: udeng-1202
--
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/2080282
Title:
Apps run on the discrete Nvidia GPU by default instead of the Intel
integrated GPU
To manage not
Right, as Daniel said in comment #2 the issue about apps failing to
launch on NVIDIA+Wayland is tracked in bug 1965563 and already resolved
in noble (but not in jammy).
So this thread is now only tracking the bug which causes apps to be
launched on the NVIDIA GPU by default in hybrid systems, rat
** Changed in: egl-wayland (Ubuntu Jammy)
Assignee: (unassigned) => Alessandro Astone (aleasto)
--
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 w
With bug 2062082 fixed, applications are now allowed to use the NVIDIA GPU on
hybrid systems on Wayland.
Together with bug 2080282, all hybrid systems running Jammy will hit this bug
making this a high priority for a Jammy SRU
** Changed in: egl-wayland (Ubuntu Jammy)
Importance: High => Crit
@azorin, could you please verify if this build solves your issue?
https://launchpad.net/~aleasto/+archive/ubuntu/tests/+build/29088125
--
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
Yea the libnvidia-egl-wayland1 "fix" upstream was to basically disable
it for hybrid systems.
--
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
** Patch added: "egl-wayland_1.1.9-1.1ubuntu1.debdiff"
https://bugs.launchpad.net/gtk/+bug/1965563/+attachment/5816995/+files/egl-wayland_1.1.9-1.1ubuntu1.debdiff
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to egl-wayland in Ubuntu.
https://
egl-wayland >= 1.1.10 basically just disables itself on hybrid systems: the
driver refuses to use a GPU that is not the compositor's primary GPU; so this
bug does not happen when bug 1965563 is fixed.
-- Note that this means that "Launch using Discrete GPU" wouldn't work even if
switcheroo-contr
*** This bug is a duplicate of bug 1965563 ***
https://bugs.launchpad.net/bugs/1965563
> NVIDIA does intend to eventually allow egl-wayland to work on hybrid
systems, but I don't see any time commitment.
Scratch that, it seems supported by setting __NV_PRIME_RENDER_OFFLOAD.
Which switcheroo-c
** Description changed:
+ [ Impact ]
+
+ * 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
+ NVIDIA GPU if it is the primary GPU. On a hybrid system the primary GPU
+ would be
Indeed installing mesa 24.2 in the snap resolves the issue.
However the patch that was linked in the mesa bug alone does not:
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/29124
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in
I don't think there's interest in upgrading mesa in jammy at this point
so here comes a 4-versions-across bisect 😰
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2083538
Title:
amdgpu: [mmhub] p
ntu Jammy)
Assignee: (unassigned) => Alessandro Astone (aleasto)
** Changed in: mesa (Ubuntu Noble)
Status: New => In Progress
** Changed in: mesa (Ubuntu Noble)
Assignee: (unassigned) => Alessandro Astone (aleasto)
** Changed in: mesa (Ubuntu)
Status: In Pro
Proposing a backport to jammy
** Patch added: "mesa_23.2.1-1ubuntu3.1~22.04.3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2083538/+attachment/5826285/+files/mesa_23.2.1-1ubuntu3.1~22.04.3.debdiff
--
You received this bug notification because you are a member of Ubuntu-X,
wh
Bisected:
https://gitlab.freedesktop.org/mesa/mesa/-/commit/bceb2328c48a3eb8a9039911393fb2a7c23d5ad1
It fixes both green artifacts and crashing
** Changed in: mesa (Ubuntu)
Status: New => In Progress
** Changed in: firefox (Ubuntu)
Status: New => Triaged
** Bug watch added: gitlab
Yeah I'll handle the SRU template.
Please coordinate the upload with tjaalton who's looking into the raspi
enablement patches.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2083538
Title:
amdg
** Description changed:
+ [ Impact ]
+
+ * amdgpu changes in kernel 6.11 make VAAPI video playback crash the GPU
+ and bring down the whole system.
+
+ * A fix was shipped in mesa 24.2, which is already in Oracular - the
+ only version with kernel 6.11 currently, but snaps bundle their own
+ v
I'm hitting the same issue `amdgpu: [mmhub] page fault (src_id:0 ring:8
vmid:1 pasid:32785)` when playing twitter videos in the firefox snap
through VAAPI -- media.ffmpeg.vaapi.enabled=true in about:config.
The firefox snap uses mesa 23.2.1 from jammy and that hasn't changed in
a while.
I get no
I cannot reproduce with the prebuilt firefox tarball from upstream,
running on oracular with mesa 24.2.3 (and LLVM 19)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2083538
Title:
amdgpu: [mmhu
** Changed in: mesa (Ubuntu)
Assignee: (unassigned) => Alessandro Astone (aleasto)
** Changed in: firefox (Ubuntu)
Assignee: (unassigned) => Alessandro Astone (aleasto)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in
Analysis from 201912_27623_journal_log.txt
Early on during boot we see:
kernel: EDID block 0 (tag 0x00) checksum is invalid, remainder is 61
kernel: [00] BAD 00 ff ff ff ff ff ff 00 04 69 c4 24 cc 83 03 00
kernel: [00] BAD 2c 18 01 03 80 35 1e 78 2a a0 a5 a6 56 52 9d 27
kernel:
kernel/drivers people, any idea how this would happen?
** Summary changed:
- External HDMI does not work after dist upgrade
+ Nvidia driver changed to nouveau after dist upgrade to oracular
** Also affects: nvidia-graphics-drivers-560 (Ubuntu)
Importance: Undecided
Status: New
** No l
> Reopened in bug 2081291(?)
Yeah, that's a different bug. A new regression with nvidia 560, for
Vulkan apps this time. The fact that gtk4 now defaults to Vulkan makes
it show up as the same bug...
I directed that issue to a new bug rather than adding more "affected
projects" here to not disturb
> > 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
*** This bug is a duplicate of bug 1965563 ***
https://bugs.launchpad.net/bugs/1965563
Also, please open a new bug because this bug report affected GSK_RENDERER=gl
while your issue does not.
I suspect the new bug is with Vulkan, which verifying that GSK_RENDERER=ngl
works should definitively
*** This bug is a duplicate of bug 1965563 ***
https://bugs.launchpad.net/bugs/1965563
Thanks!
For what we know nvidia-driver-560 is the best fit.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to egl-wayland in Ubuntu.
https://bugs.launchpad
*** This bug is a duplicate of bug 1965563 ***
https://bugs.launchpad.net/bugs/1965563
> Using: GSK_RENDERER=gl baobab doesn't crash.
Can you also try GSK_RENDERER=ngl?
Also please limit the tests to drivers available in the Ubuntu archive
like 535, 550 and 560, to avoid inserting more varia
*** This bug is a duplicate of bug 1965563 ***
https://bugs.launchpad.net/bugs/1965563
1) Please try launching the affected app with
__NV_DISABLE_EXPLICIT_SYNC=1
2) Please run these on an affected machine:
lspci -k > lspci.txt
journalctl -b0 > journal.txt
dpkg -l > packages.txt
and at
** 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
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
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
Thank you!
Marking verification complete.
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to egl-wayland in Ubuntu.
https://bugs
Verified [ Test Plan - Regression ] with libnvidia-egl-
wayland1=1:1.1.9-1.1ubuntu0.1 on Jammy 24.04.5 LTS, using nvidia drivers
470, 535 and 550.
I don't own a hybrid laptop; @azorin would you be so kind to perform this
update verification?
The build in jammy-proposed should be identical to the
We cannot just globally enable NVreg_EnableS0ixPowerManagement as, per nvidia's
documentation, it requires that "both the platform and the GPU support
S0ix-based power management", which my card does not for example.
It might be harmless to enable it even if the card does not support S0ix, but
i
** Changed in: mutter (Ubuntu)
Status: New => Won't Fix
** Changed in: xwayland (Ubuntu)
Status: New => Confirmed
** Changed in: xwayland (Ubuntu)
Assignee: (unassigned) => Alessandro Astone (aleasto)
** Also affects: mutter (Ubuntu Noble)
Importa
* Added jammy-proposed to the gnome-42-2204 snapcraft recipe
package-repositories:
- type: apt
url: http://archive.ubuntu.com/ubuntu
suites: [jammy-proposed]
components: [main, universe]
key-id: F6ECB3762474EDA9D21B7022871920D1991BC93C
key-server: keyserver.ubuntu.com
$ snapc
Any idea why the `mesa-va-drivers` binary package does not have a
`23.2.1-1ubuntu3.1~22.04.3` build in proposed, while all the other
binary packages that mesa produces do?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bu
Ahh, pardon, I didn't realize that's a universe package :o
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2083538
Title:
amdgpu: [mmhub] page fault (src_id:0 ring:8 vmid:6 pasid:32781 / Fence
So is this bug your only blocker for touchscreen on Xorg?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-libinput in Ubuntu.
https://bugs.launchpad.net/bugs/2087831
Title:
touchscreen has no response after resume from suspe
Thank you for the bug report.
Judging by the DpkgLog.txt the upgrade that triggered your issue seems
to include:
linux-firmware:all 20220329.git681281e4-0ubuntu3.35
20220329.git681281e4-0ubuntu3.36
linux-generic:amd64 5.15.0.125.124 5.15.0.126.125
linux-image-generic:amd64 5.15.0.125.124 5.15.0.
Thank you for the bug report.
Could you try this solution from the forums?
https://askubuntu.com/a/1315513
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: xorg (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
Isn't touchscreen on xorg already blocked by
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2063005
https://gitlab.gnome.org/GNOME/mutter/-/issues/3484
?
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #3484
https://gitlab.gnome.org/GNOME/mutter/-/issues/3484
--
You received
** Patch removed: "mesa_24.2.3-1ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2090934/+attachment/5841829/+files/mesa_24.2.3-1ubuntu2.debdiff
** Patch added: "mesa_24.2.3-1ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2090934/+attachment/584184
Proposed mesa_24.2.3-1ubuntu2.debdiff backporting patches from
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30988
Alternatively, we can update mesa to 24.2.8, which I see is currently in
plucky-proposed
--
You received this bug notification because you are a member of Ubuntu-X,
whic
* Installed the firefox snap from --channge=edge, which is core24
* Verified following the test plan that it would reproduce the crash
* Added noble-proposed to the mesa-2404 recipe
package-repositories:
- type: apt
url: http://archive.ubuntu.com/ubuntu
suites: [noble-proposed]
com
Public bug reported:
[ Impact ]
Applications might exceed the limit of open files, 1024 by default, because
mesa opens the mesa_shader_cache_db files too many times.
This is a regression in mesa 24.2 where the shader-cache got re-architected.
[ Test Plan ]
1. Install gstreamer1.0-plugins-bad
2
signed) => Alessandro Astone (aleasto)
** Changed in: mesa (Ubuntu Oracular)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2090934
Title:
too many mesa_shader_ca
Backporting patches from
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30988
Alternatively, we can update mesa to 24.2.8, which I see is currently in
plucky-proposed
** Patch added: "mesa_24.2.3-1ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2090934/+attachm
Upgrade: libglx-mesa0:amd64 (24.2.3-1ubuntu1, 24.2.8-1ubuntu1~24.10.1),
libgbm1:amd64 (24.2.3-1ubuntu1, 24.2.8-1ubuntu1~24.10.1), libgbm-
dev:amd64 (24.2.3-1ubuntu1, 24.2.8-1ubuntu1~24.10.1), mesa-
libgallium:amd64 (24.2.3-1ubuntu1, 24.2.8-1ubuntu1~24.10.1),
libxatracker2:amd64 (24.2.3-1ubuntu1, 24
24.2.8 is also in oracular-proposed: bug 2091079
** Changed in: mesa (Ubuntu Oracular)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2090934
Title:
*** This bug is a duplicate of bug 2084046 ***
https://bugs.launchpad.net/bugs/2084046
** This bug has been marked a duplicate of bug 2084046
[i915] Phantom "Unknown" display detected on Intel Meteor Lake
--
You received this bug notification because you are a member of Ubuntu-X,
which is
** Changed in: xwayland (Ubuntu)
Importance: Undecided => Medium
** Changed in: xwayland (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: xwayland (Ubuntu Noble)
Importance: Undecided => Medium
** Changed in: xwayland (Ubuntu Oracular)
Importance: Undecided => Medium
--
Installed xwayland=2:24.1.2-1ubuntu0.2 from oracular-proposed.
Verified the test plan. No high CPU usage, and x11 apps still work as
expected.
** Tags removed: verification-needed-oracular
** Tags added: verification-done-oracular
--
You received this bug notification because you are a member o
Noble debdiff
** Patch added: "xwayland_23.2.6-1ubuntu0.2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2043517/+attachment/5839496/+files/xwayland_23.2.6-1ubuntu0.2.debdiff
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xw
Jammy debdiff
** Patch added: "xwayland_22.1.1-1ubuntu0.15.debdiff"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2043517/+attachment/5839497/+files/xwayland_22.1.1-1ubuntu0.15.debdiff
** Changed in: xwayland (Ubuntu Jammy)
Status: New => In Progress
** Changed in: xwayland (U
Plucky debdiff
** Patch added: "xwayland_24.1.4-1ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2043517/+attachment/5839494/+files/xwayland_24.1.4-1ubuntu1.debdiff
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xwayl
Oracular debdiff
** Patch added: "xwayland_24.1.2-1ubuntu0.2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2043517/+attachment/5839495/+files/xwayland_24.1.2-1ubuntu0.2.debdiff
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
: New => Won't Fix
** Changed in: xwayland (Ubuntu)
Status: Confirmed => In Progress
** Changed in: xwayland (Ubuntu Jammy)
Assignee: (unassigned) => Alessandro Astone (aleasto)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
** Description changed:
[ Impact ]
gnome-shell running on an inactive VT will sometimes start using 100% CPU.
When that happens, the Xwayland child process is seen using 40% CPU.
[ Test Plan ]
1. Log in to GNOME Wayland
2. Open a terminal window
3. Terminate Xwayland if it w
Verified that I could reproduce the bug following the test plan in Ubuntu
22.04.5 LTS.
Installed xwayland=2:22.1.1-1ubuntu0.15.
Verified that I could not reproduce the bug anymore following the test plan: no
high CPU usage, and x11 apps still work as expected.
** Tags removed: verification-neede
** Bug watch added: gitlab.freedesktop.org/xorg/xserver/-/issues #1785
https://gitlab.freedesktop.org/xorg/xserver/-/issues/1785
** Also affects: xorg-server via
https://gitlab.freedesktop.org/xorg/xserver/-/issues/1785
Importance: Unknown
Status: Unknown
** Summary changed:
-
/
This update has failed phasing, for oracular only, because of a new crash
stacktrace reported at errors.ubuntu.com: bug 2096653.
Interestingly errors.ubuntu.com even has two hits from a date when the update
would have been in -proposed.
--
You received this bug notification because you are a me
Would be interesting to see if this is fixed by
mesa=24.2.8-1ubuntu1~24.04.1 from noble-proposed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2061118
Title:
Rendering issues in virtual machine
** Changed in: xwayland (Ubuntu)
Status: In Progress => Fix Committed
--
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/2096653
Title:
Xwayland raised SIGSEGV in drmFreeDevice from xwl_g
debdiff for sid (to be synced to plucky)
** Description changed:
+ [ Impact ]
+
+ After applying the patch for bug 2043517, it is now possible for Xwayland to
end up in a situation where it frees memory twice and crashes.
+ Prior to the patch, the code was still wrong but Xwayland got stuck wai
debdiff for jammy
** Patch added: "xwayland_22.1.1-1ubuntu0.16.debdiff"
https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/2096653/+attachment/5853703/+files/xwayland_22.1.1-1ubuntu0.16.debdiff
** Description changed:
[ Impact ]
After applying the patch for bug 2043517, it is now
debdiff for oracular
** Patch added: "xwayland_24.1.2-1ubuntu0.3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/2096653/+attachment/5853700/+files/xwayland_24.1.2-1ubuntu0.3.debdiff
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscri
debdiff for noble
** Patch added: "xwayland_23.2.6-1ubuntu0.3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/2096653/+attachment/5853702/+files/xwayland_23.2.6-1ubuntu0.3.debdiff
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
** Changed in: xwayland (Ubuntu)
Assignee: (unassigned) => Alessandro Astone (aleasto)
** Also affects: xwayland (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: xwayland (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: xwayland (Ubu
Fixed in 24.2.8-1ubuntu1~24.10.1
** Changed in: mesa (Ubuntu Oracular)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2090934
Title:
too many mesa_s
** Changed in: firefox (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2083538
Title:
amdgpu: [mmhub] page fault (src_id:0 ring:8 vmid:6 pasid:32781 / F
> All apps default to Weston window when launched
This is somewhat intended. Graphical toolkits default to using Wayland
over X11. Even if $WAYLAND_DISPLAY is not set, the default `wayland-0`
name will be attempted and if that exists it will be used, regardless of
whether it's a nested compositor
oracular debdiff
** Patch added: "xwayland_24.1.2-1ubuntu0.4.debdiff"
https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/2096653/+attachment/5857262/+files/xwayland_24.1.2-1ubuntu0.4.debdiff
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
Update on this: upstream managed to reproduce (by tweaking the code to
force it to fail) and have identified that an additional patch is
necessary to not crash further later on.
Plucky already includes this patch in 2:24.1.5-1 . Attaching new
debdiffs for the stable series.
--
You received this
jammy debdiff
** Patch added: "xwayland_22.1.1-1ubuntu0.17.debdiff"
https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/2096653/+attachment/5857264/+files/xwayland_22.1.1-1ubuntu0.17.debdiff
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed t
noble debdiff
** Patch added: "xwayland_23.2.6-1ubuntu0.4.debdiff"
https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/2096653/+attachment/5857263/+files/xwayland_23.2.6-1ubuntu0.4.debdiff
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** Changed in: egl-wayland (Ubuntu Oracular)
Assignee: (unassigned) => Alessandro Astone (aleasto)
** Tags added: udeng-6415
--
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/2087
jammy debdiff
** Patch added: "xwayland_22.1.1-1ubuntu0.18.debdiff"
https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/2096653/+attachment/5867366/+files/xwayland_22.1.1-1ubuntu0.18.debdiff
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed t
oracular debdiff
** Patch added: "xwayland_24.1.2-1ubuntu0.5.debdiff"
https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/2096653/+attachment/5867364/+files/xwayland_24.1.2-1ubuntu0.5.debdiff
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
noble debdiff
** Patch added: "xwayland_23.2.6-1ubuntu0.5.debdiff"
https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/2096653/+attachment/5867365/+files/xwayland_23.2.6-1ubuntu0.5.debdiff
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Does this only happen sometimes, or on every user session (log-out &
log-in)?
Please share the system journal:
journalctl -b > journal.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2104938
> Note: the keyboard special keys of my laptop does allows me to change
the brightness of the screen.
That's odd, because both controls use org.gnome.SettingsDaemon.Power
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bu
85 matches
Mail list logo
