** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-550
(Ubuntu)
** Also affects: nvidia-graphics-drivers-545 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://b
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
** Description changed:
+ [ Impact ]
+
+ Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as
+ during install.
+
+ [ Test Plan ]
+
+ 1. Open the default Help app by clicking the question mark icon in the
+ dock or by running 'yelp'.
+
+ 2. Verify it didn't crash and the window
Confirmed this fix is now working:
https://salsa.debian.org/webkit-team/webkit/-/merge_requests/20
--
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/2037015
Title:
Screen corruption of webkit2gtk a
** Changed in: mesa (Ubuntu)
Status: Invalid => 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/2062146
Title:
Raspberry Pi: webkit2gtk apps crash with SIGSEGV in v3d_load_utile
T
** 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/2061856
Title:
Apps are closing immediately instead of launching
To manage notifications about this bu
Please try adding a kernel parameter:
i915.enable_psr=0
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
*** This bug is a duplicate of bug 2060268 ***
https://bugs.launchpad.net/bugs/2060268
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 2060268, so it is being marked as such. Please look
ps in X11 on Raspberry Pi, such as during
install
** Changed in: mesa (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: webkit2gtk (Ubuntu)
Milestone: ubuntu-24.04 => noble-updates
--
You received this bug notification because you are a member of Ubuntu-
There appear to be repeating file system problems so I recommend
investigating those first. I can't tell if it's a harddisk or an optical
drive...
[19894.148839] SQUASHFS error: xz decompression failed, data probably corrupt
[19894.148842] SQUASHFS error: squashfs_read_data failed to read block 0x
Thanks for the bug report. Most likely the problem is an HDMI connection
problem. Please try a new HDMI cable if you can. If you can't then
please try temporarily running the external monitor at a lower
resolution to see if the flicker then goes away.
If the flicker still persists then please atta
*** This bug is a duplicate of bug 2063005 ***
https://bugs.launchpad.net/bugs/2063005
** This bug has been marked a duplicate of bug 2063005
Some shell elements don't respond to touchscreen in Xorg sessions
--
You received this bug notification because you are a member of Ubuntu-X,
which
** Also affects: xorg-server (Ubuntu)
Importance: Undecided
Status: New
** Changed in: xorg-server (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.n
Untested draft fix:
https://salsa.debian.org/webkit-team/webkit/-/merge_requests/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/2037015
Title:
Screen corruption of slides during install on Ra
** Also affects: yelp (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- MiniBrowser crashed with SIGSEGV
+ Raspberry Pi: webkit2gtk apps crash with SIGSEGV in v3d_load_utile
** Changed in: webkit2gtk (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanv
I have a hunch the problems might have started in WebKit 2.43.2 which included
a backport of:
https://github.com/WebKit/WebKit/commit/8b0ce3683045d93cd365e91a4299f7e9babfc126
That's forcing us to take a whole new code path which clearly we're just
discovering is a bit buggy on some platforms.
To
** Bug watch added: bugs.webkit.org/ #272827
https://bugs.webkit.org/show_bug.cgi?id=272827
** Also affects: webkit via
https://bugs.webkit.org/show_bug.cgi?id=272827
Importance: Unknown
Status: Unknown
** No longer affects: ubiquity (Ubuntu)
--
You received this bug notificatio
This looks like a confused installation. The GPU is Intel, but you have
an Nvidia driver installed, and an AMD kernel workaround on the command
line.
But none of that should hurt...
What will hurt is the unsupported "oibaf" packages you have replaced the
official graphics drivers with. Sorry, but
See also bug 2060938.
** Tags added: raspi raspigfx
--
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/2062146
Title:
MiniBrowser crashed with SIGSEGV
To manage notifications about this bug go to:
#0 0x7721ad7c in v3d_load_utile (gpu_stride=16, gpu=0x2840e000,
cpu_stride=4096, cpu=0x1e880f90)
at ../src/broadcom/common/v3d_cpu_tiling.h:108
#1 v3d_move_pixels_general_percpp (gpu=0x28126000, cpu=0x1e800010,
cpu_stride=4096, cpp=4, image_h=768, box=0xf
And webkit2gtk's MiniBrowser has the same crash: bug 2062146
(both in Xorg sessions)
--
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/2037015
Title:
Screen corruption of slides during install on
Thanks for the bug report.
Please try:
1. sudo rm /dev/dri/card0 # to work around bug 2060268, and then log in
again. Did that solve it?
2. When the problem starts happening please open a Terminal and run:
journalctl -b0 > journal.txt
xlsclients > xclients.txt
and attach the resulting
** Tags added: nvidia nvidia-wayland
--
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/2062082
Title:
24.04 Wayland vs Nautilus performance problem
To manage notifications about this bug go to:
ht
--
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/2062082
Title:
24.04 Wayland vs Nautilus performance problem
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+sourc
** Package changed: xorg (Ubuntu) => xserver-xorg-video-vmware (Ubuntu)
** Tags added: vmwgfx
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-vmware in Ubuntu.
https://bugs.launchpad.net/bugs/2061886
Title:
Under VMWare res
"Input/output error" suggests there's a disk problem but I suppose such
an error could occur in any kernel driver.
Next time the error pops up, please run:
journalctl -b0 > journal.txt
and attach the resulting text file here.
** Package changed: xorg-server (Ubuntu) => linux (Ubuntu)
** Chan
** Tags removed: lunar
** Tags added: noble
--
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/2038313
Title:
MESA-INTEL: warning: Haswell Vulkan support is incomplete
To manage notifications about
*** This bug is a duplicate of bug 2038313 ***
https://bugs.launchpad.net/bugs/2038313
Thanks for the bug report. I suppose it's possible all these issues are
related, but we shouldn't assume they are so quickly...
The Vulkan error message is being tracked in bug 2038313. As for
Nextcloud, Vi
*** This bug is a duplicate of bug 1861609 ***
https://bugs.launchpad.net/bugs/1861609
Patrick and Rich; both of your logs look like bug 1858336 which
redirects to bug 1861609 but I'm not sure that's right for everyone...
Also Patrick; yours looks like it is caused by a broken/missing Nvidia
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)
** Tags added: gamma nightlight
--
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/2061172
Title:
the nightlight doesn't work
To manage notific
** Bug watch added: gitlab.gnome.org/GNOME/gtk/-/issues #6542
https://gitlab.gnome.org/GNOME/gtk/-/issues/6542
** Changed in: gtk
Status: Fix Released => Unknown
** Changed in: gtk
Remote watch: gitlab.gnome.org/GNOME/gtk/-/issues #6624 =>
gitlab.gnome.org/GNOME/gtk/-/issues #6542
--
*** This bug is a duplicate of bug 2059847 ***
https://bugs.launchpad.net/bugs/2059847
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 2059847, so it is being marked as such. Please look
*** This bug is a duplicate of bug 2060659 ***
https://bugs.launchpad.net/bugs/2060659
Thanks for the bug report. These issues have already been reported in
bug 2060659 and bug 2060268.
Please be sure to report each issue as a separate bug in future.
** Package changed: xorg (Ubuntu) => mutt
Yelp also crashes soon after displaying the corruption: bug 2060938
--
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/2037015
Title:
Screen corruption of slides during install on Raspberry Pi
To m
** Tags added: noble
** Summary changed:
- Desktop environment fails to start
+ [nouveau] Xorg desktop environment fails to start with QEMU GPU passthrough
to NVIDIA
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you a
** Changed in: webkit2gtk (Ubuntu)
Status: Confirmed => In Progress
** Changed in: webkit2gtk (Ubuntu)
Importance: Undecided => Medium
** Changed in: webkit2gtk (Ubuntu)
Milestone: None => ubuntu-24.04
--
You received this bug notification because you are a member of Ubuntu-X,
whi
The integrated GPU of your Intel i5-6400 is all that I can see, which
understandably may not be enough to run Davinci. What error do you see
exactly?
Also note that errors have been reported on your installation media,
probably meaning the USB drive used to install Ubuntu was faulty. You
may want
** Changed in: webkit2gtk (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
--
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/2037015
Title:
Screen corruption of slides dur
*** This bug is a duplicate of bug 2060354 ***
https://bugs.launchpad.net/bugs/2060354
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 2060354, so it is being marked as such. Please look
A large chunk just landed upstream:
https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/967
I'm not sure if that's the only fix required...
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xwayland in Ubuntu.
https://bugs.launchpad.net/b
That's expected; it's just a different graphics memory layout with a
different GPU.
** Summary changed:
- Screen corruption of slides during install on Raspberry Pi 4
+ Screen corruption of slides during install on Raspberry Pi
--
You received this bug notification because you are a member of U
** Also affects: xwayland (Ubuntu)
Importance: Undecided
Status: New
** Changed in: xwayland (Ubuntu)
Status: New => Triaged
** Changed in: xwayland (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu-X,
which is su
** Also affects: xorg-server via
https://gitlab.freedesktop.org/xorg/xserver/-/issues/1659
Importance: Unknown
Status: Unknown
** Changed in: xorg-server (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu-X,
which is
It seems it's the *fix* for the CVE that's crashing in version
2:21.1.4-2ubuntu1.7~22.04.9 rather than the CVE itself.
https://launchpad.net/ubuntu/+source/xorg-
server/2:21.1.4-2ubuntu1.7~22.04.9
** Also affects: xorg-server (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also a
** Changed in: xorg-server (Ubuntu)
Importance: Undecided => High
--
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/2060354
Title:
Segfaults and assertion failures in Xorg's render/glyph.
Sounds like CVE-2024-31083 mentioned in
https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1463 and
fixed in Xorg 21.1.12.
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-31083
** Information type changed from Public to Public Security
** Tags added: jammy mantic nobl
** Summary changed:
- Horizonral line artifact/ghosting when scaling windows to a certain width
+ [Intel N95] Horizonral line artifact/ghosting when scaling windows to a
certain width
** Package changed: xorg (Ubuntu) => mesa (Ubuntu)
** Package changed: mesa (Ubuntu) => linux (Ubuntu)
** Pack
** Package changed: xorg (Ubuntu) => mutter (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/2060204
Title:
Resolution drop on third monitor on USB C
To manage notifications about this b
Errors messages about buggy ACPI BIOS implementations are normal and not
something we can fix. Although those messages will be hidden when bug
1970069 is fully resolved.
Is there something specific you would like this bug to be about, like
the bluetoothd messages?
** Package changed: xorg (Ubuntu
Please rename the video using Latin characters because Launchpad can't
handle other character sets and we're unable to download the video.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are a m
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
It appears the recurring problem here is:
simple-framebuffer simple-framebuffer.0: drm_WARN_ON(map->is_iomem)
WARNING: CPU: 19 PID: 4751 at drivers/gpu/drm/drm_gem_shmem_helper.c:319
drm_gem_shmem_vmap+0x1a5/0x1e0
** Summary changed:
- Xorg crash
+ Crash
** Package changed: xorg (Ubuntu) =
Please see bug 2056160 for the time being.
--
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/2043915
Title:
Booting into live session results in try/install page white screen
To manage notificatio
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
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
Here's the MR:
https://salsa.debian.org/multimedia-team/intel-vaapi-driver/-/merge_requests/5
But it looks like no one has done a release of it for a couple of years.
You might need to request Debian developers look at it (I'm not
officially one of them).
--
You received this bug notification be
** Tags added: fixed-in-mesa-24.1 fixed-upstream
--
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/2054851
Title:
[radeon] gnome-shell and Xorg both crash with SIGSEGV in
radeon_bo_reference()
T
** Changed in: intel-vaapi-driver (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: intel-vaapi-driver (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to intel
If it looks correct in GNOME then please briefly log into GNOME and run:
xrandr --verbose > gnome-xrandr.txt
and attach the resulting text file here.
Also if KDE has any monitor colour profile settings then try toggling
those.
** Summary changed:
- Notebook screen the look is "matte"
+ Note
** Changed in: intel-vaapi-driver (Ubuntu)
Importance: Undecided => Low
** Changed in: intel-vaapi-driver (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to intel-vaapi-driver in Ubuntu.
https://bugs.launch
*** This bug is a duplicate of bug 2055176 ***
https://bugs.launchpad.net/bugs/2055176
It looks like your system experienced another issue too: sublime_text
used over 40GB of RAM today around 4:01pm, before that caused other
parts of the system to fail and the kernel stepped in and killed
subl
** Changed in: xwayland (Ubuntu)
Importance: Undecided => High
--
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/2055176
Title:
Xwayland crashed with SIGSEGV in ProcXTestFakeInput()
To mana
*** This bug is a duplicate of bug 2055176 ***
https://bugs.launchpad.net/bugs/2055176
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 2055176, so it is being marked as such. Please look
Can you narrow down the list of pull requests to just those associated
with Launchpad bugs? Or open additional bugs if required? The
requirements feel too vague otherwise, and we're only weeks away from
release at which point all changes will need bug IDs anyway.
** Tags added: noble
--
You rec
*** This bug is a duplicate of bug 1961508 ***
https://bugs.launchpad.net/bugs/1961508
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 1961508, so it is being marked as such. Please look
Thanks for the bug report. Please attach a screenshot of the problem and
also run this command to automatically gather more system information:
apport-collect 2057964
** Package changed: xorg-server (Ubuntu) => gnome-shell-extension-appindicator
(Ubuntu)
** Tags added: jammy nvidia
** Chang
** Bug watch added: Debian Bug tracker #1064123
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064123
** Also affects: mesa (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064123
Importance: Unknown
Status: Unknown
--
You received this bug notification because
Thanks for the bug report. This is a common problem and is almost always
due to a bad connection or low quality cable. Please try unplugging and
replugging the cable at both ends. If that doesn't solve it then please
try a different cable. For better performance and reliability on a
Lenovo G50-70,
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
This looks like just bad UI design. The option to include the pointer
already exists but it's disabled by default and not obvious because the
button looks exactly like the mouse pointer itself (bottom right of the
dialog). Please select that option in the screen recorder dialog before
starting the
This suggests the menu is an override-redirect X11 window, so perhaps
appearing on all workspaces is 'correct' and it is a bug in Firefox.
Please also try logging into a Wayland session.
** Package changed: xorg (Ubuntu) => firefox (Ubuntu)
** Changed in: firefox (Ubuntu)
Status: New => I
*** This bug is a duplicate of bug 1961508 ***
https://bugs.launchpad.net/bugs/1961508
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 1961508, so it is being marked as such. Please look
I encountered the same kind of corruption on AMD graphics last night.
Using Firefox on Wayland in Ubuntu 24.04.
--
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/2055351
Title:
[amdgpu] Firefox and
** Also affects: xorg-server (Ubuntu Noble)
Importance: Medium
Status: Triaged
** Also affects: xorg-server (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: xorg-server (Ubuntu Jammy)
Status: New => In Progress
** Changed in: xorg-server (Ubuntu Noble)
Similar, yes. But we can't treat them as the same bug when one was
declared fixed in Firefox in September 2023, and the other declared a
problem in Firefox in February 2024.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https:/
The fix is also missing from Noble so please start with Noble.
** Bug watch added: gitlab.freedesktop.org/xorg/xserver/-/issues #1387
https://gitlab.freedesktop.org/xorg/xserver/-/issues/1387
** Also affects: xorg-server via
https://gitlab.freedesktop.org/xorg/xserver/-/issues/1387
Impor
We can't track Archlinux bugs here.
Everyone please check your xwayland package versions because bug 2055176
may have affected Noble until recently, and still does affect Mantic.
You need xwayland >= 23.2.4 to fix that.
--
You received this bug notification because you are a member of Ubuntu-X,
** Also affects: xwayland (Ubuntu)
Importance: Undecided
Status: New
** Also affects: xorg-server via
https://gitlab.freedesktop.org/xorg/xserver/-/issues/1648
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu-X,
w
Does the problem occur if Firefox is never opened?
Do you find any files in /var/crash ?
** 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
Found it:
https://gitlab.freedesktop.org/xorg/xserver/-/issues/1574
The first fix went into Xwayland 23.2.1 but that also needed fixing in
23.2.4.
** Changed in: xwayland (Ubuntu)
Status: Incomplete => New
** Changed in: xwayland (Ubuntu)
Status: New => Fix Released
** Tags added:
Thanks for the additional information. It looks like we have a better
idea of the crash location now:
?? ()
ProcXTestFakeInput (client=) at ../Xext/xtest.c:440
Dispatch () at ../dix/dispatch.c:545
dix_main (envp=, argv=, argc=) at
../dix/main.c:271
main (argc=, argv=, envp=) at
../dix/stubmain.c
Please open the Additional Drivers app and use it to install an Nvidia
driver. Then reboot and tell us if the problem persists.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
** Summary changed:
- Xorg freeze
+ Freeze
--
You received this b
This sounds like a per-application bug, but also something we would like
gnome-font-viewer to handle.
** Changed in: xorg (Ubuntu)
Importance: Undecided => Low
** Summary changed:
- Choosing font
+ Apps can't handle tens of thousands of fonts installed at once
** Package changed: xorg (Ubunt
This bug is closed. But also please refrain from reporting multiple
different issues at the same time.
The current problem with a blank window is being tracked in:
https://github.com/canonical/ubuntu-desktop-installer/issues/2418
For everything else, please open new bugs.
** Bug watch added: git
mesa (24.0.2-1ubuntu1) noble; urgency=medium
* Merge from Debian.
* radeon-fix-gnome-shell-crash.diff: Fix a regression crashing
gnome-shell. (LP: #2054851)
-- Timo Aaltonen Thu, 29 Feb 2024 09:40:21 +0200
** Changed in: mesa (Ubuntu)
Status: Confirmed => Fix Committed
** Cha
Bug 2016925 suggests the problem went away in Ubuntu 23.10
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => New
** Tags added: amdgpu
** Summary changed:
- firefox screen corruption on Athlon 200GE after fresh installation of 22.04.4
+ [amdgpu] Firefox screen corruption on Athlo
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 2055351
When reporting bugs in the future please use apport by using 'ubuntu-
The bucket is new for 2:23.2.0-1ubuntu0.4 anyway. If the crash also
happened before then and just landed in a different bucket then it
wouldn't be a regression-update.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xwayland in Ubuntu.
https://bu
The crash is:
https://errors.ubuntu.com/oops/db625975-d614-11ee-ba81-fa163e171f02
which redirects to:
https://errors.ubuntu.com/bucket/?id=failed%3A/usr/bin/Xwayland%3A6%3A/usr/lib/x86_64-linux-
gnu/libc.so.6%2B1c8e6%3A/usr/lib/x86_64-linux-
gnu/libc.so.6%2B8b7%3A/usr/bin/Xwayland%2B1479ac%3A/us
Please don't attach crash files to bugs because it's a security risk for
yourself. Instead run:
ubuntu-bug /var/crash/YOURFILE.crash
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Invalid
** Attachment removed: "_usr_bin_nautilus.1000.crash"
https
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
Thanks for the bug report.
Each time you experience a failed boot followed by a successful boot
please run:
journalctl -b-1 > failedboot.txt
And each time you experience a slow boot please run:
journalctl -b0 > slowboot.txt
and attach the resulting text files here.
** Summary changed:
-
There are lots of amdgpu errors in your system log, so let's start
there.
** Tags added: amdgpu
** Package changed: xorg (Ubuntu) => linux-hwe-6.5 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.n
** Tags added: bionic jammy mantic noble
** Summary changed:
- Xorg crashed with assertion failure (usually in a VM) at [privates.h:121/122:
dixGetPrivateAddr: Assertion `key->initialized' failed] and call stack comes
from DRIMoveBuffersHelper
+ Xorg crashed with assertion failure (usually in a
*** This bug is a duplicate of bug 1861609 ***
https://bugs.launchpad.net/bugs/1861609
** This bug has been marked a duplicate of bug 1861609
Xorg crashed with assertion failure (usually in a VM) at
[privates.h:121/122: dixGetPrivateAddr: Assertion `key->initialized' failed]
and call stac
*** This bug is a duplicate of bug 1861609 ***
https://bugs.launchpad.net/bugs/1861609
** This bug has been marked a duplicate of bug 1861609
Xorg crashed with assertion failure (usually in a VM) at
[privates.h:121/122: dixGetPrivateAddr: Assertion `key->initialized' failed]
and call stac
CurrentDmesg.txt shows the Nvidia kernel driver crashing, which is
probably not helpful. But also...
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 st
** Summary changed:
- gnome-shell crashed with SIGSEGV in radeon_bo_reference()
+ gnome-shell (and Xorg) crashes with SIGSEGV in radeon_bo_reference()
** Tags added: rls-nn-incoming
** Summary changed:
- gnome-shell (and Xorg) crashes with SIGSEGV in radeon_bo_reference()
+ [radeon] gnome-shell
*** This bug is a duplicate of bug 2054851 ***
https://bugs.launchpad.net/bugs/2054851
Yes the addresses in your crash match those of bug 2054851.
[ 149.655] (EE) 2: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
(radeon_drm_winsys_create+0x27e5) [0x7a53429ea2e5]
[ 149.658] (EE) 3: /usr/l
*** This bug is a duplicate of bug 2054851 ***
https://bugs.launchpad.net/bugs/2054851
The log in comment #1 shows Xorg crashing in radeonsi_dri.so, so this
might be bug 2054851. But also...
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like som
101 - 200 of 1011 matches
Mail list logo
