We found that the root cause is the ibus.
A workaround to fix this problem is running:
GTK_IM_MODULE=simple gnome-text-editor
Furthermore, I will open an issue in:
https://github.com/ibus/ibus
** No longer affects: gtk4 (Ubuntu)
** Also affects: ibus (Ubuntu)
Importance: Undecided
Important context from https://lists.debian.org/debian-security-
announce/2024/msg00057.html :
Andres Freund discovered that the upstream source tarballs for xz-utils,
the XZ-format compression utilities, are compromised and inject
malicious code, at build time, into the resulting liblzma5
Kuwait's demand for skilled drivers presents a promising avenue for job
seekers looking to carve out a niche in the transportation sector.
Whether chauffeuring families to appointments, navigating bustling city
streets, or providing logistical support, drivers in Kuwait uphold
standards of
It seems like you're encountering an issue with the avahi-daemon and
Zeroconf hostname changes after your ISP changes your IP address. The
behavior you described could be related to avahi-daemon reacting to the
IP address change, resulting in a change of the Zeroconf hostname. To
address this
It seems like the Avahi daemon on your Ubuntu machines is encountering a
hostname conflict during the nightly IP address change, resulting in it
appending a number to the hostname. This conflict might be due to multiple
devices trying to register the same hostname on the network.
Tracked down the cause to the Docker host, which runs on jammy, not
knowing about fchmodat2(). The syscall should normally return ENOTSUP
when called with AT_SYMLINK_NOFOLLOW on Linux, but the Docker seccomp
profile causes it to return EPERM, which confuses tar(1). Closing.
** Changed in: tar
Public bug reported:
This concerns tar 1.35+dfsg-3 in Ubuntu noble. This does NOT affect tar
1.34+dfsg-1.2ubuntu1.1 in mantic.
I'm seeing errors like this:
$ tar xvJf /extern/source/chromium_122.0.6261.111.orig.tar.xz --wildcards
Public bug reported:
I am seeing this on Ubuntu noble with polkitd 123-3.
After debootstrap'ing a minimal system, I run
# apt-get install linux-generic
which pulls in polkitd as a dependency. In the output, I see the
following:
Setting up polkitd (123-3) ...
Creating group
@juergh,
I want to express my gratitude for your dedication and efforts in
investigating the bug. Your involvement has been invaluable, and I truly
appreciate it.
I've recently updated to the new kernel version, 6.2.0-32-generic, and
will be monitoring.
Additionally, for clarity, I'd like to
In essences Trevor - yes.
I moved the directory, as i would have moved it back if the update had not been
succeeded. (Being cautions)
To clarify, the move and running the fix install was after I had rebooted using
previous 18.04 kernel set up, as the 20.04 was not complete/bootable.
So
@juergh Please, provide further information to help-us with the bug.
--
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/2031352
Title:
Ubuntu 22.04.3 LTS stuck on
Had this when updating from ubuntu (with unity) 18.4 to 20.04 Yesterday
(27 Aug)
Possible Work around?
Moved bf9d6da9.0 to desktop (Moved, just in case was not a solution as had
tried re-namaing, with no effect)
sudo apt-get install -f, then ran ok.
afterwards noted that etc/../cache/ &
Reopening this issue as I am still observing the net_admin denial in
jammy.
** Changed in: cups (Ubuntu)
Status: Expired => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
Public bug reported:
do-release-upgrade 20 to 22.
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-1039-aws 5.15.0-1039.44
ProcVersionSignature: Ubuntu 5.15.0-1039.44~20.04.1-aws 5.15.99
Uname: Linux 5.15.0-1039-aws x86_64
ApportVersion: 2.20.11-0ubuntu82.5
** Also affects: lightdm (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 in Ubuntu.
https://bugs.launchpad.net/bugs/1922414
Title:
ssh-agent fails to start
/-/issues/1279
** Summary changed:
- [media-keys] Fn media keys with lag slow/delay on Gnome with "Scroll Lock"
keyboards
+ [media-keys] Media keys with lag slow/delay on Gnome with "Scroll Lock"
keyboards
** Changed in: xkeyboard-config (Ubuntu)
Assignee: Cris
As the xkeyboard-config is not the cause of that bug, the Scroll Lock
key must return because many users use this key in some apps.
I've opened a Merge Request to return the Scroll Lock key:
https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/-/merge_requests/555
** Changed in:
** Description changed:
Hi folks,
I've been using dnsmasq for my home DNS needs, which includes returning
null entries for certain domain queries. The specific case in which I
found this segfault was returning null records for Netflix (to
ensure Netflix does not try to use my
After further testing, I can also see the crash occurs without with the
`dns-no-doh.conf` config snippet loaded, even for a regular `A` record
(so the TYPE65 query is also a red herring):
root@budgie:~# dig +short -tA test.netflix.net @127.0.0.1
root@budgie:~# dig +short -tA test.netflix.net
Public bug reported:
Hi folks,
I've been using dnsmasq for my home DNS needs, which includes returning
null entries for certain domain queries. The specific case in which I
found this segfault was returning null records for Netflix (to
ensure Netflix does not try to use my IPv6 tunnel to
About the fix for this bug:
This fix solves the problem only for ABNT2 keyboards (used in Brazil,
only).
But this bug affects all keyboards with "Scroll Lock" key.
The solution proposed in the merge request that I made in project
xkeyboard-config is not a suitable solution yet. It is not a
Public bug reported:
Touching the touch screen display removes the mouse cursor. It comes back after
blindly navigating to the menu bar. This also happends randomly without
touching the touchscreen. There doesn't appear to be a trigger for the random
disappearances that is user input.
Thanks,
wrong package
** Package changed: pulseaudio (Ubuntu) => pipewire (Ubuntu)
** Attachment removed: "ProcEnviron.txt"
https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2003743/+attachment/5643065/+files/ProcEnviron.txt
** Attachment removed: "ProcCpuinfoMinimal.txt"
Public bug reported:
Audio does not work on the MSI Z690 TOMAHAWK WIFI DDR4 (MS-7D32)
motherboard when using Kubuntu 22.10 due to Realtek ALC4080 USB audio
device issues. Earlier ALC4080 problems were resolved against Gnome but
under Plasma desktop it's still broken due to a pipewire problem.
Public bug reported:
hi Steve
recently in version 8.2112.0-2ubuntu1, 29 Dec 2021
the postinst would `chgrp syslog /var/log`
but then logrotate will not rotate files any more
unless in the file `/etc/logrotate.d/rsyslog` the option
`su root syslog`
is added
regards
a.
ProblemType: Bug
Confused about this bug.
The first entry refers to Go package compilation failing for
libcap-2.32. It is not clear which version of golang is installed, but
the whole module support for Go has changed substantially since
libcap-2.32 was new. Modern golang does not work with that old version
of
Had not heard about this specifically before. Some bug fixes to
pam_cap.so found by static analysis:
https://git.kernel.org/pub/scm/libs/libcap/libcap.git/commit/?id=954a5ce4fdf195e062909f2c921d8f915d2905b9
This was fixed upstream in libcap-2.25 :
https://git.kernel.org/pub/scm/libs/libcap/libcap.git/commit/?id=9c3d89fbb9d819ade80b544f8a35f7b90c07cd14
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libcap2 in Ubuntu.
Is this still a problem with libcap-2.66 ?
https://git.kernel.org/pub/scm/libs/libcap/libcap.git/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libcap2 in Ubuntu.
https://bugs.launchpad.net/bugs/1955804
Title:
make and
FWIW This used to be the default inside the libcap build tree, but the problems
with the container defaults (eventually fixed with
https://github.com/moby/moby/security/advisories/GHSA-2mm7-x5h6-5pvq
) changed my position on this:
as ~larsoner mentioned, those scripts contain some `return` but not in
functions, so they may fail in some cases; you should change all
`return` to `exit 0`
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
*** This bug is a duplicate of bug 1958267 ***
https://bugs.launchpad.net/bugs/1958267
Hello,
I can confirm, this is not a duplicate.
I've updated the wpasupplicant package to the fixes version on Ubuntu 22.04.
wpasupplicant:
Installed: 2:2.10-6ubuntu1
Candidate: 2:2.10-6ubuntu1
*** This bug is a duplicate of bug 1949970 ***
https://bugs.launchpad.net/bugs/1949970
This appears to have been addressed in bug #1949970 by making use of a
feature of the PAM config. In /etc/pam.d/lightdm, I see e.g.
-authoptionalpam_gnome_keyring.so
-authoptional
Note to everyone watching this bug:
The file that John modified above is in the "extra profiles" section of
the upstream AppArmor source repository. It may be found on an Ubuntu
system at
/usr/share/apparmor/extra-profiles/sbin.dhclient
and in jammy, it has his fix.
However, the
This message...
type=AVC msg=audit(1625678140.496:1898): apparmor="DENIED"
operation="open" profile="/{,usr/}sbin/dhclient"
name="/proc/8537/task/8540/comm" pid=8537 comm="dhclient"
requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
...is actually for a different issue, discussed at LP:
Note that the /proc/XX/task/YY/comm denials are addressed in LP:
#1918410.
That leaves two of this sort:
audit: type=1400 audit(1645193286.560:2012): apparmor="DENIED"
operation="mknod" profile="/{,usr/}sbin/dhclient"
name="/run/NetworkManager/dhclient-oob_net0.pid" pid=103303
** Tags added: jammy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1965923
Title:
rc.apparmor.functions should not mount /sys/kernel/security inside a
chroot
Public bug reported:
This concerns apparmor 3.0.4-2ubuntu2 in Ubuntu jammy.
When I run a command like aa-teardown(8), it will mount securityfs on
/sys/kernel/security if this is not already mounted.
On bare metal, this is reasonable. But in a chroot environment, the
command should probably exit
Public bug reported:
when attempting to play the vp8.webm file causes the Videos file to
crash
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: libgstreamer1.0-0 1.16.2-2
ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-27-generic x86_64
ApportVersion:
Public bug reported:
I have two mice each with their own dongle. 1 is the microsoft sculpt
keyboard mouse combo and the other is a logitech master2 (using dongle
not bluetooth). Both of the mice work while in the login screen but
once you log in neither will control the cursor.
I know they are
The kernel patch for 9710 is now in the sound subsystem tree, it should
be in linux-next sometime later today
https://mailman.alsa-project.org/pipermail/alsa-
devel/2021-August/188208.html
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Observed in B/aws (kernel 4.15), cycle sru-20210621.
--
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/1783881
Title:
ltp-syscalls: msgstress03 / msgstress04 fails because
Observed in B/aws (kernel 4.15), cycle sru-20210621.
--
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/1783881
Title:
ltp-syscalls: msgstress03 / msgstress04 fails because
Observed this on B/oracle-5.4, cycle sru-20210621 .
** Tags added: oracle
** Also affects: ubuntu-kernel-tests
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
** Also affects: lxc
Importance: Undecided
Status: New
** No longer affects: lxc
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1886790
Title:
lxc
Observed on B/aws-5.4 , cycle 20210621.
** Tags added: 5.4 aws bionic sru-20210621
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1886790
Title:
lxc 3.0.3-0ubuntu1~18.04.1
Observed in B/aws-5.4, cycle sru-20210621.
--
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/1783881
Title:
ltp-syscalls: msgstress03 / msgstress04 fails because systemd
nameserver
[regression potential]
failure to correctly notify systemd-resolved about new dhclient-
provided nameserver(s)
[scope]
this is needed for f and earlier
in g and later the hook script is moved to the isc-dhcp package, and
edited to correctly check is-enabled systemd-resolved
** Summary changed:
- lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with 5.4 kernels in Bionic
+ lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with B/5.4 kernels
(device_add_remove_test)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
*** This bug is a duplicate of bug 1886790 ***
https://bugs.launchpad.net/bugs/1886790
** This bug has been marked a duplicate of bug 1886790
lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with 5.4 kernels in Bionic
--
You received this bug notification because you are a member of Ubuntu
Yes, it is still an issue in focal. Was there an update since last year
that should have addressed this?
** Changed in: systemd (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd
includes a dns nameserver, verify resolvconf is using that dhcp-
provided nameserver
[regression potential]
failure to correctly notify systemd-resolved about new dhclient-
provided nameserver(s)
[scope]
this is needed for f and earlier
in g and later the hook script is moved
Found on B-5.4/aws, cycle sru-20210531 .
** Tags added: sru-20210531
--
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/1783881
Title:
ltp-syscalls: msgstress03 /
Observed with B-5.4/aws, cycle sru-20210531 .
** Tags added: sru-20210531
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1884024
Title:
lxc-test-device-add-remove from
Issue observed for a long time in 5.8 kernels, for example G/KVM.
** Tags added: 5.8 groovy kvm sru-20210531
** Tags added: sru-20210510
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https
Marked https://bugs.launchpad.net/bugs/1900662 as duplicate of this one.
Same issue, and seems (per Christian) that is fixed on 4.0.6 .
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
p on hardware with an nVidia card and select to
install 3rd party drivers
2. Proceed with installation
The following error message is displayed in /var/log/syslog
/plugininstall.py: Verifying downloads ...
/plugininstall.py: Failed to find package object for
/cdrom//pool/main/g/gcc-defaults/gcc_9
nsyde:bvrF.16:bd04/24/2014:br15.22:efr86.26:svnHewlett-Packard:pnHP15TSNotebookPC:pvr097412405F0620180:rvnHewlett-Packard:rn2211:rvr86.26:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
dmi.product.name: HP 15 TS Notebook PC
dmi.product.sku: G
is Version
dmi.ec.firmware.release: 86.26
dmi.modalias:
dmi:bvnInsyde:bvrF.16:bd04/24/2014:br15.22:efr86.26:svnHewlett-Packard:pnHP15TSNotebookPC:pvr097412405F0620180:rvnHewlett-Packard:rn2211:rvr86.26:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
dmi.pr
de:bvrF.16:bd04/24/2014:br15.22:efr86.26:svnHewlett-Packard:pnHP15TSNotebookPC:pvr097412405F0620180:rvnHewlett-Packard:rn2211:rvr86.26:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
dmi.product.name: HP 15 TS Notebook PC
dmi.product.sku: G
That's interesting, I just performed your suggested test, and I couldn't
reproduce - it's a fresh Ubuntu 20.04 install, running MATE (not KDE!)
and GNU screen 4.8.0-1. After closing the terminal, I've opened another
one and "screen -x" worked fine, as expected.
Could you try to use MATE / Gnome
Oh, so it's explained! Thanks Javier for the data. You're using an
outdated version of the package that doesn't contain this fix. You need
initramfs-tools version 0.122ubuntu8.17 - you can either try to get an
updated cloud image, or after the first boot you may be able to update
it (you could
Thanks for the report Javier! What version of initramfs-tools are you
using ?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1573095
Title:
Cloud images fail to
John, thanks a lot for your report! Definitely we don't want to delay boots -
although I'm happy to hear that eventually it boots. Can you send me logs so I
can understand what's going on?
My suggestion is to follow the steps below (as root user):
(0) [optional] Force a log rotation, in order
I was able to verify this bug with systemd from bionic-proposed (version
237-3ubuntu10.43) by following the procedure in the test case; it's
working as expected, I can see 64M in the memlock limit.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done
This is a very old LP bug, but for completeness it worth mentioning here
that recently some patches were merged on initramfs-tools and
cryptsetup, that allow a good experience booting with LUKS-encrypted
rootfs on top of a degraded RAID1 array; for details, please check:
Thanks for releasing the packages in -proposed Lukasz. I was able to
complete the validation for the Focal version, following the procedure
in the description. An user reported internally to me that the
verification of Bionic version was also successful, hence I'm hereby
marking this LP as
ols (Ubuntu)
Importance: Undecided
Status: New
** Changed in: initramfs-tools (Ubuntu)
Importance: Undecided => Medium
** Changed in: initramfs-tools (Ubuntu)
Status: New => Fix Released
** Changed in: initramfs-tools (Ubuntu)
Assignee: (unassigned) => Guilherm
Thanks a lot Alex for your review from a security point-of-view. And thanks
again Lukasz for dealing with this SRU!
Cheers,
Guilherme
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
Thanks a bunch mfo!!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1879980
Title:
Fail to boot with LUKS on top of RAID1 if the array is broken/degraded
Status
Hi Eric, all the changes are part of the same functionality - the local-bottom
script for example is a clean-up for the files created in the local-top phase.
I think it'd be unnecessary verbosity to explain file by file, and this bug is
waiting for a long time to be fixed (especially due to the
** Patch added: "bionic_cryptsetup_lp1879980.debdiff"
https://bugs.launchpad.net/ubuntu/focal/+source/mdadm/+bug/1879980/+attachment/5411486/+files/bionic_cryptsetup_lp1879980.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Patch added: "focal_cryptsetup_lp1879980_V2.debdiff"
https://bugs.launchpad.net/ubuntu/focal/+source/mdadm/+bug/1879980/+attachment/5411485/+files/focal_cryptsetup_lp1879980_V2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
After the cryptsetup FTBFS investigation (on LP #1891473), coincidentally a
security fix was released for such package, that included a fix for the FTBFS.
So, this is a "rebase" on top of the latest version for Focal/Groovy - Bionic
wasn't affected, but I'm re-uploading its debdiff
** Patch added: "This is the (tested) debdiff with the proposed SRU, for Bionic
only."
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1830746/+attachment/5409870/+files/bionic_systemd_lp1830746.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch
e/ubuntu/test1830746
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Focal)
Status: New => Fix Released
** Changed in: systemd (Ubuntu Focal)
Importance: Undecided => High
** Changed in: systemd (Ubuntu Focal)
ystemd (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: systemd (Ubuntu Cosmic)
Importance: Undecided => High
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
** Changed in: systemd (Ubuntu Disco)
Importance: Undecided =>
I've managed to verify the initramfs-tools Focal-proposed package
(version 0.136ubuntu6.3) by following 2 approaches, given that we don't
have its cryptsetup counter-part released yet:
(a) The verification by "negation" aims to check if we don't have
regression, by testing if the new package
I've tested the Focal-proposed initramfs-tools (version 0.136ubuntu6.3 )
according to the "Test Case" section in the description, and it's working as
expected. Also, the armhf autopkgtest failure is no longer an issue (test was
re-executed with success), so marking as verified!
Cheers,
The ARMHF testing was retried (thanks mfo!) and passed, likely flaky
network issues during the test. Also, since Focal was successful to
build and no issues on autopkgtest were reported (i.e., no test fails
detected), I'm hereby marking this as verified.
Cheers,
Guilherme
** Tags removed:
After discussing with Eric, seems initramfs-tools was "released" in
Groovy (even with autopkgtest), so I'm hereby attaching an updated
debdiff only with the autopkgtest fix.
** Patch added: "groovy_initramfs_lp1879980_lp1893675_V3.debdiff"
** Patch added: "focal_initramfs_lp1879980_V2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1879987/+attachment/5406228/+files/focal_initramfs_lp1879980_V2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
An issue on initramfs-tools autopkgtest was found in Groovy and Focal (see LP
#1893675) - it's non-related with the fixes proposed here, but we need to make
autopkgtest happy or we cannot get the package released, so here goes the V2 of
the initramfs-tools debdiffs.
Notice the SRU is mainly
Worth to notice that the cryptsetup release is blocked on LP #1891473 -
there's a failure on building this package from source introduced by a
recent PPA builder upgrade (from Xenial to Bionic).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
** Patch added: "focal_initramfs_lp1879980_V2.debdiff"
https://bugs.launchpad.net/ubuntu/focal/+source/mdadm/+bug/1879980/+attachment/5406230/+files/focal_initramfs_lp1879980_V2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
An issue on initramfs-tools autopkgtest was found in Groovy and Focal (see LP
#1893675) - it's non-related with the fixes proposed here, but we need to make
autopkgtest happy or we cannot get the package released, so here goes the V2 of
the initramfs-tools debdiffs.
Notice the SRU is mainly
Although the debdiffs are being hereby attached, the SRU track is
ongoing in LPs #1879987 and #1879980.
** Patch added: "groovy_initramfs_lp1879980_V2.debdiff"
** Patch added: "focal_initramfs_lp1879980_V2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1893675/+attachment/5406204/+files/focal_initramfs_lp1879980_V2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
** Description changed:
[Impact]
* Currently the initramfs-tools autopkgtest fails for at least AMD64, with
the following signature:
"mount: /tmp/autopkgtest.K1r92h/build.zdS/src/mnt: special device
/dev/loop0p1 does not exist."
* The reason for that is the test trying immediately to
: Guilherme G. Piccoli (gpiccoli)
Status: In Progress
** Also affects: initramfs-tools (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: initramfs-tools (Ubuntu Focal)
Status: New => In Progress
** Changed in: initramfs-tools (Ubuntu Groovy)
Importa
test is not executed in Debian CI given that CI has
no support for VMs, and this test requires that.
** Affects: initramfs-tools (Ubuntu)
Importance: Undecided
Assignee: Guilherme G. Piccoli (gpiccoli)
Status: In Progress
** Tags: seg
--
You received this bug notification beca
After about 10 weeks, finally my patch was merged by the Debian
maintainer: https://salsa.debian.org/kernel-team/initramfs-
tools/-/commit/c3cbf355
Cheers,
Guilherme
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Attaching a new Bionic debdiff, which now includes a fix for a third bug
(LP #1820929).
** Patch added: "bionic_initramfs_lp1879980_V2.debdiff"
https://bugs.launchpad.net/ubuntu/focal/+source/mdadm/+bug/1879980/+attachment/5401090/+files/bionic_initramfs_lp1879980_V2.debdiff
--
You received
Attaching a new Bionic debdiff, which now includes a fix for a third bug
(LP #1820929).
** Patch added: "bionic_initramfs_lp1879980_V2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1879987/+attachment/5401089/+files/bionic_initramfs_lp1879980_V2.debdiff
--
You
Although the debdiff is hereby attached, 3 bugs have fixes carried on
such patch - the main work is done on LP ##1879980 (and the other LP
handled in this SRU is #1879987) .
** Tags added: sts
** Description changed:
- This bug is a follow-up to
+ [Impact]
-
signed) => Guilherme G. Piccoli (gpiccoli)
** Changed in: initramfs-tools (Ubuntu Bionic)
Assignee: Guilherme G. Piccoli (gpiccoli) => Jay Vosburgh (jvosburgh)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ini
Just got a test result from an user that reported the issue - the packages with
the proposed patches [0] fixed the issue to him.
cheers,
Guilherme
[0] https://launchpad.net/~gpiccoli/+archive/ubuntu/lp1879980
--
You received this bug notification because you are a member of Ubuntu
Touch
** Patch added: "focal_initramfs_lp1879980.debdiff"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1879987/+attachment/5398703/+files/focal_initramfs_lp1879980.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Patch added: "xenial_initramfs_lp1879987.debdiff"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1879987/+attachment/5398705/+files/xenial_initramfs_lp1879987.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Worth to notice that the debdiffs (except Xenial's) include a fix for LP
#1879980 - we are doing a single SRU for 2 bugs.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
1 - 100 of 606 matches
Mail list logo
