Package is in proposed now. Testing in an LXC container shows a fix of
this behavior.
$ lxc launch ubuntu-daily:noble n
$ lxc shell n
# dpkg -s rsync | grep Version:
Version: 3.2.7-1build2
# rsync -F --delete-after --archive /etc/os-release /tmp/
*** buffer overflow detected ***: terminated
The debian patch looks promising in my local testing. I uploaded a test
package to run dep8 tests against. If those look green I'll submit my MP
and get it in ASAP.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in
** Changed in: rsync (Ubuntu)
Assignee: (unassigned) => Mitchell Dzurick (mitchdz)
** Changed in: rsync (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in
This looks like it could already be fixed in debian with
https://salsa.debian.org/debian/rsync/-/commit/d3a0eccf989175b096c10b6c42b02b1ee1306a00
I'll try an ubuntu build with this patch and report back.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Also affects: rsync (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: rsync (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: rsync (Ubuntu Mantic)
Importance: Undecided
Status: New
** Changed in: rsync (Ubuntu Focal)
I was able to reproduce this in a noble LXD container.
$ lxc launch ubuntu-daily:noble n
$ lxc shell n
# ssh-keygen -t rsa
# cat ~/.ssh/id_rsa.pub >> ~/.ssh/authorized_keys
# touch testfile.txt
# rsync -F --delete-after --archive /root/testfile.txt 127.0.0.1:/tmp/
The authenticity of host
Quickly testing Jammy/Mantic in a similar fashion as above I do not see
the buffer overflow.
** Changed in: rsync (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
Just want to update this bug - I have not found a fix for this. Instead
I've been relying on the Logitech universal receiver which is working
great in my experience.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in
Thanks Tim! With more people having a seemingly similar issue I re-
opened it as New and subscribed ubuntu-server to take a look at this
again.
** Changed in: dnsmasq (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Ran the autopkgtest on a new PPA with my changes enabled by default and
the test still fails[0]. I believe this is fine enough to ignore simply
because this test has always been failing like this.
[0] - https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-mitchdz-
python2.7-opt-test-enabled-
The only focal autopkgtest that really has me confused in the python2.7
failure. This is due to a unit test that fails. The strange thing is
that this unit test actually fails in the Jammy autopkgtest, but the
Jammy autopkgtest passes anyways. It has always been like this.
You will see
1643s
I wonder if the latest update to Jammy has fixed the issue? Is this
issue still occurring for you when upgrading to the Jammy package
version 2.90-0ubuntu0.22.04.1 Julia?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
i took a look at the other focal packages and put my thoughts.
RELEASE=focal
TRIGGER=python2.7/2.7.18-1~20.04.4
release arch packageversion exitcode
triggersrequester
--- --- -
Hi Andreas, the test_customize_compiler flag test has always failed. I'm
curious about why it's failing but the autopkgtest as a whole is
passing.
In fact, the same failures occur for both jammy/focal since forever -
yet they seem to be the reason w hy the Focal autopkgtest fails, whereas
Jammy
Thanks a ton Mauricio! Would we be good to start phasing the Jammy
package then while I investigate the Focal failures? I'll start taking a
look at Focal today.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in
mfo: thanks for catching the ctrlc+ctrlv error! It sounds like we are
just waiting to re-run the autopkgtest then.
Let me know if you would like any additional testing from me!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Thanks for taking the time to make this bug report to make Ubuntu
better!
I tried reproducing your failure and unfortunately am not able to in a
VM/container setup. I think this may need some extra configuration to
reproduce the failure.
Starting with something basic, would you mind sharing
I must've opened this bug up in the morning before Marc commented and
just got back around to posting the question. Apologies for asking for
the same information!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in
Also, the various packages here have a similar error message but the
error is probably caused by different things. This is a generic error
message from init-system-helpers.
Now, with that said, I agree init-system-helpers should be more verbose
when this error happens.
--
You received this bug
netvicious or Dan, do you have the AMI that you used to produce that
error with proftpd-core?
I also tried reproduction on ami-0dffe9017aa8424a2 in eu-north-1 and was
not able to reproduce that failure.
I just booted a fresh t3.micro instance with the above AMI, then
proceeded to run `apt update
Thanks for the additional info Ake!
Do you happen to have simple steps you could share to help reproduce the
issue?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2053146
Attached is my manual verification steps of testing the proposed package
for Focal.
Package version tested: 2.7.18-1~20.04.4
Part of the verification process is to ensure no regressions happen in
no-change rebuilds of the current wheels compiled with python2.7 in our
archives. It was determined
Attached is my manual verification steps of testing the proposed package
for Jammy.
Package version 2.7.18-13ubuntu1.2
Part of the verification process is to ensure no regressions happen in
no-change rebuilds of the current wheels compiled with python2.7 in our
archives. It was determined that
That's a great idea Andreas! It's a little difficult to pinpoint the
exact OPT flags as they are bunched up with the other compiler flags, so
I'll add a test in addition to the current ones which makes it easier to
see what's happening.
--
You received this bug notification because you are a
** Merge proposal linked:
https://code.launchpad.net/~mitchdz/ubuntu/+source/python2.7/+git/python2.7/+merge/459844
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
** Description changed:
[ Impact ]
When compiling Python extensions using Python2, CFLAGS optimization
flags are dropped.
This behavior has been caused by our update in this patch
http://archive.ubuntu.com/ubuntu/pool/universe/p/python2.7/python2.7_2.7.18-1~20.04.3.diff.gz
Description Updated. I'll work on getting the patch for Jammy approved
and then I will create the patch for Focal. I expect (and would love)
feedback on wording for the new print statements I made.
** Description changed:
- Compiling a Python extension using Python2 (Python 2.7.18) is making use
Thanks Nafees! I'll go ahead and prepare the SRU and move forward with
it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/2002043
Title:
Python extension modules get
Nafees, while exploring adding this change, a priority is to not cause
any regressions in packages already built in the archives. This is
unfortunately a non-trivial change so I'm proposing making this an opt-
in change, but make an informative message whenever someone compiles
wheels, so they can
** Merge proposal linked:
https://code.launchpad.net/~mitchdz/ubuntu/+source/python2.7/+git/python2.7/+merge/458533
** Changed in: python2.7 (Ubuntu Jammy)
Assignee: Ghadi Rahme (ghadi-rahme) => Mitchell Dzurick (mitchdz)
** Changed in: python2.7 (Ubuntu Focal)
Assignee: Gh
In the terminal I see dpkg-deb (sub-processo): ZSTD_decompressStream error :
Corrupted block detected
which makes me think the package was corrupted in transport.
Try
sudo apt-get clean
sudo apt-get update
** Changed in: openssh (Ubuntu)
Status: New => Incomplete
--
You received
The only Ubuntu delta is now in Debian. Requesting a sync.
** Merge proposal linked:
https://code.launchpad.net/~mitchdz/ubuntu/+source/libmnl/+git/libmnl/+merge/457925
** Tags removed: needs-merge
** Tags added: needs-sync
** Summary changed:
- Merge libmnl from Debian unstable for noble
** Changed in: libmnl (Ubuntu)
Assignee: (unassigned) => Mitchell Dzurick (mitchdz)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libmnl in Ubuntu.
https://bugs.launchpad.net/bugs/2040389
Title:
Merge libmnl f
** Tags added: server-todo
--
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 scripts with relay
Status in dnsmasq
Thank you Ivaylo for creating this bug report and helping make Ubuntu
better!
I have 2 follow up questions:
1. How often do these segmentation faults occur for you?
2. Have you tried to SSH to the Focal server from multiple other systems? Do
you encounter this issue with multiple systems, or is
Hi, I have the patch modified how I want it to, I'm still exploring ways
to blocklist the current launchpad builds, as I'm not sure I can extract
the necessary metadata in distutils.sysconfig.
I'll be exploring more next week and attempting to find a reliable way
to determine the name of the
Thank you Daniel! Over the week I upgraded my laptop to Mantic, so can
no longer test for Jammy.
I still can't discover my logitech mice in Mantic, so maybe still the
same situation.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/2040657/+attachment/5715734/+files/acpidump.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: "modified.conffile..etc.bluetooth.main.conf.txt"
https://bugs.launchpad.net/bugs/2040657/+attachment/5715736/+files/modified.conffile..etc.bluetooth.main.conf.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
apport information
** Attachment added: "syslog.txt"
https://bugs.launchpad.net/bugs/2040657/+attachment/5715738/+files/syslog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: "rfkill.txt"
https://bugs.launchpad.net/bugs/2040657/+attachment/5715737/+files/rfkill.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/2040657/+attachment/5715733/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: "getfacl.txt"
https://bugs.launchpad.net/bugs/2040657/+attachment/5715735/+files/getfacl.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/2040657/+attachment/5715732/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2040657/+attachment/5715730/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/2040657/+attachment/5715729/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/2040657/+attachment/5715731/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/2040657/+attachment/5715728/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/2040657/+attachment/5715726/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/2040657/+attachment/5715727/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/2040657/+attachment/5715725/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/2040657/+attachment/5715723/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
apport information
** Tags added: apport-collected mantic wayland-session
** Description changed:
I lost the proprietary USB dongle and decided I wanted to try bluetooth
with this particular mouse. I am able to connect with bluetooth on
Windows 11, but the device doesn't even show up in
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/2040657/+attachment/5715724/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
Thanks for taking the time to report this bug Timo!
Do you have steps for how you setup dnsmasq so it can be more easy to
reproduce your issue?
** Changed in: dnsmasq (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Hi Virginie, I tried to reproduce this in an LXD vm
$ lxc launch ubuntu:jammy j --vm
$ lxc shell j
# apt install -y sssd-ad sssd-tools realmd adcli
# pam-auth-update --enable mkhomedir
# sudo add-apt-repository "deb http://archive.ubuntu.com/ubuntu $(lsb_release
-sc) main universe restricted
I am able to connect with the unifying receiver which is good enough for
now. It'd still be nice for regular bluetooth to work.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
Actually after opening this bug I decided to try my MX master 3S with
bluetooth mode and that's not detected either. I also tried a pair of
airpods and those are not seen.
the weird part is that I am actively using some samsung galaxy buds with
this laptop via bluetooth and they work.
So perhaps
Public bug reported:
I lost the proprietary USB dongle and decided I wanted to try bluetooth
with this particular mouse. I am able to connect with bluetooth on
Windows 11, but the device doesn't even show up in `bluetoothctl scan
on`.
This is seen on Jammy with bluez 5.64-0ubuntu1
** Affects:
@Markle Liu if you still have your system in the affected state, could
you please give the output of these following commands?
# systemctl status ssh.{socket,service} tinysshd.socket
# lsof -i :22
# systemctl list-units | grep ssh
** Changed in: openssh (Ubuntu)
Status: New => Incomplete
Interesting, I tried in a new LXC container and I see it working now.
$ lxc launch ubuntu:lunar l
$ lxc shell l
# apt install -y openssh-client=1:9.0p1-1ubuntu8 -y --allow-downgrades
# apt install -y openssh-sftp-server=1:9.0p1-1ubuntu8 -y --allow-downgrades
# apt install -y
I only see those errors in a container. When I launch a VM to try this,
I see no errors.
$ lxc launch ubuntu:lunar l-vm --vm
$ lxc shell l-vm
# apt install -y openssh-client=1:9.0p1-1ubuntu8 -y --allow-downgrades
# apt install -y openssh-sftp-server=1:9.0p1-1ubuntu8 -y --allow-downgrades
# apt
Relevant Dpkg errors:
openssh-server (1:9.0p1-1ubuntu8.5) over (1:9.0p1-1ubuntu8)
...
Setting up openssh-server (1:9.0p1-1ubuntu8.5) ...
rescue-ssh.target is a disabled or a static unit not running, not starting it.
Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 145.
dpkg:
Hi Prashanth,
Unless there's a good reason, the Jammy/Focal version of openssh will
stay the version it is. Likely, any changes to this package will be
specific commits which will have to go through the SRU process[0] if it
can be justified.
Is there a reason you are trying to test the latest
** Changed in: openssh (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2038561
Title:
Requesting Ubuntu package manager to
Hello Prashanth, thank you very much for making this bug report and
making Ubuntu better!
Are you building openssl 3.1.2 or pulling the package from somewhere?
I tried installing a slightly newer version in a jammy LXC container and
see this error when trying to install libssl3 (a requirement to
Just adding that I tried rebuilding the package and tests are still
failing 2.6.1+dfsg-3
https://launchpad.net/~mitchdz/+archive/ubuntu/slic3r-prusa-
mantic/+builds?build_text=_state=all
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Hi Nafees, I'll be looking into this bug. Planning to have some more
updates next week.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/2002043
Title:
Python extension
68 matches
Mail list logo
