The crash (bug 2062146) is now awkwardly entangled with this bug. It
occurs at the same time as, or usually instead of corruption. Bisected
in Mesa:
https://gitlab.freedesktop.org/mesa/mesa/-/issues/11033#note_2385595
Prior to that regression, I still believe the corruption probably
started
** No longer affects: yelp (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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
Status
Also tracking in https://gitlab.freedesktop.org/mesa/mesa/-/issues/11008
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2061118
Title:
Rendering issues in virtual machines
Bug 2061079 being so similar makes me think long term we will find that
GTK4 is doing something wrong. We just don't know what it's doing wrong
yet.
** Changed in: gtk4 (Ubuntu Noble)
Status: Invalid => Confirmed
** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #11008
Users of the Nvidia 470 driver please see bug 2061079.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2061118
Title:
Rendering issues in virtual machines (GTK ngl backend)
Generalised to cover non-VMware (bug 2063923).
** Summary changed:
- Rendering issues in vmware with 3d on (GTK ngl backend)
+ Rendering issues in virtual machines (GTK ngl backend)
** Tags added: noble vmwgfx
--
You received this bug notification because you are a member of Ubuntu
Touch
*** This bug is a duplicate of bug 2061118 ***
https://bugs.launchpad.net/bugs/2061118
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 2061118, so it is being marked as such. Please
I can see 'gjs' crashing constantly so please try:
gnome-extensions disable d...@rastersoft.com
If that doesn't fix it then please provide a video of the problem.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)
** Tags added: focus
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2063831
Title:
Clicking on bottom half of
More than rotated framebuffers, defaulting to simpledrm means Plymouth
doesn't know the physical monitor dimensions. So it uses heuristics and
that leads to the logo scale not matching the login screen which would
be a regression of bug 2054769. Actually it already happens on some slow
booting
*** This bug is a duplicate of bug 2047975 ***
https://bugs.launchpad.net/bugs/2047975
** Summary changed:
- package systemd-resolved 252.5-2ubuntu3 failed to install/upgrade: installed
systemd-resolved package post-installation script subprocess returned error
exit status 1
+ package
** Summary changed:
- package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade: installed
systemd-resolved package post-installation script subprocess returned error
exit status 1
+ package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade: installed
systemd-resolved package
*** This bug is a duplicate of bug 2047975 ***
https://bugs.launchpad.net/bugs/2047975
** This bug is no longer a duplicate of bug 2046856
package systemd-resolved 252.5-2ubuntu3 failed to install/upgrade: installed
systemd-resolved package post-installation script subprocess returned
*** This bug is a duplicate of bug 2047975 ***
https://bugs.launchpad.net/bugs/2047975
** Summary changed:
- package systemd-resolved 253.5-1ubuntu6.1 failed to install/upgrade:
installed systemd-resolved package post-installation script subprocess returned
error exit status 1
+ package
*** This bug is a duplicate of bug 2047975 ***
https://bugs.launchpad.net/bugs/2047975
** Summary changed:
- package systemd-resolved 255.4-1ubuntu8 failed to install/upgrade: installed
systemd-resolved package post-installation script subprocess returned error
exit status 1
+ package
It looks like the kernel ran out of memory and the main culprit is a
'java' process. This is not an Ubuntu bug.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** 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
Touch seeded packages, which is subscribed to xorg
** 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
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
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2037015
Title:
Screen
** Changed in: mesa (Ubuntu)
Status: Invalid => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2062146
Title:
Raspberry Pi: webkit2gtk apps crash with SIGSEGV
** Package changed: xorg (Ubuntu) => ubuntu
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2061856
Title:
Apps are closing immediately instead of launching
Status in
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
Touch seeded packages, which is
*** 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
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
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
Sorry, I missed the "X11 session" part. Bug confirmed.
** No longer affects: gsettings-desktop-schemas (Ubuntu)
** Summary changed:
- Onscreen keyboard is disabled by default
+ Some shell elements don't respond to touchscreen in Xorg sessions
** Changed in: gnome-shell (Ubuntu)
Importance:
Looks like it's been disabled for at least 6 years:
https://gitlab.gnome.org/GNOME/gsettings-desktop-
schemas/-/blob/master/schemas/org.gnome.desktop.a11y.applications.gschema.xml.in?ref_type=heads
so whether or not it gets toggled automatically is probably up to gnome-
shell.
** Changed in:
Partially confirmed. It looks like the onscreen keyboard is always
disabled by default. You have to enable it in:
Settings > Accessibility > Typing > Screen Keyboard = ON
After I did that, all the features mentioned here started working.
** Package changed: mutter (Ubuntu) => gnome-shell
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
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2037015
Title:
Screen corruption of slides
** 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.
** 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
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,
See also bug 2060938.
** Tags added: raspi raspigfx
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2062146
Title:
MiniBrowser crashed with SIGSEGV
Status in Mesa:
#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,
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
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2037015
Title:
Screen corruption of
No longer in progress. You can get to 100% fixed by adding kernel
parameter 'plymouth.use-simpledrm' but I'm not totally sure that's
something everyone will want.
** Changed in: plymouth (Ubuntu)
Status: In Progress => Triaged
** Changed in: plymouth (Ubuntu)
Assignee: Daniel
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
** Tags added: nvidia nvidia-wayland
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2062082
Title:
24.04 Wayland vs Nautilus performance problem
Status in xorg package in
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2062082
Title:
24.04 Wayland vs Nautilus performance problem
Status in xorg package in Ubuntu:
New
Bug description:
** Package changed: xorg (Ubuntu) => xserver-xorg-video-vmware (Ubuntu)
** Tags added: vmwgfx
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2061886
Title:
Under VMWare
** Tags removed: lunar
** Tags added: noble
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2038313
Title:
MESA-INTEL: warning: Haswell Vulkan support is incomplete
Status
*** 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,
*** 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
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2061172
Title:
the nightlight doesn't
** 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
*** 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) =>
Yelp also crashes soon after displaying the corruption: bug 2060938
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2037015
Title:
Screen corruption of slides during install
** 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
Touch
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
I've installed the 20240410 iso on a couple of machines and this bug is
as good as fixed.
The systemd task would be nice to complete but that's more for the sake
of bug 1914409. Right now I have more important bugs to focus on...
** Changed in: systemd (Ubuntu)
Status: In Progress =>
** Changed in: webkit2gtk (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2037015
Title:
Screen corrupt
** Tags added: noble raspi
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/2060730
Title:
totem cannot install codecs via packagekit
Status in packagekit package in
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
Also bug 2060555.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/205
Title:
[RTL8822CE] i could not able to connect my bluetooth headphone or for
context any
See also bug 205 having trouble with the same chip.
** Also affects: linux-hwe-6.5 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-hwe-6.5 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch
Please reboot, try to connect them again, and after it fails run:
journalctl -b0 > journal.txt
and attach the resulting text file here.
Please also specify how long ago and in which Ubuntu release it was
working.
** Summary changed:
- I cant connect my bluetooth keyboard, mouse and jbl
** 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)
**
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2060204
Title:
Resolution drop on third monitor on USB C
Status in
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
** Summary changed:
- Bluetooth earbuds not being 'set up' on new machine
+ T60 Bluetooth earbuds not being 'set up' on new machine
** Changed in: bluez (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
It seems a few different manufacturers have products called 'T60' so
please mention the brand in the bug title.
** Changed in: bluez (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
In case anyone is wondering, you won't start to see an improvement until
you have at least:
linux >= 6.8.0-20.20 and
plymouth >= 24.004.60-1ubuntu6
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in 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
Yes this bug no longer happens, confirmed on two machines. But there are
other issues with many hundreds of packages being released so please log
new bugs as you find them.
** No longer affects: ubuntu-meta (Ubuntu)
** Package changed: network-manager (Ubuntu) => ubuntu
** Changed in: ubuntu
Thanks for the bug report. Please attach screenshots, photos or a video
of the problem so we can better understand the issue.
** Package changed: ubuntu-meta (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are a member
Public bug reported:
network-manager gets uninstalled on apt full-upgrade
I've tried two Noble systems this evening and both got their network-
manager packages removed. So wifi is gone.
** Affects: network-manager (Ubuntu)
Importance: High
Status: New
** Affects: ubuntu-meta
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1970069
Title:
Annoying boot messages
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
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
Touch seeded packages, 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
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
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
That commit is not meant to reflect the outcome of discussions that
happened after it (comment #93). It's just an intermediate "UNRELEASED"
commit reflecting intermediate development.
My intent with shared repos like this is to show what is being worked on
before anything is released to the
Thanks. I've reflected those changes in git:
https://salsa.debian.org/ubuntu-dev-team/plymouth/-/commits/ubuntu/latest/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Tags added: fixed-in-mesa-24.1 fixed-upstream
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2054851
Title:
[radeon] gnome-shell and Xorg both crash with SIGSEGV in
That change is in plymouth, but hooks/framebuffer is in initramfs-tools.
If you're suggesting moving the code from plymouth into initramfs-tools
then I kind of understand, but it's not directly related to fixing this
bug.
--
You received this bug notification because you are a member of Ubuntu
If you are suggesting moving the logic from plymouth into initramfs-
tools then please start by duplicating the code you'd like moved into
initramfs-tools. That would be efficient since you have commit access to
initramfs-tools, and would mean I only have to deal with plymouth here.
--
You
*** This bug is a duplicate of bug 2053228 ***
https://bugs.launchpad.net/bugs/2053228
** Summary changed:
-
/usr/bin/software-properties-gtk:ValueError:/usr/bin/software-properties-gtk@100:__init__:__init__:backup_sourceslist:__init__
+ software-properties-gtk (ValueError)
Also tracking in:
https://errors.ubuntu.com/problem/3f3a7a239df521d94b27fbe6096dc4a05f967d35
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2053228
Title:
** Summary changed:
-
/usr/share/apport/whoopsie-upload-all:TypeError:/usr/share/apport/whoopsie-upload-all@220:main:collect_info:process_report:add_gdb_info:gdb_command
+ whoopsie-upload-all (TypeError) /usr/share/apport/whoopsie-upload-all@220 →
main → collect_info → process_report →
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"
+
so prevent this bug 1970069.
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu)
Assignee: Daniel van Vugt (vanvugt) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, whi
The patch proposed in
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1970069/comments/91
will help here, but since it might not be the last plymouth change
required for this issue, it doesn't mention bug 1869655.
--
You received this bug notification because you are a member of Ubuntu
Here's a fix for plymouth/noble.
The source is in:
https://salsa.debian.org/ubuntu-dev-team/plymouth/-/commits/ubuntu/latest
We skipped ubuntu5 because that technically existed in bug 2054769 for
10 days already.
Also note this will cause some temporary initrd bloat while the
initramfs-tools
** Changed in: plymouth (Ubuntu)
Status: Won't Fix => In Progress
** Changed in: plymouth (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ini
https://code.launchpad.net/~vanvugt/ubuntu/+source/initramfs-
tools/+git/initramfs-tools/+merge/462482
** Merge proposal unlinked:
https://code.launchpad.net/~vanvugt/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/462481
--
You received this bug notification because you are a
** Merge proposal unlinked:
https://code.launchpad.net/~vanvugt/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/462481
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
** Merge proposal unlinked:
https://code.launchpad.net/~vanvugt/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/462481
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
** Merge proposal unlinked:
https://code.launchpad.net/~vanvugt/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/462481
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
** Description changed:
[ Impact ]
Kernel (and systemd) log messages appear during boot for many machines,
when the user should be seeing only the BIOS logo and/or Plymouth splash
screens.
[ Workaround ]
On most machines you can hide the problem by using these kernel
Seems it's fairly easy to make a working solution in initramfs-tools
alone, but there's a compromise. If I only include tiny/simple
framebuffer drivers in initrd then i915 starts so late that Plymouth
doesn't use it, and bug 2054769 can occur on some machines. If I include
all the current drm
Plymouth would still need patching in order to optimize the drm modules
in debian/local/plymouth.hook
** Changed in: plymouth (Ubuntu)
Status: Invalid => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
)
Importance: Undecided
Status: New
** Changed in: initramfs-tools (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: initramfs-tools (Ubuntu)
Importance: Undecided => Low
** Changed in: initramfs-tools (Ubuntu)
Status: New => In
I think the delay I'm seeing is a feature of Plymouth, not a bug:
"ignoring since we only handle SimpleDRM devices after timeout"
As much as I dislike it perpetuating bug 1869655, this feature does
prevent bug 2054769 from reoccurring.
But this raises the question: is it worth putting i915,
*** 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
Since this bug has expired it would be useful to get a fresh bug report.
Please run:
ubuntu-bug gnome-shell
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1761382
Title:
Fedora 39:
CONFIG_FB_VESA=y
CONFIG_FB_EFI=y
Ubuntu 24.04:
# CONFIG_FB_VESA is not set
# CONFIG_FB_EFI is not set
In the kernel source, DRM_SIMPLEDRM recommends SYSFB_SIMPLEFB if you
want it to work on UEFI and VESA. And we do enable SYSFB_SIMPLEFB whose
help text says:
> you should still keep
1 - 100 of 16472 matches
Mail list logo
