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 looks like there are Bluetooth packet problems at the kernel level
(if not hardware), so reassigning there.
** Summary changed:
- blutooth
+ [BCM43142] Bluetooth headset disconnects
** Package changed: bluez (Ubuntu) => linux-hwe-6.5 (Ubuntu)
--
You received this bug notification because yo
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
> Display resolution stuck at 800x600 after using nomodeset in grub.
> But my Dell monitor has 1600x900 resolution.
This is correct behaviour. "nomodeset" means to disable the graphics
driver and to disable high resolution support.
** Package changed: xorg (Ubuntu) => linux-hwe-6.5 (Ubuntu)
** C
Please check to see if the kernel is getting the button events:
sudo apt install evtest
sudo evtest
** Package changed: xorg (Ubuntu) => linux-raspi (Ubuntu)
** Changed in: linux-raspi (Ubuntu)
Status: New => Incomplete
** Package changed: linux-raspi (Ubuntu) => linux (Ubuntu)
**
Looks like systemd failed and started timing out for multiple things
before this happened. So there's nothing bluez can do about that.
** Changed in: bluez (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, whic
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
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 interfer
The userspace part of this bug is coming from our systemd patch:
debian/fsckd-daemon-for-inter-fsckd-communication.patch
In particular where systemd-fsckd.service says:
StandardOutput=journal+console
Is the patch still required at all, or can it be reordered to wait for
Plymouth to splash f
You can use the 'fastboot' kernel parameter to bypass the systemd-fsckd
issue. So overall most systems can work around the bug in full using
kernel parameters:
quiet splash loglevel=2 fastboot
After that I've only encountered one weird laptop that refused to stay
silent (even with loglevel=0).
I am also the author of the Plymouth feature that parses and renders the
fsck progress. What I think isn't being communicated here is that it's
currently useless on startup. Because Plymouth doesn't start rendering
until well after the fsck has already happened. See also bug 1869655.
--
You recei
** Changed in: plymouth (Ubuntu)
Status: Invalid => Confirmed
--
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 interfering with
I now expect the kernel patch would change before it gets proposed to
dri-devel. In particular the primary delay doesn't need to be
configurable (or even finite?), and the secondary delay probably doesn't
need to be more than zero. But the feature would still be gated on the
"splash" kernel paramet
It looks like the installation might have succeeded and just requires a
reboot. The error was:
Failed to start bluetooth.service: Unit bluetooth.service failed to load
properly, please adjust/correct and reload service manager: File exists
** Summary changed:
- package bluez 5.68-0ubuntu1.1 fail
"splash" is more appropriate than "quiet" (unfortunately) because we
would delay framebuffer takeover to the same event (primary DRM startup)
as Plymouth does.
I would also like to know why our Plymouth doesn't render on SimpleDRM
even when it's available (tested in bug 1965303). I don't really kn
Thanks. So it still sounds like SimpleDRM is in Ubuntu's future (bug
1965303). But in case that doesn't happen in time for Noble, or if we
simply want a solution that backports to jammy, then I will still focus
on plymouth/kernel changes only.
--
You received this bug notification because you are
--
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 interfering with splash screen
Status in linux package in Ubuntu:
In Progress
Status
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
** Package changed: xorg (Ubuntu) => xorg-server (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/2051694
Title:
Regression: Kubuntu 22.04 LTS overrides Xorg.conf-spec
> I belive /usr/share/initrams-tools/hooks/plymouth can be modified to stop
> including any
> drm modules and /usr/share/initramfs-tools/framebuffer can be totally dropped.
Dropping the DRM modules would also allow us to use a near-zero
device_timeout in Plymouth now. It would then render to efif
Thanks for the bug report. It appears the graphics driver and Xorg are
working correctly here. And certainly I would not expect all modern
games to maintain 60 FPS on the integrated GPU of an Intel i3-1115G4.
As for the blurry HDMI output, the Samsung un32t4300 is limited to
1366x768 so a little b
I'm not sure we even need Plymouth installed in initrd because the
device_timeout experiment mentioned in comment #18 suggests plymouthd
was starting early enough already. It's not the root filesystem that
takes too long to appear, but the i915/amdgpu drivers to fully
initialize. Also all this talk
Ah it's because the new systemd (which will fix this) is stuck in
proposed. To work around it you need to manually revert:
https://launchpadlibrarian.net/709437063/plymouth_23.360.11-0ubuntu1_23.360.11-0ubuntu2.diff.gz
** Changed in: plymouth (Ubuntu)
Status: New => In Progress
** Also af
Yes I learned that recently thanks. I'm building it on a noble desktop
(no proposed). Just apt-get source plymouth
--
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/2051765
Tit
Hmm, no plymouthd isn't starting quite early enough in Noble:
2.799s - plymouthd starts
4.080s - first show-splash attempt (rejected because DRM hasn't started yet)
5.290s - found /dev/dri/card0
5.364s - showing splash screen
What this means is that any attempt to fix the bug in plymouthd itself
A new attempt at a kernel patch. While this is pleasingly simple and
reliable in my own testing, it has a bug when "splash" is used at the
same time as there being no primary framebuffer (like with "nomodeset").
I'm not sure if that's a realistic concern and am reluctant to go back
to delays to pap
BTW bug 2050743 is making the situation worse on noble. It will be fixed
shortly.
--
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 inte
> You could detect both parameters to avoid that corner case.
Sure one can check for "splash nomodeset" to avoid the confusion in most
cases, but that wouldn't fix it for "splash $DRIVER.modeset=0" or less
common architectures which might have no primary framebuffer. I guess we
can tell people who
Here's a no-compromises patch set. No bugs, no delays, it just does the
right thing.
If I haven't changed my mind again on Friday then it will be sent
upstream.
** Patch added: "lp1970069-patchset-20240201a.patch"
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1970069/+attachment/57
I think that's a different bug. I believe it's when plymouthd is
starting and is the handover (mode set?) from efifb to DRM. It doesn't
happen at all if you add "nomodeset" (please try that).
"Really long time" might be subjective though? How long?
VT switches (or more accurately virtual console
This bug has been closed for over 14 years so if you have any current
issues then please open new bugs for each of them.
--
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/241000
GRUB_TIMEOUT > 0 also causes the vendor logo to be replaced by a black
screen, but that seems to be Grub's fault. Default Ubuntu won't have
that problem since it ships GRUB_TIMEOUT=0. And if you want a nonzero
timeout without the blackness then GRUB_TERMINAL=console is a
workaround.
--
You receiv
The blanking from GRUB_TIMEOUT>0 will be made much worse by
CONFIG_FB_EFI=n because usually in Ubuntu it's the efifb that restores
the logo after Grub has wiped it. I think not having CONFIG_FB_EFI at
the same time as using GRUB_TIMEOUT>0 explains your previous "really
long time of a black screen".
Patches sent (to multiple places per get_maintainer.pl):
https://lkml.org/lkml/2024/2/2/373
https://lkml.org/lkml/2024/2/2/375
--
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
** Tags added: amdgpu
** Tags added: flicker suspend-resume
** Summary changed:
- After screen turns off and you turn it back on, weird corruption
+ [amdgpu] After screen turns off and you turn it back on, weird corruption
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
--
You received th
It looks like the 'modesetting' Xorg driver is at fault, if we trust the
log message suggesting /dev/dri/card0 exists. Please run:
sudo apt install drm-info
sudo drm_info > drminfo.txt
and then attach the resulting text file here.
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
*
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: plymouth (Ubuntu)
Importance: Undecided => Medium
--
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.ne
Please check that this isn't being caused by local extensions. You can
remove them by running:
cd ~/.local/share/gnome-shell/
rm -rf extensions
and then log in again. If the problem persists after that then please
run:
gnome-extensions list --enabled > extensions.txt
and attach the result
Incomplete: Waiting for the bug to reoccur... It sounds to me like a
kernel or hardware problem though, in which the device itself is
believed to have disappeared, and so would the dialog.
** Tags added: mantic
** Package changed: bluez (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New
I think the crossed circle means you're hitting a special key on the
keyboard that is assigned to some on-screen display (OSD) function.
Please try to identify which key or key combo is causing it. You might
also be able to avoid the problem by enabling or disabling the
keyboard's Fn-lock (which is
* What web browser are you using?
* What is the name of the process using the most CPU?
* Maybe unrelated, but your '88x2bu' kernel driver (for USB wifi) seems
to be crashing.
* Please be sure to only use the 'Additional Drivers' app to install
Nvidia drivers because it looks like you might have
Your "13th Gen Intel(R) Core(TM) i7-13700" is too new for such an old
Linux kernel to support the graphics outputs correctly. Please install a
newer Ubuntu release such as 22.04.3:
https://ubuntu.com/download/desktop
** Package changed: xorg (Ubuntu) => linux-hwe-5.15 (Ubuntu)
** Also affects: l
Thanks for the bug report. Please start by removing any local
extensions:
cd ~/.local/share/gnome-shell/
rm -rf extensions
and then log in again.
If the problem still happens then while it is happening please run:
journalctl -b0 > journal.txt
and attach the resulting text file here.
**
This bug has been closed for a few years so please open a new one.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1870060
Title:
systemd ProtectSystem/mount namespace makes
** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-535
(Ubuntu)
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- Second (external) monitor not active after screen lock
+ [nvidia] Second (external) monitor not active after screen lock in
** Tags added: jammy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wayland in Ubuntu.
https://bugs.launchpad.net/bugs/2053235
Title:
Upgrade libwayland on ubuntu 22.04.3 LTS
Status in wayland package in Ubuntu:
New
Bu
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
** Summary changed:
- Upgrade libwayland on ubuntu 22.04.3 LTS
+ Upgrade libwayland to 1.22.0
** Also affects: wayland (Ubuntu Noble)
Importance: Undecided
Status: Invalid
** Also affects: wayland (Ubuntu Mantic)
Importance: Undecided
Status: New
** Changed in: wayland (Ubun
*** This bug is a duplicate of bug 2054221 ***
https://bugs.launchpad.net/bugs/2054221
** This bug has been marked a duplicate of bug 2054221
GNOME setting GUI bug
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg i
Thanks for the bug report. I can't yet see any cause for the freezes.
Next time it happens please:
1. Note the exact time and date of the freeze.
2. Reboot.
3. Run: journalctl -b-1 > prevboot.txt
4. Attach the resulting text file here along with a note telling us the
exact time and date of the
I wonder if the Belkin docking station has enough bandwidth to drive
multiple monitors simultaneously. Have you tried unplugging everything
from the dock and just plugging in a monitor to the DisplayPort alone?
Also next time the bug occurs, please run:
journalctl -b0 > journal.txt
and attach
Can you test some other desktop environment like GNOME? And try Wayland?
At the moment all I can see is that Xorg thinks both monitors are
working. So the bug may be Xorg, the amdgpu Xorg driver, XFCE, or the
kernel.
** Package changed: xorg (Ubuntu) => xserver-xorg-video-amdgpu (Ubuntu)
** Cha
** Package changed: xorg (Ubuntu) => gnome-control-center (Ubuntu)
** Summary changed:
- GNOME setting GUI bug
+ Sound settings flicker heavily when choosing output
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubu
Status update:
https://lists.freedesktop.org/archives/dri-devel/2024-February/442066.html
So once merged, the fix will need to be manually enabled by:
FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER_CONDITION = "splash"
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Maybe it's Mesa's fault. Yelp crashes in:
??? () at /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so
??? () at /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so
??? () at /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so
??? () at /lib/aarch64-linux-gnu/libgbm.so.1
??? () at /lib/aarch64-linux-gnu/libwebkit2gtk-4.1.so.0
** 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.
+
+ [ Test Plan ]
+
+ 1. Boot Ubuntu on a number of laptops that have the problem and verify
+ n
** 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 parameter
*** This bug is a duplicate of bug 2037015 ***
https://bugs.launchpad.net/bugs/2037015
** This bug has been marked a duplicate of bug 2037015
Screen corruption of slides during install on Raspberry Pi 4
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Same issue in Yelp (the Help app) when in Xorg sessions. So I think this
is a webkit2gtk bug that only manifests on Xorg (like our installer/live
sessions).
Also I have removed the series targets because they were getting
cluttered and likely targeting the wrong package anyway.
** Also affects: w
*** This bug is a duplicate of bug 2037015 ***
https://bugs.launchpad.net/bugs/2037015
If it's just appeared in 22.04.4 then Mesa might be to blame, but this looks
more likely:
https://launchpad.net/ubuntu/+source/webkit2gtk/2.42.5-0ubuntu0.22.04.2
--
You received this bug notification beca
Same for Weston 13.0. But since it's Nvidia asking, maybe we can help
some other way?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wayland in Ubuntu.
https://bugs.launchpad.net/bugs/2053235
Title:
Upgrade libwayland to 1
Please use 'ubuntu-bug' to report each crash file so the robots can
analyse and classify them.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to policykit-1 in Ubuntu.
https://bugs.launchpad.net/bugs/2054319
Title:
System ins
Next time the problem happens please:
1. Reboot.
2. Run:
journalctl -b-1 > prevboot.txt
3. Attach the resulting text file here.
** Summary changed:
- Xorg freeze
+ Xorg freeze: i915 flips and commits are timing out
** Package changed: xorg (Ubuntu) => linux-hwe-6.5 (Ubuntu)
** Changed i
** Tags removed: kinetic lunar
** Tags added: udeng-2004
--
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 interfering with splash scree
The tracker-extract crash may be bug 1990630 or bug 1962585, because it
looks like both fixes haven't made it into jammy yet. But also this bug
list probably needs some maintenance:
https://bugs.launchpad.net/ubuntu/+source/tracker-miners
The gnome-shell crash is now tracked in bug 2054761.
--
Y
*** This bug is a duplicate of bug 2054121 ***
https://bugs.launchpad.net/bugs/2054121
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 2054121, so it is being marked as such. Please look
Tracking upstream in:
https://gitlab.freedesktop.org/mesa/mesa/-/issues/10613
** Information type changed from Private to Public
** Summary changed:
- gnome-shell crashed with SIGSEGV
+ gnome-shell crashed with SIGSEGV in radeon_bo_reference()
** Package changed: gnome-shell (Ubuntu) => mesa (U
*** This bug is a duplicate of bug 2054121 ***
https://bugs.launchpad.net/bugs/2054121
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 2054121, so it is being marked as such. Please look
** Tags added: noble
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1922047
Title:
Touchpad scrolling is too fast
Status in Mozilla Firefox:
Fix Released
Status in GTK+
** Package changed: xorg (Ubuntu) => gnome-remote-desktop (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/2054859
Title:
VNC connection issues with 22.04
Status in g
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
** 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
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
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
Touch seeded packages, which is subscribed to xorg in Ubuntu.
http
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:
-
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
** Tags removed: flickerfree
** Tags added: flickerfreeboot
--
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/1914409
Title:
fsck integration is not flicker free
Status in s
** Changed in: systemd (Ubuntu)
Status: Won't Fix => In Progress
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: systemd (Ubuntu)
Importance: Low => Medium
--
You received this bug notification because you are a me
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
I'm starting to suspect our patch (comment #39) isn't directly to blame
for the systemd issue. Disabling or otherwise breaking systemd-
fsckd.service doesn't stop fsck output from polluting the console and
triggering this bug. Only skipping fsck avoids it. You can skip fsck
using 'fastboot' or 'fsc
It looks like the above code might not need /dev/console at all. It
should be possible to modify it to use a private pipe for fsck's stdout.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launc
This bug is currently hidden behind bug 1970069, but I do remember this
one. And it still happens on a small minority of machines. It would
happen for everyone if we fixed bug 1970069.
** Also affects: plymouth (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notific
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-
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
Also focal (20.04.6) does have the bug now, per comment #23.
** Tags added: focal
--
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 int
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
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 2055779
When reporting bugs in the future please use apport by using 'ubuntu-
bu
Noble is now shipping with SimpleDRM enabled in kernel 6.8, so the next
step is comment #49 (which would also resolve bug 1869655).
--
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/
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
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
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
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
Touch seeded packages, which is s
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
Touch seeded packages, which is subscribed to mes
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
** Changed in: initramfs-tools (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: initramfs-tools (Ubuntu)
Importance: Undecided => Medium
** Changed in: initramfs
I've analysed a couple of Noble systems today and don't think initramfs-
tools needs improving (although it might not hurt). On both systems,
plymouth-start was within 1 second of simpledrm starting (same
timestamp), but the bug still occurs. The reasons are:
1. One system actually experiences the
You can test if the above suggestion will work for you by adding these
kernel parameters:
loglevel=3 fsck.mode=skip
--
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
Maybe initramfs-tools does still need changing. plymouth-start.service
seems to run twice, and I get the feeling only the second instance is
actually succeeding in splashing on screen.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscri
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
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2055351
Title:
** Changed in: initramfs-tools (Ubuntu)
Status: Opinion => New
--
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 interfering with
*** This bug is a duplicate of bug 2053228 ***
https://bugs.launchpad.net/bugs/2053228
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 2053228, so it is being marked as such. Please look
1 - 100 of 16923 matches
Mail list logo
