Hello Ajay and thanks for this bug report. I see several "segfault" in
the attached dmesg log, e.g.
tar[35806]: segfault at 55f27d9b4d60 ip 00007f420e188304 sp
00007ffd191d5f10 error 6 in ld-2.31.so[7f420e17b000+23000]
This could indicate a bug in tag(1), but the tool is very battle tested,
and we've got no other similar bug reports. Crashes like that can happen
due to hardware issues (bad RAM), but this wouldn't be limited to tar.
Do you happen to see similar crashes while using other tools on the same
system? Can you reboot your system, start the "Memory check" from the
boot menu, and report its results here?
I'm marking this bug as Incomplete for the moment, as we're waiting for
more information about it.
** Changed in: bind9 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965719
Title:
package bind9-dnsutils 1:9.16.1-0ubuntu2.9 failed to install/upgrade:
dpkg-deb --control subprocess returned error exit status 2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1965719/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
