apt: relocation error: symbol not defined in file libapt-pkg.so.5.0 with link time reference
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
1
My apt will not run any command, e.g. sudo apt-get ____. The error message I am getting is:
relocation error: /usr/lib/x86_64-linux-gnu/libapt-private.so.0.0:
symbol _ZN13pkgSourceList16AddVolatileFilesER11CommandLinePSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS8_EE
version APTKG_5.0 not defined in file libapt-pkg.so.5.0 with link time reference
I only have access to recovery mode and Cntrl+Alt+F1 can someone please help me?
Update 1:
I am running Ubuntu 18.04, bionic.
dpkg -l apt libapt-pkg5.0 shows:
aptrunning on1.4.6~17.04.1
libapt=pkg5.0:amd64running on1.2.29
The file hashes:
868c9bb9cd23bacc2f76182902eb489d /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0
12e8c8000ae4f61d6ec50ca9218b428d /usr/lib/x86_64-linux-gnu/libapt-private.so.0.0
command-line apt 18.04 package-management dpkg
edited Feb 10 at 13:27
Byte Commander
66.3k27181310
asked Feb 9 at 19:10
Anonymous__15 274Anonymous__15 274
63
add a comment |
1
My apt will not run any command, e.g. sudo apt-get ____. The error message I am getting is:
relocation error: /usr/lib/x86_64-linux-gnu/libapt-private.so.0.0:
symbol _ZN13pkgSourceList16AddVolatileFilesER11CommandLinePSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS8_EE
version APTKG_5.0 not defined in file libapt-pkg.so.5.0 with link time reference
I only have access to recovery mode and Cntrl+Alt+F1 can someone please help me?
Update 1:
I am running Ubuntu 18.04, bionic.
dpkg -l apt libapt-pkg5.0 shows:
aptrunning on1.4.6~17.04.1
libapt=pkg5.0:amd64running on1.2.29
The file hashes:
868c9bb9cd23bacc2f76182902eb489d /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0
12e8c8000ae4f61d6ec50ca9218b428d /usr/lib/x86_64-linux-gnu/libapt-private.so.0.0
command-line apt 18.04 package-management dpkg
edited Feb 10 at 13:27
Byte Commander
66.3k27181310
asked Feb 9 at 19:10
Anonymous__15 274Anonymous__15 274
63
related: askubuntu.com/q/777803/367990 and askubuntu.com/q/448575/367990 - you seem to have a corrupted or incompatible shared library there. Can you checkdpkg -l apt libapt-pkg5.0to show your installed related package versions, andmd5sum /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0 /usr/lib/x86_64-linux-gnu/libapt-private.so.0.0to show the hash of those two library files, so that we can compare if one is corrupt. Also please add what Ubuntu release you're using.
– Byte Commander
Feb 9 at 19:33
@ByteCommander I am sorry for my late response, I am running Ubuntu 18.04, bionic. dpkg -l apt libapt-pkg5.0 shows the following Apt running on- 1.4.6~17.04.1 libapt=pkg5.0:amd64 running on- 1.2.29 868c9bb9cd23bacc2f76182902eb489d /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0 12e8c8000ae4f61d6ec50ca9218b428d /usr/lib/x86_64-linux-gnu/libapt-private.so.0.0
– Anonymous__15 274
Feb 10 at 1:54
Alright, you have two completely wrong package versions for your Ubuntu release there. Thataptversion is actually from 17.04 and thelibapt-pkg5.0is from 16.04, no surprise that doesn't work together. As a first step to fix your issue, we'll try to getaptrunning again by manually downloading and installing the correct packages. Please download apt and libapt-pkg5.0 from the bionic-update repo and install them withsudo dpkg -i /PATH/TO/PACKAGE
– Byte Commander
Feb 10 at 13:23
Onceaptis functional again, we need to investigate why you had these invalid versions installed, where they came from and whether there are more bad versions. Please edit your question and add the output ofgrep ^deb /etc/apt/sources.list{,.d/*.list}to list all your configured software sources. Don't paste the output in a comment, as that will not preserve any formatting and make it hard to read.
– Byte Commander
Feb 10 at 13:25
add a comment |
1
1
1
My apt will not run any command, e.g. sudo apt-get ____. The error message I am getting is:
relocation error: /usr/lib/x86_64-linux-gnu/libapt-private.so.0.0:
symbol _ZN13pkgSourceList16AddVolatileFilesER11CommandLinePSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS8_EE
version APTKG_5.0 not defined in file libapt-pkg.so.5.0 with link time reference
I only have access to recovery mode and Cntrl+Alt+F1 can someone please help me?
Update 1:
I am running Ubuntu 18.04, bionic.
dpkg -l apt libapt-pkg5.0 shows:
aptrunning on1.4.6~17.04.1
libapt=pkg5.0:amd64running on1.2.29
The file hashes:
868c9bb9cd23bacc2f76182902eb489d /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0
12e8c8000ae4f61d6ec50ca9218b428d /usr/lib/x86_64-linux-gnu/libapt-private.so.0.0
command-line apt 18.04 package-management dpkg
edited Feb 10 at 13:27
Byte Commander
66.3k27181310
asked Feb 9 at 19:10
Anonymous__15 274Anonymous__15 274
63
My apt will not run any command, e.g. sudo apt-get ____. The error message I am getting is:
relocation error: /usr/lib/x86_64-linux-gnu/libapt-private.so.0.0:
symbol _ZN13pkgSourceList16AddVolatileFilesER11CommandLinePSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS8_EE
version APTKG_5.0 not defined in file libapt-pkg.so.5.0 with link time reference
I only have access to recovery mode and Cntrl+Alt+F1 can someone please help me?
Update 1:
I am running Ubuntu 18.04, bionic.
dpkg -l apt libapt-pkg5.0 shows:
aptrunning on1.4.6~17.04.1
libapt=pkg5.0:amd64running on1.2.29
The file hashes:
868c9bb9cd23bacc2f76182902eb489d /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0
12e8c8000ae4f61d6ec50ca9218b428d /usr/lib/x86_64-linux-gnu/libapt-private.so.0.0
command-line apt 18.04 package-management dpkg
command-line apt 18.04 package-management dpkg
edited Feb 10 at 13:27
Byte Commander
66.3k27181310
asked Feb 9 at 19:10
Anonymous__15 274Anonymous__15 274
63
edited Feb 10 at 13:27
Byte Commander
66.3k27181310
asked Feb 9 at 19:10
Anonymous__15 274Anonymous__15 274
63
edited Feb 10 at 13:27
Byte Commander
66.3k27181310
edited Feb 10 at 13:27
Byte Commander
66.3k27181310
edited Feb 10 at 13:27
Byte Commander
66.3k27181310
66.3k27181310
asked Feb 9 at 19:10
Anonymous__15 274Anonymous__15 274
63
asked Feb 9 at 19:10
Anonymous__15 274Anonymous__15 274
63
asked Feb 9 at 19:10
Anonymous__15 274Anonymous__15 274
63
63
related: askubuntu.com/q/777803/367990 and askubuntu.com/q/448575/367990 - you seem to have a corrupted or incompatible shared library there. Can you checkdpkg -l apt libapt-pkg5.0to show your installed related package versions, andmd5sum /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0 /usr/lib/x86_64-linux-gnu/libapt-private.so.0.0to show the hash of those two library files, so that we can compare if one is corrupt. Also please add what Ubuntu release you're using.
– Byte Commander
Feb 9 at 19:33
@ByteCommander I am sorry for my late response, I am running Ubuntu 18.04, bionic. dpkg -l apt libapt-pkg5.0 shows the following Apt running on- 1.4.6~17.04.1 libapt=pkg5.0:amd64 running on- 1.2.29 868c9bb9cd23bacc2f76182902eb489d /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0 12e8c8000ae4f61d6ec50ca9218b428d /usr/lib/x86_64-linux-gnu/libapt-private.so.0.0
– Anonymous__15 274
Feb 10 at 1:54
Alright, you have two completely wrong package versions for your Ubuntu release there. Thataptversion is actually from 17.04 and thelibapt-pkg5.0is from 16.04, no surprise that doesn't work together. As a first step to fix your issue, we'll try to getaptrunning again by manually downloading and installing the correct packages. Please download apt and libapt-pkg5.0 from the bionic-update repo and install them withsudo dpkg -i /PATH/TO/PACKAGE
– Byte Commander
Feb 10 at 13:23
Onceaptis functional again, we need to investigate why you had these invalid versions installed, where they came from and whether there are more bad versions. Please edit your question and add the output ofgrep ^deb /etc/apt/sources.list{,.d/*.list}to list all your configured software sources. Don't paste the output in a comment, as that will not preserve any formatting and make it hard to read.
– Byte Commander
Feb 10 at 13:25
add a comment |
related: askubuntu.com/q/777803/367990 and askubuntu.com/q/448575/367990 - you seem to have a corrupted or incompatible shared library there. Can you checkdpkg -l apt libapt-pkg5.0to show your installed related package versions, andmd5sum /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0 /usr/lib/x86_64-linux-gnu/libapt-private.so.0.0to show the hash of those two library files, so that we can compare if one is corrupt. Also please add what Ubuntu release you're using.
– Byte Commander
Feb 9 at 19:33
@ByteCommander I am sorry for my late response, I am running Ubuntu 18.04, bionic. dpkg -l apt libapt-pkg5.0 shows the following Apt running on- 1.4.6~17.04.1 libapt=pkg5.0:amd64 running on- 1.2.29 868c9bb9cd23bacc2f76182902eb489d /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0 12e8c8000ae4f61d6ec50ca9218b428d /usr/lib/x86_64-linux-gnu/libapt-private.so.0.0
– Anonymous__15 274
Feb 10 at 1:54
Alright, you have two completely wrong package versions for your Ubuntu release there. Thataptversion is actually from 17.04 and thelibapt-pkg5.0is from 16.04, no surprise that doesn't work together. As a first step to fix your issue, we'll try to getaptrunning again by manually downloading and installing the correct packages. Please download apt and libapt-pkg5.0 from the bionic-update repo and install them withsudo dpkg -i /PATH/TO/PACKAGE
– Byte Commander
Feb 10 at 13:23
Onceaptis functional again, we need to investigate why you had these invalid versions installed, where they came from and whether there are more bad versions. Please edit your question and add the output ofgrep ^deb /etc/apt/sources.list{,.d/*.list}to list all your configured software sources. Don't paste the output in a comment, as that will not preserve any formatting and make it hard to read.
– Byte Commander
Feb 10 at 13:25
related: askubuntu.com/q/777803/367990 and askubuntu.com/q/448575/367990 - you seem to have a corrupted or incompatible shared library there. Can you check
dpkg -l apt libapt-pkg5.0 to show your installed related package versions, and md5sum /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0 /usr/lib/x86_64-linux-gnu/libapt-private.so.0.0 to show the hash of those two library files, so that we can compare if one is corrupt. Also please add what Ubuntu release you're using.– Byte Commander
Feb 9 at 19:33
related: askubuntu.com/q/777803/367990 and askubuntu.com/q/448575/367990 - you seem to have a corrupted or incompatible shared library there. Can you check
dpkg -l apt libapt-pkg5.0 to show your installed related package versions, and md5sum /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0 /usr/lib/x86_64-linux-gnu/libapt-private.so.0.0 to show the hash of those two library files, so that we can compare if one is corrupt. Also please add what Ubuntu release you're using.– Byte Commander
Feb 9 at 19:33
@ByteCommander I am sorry for my late response, I am running Ubuntu 18.04, bionic. dpkg -l apt libapt-pkg5.0 shows the following Apt running on- 1.4.6~17.04.1 libapt=pkg5.0:amd64 running on- 1.2.29 868c9bb9cd23bacc2f76182902eb489d /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0 12e8c8000ae4f61d6ec50ca9218b428d /usr/lib/x86_64-linux-gnu/libapt-private.so.0.0
– Anonymous__15 274
Feb 10 at 1:54
@ByteCommander I am sorry for my late response, I am running Ubuntu 18.04, bionic. dpkg -l apt libapt-pkg5.0 shows the following Apt running on- 1.4.6~17.04.1 libapt=pkg5.0:amd64 running on- 1.2.29 868c9bb9cd23bacc2f76182902eb489d /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0 12e8c8000ae4f61d6ec50ca9218b428d /usr/lib/x86_64-linux-gnu/libapt-private.so.0.0
– Anonymous__15 274
Feb 10 at 1:54
Alright, you have two completely wrong package versions for your Ubuntu release there. That
apt version is actually from 17.04 and the libapt-pkg5.0 is from 16.04, no surprise that doesn't work together. As a first step to fix your issue, we'll try to get apt running again by manually downloading and installing the correct packages. Please download apt and libapt-pkg5.0 from the bionic-update repo and install them with sudo dpkg -i /PATH/TO/PACKAGE– Byte Commander
Feb 10 at 13:23
Alright, you have two completely wrong package versions for your Ubuntu release there. That
apt version is actually from 17.04 and the libapt-pkg5.0 is from 16.04, no surprise that doesn't work together. As a first step to fix your issue, we'll try to get apt running again by manually downloading and installing the correct packages. Please download apt and libapt-pkg5.0 from the bionic-update repo and install them with sudo dpkg -i /PATH/TO/PACKAGE– Byte Commander
Feb 10 at 13:23
Once
apt is functional again, we need to investigate why you had these invalid versions installed, where they came from and whether there are more bad versions. Please edit your question and add the output of grep ^deb /etc/apt/sources.list{,.d/*.list} to list all your configured software sources. Don't paste the output in a comment, as that will not preserve any formatting and make it hard to read.– Byte Commander
Feb 10 at 13:25
Once
apt is functional again, we need to investigate why you had these invalid versions installed, where they came from and whether there are more bad versions. Please edit your question and add the output of grep ^deb /etc/apt/sources.list{,.d/*.list} to list all your configured software sources. Don't paste the output in a comment, as that will not preserve any formatting and make it hard to read.– Byte Commander
Feb 10 at 13:25
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1116982%2fapt-relocation-error-symbol-not-defined-in-file-libapt-pkg-so-5-0-with-link-ti%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1116982%2fapt-relocation-error-symbol-not-defined-in-file-libapt-pkg-so-5-0-with-link-ti%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
related: askubuntu.com/q/777803/367990 and askubuntu.com/q/448575/367990 - you seem to have a corrupted or incompatible shared library there. Can you check
dpkg -l apt libapt-pkg5.0to show your installed related package versions, andmd5sum /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0 /usr/lib/x86_64-linux-gnu/libapt-private.so.0.0to show the hash of those two library files, so that we can compare if one is corrupt. Also please add what Ubuntu release you're using.– Byte Commander
Feb 9 at 19:33
@ByteCommander I am sorry for my late response, I am running Ubuntu 18.04, bionic. dpkg -l apt libapt-pkg5.0 shows the following Apt running on- 1.4.6~17.04.1 libapt=pkg5.0:amd64 running on- 1.2.29 868c9bb9cd23bacc2f76182902eb489d /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0 12e8c8000ae4f61d6ec50ca9218b428d /usr/lib/x86_64-linux-gnu/libapt-private.so.0.0
– Anonymous__15 274
Feb 10 at 1:54
Alright, you have two completely wrong package versions for your Ubuntu release there. That
aptversion is actually from 17.04 and thelibapt-pkg5.0is from 16.04, no surprise that doesn't work together. As a first step to fix your issue, we'll try to getaptrunning again by manually downloading and installing the correct packages. Please download apt and libapt-pkg5.0 from the bionic-update repo and install them withsudo dpkg -i /PATH/TO/PACKAGE– Byte Commander
Feb 10 at 13:23
Once
aptis functional again, we need to investigate why you had these invalid versions installed, where they came from and whether there are more bad versions. Please edit your question and add the output ofgrep ^deb /etc/apt/sources.list{,.d/*.list}to list all your configured software sources. Don't paste the output in a comment, as that will not preserve any formatting and make it hard to read.– Byte Commander
Feb 10 at 13:25