Public bug reported:
Description:
An error in archive_wstring_append_from_mbs() (archive_string.c)
triggers an out-of-bounds read memory access that results into a crash,
via a specially crafted archive file. This bug was found using our
custom fuzzer.
Basic Information:
Version of libarchive:
This affects me too. I started seeing the error in dmesg after upgrading
from 16.04 to 18.04. Everything seems to work fine, but the message is
scary.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Description changed:
[impact]
dhclient fails to notify resolved about DNS servers due to bash-specific
redirect inside 'resolved' hook script
[test case]
see original description below
[regression potential]
any regression would likely cause resolved not to be
** Also affects: systemd (Ubuntu Focal)
Importance: Low
Status: Triaged
** Also affects: systemd (Ubuntu Eoan)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Eoan)
Status: New => Fix Released
** Changed in: systemd (Ubuntu Focal)
Status:
>these messages actually come from the kernel, I believe they are
expected (maybe only in secure boot >mode, I haven't looked into the new
'lockdown' stuff yet). The lack of 'kernel_lockdown' manpage >appears to
be already reported in bug 1767971.
This PC is indeed using secure boot. Here are the
All autopkgtests for the newly accepted systemd (240-6ubuntu5.8) for disco have
finished running.
The following regressions have been reported in tests triggered by the package:
prometheus-bind-exporter/unknown (armhf)
php7.2/7.2.24-0ubuntu0.19.04.1 (armhf)
gvfs/1.40.1-1ubuntu0.1 (ppc64el)
All autopkgtests for the newly accepted systemd (240-6ubuntu5.8) for disco have
finished running.
The following regressions have been reported in tests triggered by the package:
prometheus-bind-exporter/unknown (armhf)
php7.2/7.2.24-0ubuntu0.19.04.1 (armhf)
gvfs/1.40.1-1ubuntu0.1 (ppc64el)
All autopkgtests for the newly accepted systemd (240-6ubuntu5.8) for disco have
finished running.
The following regressions have been reported in tests triggered by the package:
prometheus-bind-exporter/unknown (armhf)
php7.2/7.2.24-0ubuntu0.19.04.1 (armhf)
gvfs/1.40.1-1ubuntu0.1 (ppc64el)
All autopkgtests for the newly accepted systemd (240-6ubuntu5.8) for disco have
finished running.
The following regressions have been reported in tests triggered by the package:
prometheus-bind-exporter/unknown (armhf)
php7.2/7.2.24-0ubuntu0.19.04.1 (armhf)
gvfs/1.40.1-1ubuntu0.1 (ppc64el)
Public bug reported:
Sometimes when I play a clip (be it a Video, song or a radiostation, it
doesn't matter) and I have the volume lowered to 10% I can't hear any
sound whatsoever. Not until I raise the volume with Fn + F12 (F12 has a
speaker icon on it to raise the volume).
It's as if
The test case here should explain to the tester how to set up an nspawn
container to reproduce this.
** Changed in: systemd (Ubuntu Disco)
Status: In Progress => Incomplete
** Changed in: systemd (Ubuntu Bionic)
Status: In Progress => Incomplete
--
You received this bug
This has been wrongly marked as fixed in eoan. It's not; the fix for
this is still in eoan-proposed in systemd 242-7ubuntu3.2. I don't know
why the separate bug LP: #1849608 was used for that SRU vs this one.
Maybe the argument is that in eoan, systemd-resolved is *never*
restarted, instead of
*** This bug is a duplicate of bug 1805183 ***
https://bugs.launchpad.net/bugs/1805183
** This bug has been marked a duplicate of bug 1805183
systemd-resolved constantly restarts on Bionic upgraded from Xenial
--
You received this bug notification because you are a member of Ubuntu
Touch
Hello Dan, or anyone else affected,
Accepted systemd into disco-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/240-6ubuntu5.8
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Dan, or anyone else affected,
Accepted systemd into disco-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/240-6ubuntu5.8
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello jrb0001, or anyone else affected,
Accepted systemd into disco-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/240-6ubuntu5.8
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Dan, or anyone else affected,
Accepted systemd into disco-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/240-6ubuntu5.8
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Che, or anyone else affected,
Accepted systemd into disco-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/240-6ubuntu5.8
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Christian, or anyone else affected,
Accepted systemd into disco-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/240-6ubuntu5.8
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Steve, or anyone else affected,
Accepted systemd into disco-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/240-6ubuntu5.8
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Neil, or anyone else affected,
Accepted systemd into disco-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/240-6ubuntu5.8
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Tom, or anyone else affected,
Accepted systemd into disco-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/240-6ubuntu5.8
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
*** This bug is a duplicate of bug 1805183 ***
https://bugs.launchpad.net/bugs/1805183
** This bug is no longer a duplicate of bug 1849608
systemd resolv should separate the output of stdout and stderr
** This bug has been marked a duplicate of bug 1805183
systemd-resolved constantly
** Description changed:
[impact]
calling the glibc function sync_file_range() on a armhf nspawn container
fails.
[test case]
see sample C program from original description below. compile and run
that inside a nspawn container on armhf and it will fail.
+
+ nspawn
Public bug reported:
applying the latest update
ProblemType: Package
DistroRelease: Ubuntu 19.10
Package: linux-firmware 1.183.1
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu8.2
Architecture:
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
All autopkgtests for the newly accepted systemd (240-6ubuntu5.8) for disco have
finished running.
The following regressions have been reported in tests triggered by the package:
prometheus-bind-exporter/unknown (armhf)
php7.2/7.2.24-0ubuntu0.19.04.1 (armhf)
gvfs/1.40.1-1ubuntu0.1 (ppc64el)
All autopkgtests for the newly accepted systemd (240-6ubuntu5.8) for disco have
finished running.
The following regressions have been reported in tests triggered by the package:
prometheus-bind-exporter/unknown (armhf)
php7.2/7.2.24-0ubuntu0.19.04.1 (armhf)
gvfs/1.40.1-1ubuntu0.1 (ppc64el)
All autopkgtests for the newly accepted systemd (240-6ubuntu5.8) for disco have
finished running.
The following regressions have been reported in tests triggered by the package:
prometheus-bind-exporter/unknown (armhf)
php7.2/7.2.24-0ubuntu0.19.04.1 (armhf)
gvfs/1.40.1-1ubuntu0.1 (ppc64el)
All autopkgtests for the newly accepted systemd (240-6ubuntu5.8) for disco have
finished running.
The following regressions have been reported in tests triggered by the package:
prometheus-bind-exporter/unknown (armhf)
php7.2/7.2.24-0ubuntu0.19.04.1 (armhf)
gvfs/1.40.1-1ubuntu0.1 (ppc64el)
All autopkgtests for the newly accepted systemd (240-6ubuntu5.8) for disco have
finished running.
The following regressions have been reported in tests triggered by the package:
prometheus-bind-exporter/unknown (armhf)
php7.2/7.2.24-0ubuntu0.19.04.1 (armhf)
gvfs/1.40.1-1ubuntu0.1 (ppc64el)
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1851906
Title:
package cups-daemon 2.1.3-4ubuntu0.10 failed to install/upgrade:
Public bug reported:
Every time a notification pops up that there is some bug in the system
!!
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: cups-daemon 2.1.3-4ubuntu0.10
ProcVersionSignature: Ubuntu 4.15.0-66.75~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-66-generic x86_64
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cups (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in 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 initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1851883
Title:
package linux-firmware 1.183.1 failed to install/upgrade:
** Changed in: apparmor
Assignee: Tyler Hicks (tyhicks) => juan serven (juanserven)
--
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/1668892
Title:
CVE-2017-6507:
** Changed in: notary (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nspr in Ubuntu.
https://bugs.launchpad.net/bugs/1851695
Title:
DEP8 failure/regression in nspr on arm64 and armhf
Public bug reported:
I encountered the following exception in python-apport while
encountering an exception `bup` which uses `python-apport`. I'm sure
that the exception lies in the responsibility of `python-apport` (the
`AttributeError` stacktrace is relevant):
```
Traceback (most recent call
Public bug reported:
I am unable to adjust the brightness of the backlight of my laptop
screen either by using the slider of by changing the value in
/sys/class/backlight/intel_backlight/brightness directly.
I have tried changing my GRUB configuration:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash
Public bug reported:
While each window partly unresponsive, the system did not freeze up completely.
I was still able to switch active windows or change to different desktops.
But within each window, only the previously active part I was still able to
interact with.
For example in my browser,
** Also affects: notary (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nspr in Ubuntu.
https://bugs.launchpad.net/bugs/1851695
Title:
DEP8 failure/regression in nspr on
Note: I ensured that the ppa uses focal-proposed, now there are even
more issues.
x86:
checking for python extension module directory... Traceback (most recent call
last):
File "", line 20, in
File "/usr/lib/python3.8/sysconfig.py", line 512, in get_path
return get_paths(scheme, vars,
Attached is a debdiff for the Xenial version of the backport. In
addition to the snap policy module patches, this includes a backport of
the libjson-c dependency removal changes from Pulse Audio 10.0 (which
applied cleanly without modification). This is required because
libjson-c and
I think i found a solution. I'm commenting this lines
#load-module module-switch-on-port-available
#load-module module-switch-on-connect
in etc/pulse/default.pa
and all work for me.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
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 1850986
When reporting bugs in the future please use apport by using 'ubuntu-
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cups (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
** Summary changed:
- DEP8 failure/regression in arm64 and armhf
+ DEP8 failure/regression in nspr on arm64 and armhf
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nspr in Ubuntu.
https://bugs.launchpad.net/bugs/1851695
apport information
** Tags added: apport-collected third-party-packages tina
** Description changed:
1st Neither
ubuntu-bug linux nor sudo ubuntu-bug linux
sudo cat /proc/version_signature > version.log
sudo lspci -vnvn > lspci-vnvn.log
work!
2 Bug reporting is so hard!
** Bug watch added: Debian Bug tracker #944346
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944346
** Also affects: notary (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944346
Importance: Unknown
Status: Unknown
--
You received this bug notification because
We are currently on golang 1.12.12, upstream has fixes in that regard
but while trying to identify I found issue [1] and think this is what we
face atm. There isn't a solution yet and my go-foo is too low.
This also affects Debian [2] and I'll file a bug there as well for awareness.
The tests
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1850986/+attachment/5303818/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1850986/+attachment/5303817/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1850986/+attachment/5303819/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
Problem occurs when using 5 Port HDMI switcher by Amazon. Works well with
everything else except PC.
On another note I cannot get my motherboard HDMI or Displayport sockets to
work. Why is this?
** Attachment removed: "ProcCpuinfoMinimal.txt"
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1850986/+attachment/5303815/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1850986/+attachment/5303821/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1850986/+attachment/5303816/+files/ProcEnviron.txt
** Description changed:
1st Neither
ubuntu-bug linux nor sudo ubuntu-bug linux
sudo cat /proc/version_signature > version.log
sudo lspci
This was triggered by:
- sync of newer nspr
- merge of newer nss
They all fail the same way.
I did run this with/without the elements from proposed - it just is
broken before any or "our" changes.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
The test history indicates this might be due to some golang changes and
indeed the entry point to the test is /usr/bin/dh_golang_autopkgtest.
While autopkgtest says:
autopkgtest [10:12:21]: test command1: preparing testbed
as usual.
There actually is no debian/test* at all, so this must be
As I expected this is the actual go build that breaks.
The package atm is also FTBFS in focal with the same error.
Buildlog: http://paste.ubuntu.com/p/dfYqvVhVBh/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nspr in
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1850986/+attachment/5303822/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1850986/+attachment/5303820/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
I can confirm that @robertjjoynt's comment works very well on my HP
ProBook 650 G1 pc which is currently operating ubuntu 18.04 (long card
name: "HDA Intel HDMI at 0xd073 irq 33).
I should say that the sound still clips every so often, but I can
finally listen to Smashmouth in peace while
Please collect an alsa-info.txt with coeff dumped:
sudo su
echo 1 > /sys/module/snd_hda_codec/parameters/dump_coef
then run alsa-info and upload the log.
thx.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in
I note this is the same problem indicator-messages had in bug 1843740.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libindicator in Ubuntu.
https://bugs.launchpad.net/bugs/1851154
Title:
libindicator ftbfs:
65 matches
Mail list logo
