I don't know the reasons, but this code has been working in this way for
10+ years, so this type of collision can not be common.
I sent the ALC285_FIXUP_THINKPAD_HEADSET_JACK patch to the lists:
https://lore.kernel.org/all/7ffae10ebba58601d25fe2ff8381a6ae3a926e62.1708687813.git.so...@irl.hu/
And
Could restore a working Kernel 6.5.0.21 with
$ sudo apt update
$ sudo apt upgrade
However, the system starts up directly without asking for the user
login, which is really weird.
There is also a security warning when updating:
$ sudo apt update
Hit:1 http://archive.ubuntu.com/ubuntu mantic
Public bug reported:
After I ran the updater last week, my computer could only have a Link
Local address for IPv6. I have now confirmed that IPv6 works normally
when I install a fresh copy of 22.04.3 LTS and has the bug even after a
fresh install of 22.04.4 LTS. Previous data and fault finding on
Public bug reported:
This happens only after I connect my Toshiba FireTV via HDMI. I don't need to
be using the TV. If I have connected TV just once it is enough to trigger this
bug. Laptop goes to sleep just fine but when it wakes up from sleep I see 5
services when I execute
$ systemctl
This bug was fixed in the package gdb - 15.0.50.20240219-0ubuntu1
---
gdb (15.0.50.20240219-0ubuntu1) noble; urgency=medium
* New upstream snapshot.
* Support for new IBM Z Hardware (IBM z16). LP: #1982336.
-- Matthias Klose Mon, 19 Feb 2024 21:49:40 +0100
** Changed in: gdb
Public bug reported:
I have several computers running 20.04 and a couple running 22.04. VNC
was great on 20.04. I could connect using remina or real vnc no problem.
on the 22.04 machines though, I cannot connect reliably at all. If the
server montitor is in sleep, the server rejects the
** Description changed:
- Since the last three weeks' updates, I have encountered several
- challenges with the audio functionality on my system. Primarily, upon
- starting my laptop, the audio often fails to work, displaying "Dummy
- Output." To resolve this, I find myself needing to restart the
DNSSEC isn't required to query a DS record. The reason your query
succeeded after you enabled DNSSEC is because systemd-resolved caches it
internally as a result of the DNSSEC lookup.
Once the DS query is cached, the bug will not manifest. Another way to
cache it is:
ubuntu@server:~$ dig
Belated response, but just for the record, Paride's recounting of upstream's
position in the context of the Debian decision was definitive for me:
On Wed, Jan 10, 2024 at 11:47:56AM -, Paride Legovini wrote:
> Back in the day I asked upstream their take on irqbalance usefulness
> with newer
The mentioned fix in the upstream report has been in systemd since 2021.
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: New => Fix Released
** Changed in: systemd (Ubuntu Focal)
Importance: Undecided => Low
** Changed in: systemd (Ubuntu)
Status: New => Won't Fix
--
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/1880839
Title:
Clock skew on testbeds
Status in Auto
I don't think that script is or was part of src:systemd?
** Changed in: systemd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Changed in: systemd (Ubuntu Noble)
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/2045621
Title:
Improve power consumption
The systemd version in question migrated.
** Changed in: systemd (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.
Uh, isn't the real problem that in this case
/etc/udev/rules.d/10-network.rules is a *directory*, and not a *file*?
--
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/1605941
Given the age of this, I am going to mark won't fix, but please re-open
if you think I am wrong.
** Changed in: systemd (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
The mentioned fix is included in v255, which is now in Noble.
** Changed in: systemd (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
I guess this only applied to Lunar? Which is EOL. So, marking this won't
fix, but correct me if I am wrong.
** Changed in: systemd (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: Incomplete => Invalid
** Changed in: systemd (Ubuntu Bionic)
Importance: Undecided => Low
--
You received this bug notification because you are a member of
** Changed in: systemd (Ubuntu)
Status: Triaged => Won't Fix
--
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/1162475
Title:
[hostnamed] Changing hostname doesn't
** Changed in: systemd (Ubuntu)
Status: Incomplete => Invalid
--
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/2017317
Title:
Ubuntu: upon reboot, forever waiting
** Changed in: systemd (Ubuntu)
Status: Incomplete => Invalid
--
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/2017846
Title:
System kept waking up after pressing
systemd-ukify is in noble now:
https://launchpad.net/ubuntu/noble/+package/systemd-ukify
** Changed in: systemd (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
@enr0n, the proposal to add:
bridges:
br0:
interfaces: [vlan1]
To the network config defeats the purpose. The goal is to not have to do
double configuration. The bridge is define in LXD, the vlan1 only in
netplan.
The other proposed fix of `KeepMaster=true` snippet in
** Changed in: systemd (Ubuntu)
Status: Incomplete => Invalid
--
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/2039083
Title:
"optional: true" flag introduces
** Changed in: systemd (Ubuntu)
Status: Incomplete => Invalid
--
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/2049392
Title:
Symlink for resolv.conf not working
** Changed in: systemd (Ubuntu)
Status: Incomplete => Invalid
--
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/2020177
Title:
Leaking sessions in pam_systemd
Status
This sounds like a question better suited for upstream. Please open a
bug there instead: https://github.com/systemd/systemd/issues
** Changed in: systemd (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: systemd (Ubuntu)
Importance: Undecided => Wishlist
--
You received this
** Tags added: rls-nn-incoming
--
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/2019026
Title:
systemd /tmp cleaning is suboptimal
Status in systemd package in Ubuntu:
The fixes you mentioned should be included in noble already. The patches
you mention do not apply to v249, which is the systemd version in jammy.
So, when 24.04 is released, the fix will be available there, but
unfortunately I don't think we will fix this in 22.04.
** Also affects: systemd
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu Jammy)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
*** This bug is a duplicate of bug 2037667 ***
https://bugs.launchpad.net/bugs/2037667
This sounds like a duplicate of 2037667, which is planned to be fixed
sometime soon-ish.
** This bug has been marked a duplicate of bug 2037667
Regression on Jammy's kernel 5.15 when creating ip6gre and
It sounds like you don't have DNSSEC=yes anywwhere. I can do the following.
root@mantic:~# resolvectl dnssec
Global: no
Link 41 (eth0): no
root@mantic:~# dig +short DS ripe.net
root@mantic:~# resolvectl dnssec eth0 yes
root@mantic:~# resolvectl dnssec
Global: no
Link 41 (eth0): yes
root@mantic:~#
** Changed in: systemd (Ubuntu)
Status: New => Opinion
--
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/1950906
Title:
etc/rc.local should Want or Require
The upstream bug is tagged for a stable backport, so we *should* get
this soon-ish in noble.
** Changed in: systemd (Ubuntu)
Status: New => Triaged
** Changed in: systemd (Ubuntu)
Importance: Undecided => Low
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Nick Rosbrook
This would take a larger coordination, and is not really a "bug" to be
assigned to systemd per se. We will likely inherit lots of this from
Debian over time.
Marking as invalid just because this is not really the place for this
(probably a thread on ubuntu-devel would be better?).
** Changed in:
The drop-in would apply to vlan1, e.g.:
$ mkdir -p /etc/systemd/network/10-netplan-vlan1.network.d
$ cat > /etc/systemd/network/10-netplan-vlan1.network.d/keep_master.conf << EOF
[Network]
KeepMaster=true
EOF
Again, if netplan has a setting equivalent to KeepMaster=, that would be
simpler. I
You have a couple options here. I think simplest would be to just add:
bridges:
br0:
interfaces: [vlan1]
to your netplan config. This will generate
/run/systemd/network/10-netplan-vlan1.network with:
[Match]
Name=vlan1
[Network]
LinkLocalAddressing=no
ConfigureWithoutCarrier=yes
Stragely though, when I reboot my ubuntu and mosue-click some times out of my
ubuntu and inside my VmWare player randomly some times, it allowed me in. and
also on reboot, it works with an Enter
( i.e removing password effected ).
Also i tried to change password with passwd command giving the
Is this still an issue on 24.04?
** Also affects: systemd (Ubuntu Mantic)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
** Changed in: systemd (Ubuntu Mantic)
Importance: Undecided => Low
--
You received this bug notification
apt and bzip2 have migrated, so we are ready to land them in the next
britney run.
** Tags removed: block-proposed
** Changed in: base-files (Ubuntu)
Status: New => Fix Released
** Changed in: glibc (Ubuntu)
Status: New => Fix Released
--
You received this bug notification
klibc (2.0.13-4) unstable; urgency=medium
[ Sven Joachim ]
* debian/initramfs-tools/hooks/klibc-utils: Avoid the use of "cp -n"
(Closes: #1055694).
[ Salvatore Bonaccorso ]
* debian/control: Add myself to Uploaders
Date: 2024-02-21 22:32:43.744541+00:00
Signed-By: Paride Legovini
** Changed in: klibc (Ubuntu)
Assignee: (unassigned) => Paride Legovini (paride)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to klibc in Ubuntu.
https://bugs.launchpad.net/bugs/2054823
Title:
Sync klibc 2.0.13-4
and here is the syslog
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2054827/+attachment/5748736/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
Public bug reported:
Dear all, after the upgrade of various mesa packages on monday
(23.2.1-1ubuntu3.1~22.04.2 from repo jammy-updates), I suffer similar symptoms
at startup (causing a blank screen with no GDM running and message "something
went wrong) than those reported there
here is the apt.log of the upgrade that have raised the issue
** Attachment added: "apt.log"
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2054827/+attachment/5748735/+files/apt.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
Public bug reported:
Please sync klibc 2.0.13-4 (main) from Debian unstable (main)
Explanation of the Ubuntu delta and why it can be dropped:
[ Klaus Frank ]
* d/i/h/klibc-utils: Fix compatibility issue with busybox and improve verbose
debug output.
(Closes: #1055694) (LP: #2046336)
*** This bug is a duplicate of bug 2053228 ***
https://bugs.launchpad.net/bugs/2053228
I deleted the files in the /etc/apt/sources.list.d and it worked
normally.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt
Note that currently in noble lvm2 fails to build due to
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/2054683 which is
unrelated to the MR linked here
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
Hello Rudra, or anyone else affected,
Accepted cups into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/cups/2.4.1op1-1ubuntu4.8 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
I also enclose the apt log describing the dist-upgrade that causes the
issue
** Attachment added: "apt.log"
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2051068/+attachment/5748703/+files/apt.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Dear all, after the upgrade of mesa packages on monday
(23.2.1-1ubuntu3.1~22.04.2 from repo jammy-updates), I suffer similar symptoms
at startup (causing a blank screen with no GDM running and message "something
went wrong). I am using 22.04.3 LTS "Jammy Jellyfish" with kernel
6.1.0-1034-oem
Fixed on Debian, and as the package is in sync, we already have the tests.
Marking FixReleased and removing myself as assignee.
** Changed in: dnsmasq (Ubuntu)
Assignee: Miriam España Acebal (mirespace) => (unassigned)
** Changed in: dnsmasq (Ubuntu)
Status: In Progress => Fix
** Bug watch added: bugs.webkit.org/ #210100
https://bugs.webkit.org/show_bug.cgi?id=210100
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnome-online-accounts in
Ubuntu.
https://bugs.launchpad.net/bugs/2023322
Title:
Hi Michael,
I already hopped over to bug #261874, as the description in #c32 over
there matches my setup exactly. The errors I get are:
> [zlatko@disclosure:~]$ liferea
> src/nv_gbm.c:99: GBM-DRV error (nv_gbm_bo_create):
> DRM_IOCTL_NVIDIA_GEM_ALLOC_NVKMS_MEMORY failed (ret=-1)
>
> Failed to
This bug is for GTK4, Liferea is GTK3. That's a separate issue that
should not be marked as a blocker for
https://bugs.webkit.org/show_bug.cgi?id=210100
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnome-online-accounts in
Hi Craig and Thomas (and Emil if you're still around): if you're still
encountering problems with NVIDIA graphics, please report new a bug and
leave a comment here linking to the new bug.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
57 matches
Mail list logo
