/usr/lib/ubuntu-advantage/apt-esm-hook causes Seg Fault
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-advantage-tools (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
This happens every time I do "sudo apt update":
Fetched 1,775 B in 3s (584 B/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
1 package can be upgraded. Run 'apt list --upgradable' to see it.
Segmentation fault (core dumped)
E: Problem executing scripts APT::Update:
E: Sub-process returned an error code
I tried a re-install:
sudo apt install --reinstall ubuntu-
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 1 not upgraded.
Need to get 50.0 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://
Fetched 50.0 kB in 0s (403 kB/s)
(Reading database ... 275280 files and directories currently installed.)
Preparing to unpack .../ubuntu-
Unpacking ubuntu-
Setting up ubuntu-
Processing triggers for man-db (2.8.7-3) ...
Same error when I run "sudo apt update".
Running Pop!_OS 19.10
Hello,
I just tried apt operations on a fresh eoan (ubuntu 19.10) system, with ua installed (but not attached, which is the default), and it works just fine. The hook also just exits 0 when called directly:
root@e1:~# /usr/lib/ ubuntu- advantage/ apt-esm- hook
root@e1:~# echo $?
0
I also installed pop_os 19.10, and apt update also worked out of the box. I then installed all available updates, including the downgrades it wanted to do. After that, apt also kept working.
Calling the hook directly is also fine in pop_os, with an exit code of zero.
All that being said, I'm unclear if ubuntu-advantage would be supported on a downstream derivative of Ubuntu. It's not ideal that it is segfaulting, but I couldn't reproduce it on either OS. Maybe you have packages from other sources installed, providing patched libraries that the ua hook is using, or some other unexpected condition that only shows up in your particular environment.
If you have a crash file in /var/crash, please attach it to this bug, or run the hook under gdb and try to provide a backtrace. Otherwise, please try to come up with clear reproduction steps after a fresh install, preferably on Ubuntu.