Public bug reported:
A few versions have been released and Ubuntu Noble still has the 6.1
version (6.1.0-1ubuntu2) from one year ago. Could it be possible to
import the latest version from Debian unstable fixing a bunch of issues
and supporting features from more recent kernels?
Please note that
** Description changed:
A few versions have been released and Ubuntu Noble still has the 6.1
version (6.1.0-1ubuntu2) from one year ago. Could it be possible to
import the latest version from Debian unstable fixing a bunch of issues
and supporting features from more recent kernels?
Pl
** 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
** Merge proposal linked:
https://code.launchpad.net/~danilogondolfo/ubuntu/+source/sudo/+git/sudo/+merge/459624
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
https://bugs.launchpad.net/bugs/2051576
Titl
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 can confirm this behavior on our server with Ubuntu Server 20.04. The
occurence is random and the symptoms and log information is the same.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https
Public bug reported:
When I built a new PC with Kubuntu 22.04 LTS, I carried over my recently
purchased GeForce RTX 3060 and copied over the Xorg.conf that was doing
perfectly well for me in 20.04 LTS, containing the following line:
Option "metamodes" "HDMI-0: 1280x1024 +3200+0,
You have been subscribed to a public bug:
wa installing wine
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: libasound2-plugins 1.2.7.1-1ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-15.15.1-lowlatency 6.5.3
Uname: Linux 6.5.0-15-lowlatency x86_64
ApportVersion: 2.27.0-0ubuntu5
Architectur
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
** Package changed: ubuntu => alsa-plugins (Ubuntu)
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/2051350
Title:
package libas
** Also affects: ubuntu-meta (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nano in Ubuntu.
https://bugs.launchpad.net/bugs/2026885
Title:
nano is not available on i386
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: pulseaudio (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launc
Merge request
https://code.launchpad.net/~xypron/ubuntu/+source/rsyslog/+git/rsyslog/+merge/459640
** Changed in: rsyslog (Ubuntu)
Assignee: Heinrich Schuchardt (xypron) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
ok, thanks, success always 👍😄
--
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/2050831
Title:
Performance
Status in xorg package in Ubuntu:
New
Bug description:
Hello, in
Public bug reported:
I am unable to turn on my Bluetooth so I unable to connect to my mouse
and earbuds to laptops
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: bluez 5.68-0ubuntu1.1
ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3
Uname: Linux 6.5.0-15-generic x86_64
ApportVers
** Tags removed: need-duplicate-check
--
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/2051705
Title:
package bluez 5.68-0ubuntu1.1 failed to install/upgrade: installed
blue
Public bug reported:
I feel like this was due to storage available at the time of the virtual
build. As it hit capacity, it started to throws errors. I have since
adjusted allotted space to 40GB from the default.
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-92-gene
AFAIK, the systemd-fsckd patch is still required, but we have vague
plans to get rid of it by making plymouth learn this functionality (i.e.
reading /run/systemd/fsck.progress directly). I have no idea about the
re-ordering, but it would be easy to test with a drop-in config.
** Changed in: system
Public bug reported:
Likely - problem with graphical card driver
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3
Uname: Linux 6.5.0-15-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
Ca
** Description changed:
In removing the LXD snap from preseeding in the server seed for Ubuntu
- 24.04 as part LP #2051346 [1] we also removed the snaps snap and the
+ 24.04 as part LP #2051346 [1] we also removed the snapd snap and the
core22 snap.
This means that are subsequent snap ins
Happened twice today I swear this is going to give some one a heart
attack
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/2051031
Title:
Occasionally system alert will
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
Oh wait, we've been through something very like this before
https://bugs.launchpad.net/cloud-initramfs-tools/+bug/1834875. I suspect
a judicious application of flock may be the most correct solution
available.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded p
** 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
> But the feature would still be gated on the "splash" kernel parameter
which is Plymouth-specific and may cause pushback from kernel
developers.
If the patch is the way you go another idea for you is to use the
"quiet" keyword to key off instead for this behavior which is already
used by the kern
Have you already looked at everything Fedora is doing in this area?
They already have simpledrm; but from what you described I would have
thought they should still lose the fbcon race.
Is it just that they don't have systemd-fsckd patch? I would think they
still end up showing ERR/WARN kernel mes
"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
On Tue, Jan 30, 2024 at 6:21 PM Michael Hudson-Doyle
<2045...@bugs.launchpad.net> wrote:
>
> Oh wait, we've been through something very like this before
> https://bugs.launchpad.net/cloud-initramfs-tools/+bug/1834875. I suspect
> a judicious application of flock may be the most correct solution
> a
> I don't really know if Fedora does that better or they just failed to
notice the bug.
I have Fedora 39 and Ubuntu both set up on a Z13 and Plymouth comes up in
Fedora with simpledrm; never see the console. That's why I was thinking
something might be missing and worth looking at.
* Fedora doe
Something "big" I notice different is that by default Ubuntu doesn't put
plymouth in the initramfs but Fedora does.
Maybe plymouthd really isn't running at the time systemd-fsckd is
running.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Yeah; so try forcing plymouth to the Ubuntu initrd like this:
echo "FRAMEBUFFER=y" | sudo tee /etc/initramfs-tools/conf.d/splash
Then if you rebuild the initrd you'll end up with plymouth in it.
This unfortunately DOUBLES the initramfs size; but it's because it puts all the
drm modules in there
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
** Merge proposal linked:
https://code.launchpad.net/~alexmurray/ufw/+git/ufw/+merge/459690
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/2051540
Title:
ufw ftbfs with Pyt
** Also affects: ufw
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/2051540
Title:
ufw ftbfs with Python 3.12 as default
Status in
Sorry for the late reply. Proposed package 23.2.1-1ubuntu3.1~22.04.2
amd64 [installed,automatic], GUI displayed normally, thank you for the
help!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.lau
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
packages in launchpad always build against -proposed. How are you
building this that you're not getting the systemd in proposed?
** Tags removed: regression-release
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
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
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/2042587
Title:
jammy's version breaks existing dhcp sc
48 matches
Mail list logo
