** Attachment added: "/var/log/installer/dm"
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1871268/+attachment/5417189/+files/dm
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
I have this issue as well on a Lenovo T420s installing a freshly downloaded
20.04.01 LTS image. What's the easiest way to post or collect logs in such
cases?
I wanted to upload all logs but I can add only a single attachement to this
message.
** Attachment added: "/var/log/installer/debug"
Public bug reported:
On Ubuntu Focal desktop 64 bit, neither Samsung SCX-472FD monochrome
laser printer nor HP M254dw colour laser printer prints duplex. Was OK
on Ubuntu Bionic until upgrade to Focal.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: cups 2.3.1-9ubuntu1.1
** Changed in: findutils (Ubuntu)
Status: New => Fix Committed
** Changed in: findutils (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 findutils in Ubuntu.
** Description changed:
+ [Impact]
+
+ * fsck messages is shown by plymouth, despite all fscks already
+ completed.
+
+ [Test Case]
+
+ * Install Ubuntu Desktop with full disk encryption
+
+ * Observe that fsck messages (press ctrl+c) is shown, and remains there
+ on screen for a little
restarting systemd-logind is not safe, as existing sessions can be
logged out.
also performing daemon-reload, mid-boot, also is not safe.
Can you explain the usecase and why these actions are performed
together, racing each other?
--
You received this bug notification because you are a member
Still chasing this down
The apparmor.systemd file is unchanged from focal.
The change is in rc.apparmor.functions which is a dependency of
apparmor.systemd.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in
The patch mentioned alone does not apply on 1.1.1f in Ubuntu, it seems
it also needs
9cc834d966ea5afc38fb829bfe498aed4c5d498d
0d011f540400b425aba1c3e59624ad9dbabe83cb
a1ec85c169a8e53e52ab35914ad47b5baea84070
53eb05bdf00d7237e3b12976c2ac38d68206eb13
e6a80cbad28ee748830815634917efe96948f2f3
Will
** Changed in: openssl (Ubuntu)
Status: New => Triaged
** Changed in: openssl (Ubuntu)
Importance: Undecided => Low
** Changed in: openssl (Ubuntu)
Importance: Low => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Public bug reported:
[Impact]
* needrestart is a better solution to track and restart services that use
openssl
* when needrestart is available, openssl should not ask about restarting
services or rebooting the host, as needrestart is a better way to report that.
[Test Case]
* Install
** Information type changed from Private to Public
** Changed in: openssl (Ubuntu)
Status: Incomplete => In Progress
** Changed in: ubuntu-z-systems
Status: Expired => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
If you require using obsolete, deprecated, old protocols, with weak
keys, and broken hash algorithms you can use these instructions to
downgrade security on your systems https://discourse.ubuntu.com/t
/default-to-tls-v1-2-in-all-tls-libraries-in-20-04-lts/12464/8?u=xnox
** Changed in: openssl
** Changed in: openssl (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1879826
Title:
User interface error when executing
Please use https://www.orange.sk/napiste-nam/internetove-sluzby
/vseobecne-informacie-o-internetovych-sluzbach-a-ich-dostupnosti with
your mobile phone number requesting orange to add support for TLSv1.2
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Instructions on how to make your system insecure and easy to hack are
here https://discourse.ubuntu.com/t/default-to-tls-v1-2-in-all-tls-
libraries-in-20-04-lts/12464/8?u=xnox
** Changed in: openssl (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you
a legacy app most likely will not be using libssl1.1 but the older
libssl1.0.0 which is no longer provided in ubuntu.
you need to create a chroot or a VM, or manually enable old series to
download old libssl1.0 which may still be available for i386.
** Changed in: openssl (Ubuntu)
Status:
Please attempt to reinstall / upgrade the package again.
I.e. $ sudo dpkg --configure -a
or
$ sudo apt install --reinstall libssl1.1
** Changed in: openssl (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Hi,
After inspecting imap4.orangemail.sk host, it appears to only support
TLS1.0 and does not support TLS1.1 or TLS1.2 which have been release
more than 12 years ago and widely adopted. It only supports TLS1.0 which
has been deprecated this year and is no longer supported by default as
it is weak
The patch to address this is rather large, and doesn't quite apply
cleanly to 1.1.1f that we currently ship.
Also there is a workaround for this - just generate a better / different
self-signed cert which is identified as such by openssl.
But I do understand that doing that may be very
The status of this bug is invalid, because we will not downgrade default
security level to the one that allows broken crypto to be used by
default. And instructions on how to self-compromise systems are
available and are currently known to work.
--
You received this bug notification because you
I'm not quite sure about the attempts written in the description of the
bug, as they do not look like correct instructions to downgrade openssl
to Seclevel 0.
If you are looking for instuctions on how to make your systems insecure
and allow using weak keys, broken certificates and obsolete
It is true that said vulnerability is not patched in xenial; but also it
is low; and no public patches for it exist.
Please upgrade to bionic or focal? which are unaffected / fixes
released?
** Information type changed from Public to Public Security
** Also affects: openssl (Ubuntu Xenial)
I am experiencing this same problem and I can confirm that when I mask the
apport-autoreport.service the problem stops.
I am on Ubuntu 20.10 with Kernel 5.8.0-18-generic. I also have Ubuntu 20.04
with Kernel 5.8.0-05-generic and
can confirm the problem does not happen there
John
--
You
Hm, so is desktop working on this? Have we figured out at all what is
happening? Or just the general symptoms that dbus seems to be non-
responsive and then everything goes bad?
** Changed in: dbus (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: dbus (Ubuntu Focal)
Status:
Public bug reported:
* linux lacks CET, not upstream yet
* snapd lacks CET, as golang has no support for CET yet
* libunwind lacks CET, as no upstream support yet
* klibc lacks CET, no upstream support yet
** Affects: golang-defaults (Ubuntu)
Importance: Undecided
Status: New
On a bionic system, with atomics & libc6-lse installed, I observed that
whilst atomics libraries were present in the initrd, and libpthread.
libgcc_s was not at all.
$ lsinitramfs /boot/initrd.img-5.3.0-1034-aws | grep atomics
lib/aarch64-linux-gnu/atomics
lib/aarch64-linux-gnu/atomics/libc.so.6
Public bug reported:
https://github.com/openssl/openssl/pull/9780/files breaks golang, so
would be useful to backport in bionic which ships openssl 1.1.1 now too.
** Affects: openssl (Ubuntu)
Importance: Undecided
Status: New
** Affects: openssl (Ubuntu Bionic)
Importance:
This bluetooth stutter bug still exists in 20.04. On my system, it
stutters when the screensaver tries to kick in and music is playing from
the files on a hard drive. Currently using Clementine, but seems to
occur regardless of which music player is being used.
--
You received this bug
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to kmod in Ubuntu.
https://bugs.launchpad.net/bugs/1894611
Title:
kmod in bionic can't parse
can you look in dmesg or kern.log for the actual apparmor denial?
> I have absolutely no idea what "ixr"
allow r (read) permission
allow ix == on eXecute inherit the current profile
an exec permission can specify different options that should be taken,
inherit the current profile, transition to
Public bug reported:
kmod in bionic can't parse hwe/cloud kernel signatures
kmod 27 https://lwn.net/Articles/812803/
linxu v5.2-rc1 changed kernel module signatures, which bionic's kmod 24
cannot parse. Only kmod 27 gained that ability.
But we have backported v5.3+ kernels to bionic, resulting
All tests run automatically, and yes flatpak-builder was automatically
tested and new flatpak with this fix migrated fine.
See http://autopkgtest.ubuntu.com/packages/flatpak-builder/groovy/s390x
** Also affects: flatpak (Ubuntu)
Importance: Undecided
Status: New
** Changed in: flatpak
** Description changed:
[Impact]
* update-initramfs -u fails on arm64 m6g instances in AWS
[Test Case]
* launch m6g instance in AWS
* install libc6-lse (if not installed)
* run $ update-initramfs -u
* It should suceed
+ * It should contain pthread, and libgcc_s
to make it recover. Only way to recover seems to be to do a
cold reboot. A simple warm reboot does not fix the problem, but this
can be related to problem 1.
A few dumps
john@hydra:~$ dmesg | fgrep 'Blue'
[3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0
[8.417252
@satmandu
Thank you for pointing that documentation out.
It is correct that it is helpful to test Proposed, but I think that
information was written when packages in proposed were only published
for stable series, which only contain prospective Stable Release
Updates, and is the way "for testing
The deps are now out of date. At least mozjs68 has now moved.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libffi in Ubuntu.
https://bugs.launchpad.net/bugs/1892915
Title:
gnome-shell crashing (libffi8ubuntu1 upgrade
also using groovy-proposed is not supported, as it contains incompatible
mix of packages.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libffi in Ubuntu.
https://bugs.launchpad.net/bugs/1892915
Title:
gnome-shell
I'm not quite sure what is the point of wireguard package / wireguard-
tools on Ubuntu.
Our kernel ships wireguard modules by default anyway, and one can
configure wireguard via networkd and soon via netplan. Which is our
default tooling to interact with the wireguard kernel module.
wg /
Also see prior discussions on similar topic at
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1713803
--
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/1892798
Title:
Arch used to use openresolv, openresolv compat was added to systemd-
resolved, and yes hence they were able to switch to systemd-resolved
providing openresolv symlink / compat / integration. Either by default,
or as an option.
That is not possible for Debian/Ubuntu because of more than three
Ubuntu/Debian has never used openresolv, and yes systemd-resolved had a
contribution to have openresolv compatible input interface.
I am not asking for wireguard to implement any legacy/compat interfaces,
but use directly systemd-resolved standard interface which has abi
guarantees.
There is a
wireguard package => please feed DNS data direct to systemd-resolved
using either dbus or the cli.
--
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/1892798
Title:
In ubuntu everything should feed DNS information direct into resolved whenever
possible.
We are working on improving it, for example in groovy isc-dhcp-client &
ifupdown started to do that too.
Unfortunately systemd's resolved's resolvctl is not compatible with
Debian's/Ubuntu's historical
I have the same problem. I ran Pop!_OS 20.04 from USB and the bluetooth
worked fine. And after doing a clean install, bluetooth also worked. But
when I did the initial updates, I had the same problem: device appeared
in settings and connected, but no sound. Something in the initial
updates messed
Proof that we must not use performance governor attached, from one of my
team mates.
** No longer affects: systemd (Ubuntu)
** Attachment added: "performance-governor.jpg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885730/+attachment/5403156/+files/performance-governor.jpg
--
** Description changed:
[Impact]
* Kernel should have sensible default governor set to
CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y for the generic, hwe, raspi,
- riscv64, oem kernel flavours in Focal and Groovy+.
+ riscv, oem kernel flavours in Focal and Groovy+.
* ondemand.service
** Description changed:
- In a recent merge from Debian we lost ondemand.service, meaning all CPUs
- now run in Turbo all the time when idle, which is clearly suboptimal.
+ [Impact]
- The discussion in bug 1806012 seems misleading, focusing on p-state vs
- other drivers, when in fact, the
** Summary changed:
- Bring back ondemand.service or switch kernel default governor for pstate -
pstate now defaults to performance governor
+ Please switch default kernel governor to ondemand, such that advanced
userspace utilities such as game-mode can be later used to rev-up to to
Plymouth does not clear the footer at the end of fsck.
But with that fix in-place it still looks like fsckd flickers the ctrl+c
message, despite not having any progress to show.
** Changed in: plymouth (Ubuntu Groovy)
Status: Confirmed => Fix Committed
--
You received this bug
It is unclear how to reproduce the issue.
So far, I always have multiple VLANs configured and accessible. The only
time I see errors similar to the ones from the reporter, is when the
same vlan with the same name is configured multiple times in a row
(which is an input/configuration error)
This
tah.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/1890619
Title:
poppler fails to build on s390x with gcc10 due to symbols changes
Status in poppler package in Ubuntu:
Public bug reported:
improved resolved configuration
* isc-dhcp-client pushes DNS data to resolved via a hook it ships
* ifupdown pushes DNS data to resolved via a hook it ships
* resolvconf skips pulling DNS data that is pushed to resolved
* systemd doesn't have enter hook anymore
This way
** Also affects: lvm2 (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: lvm2 (Ubuntu Groovy)
Importance: Undecided
Status: Confirmed
** Tags removed: rls-gg-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Description changed:
[impact]
systemd-networkd double-free causes crash under some circumstances, such
as adding/removing ip rules
[test case]
- see original description
+ Use networkd-dispatcher events to add and remove IP rules. The example
+ scripts below are contrived (and
The scripts for configured.d and configuring.d to add and remove IP
rules (included above) are likely the culprit. @ddstreet would you like
me to write that up more compactly?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Changed in: kmod (Ubuntu Bionic)
Milestone: None => ubuntu-18.04.5
** Changed in: systemd (Ubuntu Bionic)
Milestone: None => ubuntu-18.04.5
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to kmod in Ubuntu.
Preparing uploads in https://bileto.ubuntu.com/#/ticket/4162
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1889068
Title:
Improve resolved integration
Status in
Public bug reported:
Insure that ifupdown & dhcp DNS information is always added to resolved.
Move the resolved hooks from systemd package to isc-dhcp-client and
ifupdown themselves.
Figure out how to integrate "eth0" resolver => Manager resolver.
Blog / document how to control this.
**
@colin-king @juliank
It feels to me that the oem flavour should default to
(powersave/ondemand), as it is more-or-less laptop kernel flavour.
I feel like generic kernel flavour should remain on performance.
I feel like we should have a unit, that for chassis=laptop turns on
I have a galaxy book ion with ubuntu 20.04 and have exactly the same issue.
I have found that I can make the headset jack work if I issue this
command :
sudo hda-verb /dev/snd/hwC0D0 0x1a SET_PIN_WIDGET_CONTROL 0x5
But it only lasts until the sound subsystem goes to sleep (i.e. no sound
to
Related gcc patches are at
https://bugs.launchpad.net/ubuntu/+source/gcc-9/+bug/1888653
** Package changed: linux (Ubuntu) => binutils (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
binutils in groovy is at 20200716 snapshot from 2.35 branch of binutils.
Inspecting source code, I think we already ship this.
** Changed in: binutils (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
No crashes on my test machine for 12 days. Push it!
--
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/1881972
Title:
systemd-networkd crashes with invalid pointer
Status in
** Description changed:
Opening Settings -> Display and selecting an orientation other than Landscape
doesn't work.
Similarly, selecting Fractional Scaling and then picking a scale factor has
no effect.
This is a recently installed Ubuntu 20.04, fully updated, on a recently
released
** Attachment added: "This is my screen just after I slide the Fractional
Scaling slider. The icons in the left margin, and the text at the top of the
screen, have changed size (despite me not picking any new scale) and nothing
else has scaled."
** Attachment added: "This is my screen after I chose "125%" as a fractional
scale, then pressed Apply. The pop-up has dimmed the underlying windows, but
you can see that the Scale setting in the underlying Displays window has
reverted to "100%", and nothing on the screen has changed its scale
** Attachment added: "This is my screen before I slide the "Fractional Scaling"
slider."
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1888088/+attachment/5393945/+files/Screenshot%20from%202020-07-18%2014-21-25%20-%20before%20fractional%20scaling.png
--
You received this bug
Public bug reported:
Opening Settings -> Display and selecting an orientation other than Landscape
doesn't work.
Similarly, selecting Fractional Scaling and then picking a scale factor has no
effect.
This is a recently installed Ubuntu 20.04, fully updated, on a recently
released laptop/tablet
** Changed in: gpgme1.0 (Ubuntu)
Importance: Undecided => Critical
** Also affects: gpgme1.0 (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gpgme1.0 in Ubuntu.
** Tags added: rls-gg-incoming
** Changed in: lvm2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1887372
Title:
Cannot create lvm
@seth-arnold: yeah another autopackage test failure but that one is
definitely a different issue.
--
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/1887542
Title:
apparmor
Public bug reported:
I was upgrading from 18.04 LTS to 20.04 LTS and this popped up. Not sure
what else to say.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: python3 3.8.2-0ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
@Seth, is this new for those kernels? This is the first I have heard of
it.
And just to double check these failures were all on groovy?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
it recover. Only way to recover seems to be to do a
cold reboot. A simple warm reboot does not fix the problem, but this
can be related to problem 1.
A few dumps
john@hydra:~$ dmesg | fgrep 'Blue'
[3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0
[8.417252] Bluetooth: Core ver
is missing as an output device. I have not been
able to figure out what makes the sound system fail, and I have not
been able to make it recover. Only way to recover seems to be to do a
cold reboot. A simple warm reboot does not fix the problem, but this
can be related to problem 1.
A few dum
.
A few dumps
john@hydra:~$ dmesg | fgrep 'Blue'
[3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0
[8.417252] Bluetooth: Core ver 2.22
[8.417280] Bluetooth: HCI device and connection manager initialized
[8.417284] Bluetooth: HCI socket layer initialized
[
is missing as an output device. I have not been
able to figure out what makes the sound system fail, and I have not
been able to make it recover. Only way to recover seems to be to do a
cold reboot. A simple warm reboot does not fix the problem, but this
can be related to problem 1.
A few dumps
is missing as an output device. I have not been
able to figure out what makes the sound system fail, and I have not
been able to make it recover. Only way to recover seems to be to do a
cold reboot. A simple warm reboot does not fix the problem, but this
can be related to problem 1.
A few dum
is missing as an output device. I have not been
able to figure out what makes the sound system fail, and I have not
been able to make it recover. Only way to recover seems to be to do a
cold reboot. A simple warm reboot does not fix the problem, but this
can be related to problem 1.
A few dumps
is missing as an output device. I have not been
able to figure out what makes the sound system fail, and I have not
been able to make it recover. Only way to recover seems to be to do a
cold reboot. A simple warm reboot does not fix the problem, but this
can be related to problem 1.
A few dumps
problem 1.
A few dumps
john@hydra:~$ dmesg | fgrep 'Blue'
[3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0
[8.417252] Bluetooth: Core ver 2.22
[8.417280] Bluetooth: HCI device and connection manager initialized
[8.417284] Bluetooth: HCI socket layer initialized
[
is missing as an output device. I have not been
able to figure out what makes the sound system fail, and I have not
been able to make it recover. Only way to recover seems to be to do a
cold reboot. A simple warm reboot does not fix the problem, but this
can be related to problem 1.
A few dum
few dumps
john@hydra:~$ dmesg | fgrep 'Blue'
[3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0
[8.417252] Bluetooth: Core ver 2.22
[8.417280] Bluetooth: HCI device and connection manager initialized
[8.417284] Bluetooth: HCI socket layer initialized
[8.417286]
is missing as an output device. I have not been
able to figure out what makes the sound system fail, and I have not
been able to make it recover. Only way to recover seems to be to do a
cold reboot. A simple warm reboot does not fix the problem, but this
can be related to problem 1.
A few dumps
is missing as an output device. I have not been
able to figure out what makes the sound system fail, and I have not
been able to make it recover. Only way to recover seems to be to do a
cold reboot. A simple warm reboot does not fix the problem, but this
can be related to problem 1.
A few dum
is missing as an output device. I have not been
able to figure out what makes the sound system fail, and I have not
been able to make it recover. Only way to recover seems to be to do a
cold reboot. A simple warm reboot does not fix the problem, but this
can be related to problem 1.
A few dumps
few dumps
john@hydra:~$ dmesg | fgrep 'Blue'
[3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0
[8.417252] Bluetooth: Core ver 2.22
[8.417280] Bluetooth: HCI device and connection manager initialized
[8.417284] Bluetooth: HCI socket layer initialized
[8.417286]
few dumps
john@hydra:~$ dmesg | fgrep 'Blue'
[3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0
[8.417252] Bluetooth: Core ver 2.22
[8.417280] Bluetooth: HCI device and connection manager initialized
[8.417284] Bluetooth: HCI socket layer initialized
[8.417286]
few dumps
john@hydra:~$ dmesg | fgrep 'Blue'
[3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0
[8.417252] Bluetooth: Core ver 2.22
[8.417280] Bluetooth: HCI device and connection manager initialized
[8.417284] Bluetooth: HCI socket layer initialized
[8.417286]
to figure out what makes the sound system fail, and I have not been able
to make it recover. Only way to recover seems to be to do a cold reboot.
A simple warm reboot does not fix the problem, but this can be related
to problem 1.
A few dumps
john@hydra:~$ dmesg | fgrep 'Blue
So far so good running the latest package for 10 hours. I'll let it run
another day or two but previously I would have seen the issue by now.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
> Is this a native s390x build, or something qemu-user? Thanks.
That's a very good question.
The failing autopkgtest, was run on an LPAR, which is running OpenStack
Nova, which launched qemu-system kvm, v5.4 Ubuntu kernel, and then run
make inside that.
I will double check if those old builds
I was not able to reproduce the original issue on
237-3ubuntu10.42~202007071725~ubuntu18.04.1 after letting it run for 12+
hours. I have now installed the newer
237-3ubuntu10.42~202007081907~ubuntu18.04.1 from the same PPA. I no
longer see a SEGV when the service first starts at boot, thanks! I
Here's one of the new coredumps I'm getting at boot now. Note that I don't have
debugging symbols installed for the PPA version of systemd.
# coredumpctl gdb 714
PID: 714 (systemd-network)
UID: 100 (systemd-network)
GID: 102 (systemd-network)
Signal: 11
I added the ppa and did a dist-upgrade then rebooted. systemd-networkd
now consistently crashes once at boot (looks like a different crash
though). But then everything appears to work after networkd restarts
once. I will let it run and see if the invalid pointer crash happens.
# journalctl -l -u
Public bug reported:
posix_spawn usage in gnu make causes failures on s390x
Recently in gnu-make v4.3 https://paste.ubuntu.com/p/tYhbJFKN76/ it
started to use posix_spawn, instead of fork()/exec().
This has caused failure of an unrelated package flatpak-builder
autopkgtests on s390x only, like
kes the sound system fail, and I have not
been able to make it recover. Only way to recover seems to be to do a
cold reboot. A simple warm reboot does not fix the problem, but this
can be related to problem 1.
A few dumps
john@hydra:~$ dmesg | fgrep 'Blue'
[3.089584] usb 1-2.2: Prod
the sound system fail, and I have not been able
to make it recover. Only way to recover seems to be to do a cold reboot.
A simple warm reboot does not fix the problem, but this can be related
to problem 1.
A few dumps
john@hydra:~$ dmesg | fgrep 'Blue'
[3.089584] usb 1-2.2: Product
After the crash (hid hangs, could be a side effect) this is the dmesg.0
file still existing
john@hydra:~$ tail -100 /var/log/dmesg.0
[7.277226] kernel: nvidia-uvm: Loaded the UVM driver, major device number
237.
[7.498321] kernel: cfg80211: Loading compiled-in X.509 certificates
be related to problem 1.
A few dumps
john@hydra:~$ dmesg | fgrep 'Blue'
[3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0
[8.417252] Bluetooth: Core ver 2.22
[8.417280] Bluetooth: HCI device and connection manager initialized
[8.417284] Bluetooth: HCI socket layer
701 - 800 of 4696 matches
Mail list logo
