Verified fixed in version 2:22.1.1-1ubuntu0.2 on jammy (arm64 Xilinx
Kria board).
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xwayland in Ubuntu.
** Summary changed:
- Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()
+ Crash with SIGABRT in _iris_batch_flush from iris_fence_flush()
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1139
https://gitlab.gnome.org/GNOME/mutter/-/issues/1139
** Also affects: mutter via
https://gitlab.gnome.org/GNOME/mutter/-/issues/1139
Importance: Unknown
Status: Unknown
--
You received this bug notification because
** Also affects: nvidia-graphics-drivers-470 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1799679
Title:
Nvidia
** Summary changed:
- Brightness bar not working properly
+ Brightness bar not working properly on HP EliteBook 8460p
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
Please describe the problem you would like to report in more detail. And
if you have multiple problems to report then please ensure each is
logged as a separate bug.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug
There are no alternate drivers you can or should install for Intel
graphics. The drivers are built-in already, and will get automatic
updates.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Invalid
--
You received this bug notification because you are a
Thanks for the bug report.
Next time the bug happens, please:
1. Use the workaround to recover.
2. Run:
journalctl -b0 > journal.txt
3. Attach the resulting text file here.
** Tags added: radeon
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)
** Changed in: mutter (Ubuntu)
** Tags removed: fixed-upstream
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1848951
Title:
High CPU when just moving the mouse
To manage notifications about this bug go to:
** Changed in: mesa-demos (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa-demos in Ubuntu.
https://bugs.launchpad.net/bugs/1753677
Title:
es2gears_wayland on mutter sticks to 119 FPS
** Changed in: xorg-server (Ubuntu)
Status: Fix Committed => Fix Released
--
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/1823516
Title:
Nvidia driver installed but X apps are using
Fixed in focal updates and all later releases.
** Changed in: xorg-server (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1870512
Title:
Fixed in Ubuntu 22.04 and later.
** Changed in: libx11 (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libx11 in Ubuntu.
https://bugs.launchpad.net/bugs/1941962
Title:
pulseaudio crashed
Please don't install xserver-xorg-video-intel because it is old and
buggy.
The latest (and only) driver is the one that ships with Ubuntu by
default.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Invalid
--
You received this bug notification because
Thanks for the bug report.
You seem to have an unsupported version of libdrm installed:
libdrm-amdgpu1 2.4.110.5+1038 [origin: ubuntu focal]
libdrm-common 2.4.110.5+1038 [origin: ubuntu focal]
libdrm-intel1 2.4.110.5+1038 [origin: ubuntu focal]
libdrm-nouveau2 2.4.110.5+1038 [origin: ubuntu
Thanks for the bug report.
It appears you're using a Wayland session which doesn't use the Xorg
config file you have written. Please try selecting 'Ubuntu on Xorg' from
the login screen instead.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
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. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell
*** This bug is a duplicate of bug 1965563 ***
https://bugs.launchpad.net/bugs/1965563
** This bug has been marked a duplicate of bug 1965563
GNOME apps crash with "Protocol error" in NVIDIA Wayland sessions
--
You received this bug notification because you are a member of Ubuntu-X,
** No longer affects: gnome-shell (Ubuntu)
** Summary changed:
- gnome-extensions-app fails to start [Error reading events from display:
Protocol error]
+ GNOME apps crash with "Protocol error" in NVIDIA Wayland sessions
** No longer affects: gtk+3.0 (Ubuntu)
** Changed in: egl-wayland
*** This bug is a duplicate of bug 1969959 ***
https://bugs.launchpad.net/bugs/1969959
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1969959, so it is being marked as such. Please
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1988484
Title:
Holding down volume keys sometimes crashes xorg
To manage
Thanks for the bug report. I don't think crocus (which we do use
automatically in Ubuntu 22.04) can solve this because the GLSL
requirements come from the hardware.
Have you tried regular Ubuntu 22.04 with GNOME that defaults to Wayland instead?
https://ubuntu.com/download/desktop
** Package
** Summary changed:
-
/usr/lib/xorg/Xorg:6:drmmode_sprite_do_set_cursor:drmmode_sprite_move_cursor:ProcXTestFakeInput:Dispatch:dix_main
+ Xorg crashed with SIGABRT in drmmode_sprite_do_set_cursor() from
drmmode_sprite_move_cursor() from ProcXTestFakeInput() from Dispatch() from
dix_main()
--
These Ubuntu releases are also no longer supported.
** Changed in: xorg-server (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/659793
Title:
*** This bug is a duplicate of bug 1988275 ***
https://bugs.launchpad.net/bugs/1988275
Ubuntu 19.04 is no longer supported but the issue continues in bug
1988275.
** This bug has been marked a duplicate of bug 1988275
Xephyr does not recognize keyboard or mouse
--
You received this bug
** Summary changed:
- Xephyr does not recognize keyboard or mouse
+ Xephyr does not recognize keyboard or mouse [unrecognised device identifier]
** Bug watch added: gitlab.freedesktop.org/xorg/xserver/-/issues #1289
https://gitlab.freedesktop.org/xorg/xserver/-/issues/1289
** Also affects:
Patch for jammy
** Patch added: "xwayland_22.1.1-1ubuntu0.2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/1987628/+attachment/5612505/+files/xwayland_22.1.1-1ubuntu0.2.debdiff
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
** Description changed:
+ [Impact]
+
Xwayland fails to start on Xilinx:
/usr/bin/Xwayland: symbol lookup error: /usr/bin/Xwayland: undefined
symbol: gbm_bo_get_fd_for_plane
This is particularly important since it prevents gnome-shell from
starting Wayland sessions.
+
+ [Test
xwayland (2:22.1.3-2) unstable; urgency=medium
[ Daniel van Vugt ]
* Add xwayland-Detect-gbm_bo_get_fd_for_plane-at-runtime.patch
-- Timo Aaltonen Thu, 25 Aug 2022 13:03:43 +0300
** Changed in: xwayland (Ubuntu)
Status: In Progress => Fix Released
** Also affects: xwayl
** Tags added: nvidia
--
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-extensions-app fails to start [Error reading events from
display: Protocol error]
To manage
Thanks. It sounds like the problem is now happening in Wayland sessions.
Since essentially the same bug was first reported in Xorg that would
make this a kernel bug.
Please try adding this line to /etc/environment:
MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0
and then reboot. It will change the way the
** Tags added: jammy
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1799679
Title:
Nvidia driver causes Xorg to use 100% CPU and huge lag when dragging
OpenGL app
Nvidia's latest assessment is that this is indeed a driver bug so we
don't need to keep the mutter and metacity tasks open here...
https://gitlab.gnome.org/GNOME/mutter/-/issues/2233#note_1538392
** Also affects: nvidia-graphics-drivers-515 (Ubuntu)
Importance: Undecided
Status: New
Thanks for the bug report.
Please run these commands:
journalctl -b0 > journal.txt
xrandr --verbose > xrandr.txt
and attach the resulting text files here.
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
** Changed in: xorg-server (Ubuntu)
Status: New => Incomplete
--
And to Debian:
https://salsa.debian.org/xorg-team/wayland/xwayland/-/merge_requests/2
--
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/1987628
Title:
Xwayland fails to start on Xilinx: symbol
Proposed fix:
https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/946
--
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/1987628
Title:
Xwayland fails to start on Xilinx: symbol lookup
)
Importance: High
Assignee: Daniel van Vugt (vanvugt)
Status: In Progress
** Tags: jammy wayland wayland-session xilinx
** Description changed:
Xwayland fails to start on Xilinx:
/usr/bin/Xwayland: symbol lookup error: /usr/bin/Xwayland: undefined
symbol: gbm_bo_get_fd_for_plane
** Tags added: fixed-in-22.1.5
** Changed in: mesa (Ubuntu)
Status: Triaged => Fix Released
** Tags added: rls-jj-incoming
--
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/1972977
Title:
Thanks for the bug report.
Can you please attach a photo to confirm whether the system is waking to
the lock screen or login screen?
If it's really the login screen then please check for crashes by:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment
**
On Linux you have two or three graphics drivers all working at the same
time at different levels:
* Kernel: i915
* Mesa: iris
* Xorg: modeset (replaces the old "intel" driver)
To confirm which Xorg driver is in use you can find it in the Xorg
system log messages:
journalctl -b0
Thanks for the bug report. I can see radeon kernel debug messages in the
log even though debugging doesn't seem to be enabled. This may indicate
the bug is in the radeon kernel driver.
** Tags added: radeon
** Summary changed:
- lag in animations and some other bugs
+ [radeon] lag in
The error at the bottom of DpkgTerminalLog.txt looks like either disk
corruption or just network corruption in downloading the update.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1987169
Those error messages usually refer to bugs in the BIOS rather than bugs
in Ubuntu.
** Summary changed:
- mtds device is empty
+ [Dell Inspiron 5570] ACPI errors on boot
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of
Thanks for the bug report.
The reason you have no resolution options is because the system has
booted in recovery/safe mode which disables the graphics driver. You can
tell this by the "recovery nomodeset" kernel parameters. Sometimes
Ubuntu gets stuck in recovery mode if it was used during
Thanks for the bug report. Please check to see if some part of the
system has crashed:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.
2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID
> problem dissapears if application window not maximized
Do you mean full screen?
** Tags added: cursor radeon
** Summary changed:
- mouse not visible on other screens
+ [radeon] mouse not visible on other screens
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)
--
You received this bug
Thanks for the bug report. It sounds like the kernel was unable to
retrieve the EDID data from the monitor. This often happens with analog
VGA connectors so I assume that's the issue... Are you able to try the
mini-DisplayPort connector instead?
** Package changed: xorg (Ubuntu) => linux
*** This bug is a duplicate of bug 1899235 ***
https://bugs.launchpad.net/bugs/1899235
** Summary changed:
- Touchpad stops functioning after wakeup
+ [Dell Inspiron 3180] Touchpad stops functioning after wakeup
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** This bug has been
That config section you mention needs to be removed entirely because the
"intel" driver is buggy, unsupported and was only designed to handle
much older Intel GPUs.
Sadly that does mean you lose the "TearFree" option. It has been
requested in the new driver for some time
Thanks for the bug report. Next time the problem happens, after
rebooting please run:
journalctl -b-1 > prevboot.txt
and attach the resulting text file here.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug
Thanks for the bug report.
It appears you're using the old unsupported (and buggy) 'intel' graphics
driver. Please remove any config files you have loading that and even
consider removing the entire driver:
sudo apt remove xserver-xorg-video-intel
Alternatively, please just log into 'Ubuntu'
** Summary changed:
- ubuntu dock bug
+ Can't click context menu items when they cover the dock
** Package changed: xorg (Ubuntu) => gnome-shell-extension-ubuntu-dock
(Ubuntu)
** Summary changed:
- Can't click context menu items when they cover the dock
+ Can't click context menu items when
At a guess, you have a Xorg config file but are using Wayland by default
(like most users of 22.04). Please try selecting 'Ubuntu on Xorg' on the
login screen.
** Tags added: jammy
** Package changed: xorg (Ubuntu) => libinput (Ubuntu)
** Also affects: xserver-xorg-input-libinput (Ubuntu)
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. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell
Thanks for the bug report. Please attach a video showing the problem.
The easiest way to do that is to press PrtScn.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
** Tags added: nouveau
** Summary changed:
- display resolution max is 1920x1080, video card supports higher resolution,
would like 2560x1440
+ [nouveau] display resolution max is 1920x1080, video card supports higher
resolution, would like 2560x1440
** Package changed: xorg (Ubuntu) => linux
Thanks for the bug report. Can you provide a photo of the problem?
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Thanks for the bug report. I think we need proper debug symbols to get a
more accurate stack trace. So please just follow these steps:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.
2. If step 1 failed then look
Thanks for the bug report. This may be caused by:
* The Intel kernel graphics crash mentioned in CurrentDmesg.txt
* An Nvidia driver problem (if the HDMI port is wired to the Nvidia GPU)
* Something else
Firstly, to see if we can stop the Intel graphics crash from happening
please try adding
When I say "Wayland in Mutter" I do mean GNOME. That's what we are
involved in the development of, and recommend as the primary Ubuntu
environment.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
** Summary changed:
- gnome-shell crashed with SIGSEGV in crocus_begin_query() from
crocus_begin_query() from crocus_end_query() from crocus_end_query() from
tc_call_end_query()
+ gnome-shell crashed (out of memory) with SIGSEGV in crocus_begin_query() from
crocus_begin_query() from
I misinterpreted mesa's branching structure. The commit is indeed in
22.2 (not tagged yet).
** Tags removed: fixed-in-23
** Tags added: fixed-in-22.2
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
Maybe open a new bug from an affected system if you find any similar
bugs in more recent releases.
** Changed in: xorg-server (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
** Bug watch added: Debian Bug tracker #1012474
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012474
** Also affects: xorg (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012474
Importance: Unknown
Status: Unknown
--
You received this bug notification
This is certainly not a xorg bug. My first guess would be libnotify.
** Package changed: xorg (Ubuntu) => libnotify (Ubuntu)
--
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/1983183
Title:
miss
I agree... it's just desktop team policy requested by seb128.
** Changed in: mesa (Ubuntu)
Status: Fix Committed => Triaged
--
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/1972977
Title:
** Package changed: xorg (Ubuntu) => ubuntu
--
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/1983000
Title:
IDK
To manage notifications about this bug go to:
Please explain what the bug is you would like to report.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
Only fixed in Mesa 23 right now but I would expect to see it in 22.x
--
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/1972977
Title:
gnome-shell crashed with SIGSEGV in crocus_begin_query() from
Upstream says the crash is caused by a leak and reviewing the Mesa code
seems to support that theory. The fix is:
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/17731
** Tags added: gnome-shell-leak
** Changed in: mesa (Ubuntu)
Importance: Undecided => High
** Changed in: mesa
** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #6887
https://gitlab.freedesktop.org/mesa/mesa/-/issues/6887
** Also affects: mesa via
https://gitlab.freedesktop.org/mesa/mesa/-/issues/6887
Importance: Unknown
Status: Unknown
--
You received this bug notification
*** This bug is a duplicate of bug 1982650 ***
https://bugs.launchpad.net/bugs/1982650
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1982650, so it is being marked as such. Please
*** This bug is a duplicate of bug 1982650 ***
https://bugs.launchpad.net/bugs/1982650
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1982650, so it is being marked as such. Please
*** This bug is a duplicate of bug 1982650 ***
https://bugs.launchpad.net/bugs/1982650
Same machine so assume it's the same bug.
** This bug has been marked a duplicate of bug 1982650
screen flickering
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:
apport-collect 1982667
When reporting bugs in the future please use apport by using 'ubuntu-
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. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
--
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/1982113
Title:
My screen is horizontally divided into two parts.
To manage notifications
Thanks for the bug report.
Next time the problem happens, please:
1. Wait 10 seconds.
2. Reboot.
3. Run: journalctl -b-1 > prevboot.txt
4. Attach the resulting text file here.
And if possible please use Ubuntu 22.04 instead:
https://ubuntu.com/download/desktop
** Package changed: xorg
Sounds similar to an issue that people with HP AIO desktop displays
reported in the past. That one was a hardware flaw/quirk and to get it
working properly the owners had to change between UEFI and legacy BIOS
modes. Doing so likely also requires reinstalling Ubuntu.
--
You received this bug
Yes, please use Wayland if you can. It's usually the login option
labelled "Ubuntu".
I've been testing and fixing DisplayLink for Wayland in Mutter for much
of this year so I would expect it to be a better experience than Xorg by
now.
--
You received this bug notification because you are a
Thank you for reporting this bug to Ubuntu.
Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing
** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #6885
https://gitlab.freedesktop.org/mesa/mesa/-/issues/6885
** Also affects: mesa via
https://gitlab.freedesktop.org/mesa/mesa/-/issues/6885
Importance: Unknown
Status: Unknown
--
You received this bug notification
If the above command does not work then please run:
journalctl -b0 > journal.txt
lspci -k > lspci.txt
and attach the resulting text files along with a photo of the issue
here.
** Package changed: xserver-xorg-video-intel (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Please try these separately:
* Add kernel parameter: intel_iommu=igfx_off
* Use the 'Additional Drivers' app to install an official Nvidia
driver.
** Summary changed:
- Xorg freeze
+ After reboot, the screen was blank/black and unresponsive
** Tags added: nouveau
** Package changed: xorg
** Also affects: linux via
https://gitlab.freedesktop.org/drm/amd/-/issues/2088
Importance: Unknown
Status: Unknown
--
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/1979053
Title:
UI
** Tags removed: impish
** Tags added: kinetic
--
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/1746656
Title:
Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from
** Tags removed: impish
** Tags added: jammy
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-amdgpu in Ubuntu.
https://bugs.launchpad.net/bugs/1937015
Title:
Xorg crashed with SIGSEGV in drmmode_set_mode() from
Looks like all recent reports are pointing to bug 1683383 instead so
let's just use that.
** Changed in: xorg-server (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to the bug report.
No crashes reported since Ubuntu 21.04 so consider it fixed.
** Changed in: xorg-server (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
** Tags removed: impish
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/36812
Title:
Keyboard layout change on hotkeys press instead of release and do not
work well with shortcuts
To manage
** Tags removed: impish
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1683383
Title:
Keyboard layout change on hotkeys press instead of release and do not
work well with shortcuts
** Tags removed: impish
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1811023
Title:
Xorg aborts with ../../../../dix/privates.c:384:
dixRegisterPrivateKey: Assertion
** Tags removed: impish
--
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/1922414
Title:
ssh-agent fails to start (has_option: command not found)
To manage notifications about this bug go to:
** Changed in: wayland (Ubuntu)
Status: Fix Committed => Fix Released
--
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/1964274
Title:
Xwayland crashes with wl_display@1: error 1:
** Tags removed: impish
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xkeyboard-config in Ubuntu.
https://bugs.launchpad.net/bugs/1969396
Title:
Right Alt not working reliably as compose key unless the layout in
effect is first in the
** Changed in: libinput (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1950471
Title:
Touchpad on HP Spectre x360 gets into unusable state
To manage
** Tags removed: hirsute impish
--
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/1971124
Title:
gnome-shell crashed with SIGSEGV in v3d_job_submit() from v3d_flush()
from v3d_pipe_flush()
To
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/1970473
Title:
[radeon] Xorg crashed with
** Also affects: intel-media-driver (Ubuntu)
Importance: Undecided
Status: New
** Changed in: intel-media-driver (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to intel-media-driver in Ubuntu.
Wow, yes installing intel-media-va-driver-non-free fixes it.
** Also affects: intel-media-driver-non-free (Ubuntu)
Importance: Undecided
Status: New
** Changed in: intel-media-driver-non-free (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because
901 - 1000 of 9936 matches
Mail list logo
